Bug#892939: 4.19.0-6
This error still exist in latest Debian Stable kernel Linux ci547 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2 (2019-08-28) x86_64 GNU/Linux
Bug#932168: Correct version of libc-dev not found on security.debian.org
The error I encountered was only slightly different, instead of deb9u2, I got it on deb9u3: Unable to correct missing packages. E: Failed to fetch http://security.debian.org/debian-security/pool/updates/main/l/linux/linux-libc-dev_4.9.168-1+deb9u3_amd64.deb 404 Not Found The solution I found was to simply change " http://security.debian.org/debian-security; in sources.list to " http://deb.debian.org/debian-security;. I do not understand why the URL alias failed on only this package. RUN sed -i "s#deb http://security.debian.org/debian-security stretch/updates main#deb http://deb.debian.org/debian-security stretch/updates main#g" /etc/apt/sources.list Thereafter I can build normally.
Bug#934781: firmware-iwlwifi: iwl4965: Microcode SW error detected
Package: firmware-iwlwifi Version: 20190717-2 Followup-For: Bug #934781 I did some further digging - in my case, at least, the problem seems to be triggered by some relatively recent kernel change. I combed through the system journal for the last few months, and the problem first starts appearing in the logs a few days after I began running kernel 5.2.x (from 5.2.7 through 5.2.9). Previously, while running 4.19.x, the problem never appears. I haven't done a bisection, but it seems pretty clear at this point that there's a microcode bug that has begun to be triggered by something in newer kernels. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-iwlwifi depends on no packages. firmware-iwlwifi recommends no packages. Versions of packages firmware-iwlwifi suggests: ii initramfs-tools 0.135 -- no debconf information
Bug#939697: Kernel regression with b44 and kernels 5.x?
After doing some research online, I was able to find people experiencing the same issues across other distros with the very same NIC on 5.x kernels: https://bugzilla.redhat.com/show_bug.cgi?id=1709671 (Fedora) https://bbs.archlinux.org/viewtopic.php?pid=1844324#p1844324 (Arch) Playing with the swiotlb kernel parameter is of no help - tried with 256, 512, and 4096, but with those I get a null pointer dereference, no wired networking at all, and a system that can only be rebooted through the Magic SysRq key sequence. With swiotlb=force I get "can't perform DMA" errors instead. Apparently this is the offending kernel commit: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/kernel/dma/direct.c?h=v5.2.13=55897af63091ebc2c3f239c6af748113ac50 ...which was merged sometime after 4.19 kernels, and it impacts the entire 5.x line. That commit introduced the swiotlb stuff on direct DMA transactions to simplify some stuff), and judging by the stackdumps on the affected systems, rolling it back should be enough to fix this issue. As I've said, kernels prior to it (which includes the 4.19 series used on Stable) are unaffected. Some users might blame the following commit on b44: https://github.com/torvalds/linux/commit/0f0ed8282e5bfdc87cdd562e58f3d90d893e7ee5#diff-5ab1294594ceb973d7ba266e32b767ea ...but it seems irrelevant IMO, despite being the sole actual change on the b44 driver source merged this year. But then, I'm no kernel hacker. Surprisingly, b44 and swiotlb do have some background of not playing nice: https://groups.google.com/forum/#!topic/linux.kernel/GEx80ZCue1o These wired Broadcom NICs are present on most 2005~2008-era Dell laptops (most notably the Inspiron 6400/E1505/640m series, which are Core/Core 2 builds still being widely used, over a decade after its introduction), some Dell Optiplex desktops, and some HP computers (IIRC the Compaq nx6110 laptop also has a BCM4401 wired NIC). This bug not only breaks wired networking, it can also completely cripple networking support on said systems causing NetworkManager to fail or hang, blocking you from using any alternative NIC (be it wired or wireless, no matter the chipset) on said computers.
Bug#939781: Please include Navi10 firmware files
Package: firmware-amd-graphics Version: 20190717-2 Can you include firmware files for the AMD Navi10 card in to the firmware-amd-graphics package? https://people.freedesktop.org/~agd5f/radeon_ucode/navi10/ The Linux kernel 5.3 has support for the Navi10 card. The Oibaf ppa Mesa master bionic version works with Debian Sid so Mesa support is available too.
Bug#939773: linux-image-5.2.0-2-amd64: MOK key not used for verification of modules signatures.
Package: src:linux Version: 5.2.9-2 Severity: important Dear Maintainer, I've updated kernel from 4.19 to 5.2 and kernel stopped accepting modules signed with MOK key. I have secure boot enabled on my system and enrolled generated MOK key. I use some out-of-tree modules that use DKMS. In the previous version of the kernel I was signing those modules with the MOK key and they loaded just fine as MOK key was loaded into the trusted keyring in the kernel. After the kernel update, MOK key gets inserted into the .platform keyring (I see CONFIG_INTEGRITY_PLATFORM_KEYRING is set to true in the kernel config) which apparently isn't used for validation of module signatures so I'm unable to load MOK signed modules. I would expect this to still work as the only option I have right now for using DKMS modules is building and using my own kernel image... This is also the method described in https://wiki.debian.org/SecureBoot. I've found this related bug in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1701096. There are some links to upstream patches but I've just checked linux master and kernel/module_signing.c is still using only secondary_trusted_keyring and builtin_trusted_keyring to verify modules signatures. Thank you, Marek Rusinowski
Bug#935456: No GPU hardware detected with kernel 5.2 for Rpi2b and Rpi3b
Hi, Kernel 5.2.0-2 with device_tree from kernel 4.19 works: armhfCard arm64Card 4.19.0-5: Rpi2b Success NotPossible32bitCpu Rpi3b Success Success Rpi3b+ Success Success 5.2.0-2 with device_tree from kernel 4.19: Rpi2b Success*1) NotPossible32bitCpu Rpi3b Success*1) Success*1) Rpi3b+ Success*1) Success*1) // Bug report 939633 # cat cmdline.txt dwc_otg.lpm_enable=0 console=tty0 root=/dev/mmcblk0p3 rootfstype=f2fs elevator=deadline fsck.repair=yes rootwait cma=416M # cat config.txt// Rpi3b, armhfCard device_tree=bcm2837-rpi-3-b.dtb.4.19 kernel=vmlinuz-5.2.0-2-armmp initramfs initrd.img-5.2.0-2-armmp followkernel *1) "Success" 5.2.0-2 with device_tree from kernel 4.19: Kde runs very well and stable. The exception is the Hdmi audio which does not work. shutdown -h now // It does not disconnect the power to the monitor. It leaves the monitor on with the text (last row): "reboot: System halted" shutdown -r now // It does not restart. It leaves the monitor on with the text (last row): "Reboot failed -- System halted" Shutdown processes: Stopped Login Service Manage Sound Card // Delay for about a minute with text rows coming before "A stop job is running for"... Rpi3b logs for different configurations (in a search for hdmi audio problem): --- 4.19 kernel and device_tree=bcm2837-rpi-3-b.dtb.4.19: // Hdmi audio works! # journalctl|grep -i bcm Sep 07 19:06:19 irena kernel: Kernel command line: video=HDMI-A-1:1920x1080@60 dma.dmachans=0x7f35 bcm2709.boardrev=0xa02082 bcm2709.serial=0x3f3d54e2 bcm2709.uart_clock=4800 smsc95xx.macaddr=B8:27:EB:3D:54:E2 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty0 root=/dev/mmcblk0p3 rootfstype=f2fs elevator=deadline fsck.repair=yes rootwait cma=416M Sep 07 19:06:19 irena kernel: bcm2835: system timer (irq = 27) Sep 07 19:06:19 irena kernel: bcm2835-mbox 3f00b880.mailbox: mailbox enabled Sep 07 19:06:19 irena kernel: i2c-bcm2835 3f805000.i2c: Could not read clock-frequency property Sep 07 19:06:19 irena kernel: sdhost-bcm2835 3f202000.mmc: loaded - DMA enabled (>1) Sep 07 19:06:20 irena kernel: bcm2835-wdt 3f10.watchdog: Broadcom BCM2835 watchdog timer Sep 07 19:06:20 irena kernel: bcm2835-rng 3f104000.rng: hwrng registered Sep 07 19:06:21 irena kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 # journalctl|grep -i hdmi Sep 07 19:06:19 irena kernel: Kernel command line: video=HDMI-A-1:1920x1080@60 dma.dmachans=0x7f35 bcm2709.boardrev=0xa02082 bcm2709.serial=0x3f3d54e2 bcm2709.uart_clock=4800 smsc95xx.macaddr=B8:27:EB:3D:54:E2 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty0 root=/dev/mmcblk0p3 rootfstype=f2fs elevator=deadline fsck.repair=yes rootwait cma=416M Sep 07 19:06:19 irena kernel: vc4_hdmi 3f902000.hdmi: ASoC: Failed to create component debugfs directory Sep 07 19:06:19 irena kernel: vc4_hdmi 3f902000.hdmi: vc4-hdmi-hifi <-> 3f902000.hdmi mapping ok Sep 07 19:06:19 irena kernel: vc4_hdmi 3f902000.hdmi: ASoC: no DMI vendor name! Sep 07 19:06:19 irena kernel: vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops [vc4]) Sep 07 19:07:17 irena sddm-greeter[549]: Adding view for "HDMI-1" QRect(0,0 1920x1080) # journalctl -p 3 -- Logs begin at Sun 2019-09-08 06:20:52 UTC, end at Sun 2019-09-08 07:42:01 UTC. -- Sep 08 06:20:54 irena kernel: brcmfmac mmc1:0001:1: firmware: failed to load brcm/brcmfmac43430-sdio.bin (-2) Sep 08 06:20:54 irena kernel: firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware Sep 08 06:20:55 irena kernel: brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 0x50 Sep 08 06:20:58 irena lircd-0.10.1[384]: Cannot stat socket path /var/run/lirc/lircd: No such file or directory Sep 08 06:20:58 irena lircd-0.10.1[384]: Error: Cannot setup input file descriptor. Sep 08 06:21:04 irena ntpd[481]: error resolving pool 0.debian.pool.ntp.org: Temporary failure in name resolution (-3) Sep 08 06:21:05 irena ntpd[481]: error resolving pool 1.debian.pool.ntp.org: Temporary failure in name resolution (-3) --- 5.2 kernel and device_tree=bcm2837-rpi-3-b.dtb.5.2: // KDE does not work! # journalctl|grep -i bcm Sep 07 19:00:21 irena kernel: Kernel command line: video=HDMI-A-1:1920x1080@60 dma.dmachans=0x7f35 bcm2709.boardrev=0xa02082 bcm2709.serial=0x3f3d54e2 bcm2709.uart_clock=4800 smsc95xx.macaddr=B8:27:EB:3D:54:E2 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty0 root=/dev/mmcblk0p3 rootfstype=f2fs elevator=deadline fsck.repair=yes rootwait cma=416M Sep 07 19:00:21 irena kernel: bcm2835: system timer (irq = 27) Sep 07 19:00:21 irena kernel: bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver Sep 07 19:00:21 irena kernel: bcm2835-mbox 3f00b880.mailbox: mailbox enabled Sep 07 19:00:21 irena kernel: i2c-bcm2835 3f805000.i2c: Could not read clock-frequency property Sep 07 19:00:21
