Bug#983357: Workaround for #983357
Hello, On the XenProject Matrix channel, a user suggested adding "vkb_device=0" to the domU config to work around this bug. I have tested the workaround and can report that it works for me. I have been able to install using the Debian 11.1 and 12.5 netinst ISO images. Config that I tested: # Domain name name= 'vm2' # CPU and memory configuration memory = '2048' maxmem = '2048' vcpus = 4 maxvcpus= 4 type= 'hvm' # HVM config pae=1 # recommended #acpi=1 # recommended to omit, default is on #apic=1 # recommended to omit, default is on #nx=1 # recommended to omit, default is on serial=[ 'pty' ] tsc_mode='default' nomigrate=1 usb=1 usbdevice='tablet' keymap='en-gb' # Work around Debian bug #983357 vkb_device=0 # Disk device(s). boot= 'dc' hdtype = 'ahci' disk= [ '/dev/rootvg/vm2,raw,xvda,w', #'/var/lib/media/debian-11.1.0-amd64-netinst.iso,raw,hdc,devtype=cdrom', '/var/lib/media/debian-12.5.0-amd64-netinst.iso,raw,hdc,devtype=cdrom', ] # Framebuffer vfb=[ 'vnc=1' ] # Networking vif = [ 'mac=fe:fd:02:02:23:1f, bridge=br0vl40' ] # Behaviour on_poweroff = 'destroy' on_reboot = 'restart' on_crash= 'restart' Regards, Leigh.
Bug#1034394: unblock: zabbix/1:6.0.14+dfsg-1
Hi All, I raised the bug report[1] that was fixed by upgrading Zabbix to 6.0.14. Currently, performing a fresh install of Debian Bookworm and then installing Zabbix will result in a non-working Zabbix (as Zabbix 6.0.13 does not work with PHP 8.2). That is not a good user experience. Therefore, it would be great if this version could be included in the release in order that anyone wanting to install Zabbix get something that works. Thanks for your consideration. Regards, Leigh. -- [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033241
Bug#1033241: Unsupported PHP configuration for Zabbix when upgrading from bullseye to testing (bookworm)
Package: zabbix Version: 6.0.13+dfsg-1 I upgraded a VM running Zabbix from bullseye to testing (bookworm). This upgraded PHP to version 8.2, which is not supported by Zabbix version 6.0.13. When attempting to access the web front end, the screen is filled with deprecated function errors, and therefore it is not usable: Creation of dynamic property CList::$attributes is deprecated [zabbix.php:22 → require_once() → ZBase->run() → ZBase->processRequest() → ZBase->processResponseFinal() → CView->getOutput() → include() → CWidget->show() → CWidget->toString() → get_prepared_messages() → makeMessageBox() → CList->__construct() → CTag->__construct() in include/classes/html/CTag.php:58] Creation of dynamic property CList::$tagname is deprecated [zabbix.php:22 → require_once() → ZBase->run() → ZBase->processRequest() → ZBase->processResponseFinal() → CView->getOutput() → include() → CWidget->show() → CWidget->toString() → get_prepared_messages() → makeMessageBox() → CList->__construct() → CTag->__construct() in include/classes/html/CTag.php:59] Creation of dynamic property CList::$paired is deprecated [zabbix.php:22 → require_once() → ZBase->run() → ZBase->processRequest() → ZBase->processResponseFinal() → CView->getOutput() → include() → CWidget->show() → CWidget->toString() → get_prepared_messages() → makeMessageBox() → CList->__construct() → CTag->__construct() in include/classes/html/CTag.php:60] [and so on] According to the release notes of version 6.0.14, it now supports PHP 8.2. I am using the following package versions: libapache2-mod-php8.2 8.2.2-3 php 2:8.2+93 php-bcmath 2:8.2+93 php-common 2:93 php-gd 2:8.2+93 php-mbstring 2:8.2+93 php-pgsql 2:8.2+93 php-xml 2:8.2+93 php8.2 8.2.2-3 php8.2-bcmath 8.2.2-3 php8.2-cli 8.2.2-3 php8.2-common 8.2.2-3 php8.2-gd 8.2.2-3 php8.2-mbstring 8.2.2-3 php8.2-opcache 8.2.2-3 php8.2-pgsql 8.2.2-3 php8.2-readline 8.2.2-3 php8.2-xml 8.2.2-3 zabbix-agent 1:6.0.13+dfsg-1+b1 zabbix-frontend-php 1:6.0.13+dfsg-1 zabbix-server-pgsql 1:6.0.13+dfsg-1+b1 Regards, Leigh.
Bug#924494: chrony fails to start when seccomp enabled on armel
Hi Vincent, On 2019-03-14 15:32, Vincent Blut wrote: Control: tags -1 - moreinfo Hello, On Thu, Mar 14, 2019 at 09:19:31AM +, Leigh Brown wrote: Hi Vincent, (Your mail bounced as free.fr is being identified by spamcop as a source of spam) Indeed, I’ve just seen that. To answer your question, it fails to start with the default configuration, which passes "-F -1" to chronyd. When I removed that, it worked. Ok, that is what I wanted to know, thank you. I’ll do my best to work on this this weekend, hope that’s ok‽ No worries. I'm running a patched version of the package that will get upgraded when the next version hits testing. I used strace to see that seccomp was blocking the recv() system call, fixed that and then saw that it was also blocking send(). After applying the fix for both, the default configuration then worked fine. Perfect. Your patch has been accepted¹ upstream btw. Great, I saw that. Regards, Leigh. Cheers, Vincent ¹ https://git.tuxfamily.org/chrony/chrony.git/commit/?id=79db0b7eca31b6c6a86cf1a342a40cc76d2f Thanks for fixing this. Regards, Leigh.
Bug#924494: chrony fails to start when seccomp enabled on armel
Hi Vincent, (Your mail bounced as free.fr is being identified by spamcop as a source of spam) To answer your question, it fails to start with the default configuration, which passes "-F -1" to chronyd. When I removed that, it worked. I used strace to see that seccomp was blocking the recv() system call, fixed that and then saw that it was also blocking send(). After applying the fix for both, the default configuration then worked fine. I hope that is clear. Regards, Leigh.
Bug#924494: chrony fails to start when seccomp enabled on armel
Package: chrony Version: 3.4-3 Severity: important Tags: patch upstream Dear Maintainer, chrony on armel does not start due to seccomp not allowing all required system calls. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 4.19.0-2-marvell Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages chrony depends on: ii adduser 3.118 ii init-system-helpers 1.56+nmu1 ii iproute2 4.20.0-2 ii libc62.28-8 ii libcap2 1:2.25-2 ii libedit2 3.1-20181209-1 ii libnettle6 3.4.1-1 ii libseccomp2 2.3.3-4 ii lsb-base 10.2018112800 ii ucf 3.0038+nmu1 chrony recommends no packages. Versions of packages chrony suggests: pn dnsutils pn networkd-dispatcher -- no debconf information --- chrony-3.4.orig/sys_linux.c +++ chrony-3.4/sys_linux.c @@ -504,8 +504,8 @@ SYS_Linux_EnableSystemCallFilter(int lev SCMP_SYS(stat64), SCMP_SYS(statfs), SCMP_SYS(statfs64), SCMP_SYS(unlink), /* Socket */ SCMP_SYS(bind), SCMP_SYS(connect), SCMP_SYS(getsockname), SCMP_SYS(getsockopt), -SCMP_SYS(recvfrom), SCMP_SYS(recvmmsg), SCMP_SYS(recvmsg), +SCMP_SYS(recvfrom), SCMP_SYS(recvmmsg), SCMP_SYS(recvmsg),SCMP_SYS(recv), -SCMP_SYS(sendmmsg), SCMP_SYS(sendmsg), SCMP_SYS(sendto), +SCMP_SYS(sendmmsg), SCMP_SYS(sendmsg), SCMP_SYS(sendto),SCMP_SYS(send), /* TODO: check socketcall arguments */ SCMP_SYS(socketcall), /* General I/O */
Bug#923379: u-boot: Dreamplug fails to detect SPI and USB
Package: u-boot Version: 2019.01+dfsg-1 Severity: important Tags: upstream Dear Maintainer, I flashed u-boot 2019.01+dfsg-1 on my Dreamplug. I found that u-boot was unable to detect the SPI flash on the device (and thus could not read the u-boot environment). It could also not detect the usb storage. On booting, the following output is observed: 8< U-Boot 2019.01+dfsg-1 (Jan 15 2019 - 00:36:19 +) Marvell-DreamPlug oC: Kirkwood 88F6281_A1 DRAM: 512 MiB Loading Environment from SPI Flash... Invalid bus 0 (err=-19) *** Warning - spi_flash_probe_bus_cs() failed, using default environment In:serial Out: serial Err: serial Net: egiga0 Error: egiga0 address not set. , egiga1 Error: egiga1 address not set. 88E1116 Initialized on egiga0 88E1116 Initialized on egiga1 IDE: ide_preinit failed Hit any key to stop autoboot: 0 => usb start starting USB... USB0: USB EHCI 1.00 scanning bus 0 for devices... EHCI timed out on TD - token=0x80008d80 EHCI timed out on TD - token=0x80008c80 EHCI timed out on TD - token=0x80008c80 EHCI timed out on TD - token=0x80008c80 ERROR: NOT USB_CONFIG_DESC a3 EHCI timed out on TD - token=0x80008d80 EHCI timed out on TD - token=0x80008c80 EHCI timed out on TD - token=0x80008c80 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found 8< I then compiled u-boot from the upstream git tree and tried various versions. The results are as follows: v2018.01 all works v2018.07 all works v2018.09 all works v2018.11 USB fails v2019.01 SPI flash fails, USB fails I then bisected both issues. The USB issue was caused by the following commit: commit 93b283d49f933f95f3a6f40762936f454ac655a8 Author: Adam Ford Date: Thu Aug 16 13:23:11 2018 -0500 ARM: CPU: arm926ejs: Consolidate cache routines to common file Four different boards had different options for enabling cache that were virtually all the same. This consolidates these common functions into arch/arm/cpu/arm926ejs/cache.c This also has the positive side-effect of enabling cache on the Davinci (da850) boards. Signed-off-by: Adam Ford [trini: Add mach-at91 to the list of consolidations] Signed-off-by: Tom Rini I used the following patch to temporarily fix up the issue (I am no expert on ARM so cannot say whether this is in any way correct): iff --git a/arch/arm/mach-kirkwood/cpu.c b/arch/arm/mach-kirkwood/cpu.c index d54de53f31..8a065d73ae 100644 --- a/arch/arm/mach-kirkwood/cpu.c +++ b/arch/arm/mach-kirkwood/cpu.c @@ -291,7 +291,6 @@ int arch_misc_init(void) temp |= (1 << 22); writefr_extra_feature_reg(temp); - icache_enable(); /* Change reset vector to address 0x0 */ temp = get_cr(); set_cr(temp & ~CR_V); diff --git a/include/configs/dreamplug.h b/include/configs/dreamplug.h index f4d717213c..6348935c68 100644 --- a/include/configs/dreamplug.h +++ b/include/configs/dreamplug.h @@ -79,4 +79,6 @@ #define CONFIG_SYS_ATA_IDE0_OFFSET MV_SATA_PORT0_OFFSET #endif /*CONFIG_MVSATA_IDE*/ +#define CONFIG_SYS_DCACHE_OFF + #endif /* _CONFIG_DREAMPLUG_H */ I then bisected the SPI flash issue, and found it was caused by the following commit: commit 6aaf76beb131c2ff2b7184c2d63c2c63e5ab339c Author: Chris Packham Date: Wed Nov 21 22:22:23 2018 +1300 arm: kirkwood: configs: dreamplug: Convert to DM_SPI Enable CONFIG_DM_SPI=y and CONFIG_DM_SPI_FLASH=y in the defconfig. Signed-off-by: Chris Packham Reviewed-by: Stefan Roese Signed-off-by: Stefan Roese I don't know enough about u-boot to easily diagnose this issue. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 4.19.7+ Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) -- no debconf information
Bug#917388: linux-image-4.18.0-3-amd64: Touchpad not working on Gemini Lake laptop due to missing kernel config option
Package: src:linux Version: 4.18.20-2 Severity: important Tags: d-i Dear Maintainer, I have installed Debian Buster on a Gemini Lake based laptop. Following installation the touchpad does not work. After some investigation, I have discovered that this is because of a missing kernel option. The missing option is; CONFIG_PINCTRL_GEMINILAKE=y I have compiled a 4.18.20 kernel using the Debian configuration, but with the above option enabled, and that fixes the problem. Please enable the option :-) Regards, Leigh. -- Package-specific info: ** Version: Linux version 4.18.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-30)) #1 SMP Debian 4.18.20-2 (2018-11-23) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.18.0-3-amd64 root=/dev/mapper/rootvg-rootlv ro quiet ** Not tainted ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: PC Specialist LTD product_name: Gemini II product_version: Default string chassis_vendor: Default string chassis_version: Default string bios_vendor: American Megatrends Inc. bios_version: 1.5 board_vendor: Akstron board_name: Gemini II board_version: Default string ** Loaded modules: rfcomm ctr ccm fuse snd_hda_codec_hdmi cmac bnep snd_hda_codec_realtek snd_hda_codec_generic nls_ascii nls_cp437 vfat fat intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel efi_pstore kvm irqbypass crct10dif_pclmul crc32_pclmul arc4 ghash_clmulni_intel intel_cstate evdev intel_rapl_perf serio_raw pcspkr efivars spi_pxa2xx_platform rtsx_usb_ms memstick iwlmvm btusb btrtl btbcm btintel bluetooth mac80211 uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common jitterentropy_rng snd_usb_audio videodev snd_usbmidi_lib media snd_rawmidi snd_seq_device drbg ansi_cprng iwlwifi ecdh_generic cfg80211 rfkill ucsi_acpi idma64 typec_ucsi typec sg snd_soc_skl snd_soc_skl_ipc i915 snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_acpi snd_soc_core snd_compress snd_hda_intel drm_kms_helper snd_hda_codec ac battery snd_hda_core snd_hwdep video snd_pcm tpm_crb button snd_timer tpm_tis tpm_tis_core drm snd tpm intel_hid soundcore processor_thermal_device pcc_cpufreq rng_core int3400_thermal mei_me i2c_algo_bit int340x_thermal_zone mei acpi_thermal_rel intel_soc_dts_iosf sparse_keymap parport_pc ppdev lp parport efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb dm_mod sd_mod rtsx_usb_sdmmc rtsx_usb mmc_block crc32c_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper i2c_i801 sdhci_pci cqhci sdhci mmc_core intel_lpss_pci intel_lpss ahci libahci xhci_pci libata xhci_hcd scsi_mod usbcore usb_common fan thermal i2c_hid hid ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:31f0] (rev 03) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:0e.0 Audio device [0403]: Intel Corporation Device [8086:3198] (rev 03) Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:10fc] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl 00:0f.0 Communication controller [0780]: Intel Corporation Device [8086:319a] (rev 03) Subsystem: Intel Corporation Device [8086:7270] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: mei_me Kernel modules: mei_me 00:12.0 SATA controller [0106]: Intel Corporation Device [8086:31e3] (rev 03) (prog-if 01 [AHCI 1.0]) Subsystem: Intel Corporation Device [8086:7270] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ahci Kernel modules: ahci 00:13.0 PCI bridge [0604]: Intel Corporation Device [8086:31d8] (rev f3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B-
Bug#260403: 7025-F30 not working
On Wed, May 4, 2005 12:03 pm, Warren Turkal said: > I just wanted to say that I have a 7025-F30 that will not boot for what > appears to be the same reason for this bug. I have gone expert mode and > went manually to a commandline and found the sym53c8xx module not to > load due to missing symbols. I then did depmod -a. The next time I tried > to load the module, the box locked. I couldn't ^C out. I had to do a cold > reboot. Ahem. Since I've performed a successful install with the Sarge installer I think (from my point of view) this bug can be closed. In fact, I'd be inclined to suggest that the reason the F30 isn't working is because the 2.6.8 kernel provided by the installer doesn't support the F30. I think Sven Luther has 2.6.11 kernel that you might be able to boot from to see if that works any better (my patches to support more PReP boxes went in to the 2.6.9 kernel). I have a (slightly non-working now, sadly) F30 in my garage which I definitely booted Linux on, so it should be possible. Cheers, Leigh.
