[Kernel-packages] [Bug 1907761] Re: vanishing kernel 5.4.0-56-generic
I have created Bug 1907814 to complain about apport refusing to report bugs about unknown updates with an unhelpful message. I believe these remain two separate concerns: a) Retracting security upgrades on purpose after releasing them to non-proposed channels needs a better workflow, reverting in a lower version number is probably entirely unnecessary for smooth upgrades. b) Apport should still be improved even if this is never done on purpose again, because there are other reasons a Package might vanish (outdated mirrors I guess) which apport should be failing gracefully about. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1907761 Title: vanishing kernel 5.4.0-56-generic Status in linux-meta package in Ubuntu: Incomplete Bug description: Kernel version 5.4.0-56-generic has just vanished off the face of the earth, after an update to that version some days ago. This was not updated from "proposed" or anything like that, it was updated in the normal way from "focal-updates". I had to revert several systems to kernel version 5.4.0-54-generic, after apt reported that my installed 5.4.0-56-generic packages were foreign, unknown and unaccounted-for. Have you lost your damn minds? By all means issue a fix for this outrageous situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1907761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907761] Re: vanishing kernel 5.4.0-56-generic
This affects multiple GA and HWE (including -edge) stacks. These are the notices announcing the now missing package versions as intentional releases: https://ubuntu.com/security/notices/USN-4658-1 https://ubuntu.com/security/notices/USN-4659-1 https://ubuntu.com/security/notices/USN-4660-1 https://ubuntu.com/security/notices/USN-4657-1 These are the "-generic" package names that should include the security backports for (among others) CVE-2020-28915 but are now missing: linux-image-5.8.0-31-generic linux-image-5.4.0-56-generic linux-image-4.15.0-126-generic These links at this moment point nowhere: https://packages.ubuntu.com/focal/linux-image-5.8.0-31-generic https://packages.ubuntu.com/bionic/linux-image-5.4.0-56-generic https://packages.ubuntu.com/xenial/linux-image-4.15.0-126-generic ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-28915 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1907761 Title: vanishing kernel 5.4.0-56-generic Status in linux-meta package in Ubuntu: Incomplete Bug description: Kernel version 5.4.0-56-generic has just vanished off the face of the earth, after an update to that version some days ago. This was not updated from "proposed" or anything like that, it was updated in the normal way from "focal-updates". I had to revert several systems to kernel version 5.4.0-54-generic, after apt reported that my installed 5.4.0-56-generic packages were foreign, unknown and unaccounted-for. Have you lost your damn minds? By all means issue a fix for this outrageous situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1907761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1907761] Re: vanishing kernel 5.4.0-56-generic
This link is what *should* have been easily discoverable for anyone wondering about the vanished version: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907262 Ideas: * allow updating USNs even when no new binaries are available, simply because changelogs are *not* * add this possibility to the list of theories ubuntu-security-status (update-manager) helpfully explains when reporting unknown packages * make "DELETED" a more prominent feature on links from USNs (obvious: https://launchpad.net/ubuntu/+source/linux/5.4.0-56.62/+publishinghistory - not obvious: https://launchpad.net/ubuntu/+source/linux/5.4.0-56.62) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1907761 Title: vanishing kernel 5.4.0-56-generic Status in linux-meta package in Ubuntu: Incomplete Bug description: Kernel version 5.4.0-56-generic has just vanished off the face of the earth, after an update to that version some days ago. This was not updated from "proposed" or anything like that, it was updated in the normal way from "focal-updates". I had to revert several systems to kernel version 5.4.0-54-generic, after apt reported that my installed 5.4.0-56-generic packages were foreign, unknown and unaccounted-for. Have you lost your damn minds? By all means issue a fix for this outrageous situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1907761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908423] [NEW] 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive
Public bug reported: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing randomly, about once every few hours. Diagnostics so far have not turned up anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.speed=1 hang reported with firmware-1.20200601 & firmware-1.20201201 hang reported with /proc/device-tree/model "Raspberry Pi 3 Model B Rev 1.2" & "Raspberry Pi 3 Model B Plus Rev 1.3" hang reported with & without config.txt enable_uart=1,uart_2ndstage=1 hang reported with config.txt boot_delay=2 bootcode_delay=2 hang reported with EFI "rpi3 tianocore 1.27" & "rpi3 tianocore 1.31" hang reported with 5.4.0-56-generic usually after a few hours of uptime hang reported with 5.4.0-58-generic usually after a few hours of uptime hang reported with (hwe-edge) 5.8.0-31-generic usually after a few hours of uptime hang reported with 5.4.0-59-generic usually after a few hours of uptime never seen in versions 5.4.0-26-generic through 5.4.0-53-generic, with one notable exception while investigating: similiar hang reported with 5.4.0-53-generic if and only if attempting to unload i2c_bcm2835 module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-58-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/seq', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip Date: Tue Dec 15 16:46:43 2020 IwConfig: Error: [Errno 2] No such file
[Kernel-packages] [Bug 1908423] Re: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive
apport information ** Tags added: apport-collected ** Description changed: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing randomly, about once every few hours. Diagnostics so far have not turned up anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.speed=1 hang reported with firmware-1.20200601 & firmware-1.20201201 hang reported with /proc/device-tree/model "Raspberry Pi 3 Model B Rev 1.2" & "Raspberry Pi 3 Model B Plus Rev 1.3" hang reported with & without config.txt enable_uart=1,uart_2ndstage=1 hang reported with config.txt boot_delay=2 bootcode_delay=2 hang reported with EFI "rpi3 tianocore 1.27" & "rpi3 tianocore 1.31" hang reported with 5.4.0-56-generic usually after a few hours of uptime hang reported with 5.4.0-58-generic usually after a few hours of uptime hang reported with (hwe-edge) 5.8.0-31-generic usually after a few hours of uptime hang reported with 5.4.0-59-generic usually after a few hours of uptime never seen in versions 5.4.0-26-generic through 5.4.0-53-generic, with one notable exception while investigating: similiar hang reported with 5.4.0-53-generic if and only if attempting to unload i2c_bcm2835 module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-58-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/seq', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Ami
[Kernel-packages] [Bug 1908423] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1908423/+attachment/5444234/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing randomly, about once every few hours. -56, -58 and -59 are affected, reverting *only* the kernel back to -53 got me 3 days without freeze. Diagnostics so far have not turned up anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.speed=1 hang reported with firmware-1.20200601 & firmware-1.20201201 hang reported with /proc/device-tree/model "Raspberry Pi 3 Model B Rev 1.2" & "Raspberry Pi 3 Model B Plus Rev 1.3" hang reported with & without config.txt enable_uart=1,uart_2ndstage=1 hang reported with config.txt boot_delay=2 bootcode_delay=2 hang reported with EFI "rpi3 tianocore 1.27" & "rpi3 tianocore 1.31" hang reported with 5.4.0-56-generic usually after a few hours of uptime hang reported with 5.4.0-58-generic usually after a few hours of uptime hang reported with (hwe-edge) 5.8.0-31-generic usually after a few hours of uptime hang reported with 5.4.0-59-generic usually after a few hours of uptime never seen in versions 5.4.0-26-generic through 5.4.0-53-generic, with one notable exception while investigating: similiar hang reported with 5.4.0-53-generic if and only if attempting to unload i2c_bcm2835 module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-58-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 ArecordDevices:
[Kernel-packages] [Bug 1908423] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1908423/+attachment/5444232/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing randomly, about once every few hours. -56, -58 and -59 are affected, reverting *only* the kernel back to -53 got me 3 days without freeze. Diagnostics so far have not turned up anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.speed=1 hang reported with firmware-1.20200601 & firmware-1.20201201 hang reported with /proc/device-tree/model "Raspberry Pi 3 Model B Rev 1.2" & "Raspberry Pi 3 Model B Plus Rev 1.3" hang reported with & without config.txt enable_uart=1,uart_2ndstage=1 hang reported with config.txt boot_delay=2 bootcode_delay=2 hang reported with EFI "rpi3 tianocore 1.27" & "rpi3 tianocore 1.31" hang reported with 5.4.0-56-generic usually after a few hours of uptime hang reported with 5.4.0-58-generic usually after a few hours of uptime hang reported with (hwe-edge) 5.8.0-31-generic usually after a few hours of uptime hang reported with 5.4.0-59-generic usually after a few hours of uptime never seen in versions 5.4.0-26-generic through 5.4.0-53-generic, with one notable exception while investigating: similiar hang reported with 5.4.0-53-generic if and only if attempting to unload i2c_bcm2835 module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-58-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 ArecordDevices: Error:
[Kernel-packages] [Bug 1908423] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1908423/+attachment/5444237/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing randomly, about once every few hours. -56, -58 and -59 are affected, reverting *only* the kernel back to -53 got me 3 days without freeze. Diagnostics so far have not turned up anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.speed=1 hang reported with firmware-1.20200601 & firmware-1.20201201 hang reported with /proc/device-tree/model "Raspberry Pi 3 Model B Rev 1.2" & "Raspberry Pi 3 Model B Plus Rev 1.3" hang reported with & without config.txt enable_uart=1,uart_2ndstage=1 hang reported with config.txt boot_delay=2 bootcode_delay=2 hang reported with EFI "rpi3 tianocore 1.27" & "rpi3 tianocore 1.31" hang reported with 5.4.0-56-generic usually after a few hours of uptime hang reported with 5.4.0-58-generic usually after a few hours of uptime hang reported with (hwe-edge) 5.8.0-31-generic usually after a few hours of uptime hang reported with 5.4.0-59-generic usually after a few hours of uptime never seen in versions 5.4.0-26-generic through 5.4.0-53-generic, with one notable exception while investigating: similiar hang reported with 5.4.0-53-generic if and only if attempting to unload i2c_bcm2835 module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-58-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.14 Architecture: a
[Kernel-packages] [Bug 1908423] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1908423/+attachment/5444239/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing randomly, about once every few hours. -56, -58 and -59 are affected, reverting *only* the kernel back to -53 got me 3 days without freeze. Diagnostics so far have not turned up anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.speed=1 hang reported with firmware-1.20200601 & firmware-1.20201201 hang reported with /proc/device-tree/model "Raspberry Pi 3 Model B Rev 1.2" & "Raspberry Pi 3 Model B Plus Rev 1.3" hang reported with & without config.txt enable_uart=1,uart_2ndstage=1 hang reported with config.txt boot_delay=2 bootcode_delay=2 hang reported with EFI "rpi3 tianocore 1.27" & "rpi3 tianocore 1.31" hang reported with 5.4.0-56-generic usually after a few hours of uptime hang reported with 5.4.0-58-generic usually after a few hours of uptime hang reported with (hwe-edge) 5.8.0-31-generic usually after a few hours of uptime hang reported with 5.4.0-59-generic usually after a few hours of uptime never seen in versions 5.4.0-26-generic through 5.4.0-53-generic, with one notable exception while investigating: similiar hang reported with 5.4.0-53-generic if and only if attempting to unload i2c_bcm2835 module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-58-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 Arecord
[Kernel-packages] [Bug 1908423] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1908423/+attachment/5444233/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing randomly, about once every few hours. -56, -58 and -59 are affected, reverting *only* the kernel back to -53 got me 3 days without freeze. Diagnostics so far have not turned up anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.speed=1 hang reported with firmware-1.20200601 & firmware-1.20201201 hang reported with /proc/device-tree/model "Raspberry Pi 3 Model B Rev 1.2" & "Raspberry Pi 3 Model B Plus Rev 1.3" hang reported with & without config.txt enable_uart=1,uart_2ndstage=1 hang reported with config.txt boot_delay=2 bootcode_delay=2 hang reported with EFI "rpi3 tianocore 1.27" & "rpi3 tianocore 1.31" hang reported with 5.4.0-56-generic usually after a few hours of uptime hang reported with 5.4.0-58-generic usually after a few hours of uptime hang reported with (hwe-edge) 5.8.0-31-generic usually after a few hours of uptime hang reported with 5.4.0-59-generic usually after a few hours of uptime never seen in versions 5.4.0-26-generic through 5.4.0-53-generic, with one notable exception while investigating: similiar hang reported with 5.4.0-53-generic if and only if attempting to unload i2c_bcm2835 module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-58-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 Areco
[Kernel-packages] [Bug 1908423] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1908423/+attachment/5444240/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing randomly, about once every few hours. -56, -58 and -59 are affected, reverting *only* the kernel back to -53 got me 3 days without freeze. Diagnostics so far have not turned up anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.speed=1 hang reported with firmware-1.20200601 & firmware-1.20201201 hang reported with /proc/device-tree/model "Raspberry Pi 3 Model B Rev 1.2" & "Raspberry Pi 3 Model B Plus Rev 1.3" hang reported with & without config.txt enable_uart=1,uart_2ndstage=1 hang reported with config.txt boot_delay=2 bootcode_delay=2 hang reported with EFI "rpi3 tianocore 1.27" & "rpi3 tianocore 1.31" hang reported with 5.4.0-56-generic usually after a few hours of uptime hang reported with 5.4.0-58-generic usually after a few hours of uptime hang reported with (hwe-edge) 5.8.0-31-generic usually after a few hours of uptime hang reported with 5.4.0-59-generic usually after a few hours of uptime never seen in versions 5.4.0-26-generic through 5.4.0-53-generic, with one notable exception while investigating: similiar hang reported with 5.4.0-53-generic if and only if attempting to unload i2c_bcm2835 module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-58-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 ArecordDevices: Er
[Kernel-packages] [Bug 1908423] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1908423/+attachment/5444241/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing randomly, about once every few hours. -56, -58 and -59 are affected, reverting *only* the kernel back to -53 got me 3 days without freeze. Diagnostics so far have not turned up anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.speed=1 hang reported with firmware-1.20200601 & firmware-1.20201201 hang reported with /proc/device-tree/model "Raspberry Pi 3 Model B Rev 1.2" & "Raspberry Pi 3 Model B Plus Rev 1.3" hang reported with & without config.txt enable_uart=1,uart_2ndstage=1 hang reported with config.txt boot_delay=2 bootcode_delay=2 hang reported with EFI "rpi3 tianocore 1.27" & "rpi3 tianocore 1.31" hang reported with 5.4.0-56-generic usually after a few hours of uptime hang reported with 5.4.0-58-generic usually after a few hours of uptime hang reported with (hwe-edge) 5.8.0-31-generic usually after a few hours of uptime hang reported with 5.4.0-59-generic usually after a few hours of uptime never seen in versions 5.4.0-26-generic through 5.4.0-53-generic, with one notable exception while investigating: similiar hang reported with 5.4.0-53-generic if and only if attempting to unload i2c_bcm2835 module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-58-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 ArecordDe
[Kernel-packages] [Bug 1908423] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1908423/+attachment/5444236/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing randomly, about once every few hours. -56, -58 and -59 are affected, reverting *only* the kernel back to -53 got me 3 days without freeze. Diagnostics so far have not turned up anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.speed=1 hang reported with firmware-1.20200601 & firmware-1.20201201 hang reported with /proc/device-tree/model "Raspberry Pi 3 Model B Rev 1.2" & "Raspberry Pi 3 Model B Plus Rev 1.3" hang reported with & without config.txt enable_uart=1,uart_2ndstage=1 hang reported with config.txt boot_delay=2 bootcode_delay=2 hang reported with EFI "rpi3 tianocore 1.27" & "rpi3 tianocore 1.31" hang reported with 5.4.0-56-generic usually after a few hours of uptime hang reported with 5.4.0-58-generic usually after a few hours of uptime hang reported with (hwe-edge) 5.8.0-31-generic usually after a few hours of uptime hang reported with 5.4.0-59-generic usually after a few hours of uptime never seen in versions 5.4.0-26-generic through 5.4.0-53-generic, with one notable exception while investigating: similiar hang reported with 5.4.0-53-generic if and only if attempting to unload i2c_bcm2835 module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-58-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 Arecord
[Kernel-packages] [Bug 1908423] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1908423/+attachment/5444238/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing randomly, about once every few hours. -56, -58 and -59 are affected, reverting *only* the kernel back to -53 got me 3 days without freeze. Diagnostics so far have not turned up anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.speed=1 hang reported with firmware-1.20200601 & firmware-1.20201201 hang reported with /proc/device-tree/model "Raspberry Pi 3 Model B Rev 1.2" & "Raspberry Pi 3 Model B Plus Rev 1.3" hang reported with & without config.txt enable_uart=1,uart_2ndstage=1 hang reported with config.txt boot_delay=2 bootcode_delay=2 hang reported with EFI "rpi3 tianocore 1.27" & "rpi3 tianocore 1.31" hang reported with 5.4.0-56-generic usually after a few hours of uptime hang reported with 5.4.0-58-generic usually after a few hours of uptime hang reported with (hwe-edge) 5.8.0-31-generic usually after a few hours of uptime hang reported with 5.4.0-59-generic usually after a few hours of uptime never seen in versions 5.4.0-26-generic through 5.4.0-53-generic, with one notable exception while investigating: similiar hang reported with 5.4.0-53-generic if and only if attempting to unload i2c_bcm2835 module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-58-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 A
[Kernel-packages] [Bug 1908423] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1908423/+attachment/5444235/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing randomly, about once every few hours. -56, -58 and -59 are affected, reverting *only* the kernel back to -53 got me 3 days without freeze. Diagnostics so far have not turned up anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.speed=1 hang reported with firmware-1.20200601 & firmware-1.20201201 hang reported with /proc/device-tree/model "Raspberry Pi 3 Model B Rev 1.2" & "Raspberry Pi 3 Model B Plus Rev 1.3" hang reported with & without config.txt enable_uart=1,uart_2ndstage=1 hang reported with config.txt boot_delay=2 bootcode_delay=2 hang reported with EFI "rpi3 tianocore 1.27" & "rpi3 tianocore 1.31" hang reported with 5.4.0-56-generic usually after a few hours of uptime hang reported with 5.4.0-58-generic usually after a few hours of uptime hang reported with (hwe-edge) 5.8.0-31-generic usually after a few hours of uptime hang reported with 5.4.0-59-generic usually after a few hours of uptime never seen in versions 5.4.0-26-generic through 5.4.0-53-generic, with one notable exception while investigating: similiar hang reported with 5.4.0-53-generic if and only if attempting to unload i2c_bcm2835 module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-58-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 ArecordDevices:
[Kernel-packages] [Bug 1908423] Re: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive
** Description changed: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing - randomly, about once every few hours. Diagnostics so far have not turned - up anything useful, still busy figuring out cross-compile bisect and a + randomly, about once every few hours. + + -56, -58 and -59 are affected, reverting *only* the kernel back to -53 + got me 3 days without freeze. Diagnostics so far have not turned up + anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.speed=1 hang reported with firmware-1.20200601 & firmware-1.20201201 hang reported with /proc/device-tree/model "Raspberry Pi 3 Model B Rev 1.2" & "Raspberry Pi 3 Model B Plus Rev 1.3" hang reported with & without config.txt enable_uart=1,uart_2ndstage=1 hang reported with config.txt boot_delay=2 bootcode_delay=2 hang reported with EFI "rpi3 tianocore 1.27" & "rpi3 tianocore 1.31" hang reported with 5.4.0-56-generic usually after a few hours of uptime hang reported with 5.4.0-58-generic usually after a few hours of uptime hang reported with (hwe-edge) 5.8.0-31-generic usually after a few hours of uptime hang reported with 5.4.0-59-generic usually after a few hours of uptime never seen in versions 5.4.0-26-generic through 5.4.0-53-generic, with one notable exception while investigating: similiar hang reported with 5.4.0-53-generic if and only if attempting to unload i2c_bcm2835 module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-58-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.14 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/seq', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/
[Kernel-packages] [Bug 1908423] Re: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive
The logs attached to the original bug relate to the issue I care about. The logs attached to fulfill ubuntu-kernel-bot demands contain the dmesg output produced when doing `modprobe -r -v i2c_bcm2835` that demonstrate how these kernel messages share some similarities. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: Since upgrading to 5.4.0-56-generic my RPI3 devices started freezing randomly, about once every few hours. -56, -58 and -59 are affected, reverting *only* the kernel back to -53 got me 3 days without freeze. Diagnostics so far have not turned up anything useful, still busy figuring out cross-compile bisect and a reasonably fast reproduction. The devices are also known as (/proc/device-tree/compatible) raspberrypi,3-model-bbrcm,bcm2837 raspberrypi,3-model-b-plusbrcm,bcm2837 I only use them in ARM64 mode, and I only run -generic kernels via Pete Batards EDKII builds. (unreliable, slow) reproduction: 1. run affected aarch64 kernel 2. set low non-zero /proc/sys/kernel/hung_task_timeout_secs 3. utilize xorg through vc4 kms 4. check dmesg when display freezes symptom 1 (always the same -62): 13:52:01.832230 kernel: raspberrypi-firmware soc:firmware: mbox_send_message returned -62 13:52:01.839310 kernel: raspberrypi-clk raspberrypi-clk: Failed to change pllb frequency: -62 Note: similar message in Bug 1889637 + Exactly one Google search result for the exact message: https://forum.openwrt.org/t/rpi-4-failed-to-change-pllb-frequency/81840 symptom 2 (varying hangs): [Dez15 16:09] INFO: task kworker/2:1:36 blocked for more than 120 seconds. [ +0,19] Tainted: G C E 5.4.0-58-generic #64-Ubuntu [ +0,04] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0,06] kworker/2:1 D036 2 0x0028 [ +0,22] Workqueue: events dbs_work_handler [ +0,04] Call trace: [ +0,09] __switch_to+0xf8/0x1b0 [ +0,08] __schedule+0x310/0x7d8 [ +0,05] schedule+0x40/0xb8 [ +0,04] schedule_timeout+0xa0/0x198 [ +0,05] __wait_for_common+0xf0/0x230 [ +0,05] wait_for_completion_timeout+0x38/0x48 [ +0,06] mbox_send_message+0xd0/0x170 [ +0,06] rpi_firmware_property_list+0xec/0x250 [ +0,04] rpi_firmware_property+0x78/0xb8 [ +0,10] raspberrypi_fw_pll_set_rate+0x60/0xe0 [clk_raspberrypi] [ +0,08] clk_change_rate+0xdc/0x420 [ +0,04] clk_core_set_rate_nolock+0x1cc/0x1f0 [ +0,03] clk_set_rate+0x3c/0xc0 [ +0,06] dev_pm_opp_set_rate+0x3d4/0x520 [ +0,04] set_target+0x4c/0x90 [ +0,07] __cpufreq_driver_target+0x2c8/0x678 [ +0,04] od_dbs_update+0x144/0x1a0 [ +0,03] dbs_work_handler+0x48/0x80 [ +0,06] process_one_work+0x1d0/0x468 [ +0,05] worker_thread+0x154/0x4e0 [ +0,04] kthread+0xf0/0x118 [ +0,04] ret_from_fork+0x10/0x18 non-kernel-version explanations ruled out: network adapter is neither idle nor saturated (~32MiB / hour on enxb827eb..) 4 different power supply models, 2 of them bad but not correlated with frequency of hang swap size & usage obviously does change system responsiveness, but not correlated with frequency of hang hang reported with & without use of wifi of device or any other device within 1m hang reported with & without config.txt dtoverlay=disable-wifi (NOT confirmed that even works) hang reported with cpu_thermal-virtual-0 between 59-67°C (3 copper plates, no fan) hang reported with & without kernel cmdline memtest=2 hang reported with & without kernel cmdline dwc_otg.speed=1 hang reported with firmware-1.20200601 & firmware-1.20201201 hang reported with /proc/device-tree/model "Raspberry Pi 3 Model B Rev 1.2" & "Raspberry Pi 3 Model B Plus Rev 1.3" hang reported with & without config.txt enable_uart=1,uart_2ndstage=1 hang reported with config.txt boot_delay=2 bootcode_delay=2 hang reported with EFI "rpi3 tianocore 1.27" & "rpi3 tianocore 1.31" hang reported with 5.4.0-56-generic usually after a few hours of uptime hang reported with 5.4.0-58-generic usually after a few hours of uptime hang reported with (hwe-edge) 5.8.0-31-generic usually after a few hours of uptime hang reported with 5.4.0-59-generic usually after a few hours of uptime never seen in versions 5.4.0-26-generic through 5.4.0-53-generic, with one notable exception while investigating: similiar hang reported with 5.4.0-53-generic if and only if attempting to unload i2c_bcm2835 module ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-58-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' Appor
[Kernel-packages] [Bug 2039747] [NEW] snd_intel_dsp_driver_probe page fault on linux 6.2
Public bug reported: Workaround snd-intel-sdw-acpi.dsp_driver=1 allows sound output, did not investigate further. Saw some upstream work mentioning "DSPless" mode that sounds like this might become relevant on 6.5 again. Recent 6.5 report where DSP detect worked, but sound did not: LP: #2039320 Note that kvm_intel was loaded, also: /sys/class/firmware-attributes/thinklmi/attributes/KernelDMAProtection/current_value:Enable /sys/class/firmware-attributes/thinklmi/attributes/MicrophoneAccess/current_value:Disable /sys/class/firmware-attributes/thinklmi/attributes/IntegratedAudioAccess/current_value:Enable /sys/class/firmware-attributes/thinklmi/attributes/SGXControl/current_value:Disable (in case some tool refuses parsing the dmesg cutout: I left the inserted "rmi4_smbus" message untouched) DMAR: IOMMU enabled SMT: disabled microcode: Microcode Update Driver: v2.2. [..] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 BUG: unable to handle page fault for address: a412796b5325 #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page PGD 10067 P4D 10067 PUD 0 Oops: [#1] PREEMPT SMP NOPTI CPU: 1 PID: 698 Comm: systemd-udevd Not tainted 6.2.0-36-generic #37~22.04.1-Ubuntu Hardware name: LENOVO 20S5GE/20S5GE, BIOS N2XET39W (1.29 ) 07/25/2023 RIP: 0010:intel_nhlt_has_endpoint_type+0x2a/0x60 [snd_intel_dspcfg] Code: 0f 1f 44 00 00 55 48 89 e5 48 85 ff 74 35 48 8d 47 25 0f b6 7f 24 85 ff 74 29 31 d2 eb 0c 8b 08 83 c2 01 48 01 c8 39 fa 74 19 <40> 38 70 04 75 ee b8 01 00 00 00 5d> RSP: 0018:a41200b778e0 EFLAGS: 00010297 RAX: a412796b5321 RBX: 889c8187d810 RCX: 796802fc RDX: 0001 RSI: 0002 RDI: 00a7 RBP: a41200b778e0 R08: R09: R10: R11: R12: a41200035000 R13: 02c8 R14: 889c819530d0 R15: c137c4b0 FS: 7f3ddea9d8c0() GS:889fce48() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: a412796b5325 CR3: 000103d1e003 CR4: 003706e0 Call Trace: ? show_regs+0x72/0x90 ? __die+0x25/0x80 ? page_fault_oops+0x79/0x190 ? search_exception_tables+0x67/0x80 ? kernelmode_fixup_or_oops+0xb2/0x140 ? __bad_area_nosemaphore+0x1a5/0x2e0 ? bad_area_nosemaphore+0x16/0x30 ? do_kern_addr_fault+0x7b/0xa0 ? exc_page_fault+0x10f/0x1b0 ? asm_exc_page_fault+0x27/0x30 ? intel_nhlt_has_endpoint_type+0x2a/0x60 [snd_intel_dspcfg] snd_intel_dsp_driver_probe.part.0+0x232/0x2a0 [snd_intel_dspcfg] snd_intel_dsp_driver_probe+0x38/0x70 [snd_intel_dspcfg] azx_probe+0x22d/0x4e0 [snd_hda_intel] local_pci_probe+0x48/0xb0 pci_call_probe+0x55/0x190 pci_device_probe+0x84/0x120 really_probe+0x1ea/0x450 __driver_probe_device+0x8a/0x190 driver_probe_device+0x23/0xd0 __driver_attach+0x10f/0x220 ? __pfx___driver_attach+0x10/0x10 bus_for_each_dev+0x80/0xe0 driver_attach+0x1e/0x30 bus_add_driver+0x152/0x250 driver_register+0x83/0x160 ? __pfx_init_module+0x10/0x10 [snd_hda_intel] __pci_register_driver+0x68/0x80 azx_driver_init+0x23/0xff0 [snd_hda_intel] do_one_initcall+0x46/0x240 ? kmalloc_trace+0x2a/0xb0 do_init_module+0x52/0x240 load_module+0xb96/0xd60 ? kernel_read_file+0x25c/0x2b0 __do_sys_finit_module+0xcc/0x150 ? __do_sys_finit_module+0xcc/0x150 __x64_sys_finit_module+0x18/0x30 do_syscall_64+0x59/0x90 ? exit_to_user_mode_prepare+0x3b/0xd0 ? syscall_exit_to_user_mode+0x38/0x60 ? do_syscall_64+0x69/0x90 ? exit_to_user_mode_prepare+0x3b/0xd0 ? syscall_exit_to_user_mode+0x38/0x60 ? do_syscall_64+0x69/0x90 ? do_syscall_64+0x69/0x90 ? do_syscall_64+0x69/0x90 ? do_syscall_64+0x69/0x90 entry_SYSCALL_64_after_hwframe+0x73/0xdd RIP: 0033:0x7f3dde91ea7d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d> RSP: 002b:7ffe1ebf2a98 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 5654c0d70fe0 RCX: 7f3dde91ea7d RDX: RSI: 7f3ddeb5c441 RDI: 0013 RBP: 0002 R08: R09: 0002 R10: 0013 R11: 0246 R12: 7f3ddeb5c441 R13: 5654c0c26000 R14: 0068 R15: 5654c0d65bb0 Modules linked in: snd_hda_intel(+) input_leds snd_intel_dspcfg rapl(+) snd_seq_midi rmi_smbus(+) rmi_core libarc4 snd_intel_sdw_acpi intel_cstate videobuf2_vmalloc snd_> rmi4_smbus 0-002c: registering SMbus-connected sensor mtd mc nvram ee1004 snd_seq processor_thermal_rapl mei_me cfg80211 intel_rapl_common snd_seq_device mei intel_pch_thermal intel_soc_dts_iosf snd_timer snd soundcore int> rtsx_pci typec_ucsi xhci_pci_renesas video typec wmi pinctrl_cannonlake CR2: a412796b5325 ---[ end trace ]--- RIP: 0010:intel_nhlt_has_endpoint_type+0x2a/0x60 [snd_intel_dspcfg] Code: 0f 1f 44
[Kernel-packages] [Bug 2039747] Re: snd_intel_dsp_driver_probe page fault on linux 6.2
** Description changed: - Workaround snd-intel-sdw-acpi.dsp_driver=1 allows sound output, did not investigate further. + Workaround snd-intel-sdw-acpi.dsp_driver=1 allows sound output, did not + investigate further. + Saw some upstream work mentioning "DSPless" mode that sounds like this might become relevant on 6.5 again. + Recent 6.5 report where DSP detect worked, but sound did not: LP: #2039320 Note that kvm_intel was loaded, also: /sys/class/firmware-attributes/thinklmi/attributes/KernelDMAProtection/current_value:Enable /sys/class/firmware-attributes/thinklmi/attributes/MicrophoneAccess/current_value:Disable /sys/class/firmware-attributes/thinklmi/attributes/IntegratedAudioAccess/current_value:Enable /sys/class/firmware-attributes/thinklmi/attributes/SGXControl/current_value:Disable (in case some tool refuses parsing the dmesg cutout: I left the inserted "rmi4_smbus" message untouched) DMAR: IOMMU enabled SMT: disabled microcode: Microcode Update Driver: v2.2. [..] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 BUG: unable to handle page fault for address: a412796b5325 #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page - PGD 10067 P4D 10067 PUD 0 + PGD 10067 P4D 10067 PUD 0 Oops: [#1] PREEMPT SMP NOPTI CPU: 1 PID: 698 Comm: systemd-udevd Not tainted 6.2.0-36-generic #37~22.04.1-Ubuntu Hardware name: LENOVO 20S5GE/20S5GE, BIOS N2XET39W (1.29 ) 07/25/2023 RIP: 0010:intel_nhlt_has_endpoint_type+0x2a/0x60 [snd_intel_dspcfg] Code: 0f 1f 44 00 00 55 48 89 e5 48 85 ff 74 35 48 8d 47 25 0f b6 7f 24 85 ff 74 29 31 d2 eb 0c 8b 08 83 c2 01 48 01 c8 39 fa 74 19 <40> 38 70 04 75 ee b8 01 00 00 00 5d> RSP: 0018:a41200b778e0 EFLAGS: 00010297 RAX: a412796b5321 RBX: 889c8187d810 RCX: 796802fc RDX: 0001 RSI: 0002 RDI: 00a7 RBP: a41200b778e0 R08: R09: R10: R11: R12: a41200035000 R13: 02c8 R14: 889c819530d0 R15: c137c4b0 FS: 7f3ddea9d8c0() GS:889fce48() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: a412796b5325 CR3: 000103d1e003 CR4: 003706e0 Call Trace: - - ? show_regs+0x72/0x90 - ? __die+0x25/0x80 - ? page_fault_oops+0x79/0x190 - ? search_exception_tables+0x67/0x80 - ? kernelmode_fixup_or_oops+0xb2/0x140 - ? __bad_area_nosemaphore+0x1a5/0x2e0 - ? bad_area_nosemaphore+0x16/0x30 - ? do_kern_addr_fault+0x7b/0xa0 - ? exc_page_fault+0x10f/0x1b0 - ? asm_exc_page_fault+0x27/0x30 - ? intel_nhlt_has_endpoint_type+0x2a/0x60 [snd_intel_dspcfg] - snd_intel_dsp_driver_probe.part.0+0x232/0x2a0 [snd_intel_dspcfg] - snd_intel_dsp_driver_probe+0x38/0x70 [snd_intel_dspcfg] - azx_probe+0x22d/0x4e0 [snd_hda_intel] - local_pci_probe+0x48/0xb0 - pci_call_probe+0x55/0x190 - pci_device_probe+0x84/0x120 - really_probe+0x1ea/0x450 + + ? show_regs+0x72/0x90 + ? __die+0x25/0x80 + ? page_fault_oops+0x79/0x190 + ? search_exception_tables+0x67/0x80 + ? kernelmode_fixup_or_oops+0xb2/0x140 + ? __bad_area_nosemaphore+0x1a5/0x2e0 + ? bad_area_nosemaphore+0x16/0x30 + ? do_kern_addr_fault+0x7b/0xa0 + ? exc_page_fault+0x10f/0x1b0 + ? asm_exc_page_fault+0x27/0x30 + ? intel_nhlt_has_endpoint_type+0x2a/0x60 [snd_intel_dspcfg] + snd_intel_dsp_driver_probe.part.0+0x232/0x2a0 [snd_intel_dspcfg] + snd_intel_dsp_driver_probe+0x38/0x70 [snd_intel_dspcfg] + azx_probe+0x22d/0x4e0 [snd_hda_intel] + local_pci_probe+0x48/0xb0 + pci_call_probe+0x55/0x190 + pci_device_probe+0x84/0x120 + really_probe+0x1ea/0x450 __driver_probe_device+0x8a/0x190 - driver_probe_device+0x23/0xd0 - __driver_attach+0x10f/0x220 - ? __pfx___driver_attach+0x10/0x10 - bus_for_each_dev+0x80/0xe0 - driver_attach+0x1e/0x30 - bus_add_driver+0x152/0x250 - driver_register+0x83/0x160 - ? __pfx_init_module+0x10/0x10 [snd_hda_intel] - __pci_register_driver+0x68/0x80 - azx_driver_init+0x23/0xff0 [snd_hda_intel] - do_one_initcall+0x46/0x240 - ? kmalloc_trace+0x2a/0xb0 - do_init_module+0x52/0x240 - load_module+0xb96/0xd60 - ? kernel_read_file+0x25c/0x2b0 - __do_sys_finit_module+0xcc/0x150 - ? __do_sys_finit_module+0xcc/0x150 - __x64_sys_finit_module+0x18/0x30 - do_syscall_64+0x59/0x90 - ? exit_to_user_mode_prepare+0x3b/0xd0 - ? syscall_exit_to_user_mode+0x38/0x60 - ? do_syscall_64+0x69/0x90 - ? exit_to_user_mode_prepare+0x3b/0xd0 - ? syscall_exit_to_user_mode+0x38/0x60 - ? do_syscall_64+0x69/0x90 - ? do_syscall_64+0x69/0x90 - ? do_syscall_64+0x69/0x90 - ? do_syscall_64+0x69/0x90 - entry_SYSCALL_64_after_hwframe+0x73/0xdd + driver_probe_device+0x23/0xd0 + __driver_attach+0x10f/0x220 + ? __pfx___driver_attach+0x10/0x10 + bus_for_each_dev+0x80/0xe0 + driver_attach+0x1e/0x30 + bus_add_driver+0x152/0x250 + driver_register+0x83/0
[Kernel-packages] [Bug 2020524] [NEW] iptables physdev match broken via upstream stable patchset 2023-04-06 / v5.15.93, fixed upstream in 5.15.109
Public bug reported: physdev iptables match was broken in a stable update. A fix is described in upstream releases 5.15.109 and 6.1.26 == Regression details == Discovered in version: 5.19.0-42.43~22.04.1 Last known good version: 5.19.0-41.42~22.04.1 How to tell? Add & use a bridge interface, add catchall filter (no -j ACTION needed) see if *any* bridge traffic is tracked: # iptables -A INPUT -m physdev --physdev-in + -m comment --comment "watch me" # iptables -nvL INPUT | grep watch The match behaves as if the matched packets were not bridge traffic, and consistently so: negation works. Security impact highly depends on rule design. KVM hosts, probably. LP: #2015511 LP: #2012665 bridge info discarded after 2b272bb558f1d3a5aa95ed8a82253786fd1a48ba "netfilter: br_netfilter: disable sabotage_in hook after first suppression" bridge info no longer discarded after 94623f579ce338b5fa61b5acaa5beb8aa657fb9e "netfilter: br_netfilter: fix recent physdev match breakage" related module names: xt_physdev nft_meta_bridge br_netfilter ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Committed ** Changed in: linux (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2020524 Title: iptables physdev match broken via upstream stable patchset 2023-04-06 / v5.15.93, fixed upstream in 5.15.109 Status in linux package in Ubuntu: Fix Committed Bug description: physdev iptables match was broken in a stable update. A fix is described in upstream releases 5.15.109 and 6.1.26 == Regression details == Discovered in version: 5.19.0-42.43~22.04.1 Last known good version: 5.19.0-41.42~22.04.1 How to tell? Add & use a bridge interface, add catchall filter (no -j ACTION needed) see if *any* bridge traffic is tracked: # iptables -A INPUT -m physdev --physdev-in + -m comment --comment "watch me" # iptables -nvL INPUT | grep watch The match behaves as if the matched packets were not bridge traffic, and consistently so: negation works. Security impact highly depends on rule design. KVM hosts, probably. LP: #2015511 LP: #2012665 bridge info discarded after 2b272bb558f1d3a5aa95ed8a82253786fd1a48ba "netfilter: br_netfilter: disable sabotage_in hook after first suppression" bridge info no longer discarded after 94623f579ce338b5fa61b5acaa5beb8aa657fb9e "netfilter: br_netfilter: fix recent physdev match breakage" related module names: xt_physdev nft_meta_bridge br_netfilter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2020524] Re: iptables physdev match broken via upstream stable patchset 2023-04-06 / v5.15.93, fixed upstream in 5.15.109
** Description changed: physdev iptables match was broken in a stable update. - A fix is described in upstream releases 5.15.109 and 6.1.26 + + A fix was already committed in upstream releases + 5.4.242 + 5.15.109 + 6.1.26 + 6.2.13 / LP: #2023929 == Regression details == Discovered in version: 5.19.0-42.43~22.04.1 Last known good version: 5.19.0-41.42~22.04.1 How to tell? Add & use a bridge interface, add catchall filter (no -j ACTION needed) see if *any* bridge traffic is tracked: # iptables -A INPUT -m physdev --physdev-in + -m comment --comment "watch me" # iptables -nvL INPUT | grep watch The match behaves as if the matched packets were not bridge traffic, and consistently so: negation works. Security impact highly depends on rule design. KVM hosts, probably. - LP: #2015511 - LP: #2012665 + bug introduced, bridge info discarded + 5.4.232 dffe83a198a6c293155f99958e51ab84442424c5 LP: #2011625 + 5.15.93 89a69216f17005e28bd9a333662dcb3247dd0f56 LP: #2015511 + 6.1.11 a1512f11ec02458c0986f169f29c90a92c150cc4 LP: #2012665 + 6.2 2b272bb558f1d3a5aa95ed8a82253786fd1a48ba + netfilter: br_netfilter: disable sabotage_in hook after first suppression - bridge info discarded after 2b272bb558f1d3a5aa95ed8a82253786fd1a48ba - "netfilter: br_netfilter: disable sabotage_in hook after first suppression" - - bridge info no longer discarded after 94623f579ce338b5fa61b5acaa5beb8aa657fb9e - "netfilter: br_netfilter: fix recent physdev match breakage" + fixed, bridge info no longer discarded + 5.4.242 36f098e1e4d1a372329c6244b220047a19e60dbd + 5.15.109 cb9b96c154a10dd4802b82281c9246eabe081026 + 6.1.26 ea854a25c8327f51f7ff529b745794a985185563 + 6.2.13 22134b86de9c2afe28e1f406062cd93bdcac4149 + master 94623f579ce338b5fa61b5acaa5beb8aa657fb9e + netfilter: br_netfilter: fix recent physdev match breakage related module names: xt_physdev nft_meta_bridge br_netfilter ** Patch added: "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=94623f579ce338b5fa61b5acaa5beb8aa657fb9e"; https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=94623f579ce338b5fa61b5acaa5beb8aa657fb9e -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2020524 Title: iptables physdev match broken via upstream stable patchset 2023-04-06 / v5.15.93, fixed upstream in 5.15.109 Status in linux package in Ubuntu: Fix Committed Bug description: physdev iptables match was broken in a stable update. A fix was already committed in upstream releases 5.4.242 5.15.109 6.1.26 6.2.13 / LP: #2023929 == Regression details == Discovered in version: 5.19.0-42.43~22.04.1 Last known good version: 5.19.0-41.42~22.04.1 How to tell? Add & use a bridge interface, add catchall filter (no -j ACTION needed) see if *any* bridge traffic is tracked: # iptables -A INPUT -m physdev --physdev-in + -m comment --comment "watch me" # iptables -nvL INPUT | grep watch The match behaves as if the matched packets were not bridge traffic, and consistently so: negation works. Security impact highly depends on rule design. KVM hosts, probably. bug introduced, bridge info discarded 5.4.232 dffe83a198a6c293155f99958e51ab84442424c5 LP: #2011625 5.15.93 89a69216f17005e28bd9a333662dcb3247dd0f56 LP: #2015511 6.1.11 a1512f11ec02458c0986f169f29c90a92c150cc4 LP: #2012665 6.2 2b272bb558f1d3a5aa95ed8a82253786fd1a48ba netfilter: br_netfilter: disable sabotage_in hook after first suppression fixed, bridge info no longer discarded 5.4.242 36f098e1e4d1a372329c6244b220047a19e60dbd 5.15.109 cb9b96c154a10dd4802b82281c9246eabe081026 6.1.26 ea854a25c8327f51f7ff529b745794a985185563 6.2.13 22134b86de9c2afe28e1f406062cd93bdcac4149 master 94623f579ce338b5fa61b5acaa5beb8aa657fb9e netfilter: br_netfilter: fix recent physdev match breakage related module names: xt_physdev nft_meta_bridge br_netfilter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2077416] [NEW] error in audit_log_object_context
Public bug reported: Patch "UBUNTU: SAUCE: apparmor4.0.0 [42/76]: Stacking v38: Audit: Add record for multiple object contexts" - see LP: #2028253 - emits a new kernel error: "error in audit_log_object_context" Could use some explanation, and likely workarounds in whatever software (update, possibly?) is triggering it. https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=hwe-6.8-next&id=dac9a8cf860b2859065e2bdf049c8c7b1404c7be Saw it on Ubuntu 22.04 + Linux 6.5; this report mentions 24.04: https://github.com/linux-audit/audit-userspace/issues/378 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: Patch "UBUNTU: SAUCE: apparmor4.0.0 [42/76]: Stacking v38: Audit: Add record for multiple object contexts" - see LP: #2028253 - emits a new kernel error: "error in audit_log_object_context" Could use some explanation, and likely workarounds in whatever software (update, possibly?) is triggering it. - https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?h=hwe-6.8-next&id=dac9a8cf860b2859065e2bdf049c8c7b1404c7be + https://git.launchpad.net/~ubuntu- + kernel/ubuntu/+source/linux/+git/jammy/commit/?h=hwe-6.8-next&id=dac9a8cf860b2859065e2bdf049c8c7b1404c7be + + Saw it on Ubuntu 22.04 + Linux 6.5; this report mentions 24.04: https://github.com/linux-audit/audit-userspace/issues/378 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2077416 Title: error in audit_log_object_context Status in linux package in Ubuntu: New Bug description: Patch "UBUNTU: SAUCE: apparmor4.0.0 [42/76]: Stacking v38: Audit: Add record for multiple object contexts" - see LP: #2028253 - emits a new kernel error: "error in audit_log_object_context" Could use some explanation, and likely workarounds in whatever software (update, possibly?) is triggering it. https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=hwe-6.8-next&id=dac9a8cf860b2859065e2bdf049c8c7b1404c7be Saw it on Ubuntu 22.04 + Linux 6.5; this report mentions 24.04: https://github.com/linux-audit/audit-userspace/issues/378 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2077416] Re: error in audit_log_object_context
** Description changed: Patch "UBUNTU: SAUCE: apparmor4.0.0 [42/76]: Stacking v38: Audit: Add record for multiple object contexts" - see LP: #2028253 - emits a new kernel error: "error in audit_log_object_context" Could use some explanation, and likely workarounds in whatever software (update, possibly?) is triggering it. https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=hwe-6.8-next&id=dac9a8cf860b2859065e2bdf049c8c7b1404c7be Saw it on Ubuntu 22.04 + Linux 6.5; this report mentions 24.04: https://github.com/linux-audit/audit-userspace/issues/378 + + edit: correlation: systems seeing this error had the snap firefox + running at the time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2077416 Title: error in audit_log_object_context Status in linux package in Ubuntu: New Bug description: Patch "UBUNTU: SAUCE: apparmor4.0.0 [42/76]: Stacking v38: Audit: Add record for multiple object contexts" - see LP: #2028253 - emits a new kernel error: "error in audit_log_object_context" Could use some explanation, and likely workarounds in whatever software (update, possibly?) is triggering it. https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=hwe-6.8-next&id=dac9a8cf860b2859065e2bdf049c8c7b1404c7be Saw it on Ubuntu 22.04 + Linux 6.5; this report mentions 24.04: https://github.com/linux-audit/audit-userspace/issues/378 edit: correlation: systems seeing this error had the snap firefox running at the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2040181] Re: upgrade zfs-linux to 2.2.0 final
Extra step needed when testing these proposed packages against kernels providing the rc: dkms and dpkg disagree on version sort order. # dpkg prioritizes tilde dpkg --compare-versions '2.2.0-0ubuntu1~23.10' gt '2.2.0~rc3-0ubuntu4' ; echo $? # dkms determines dash comes first dpkg-reconfigure zfs-dkms [..] zfs.ko.zst: Running module version sanity check. Error! Module version 2.2.0-0ubuntu1~23.10 for zfs.ko.zst is not newer than what is already found in kernel 6.5.0-10-generic (2.2.0~rc3-0ubuntu4). You may override by specifying --force. Doing as suggested works: sudo dkms install --force zfs/2.2.0 Suppose this cannot be changed (breaking compat) in dkms, but looking at the dkms code, assigning monotonic (under both regimen) versions for the next pre-release versions seems possible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2040181 Title: upgrade zfs-linux to 2.2.0 final Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Mantic: Fix Committed Status in zfs-linux source package in Noble: Fix Released Bug description: [ Impact ] * Potential data loss with zfs 2.2.0-rc3 resolved in -rc5, proposal to update to final * Ubuntu Mantic shipped 2.2.0-rc3 with approximately 10 additional cherrypicks, or kernel team created fixes that got contributed & accepted upstream. At the time this was the only way to get zfs working with v6.5 kernels and also drop the need for shiftfs (due to zfs impovements). Since us shipping this package, upstream has identified and fixed multiple small bugfixes in the subsequent RC and the final releases, including one bug fix that can lead to potential data loss. * The 2.2.0 release branch was frozen for a long time already, and outstanding number of commits of fixes that Mantic does not have is less than 30 small patches. * Proposal to upgrade our build to 2.2.0 final, pick up all the regression fixes, and drop all the cherrypicked patches that enable v6.5 support. This will give us the best kernel driver to support in the runnup to next Ubuntu LTS. [ Test Plan ] * autopkgtest pass * kernel regression zfs testsuite pass * zsys integration test pass * LXD support retested [ Where problems could occur ] * LXD snap in edge shipped zfs tooling of RC5 version until 16th October when they upgraded to 2.2.0 final, there are no kernel- userspace incompatiblities between RC & final, but we should explicitly test this. [ Other Info ] * Upstream is alerting us to the potential data loss and requesting upgrade to 2.2.0-rc5 or better. [ Abbriviated changes being introduced ] $ git log --oneline 4a104ac047..95785196f2 -- cmd/ lib/ module/os/linux/ | grep -v compat 810fc49a3e Ensure we call fput when cloning fails due to different devices. a80e1f1c90 zvol: Temporally disable blk-mq 33d7c2d165 import: require force when cachefile hostid doesn't match on-disk 8015e2ea66 Add '-u' - nomount flag for zfs set c53bc3837c Improve the handling of sharesmb,sharenfs properties e9dc31c74e Update the behavior of mountpoint property 608741d062 Report ashift of L2ARC devices in zdb 0ce1b2ca19 Invoke zdb by guid to avoid import errors 0aabd6b482 ZIL: Avoid dbuf_read() in ztest_get_data() a199cac6cd status: report pool suspension state under failmode=continue 729507d309 Fix occasional rsend test crashes 3af63683fe cmd: add 'help' subcommand to zpool and zfs 9aa1a2878e Fix incorrect expected error in ztest f7a07d76ee Retire z_nr_znodes 54c6fbd378 zed: Allow autoreplace and fault LEDs for removed vdevs 32949f2560 Relax error reporting in zpool import and zpool split 63159e5bda checkstyle: fix action failures e99e684b33 zed: update zed.d/statechange-slot_off.sh d19304ffee zed: Add zedlet to power off slot when drive is faulted 92f095a903 copy_file_range: fix fallback when source create on same txg 895cb689d3 zfs_clone_range should return a descriptive error codes 6bdc7259d1 libzfs: sendrecv: send_progress_thread: handle SIGINFO/SIGUSR1 df8c9f351d ZIL: Second attempt to reduce scope of zl_issuer_lock. 0ae7bfc0a4 zpool_vdev_remove() should handle EALREADY error return bd1eab16eb linux: zfs: ctldir: set [amc]time to snapshot's creation property c47f0f4417 linux/copy_file_range: properly request a fallback copy on Linux <5.3 12f2b1f65e zdb: include cloned blocks in block statistics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2040181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2043197] Re: USB bus error after upgrading to proposed kernel on lunar and jammy
SuperSpeed, specifically: https://lore.kernel.org/all/c1a18876-c505-4d4f-9f58-264199135...@rowland.harvard.edu/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2043197 Title: USB bus error after upgrading to proposed kernel on lunar and jammy Status in linux package in Ubuntu: Confirmed Bug description: [Summary] Some of machines in cert lab after upgrading to proposed kernel on jammy and lunar, all usb devices were gone. I found this issue on linux-image-6.2.0-38-generic and linux- image-5.15.0-90-generic on some specific machines. Since some of machines are using usb ethernet adapter so after upgrading, those machines are not accessible. Following are the machine list I've seen impacted by this issue, I believe there will be more if I check further. https://certification.canonical.com/hardware/202005-27899/ https://certification.canonical.com/hardware/201903-26881/ https://certification.canonical.com/hardware/201903-26932/ https://certification.canonical.com/hardware/202005-27944/ https://certification.canonical.com/hardware/202008-28166/ https://certification.canonical.com/hardware/202008-28167/ https://certification.canonical.com/hardware/202102-28728/ https://certification.canonical.com/hardware/202008-28176/ https://certification.canonical.com/hardware/202008-28177/ https://certification.canonical.com/hardware/202202-29946/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-90-generic 5.15.0-90.100 ProcVersionSignature: Ubuntu 5.15.0-90.100-generic 5.15.131 Uname: Linux 5.15.0-90-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.15.0-90-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.156.25:5248/MAAS/metadata/) Date: Fri Nov 10 12:04:10 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 002: ID 05c8:03cb Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProOne 600 G6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-90-generic root=UUID=6da4d16a-a5a6-47db-a882-3fc3becd4204 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-90-generic N/A linux-backports-modules-5.15.0-90-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2023 dmi.bios.release: 16.0 dmi.bios.vendor: HP dmi.bios.version: S12 Ver. 02.16.00 dmi.board.name: 8810 dmi.board.vendor: HP dmi.board.version: KBC Version 09.08.23 dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.8 dmi.modalias: dmi:bvnHP:bvrS12Ver.02.16.00:bd06/26/2023:br16.0:efr9.8:svnHP:pnHPProOne600G6:pvr:rvnHP:rn8810:rvrKBCVersion09.08.23:cvnHP:ct13:cvr:sku123456#ABA: dmi.product.family: 103C_53307F HP ProOne dmi.product.name: HP ProOne 600 G6 dmi.product.sku: 123456#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2023230] Re: Jammy update: v5.15.105 upstream stable release
In the last line, what does 861d25eea98e reference? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2023230 Title: Jammy update: v5.15.105 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.105 upstream stable release from git://git.kernel.org/ interconnect: qcom: osm-l3: fix icc_onecell_data allocation perf/core: Fix perf_output_begin parameter is incorrectly invoked in perf_event_bpf_output perf: fix perf_event_context->time tracing/hwlat: Replace sched_setaffinity with set_cpus_allowed_ptr serial: fsl_lpuart: Fix comment typo tty: serial: fsl_lpuart: switch to new dmaengine_terminate_* API tty: serial: fsl_lpuart: fix race on RX DMA shutdown serial: 8250: SERIAL_8250_ASPEED_VUART should depend on ARCH_ASPEED serial: 8250: ASPEED_VUART: select REGMAP instead of depending on it kthread: add the helper function kthread_run_on_cpu() trace/hwlat: make use of the helper function kthread_run_on_cpu() trace/hwlat: Do not start per-cpu thread if it is already running net: tls: fix possible race condition between do_tls_getsockopt_conf() and do_tls_setsockopt_conf() power: supply: bq24190_charger: using pm_runtime_resume_and_get instead of pm_runtime_get_sync power: supply: bq24190: Fix use after free bug in bq24190_remove due to race condition power: supply: da9150: Fix use after free bug in da9150_charger_remove due to race condition ARM: dts: imx6sll: e60k02: fix usbotg1 pinctrl ARM: dts: imx6sl: tolino-shine2hd: fix usbotg1 pinctrl arm64: dts: imx8mn: specify #sound-dai-cells for SAI nodes xsk: Add missing overflow check in xdp_umem_reg iavf: fix inverted Rx hash condition leading to disabled hash iavf: fix non-tunneled IPv6 UDP packet type and hashing intel/igbvf: free irq on the error path in igbvf_request_msix() igbvf: Regard vf reset nack as success igc: fix the validation logic for taprio's gate list i2c: imx-lpi2c: check only for enabled interrupt flags i2c: hisi: Only use the completion interrupt to finish the transfer scsi: scsi_dh_alua: Fix memleak for 'qdata' in alua_activate() net: dsa: b53: mmap: fix device tree support net: usb: smsc95xx: Limit packet length to skb->len qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info net: phy: Ensure state transitions are processed from phy_stop() net: mdio: fix owner field for mdio buses registered using device-tree net: mdio: fix owner field for mdio buses registered using ACPI drm/i915/gt: perform uc late init after probe error injection net: qcom/emac: Fix use after free bug in emac_remove due to race condition net/ps3_gelic_net: Fix RX sk_buff length net/ps3_gelic_net: Use dma_mapping_error octeontx2-vf: Add missing free for alloc_percpu bootconfig: Fix testcase to increase max node keys: Do not cache key in task struct if key is requested from kernel thread iavf: fix hang on reboot with ice i40e: fix flow director packet filter programming bpf: Adjust insufficient default bpf_jit_limit net/mlx5e: Set uplink rep as NETNS_LOCAL net/mlx5: Fix steering rules cleanup net/mlx5: Read the TC mapping of all priorities on ETS query net/mlx5: E-Switch, Fix an Oops in error handling code net: dsa: tag_brcm: legacy: fix daisy-chained switches atm: idt77252: fix kmemleak when rmmod idt77252 erspan: do not use skb_mac_header() in ndo_start_xmit() net/sonic: use dma_mapping_error() for error check nvme-tcp: fix nvme_tcp_term_pdu to match spec hvc/xen: prevent concurrent accesses to the shared ring ksmbd: add low bound validation to FSCTL_SET_ZERO_DATA ksmbd: add low bound validation to FSCTL_QUERY_ALLOCATED_RANGES ksmbd: fix possible refcount leak in smb2_open() gve: Cache link_speed value from device net: dsa: mt7530: move enabling disabling core clock to mt7530_pll_setup() net: dsa: mt7530: move lowering TRGMII driving to mt7530_setup() net: dsa: mt7530: move setting ssc_delta to PHY_INTERFACE_MODE_TRGMII case net: mdio: thunder: Add missing fwnode_handle_put() Bluetooth: btqcomsmd: Fix command timeout after setting BD address Bluetooth: L2CAP: Fix responding with wrong PDU type platform/chrome: cros_ec_chardev: fix kernel data leak from ioctl thread_info: Add helpers to snapshot thread flags entry: Snapshot thread flags entry/rcu: Ch
[Kernel-packages] [Bug 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load
0.15.06-2 against 6.2.0-1006-kvm also eats memory, but sometimes adds: 13:06:48.136501 AppArmor DFA next/check upper bounds error 13:06:48.204486 AppArmor DFA next/check upper bounds error 13:06:48.228502 AppArmor DFA next/check upper bounds error 13:06:48.476002 AppArmor DFA state with invalid match flags 13:06:48.476068 BUG: kernel NULL pointer dereference, address: 0030 13:06:48.476526 #PF: supervisor read access in kernel mode 13:06:48.485451 #PF: error_code(0x) - not-present page 13:06:48.485583 PGD 0 P4D 0 13:06:48.485653 Oops: [#1] SMP NOPTI 13:06:48.485696 CPU: 3 PID: 16589 Comm: stress-ng-appar Not tainted 6.2.0-1006-kvm #6-Ubuntu 13:06:48.485729 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 13:06:48.485757 RIP: 0010:0xb55599e8 13:06:48.485788 Code: b6 48 89 4d d0 0f 42 d8 e8 15 4b e6 ff 85 c0 74 19 4c 63 e0 48 83 c4 18 4c 89 e0 5b 41 5c 41 5d 41 5e 41 5f 5d e9 1c a8 59 00 <4d> 8b 55 30 49 8d 82 a0 00 00 00 4c 89 55 c0 48 89 c7 48 89 45 c8 13:06:48.485814 RSP: 0018:b23b01037c70 EFLAGS: 00010246 13:06:48.485848 RAX: RBX: 41ed RCX: 13:06:48.485867 RDX: 00033090 RSI: b6e6bca8 RDI: 13:06:48.485898 RBP: b23b01037cb0 R08: R09: 13:06:48.485947 R10: b53a8f4b R11: 0246 R12: b5f00026 13:06:48.485981 R13: R14: R15: 13:06:48.486006 FS: 7fb551056740() GS:9e3177cc() knlGS: 13:06:48.486033 CS: 0010 DS: ES: CR0: 80050033 13:06:48.486051 CR2: 0030 CR3: 000103c86000 CR4: 00350ee0 13:06:48.486076 Call Trace: 13:06:48.486102 13:06:48.486126 0xb555e326 13:06:48.486156 0xb556b7cb 13:06:48.486169 0xb555bf9f 13:06:48.486193 0xb555c0e9 13:06:48.486226 0xb53832fa 13:06:48.486251 ? 0xb51f8bd0 13:06:48.486271 0xb53837d2 13:06:48.486295 0xb5383878 13:06:48.486320 0xb5addf37 13:06:48.486351 ? 0xb5ae24f5 13:06:48.486370 ? 0xb5addf43 13:06:48.486401 ? 0xb5ae25b1 13:06:48.486427 ? 0xb5ae1c3f 13:06:48.486446 0xb5c000ae 13:06:48.486465 RIP: 0033:0x7fb550d069e4 13:06:48.486490 Code: 15 39 a4 0e 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 80 3d fd 2b 0f 00 00 74 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 c3 0f 1f 00 48 83 ec 28 48 89 54 24 18 48 13:06:48.486508 RSP: 002b:7ffe81ae16a8 EFLAGS: 0202 ORIG_RAX: 0001 13:06:48.486532 RAX: ffda RBX: 556e11d97fc0 RCX: 7fb550d069e4 13:06:48.486564 RDX: 00010d92 RSI: 556e11d9a890 RDI: 0005 13:06:48.486589 RBP: 00010d92 R08: 556e11dc7510 R09: 13:06:48.486608 R10: R11: 0202 R12: 556e11d9a890 13:06:48.486633 R13: 0005 R14: R15: 7fb54f37e000 13:06:48.486657 13:06:48.486676 Modules linked in: ip6t_REJECT nf_reject_ipv6 nft_limit nft_chain_nat nf_nat xt_owner xt_hashlimit xt_tcpudp ipt_REJECT nf_reject_ipv4 xt_conntrack xt_LOG nf_log_syslog xt_limit xt_comment nft_compat nf_tables nls_iso8859_1 nls_cp437 vfat fat fuse configfs ip_tables x_tables btrfs blake2b_generic xor lzo_compress raid6_pq efivarfs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c polyval_clmulni polyval_generic gf128mul ahci libahci 13:06:48.486699 CR2: 0030 13:06:48.486712 ---[ end trace ]--- 13:06:48.486734 RIP: 0010:0xb55599e8 13:06:48.486753 Code: b6 48 89 4d d0 0f 42 d8 e8 15 4b e6 ff 85 c0 74 19 4c 63 e0 48 83 c4 18 4c 89 e0 5b 41 5c 41 5d 41 5e 41 5f 5d e9 1c a8 59 00 <4d> 8b 55 30 49 8d 82 a0 00 00 00 4c 89 55 c0 48 89 c7 48 89 45 c8 13:06:48.486773 RSP: 0018:b23b01037c70 EFLAGS: 00010246 13:06:48.486792 RAX: RBX: 41ed RCX: 13:06:48.486811 RDX: 00033090 RSI: b6e6bca8 RDI: 13:06:48.486823 RBP: b23b01037cb0 R08: R09: 13:06:48.486834 R10: b53a8f4b R11: 0246 R12: b5f00026 13:06:48.486852 R13: R14: R15: 13:06:48.486870 FS: 7fb551056740() GS:9e3177cc() knlGS: 13:06:48.486889 CS: 0010 DS: ES: CR0: 80050033 13:06:48.486902 CR2: 0030 CR3: 000103c86000 CR4: 00350ee0 13:06:48.486920 note: stress-ng-appar[16589] exited with irqs disabled -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024599 Title: linux-image-5.15.0-1032-realtime locks up under scheduler test load Status in linux package in Ubuntu: Incomplete Status in linux
[Kernel-packages] [Bug 2020524] Re: iptables physdev match broken via upstream stable patchset 2023-04-06 / v5.15.93, fixed upstream in 5.15.109
Fixed in: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Available on jammy via: linux-image-generic-hwe-22.04-edge ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Description changed: physdev iptables match was broken in a stable update. A fix was already committed in upstream releases 5.4.242 5.15.109 6.1.26 - 6.2.13 / LP: #2023929 + 6.2.13 / LP: #2023929 / LP: #2026752 == Regression details == Discovered in version: 5.19.0-42.43~22.04.1 Last known good version: 5.19.0-41.42~22.04.1 How to tell? Add & use a bridge interface, add catchall filter (no -j ACTION needed) see if *any* bridge traffic is tracked: # iptables -A INPUT -m physdev --physdev-in + -m comment --comment "watch me" # iptables -nvL INPUT | grep watch The match behaves as if the matched packets were not bridge traffic, and consistently so: negation works. Security impact highly depends on rule design. KVM hosts, probably. bug introduced, bridge info discarded 5.4.232 dffe83a198a6c293155f99958e51ab84442424c5 LP: #2011625 5.15.93 89a69216f17005e28bd9a333662dcb3247dd0f56 LP: #2015511 6.1.11 a1512f11ec02458c0986f169f29c90a92c150cc4 LP: #2012665 6.2 2b272bb558f1d3a5aa95ed8a82253786fd1a48ba netfilter: br_netfilter: disable sabotage_in hook after first suppression fixed, bridge info no longer discarded 5.4.242 36f098e1e4d1a372329c6244b220047a19e60dbd 5.15.109 cb9b96c154a10dd4802b82281c9246eabe081026 6.1.26 ea854a25c8327f51f7ff529b745794a985185563 6.2.13 22134b86de9c2afe28e1f406062cd93bdcac4149 master 94623f579ce338b5fa61b5acaa5beb8aa657fb9e netfilter: br_netfilter: fix recent physdev match breakage related module names: xt_physdev nft_meta_bridge br_netfilter -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2020524 Title: iptables physdev match broken via upstream stable patchset 2023-04-06 / v5.15.93, fixed upstream in 5.15.109 Status in linux package in Ubuntu: Fix Released Bug description: physdev iptables match was broken in a stable update. A fix was already committed in upstream releases 5.4.242 5.15.109 6.1.26 6.2.13 / LP: #2023929 / LP: #2026752 == Regression details == Discovered in version: 5.19.0-42.43~22.04.1 Last known good version: 5.19.0-41.42~22.04.1 How to tell? Add & use a bridge interface, add catchall filter (no -j ACTION needed) see if *any* bridge traffic is tracked: # iptables -A INPUT -m physdev --physdev-in + -m comment --comment "watch me" # iptables -nvL INPUT | grep watch The match behaves as if the matched packets were not bridge traffic, and consistently so: negation works. Security impact highly depends on rule design. KVM hosts, probably. bug introduced, bridge info discarded 5.4.232 dffe83a198a6c293155f99958e51ab84442424c5 LP: #2011625 5.15.93 89a69216f17005e28bd9a333662dcb3247dd0f56 LP: #2015511 6.1.11 a1512f11ec02458c0986f169f29c90a92c150cc4 LP: #2012665 6.2 2b272bb558f1d3a5aa95ed8a82253786fd1a48ba netfilter: br_netfilter: disable sabotage_in hook after first suppression fixed, bridge info no longer discarded 5.4.242 36f098e1e4d1a372329c6244b220047a19e60dbd 5.15.109 cb9b96c154a10dd4802b82281c9246eabe081026 6.1.26 ea854a25c8327f51f7ff529b745794a985185563 6.2.13 22134b86de9c2afe28e1f406062cd93bdcac4149 master 94623f579ce338b5fa61b5acaa5beb8aa657fb9e netfilter: br_netfilter: fix recent physdev match breakage related module names: xt_physdev nft_meta_bridge br_netfilter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031093] Re: libgnutls report "trap invalid opcode" when trying to install packages over https
Is there a way to have either launchpad or snapd track the status in snap-managed library hardcopies? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2031093 Title: libgnutls report "trap invalid opcode" when trying to install packages over https Status in ubuntu-kernel-tests: New Status in gnutls28 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in gnutls28 source package in Focal: Confirmed Status in linux source package in Focal: Fix Released Status in gnutls28 source package in Jammy: Confirmed Status in linux source package in Jammy: Fix Released Status in gnutls28 source package in Lunar: Confirmed Status in linux source package in Lunar: Fix Released Bug description: [Impact] When booting linux with Gather Data Sampling mitigations without updated microcode on an affected CPU, AVX will be disabled. This will cause programs connecting to https using gnutls on Jammy to break, including apt and git. [Test case] git clone https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] Works fine with the mitigation disabled by default. [Potential regressions] Users booting on affected parts without microcode updates will be subject to Gather Data Sampling attacks (which can be done by local untrusted attackers), which may leak confidential data, including keys. - When trying to install linux-libc-dev on Oracle BM.Standard2.52 (seems to be the only affected instance) with Jammy 5.15.0-81-generic, it will get interrupted with: E: Method https has died unexpectedly! E: Sub-process https received signal 4. $ sudo apt install linux-libc-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done The following NEW packages will be installed: linux-libc-dev 0 upgraded, 1 newly installed, 0 to remove and 54 not upgraded. Need to get 1353 kB of archives. After this operation, 6943 kB of additional disk space will be used. E: Method https has died unexpectedly! E: Sub-process https received signal 4. From dmesg you will see: [ 1078.750067] traps: https[4572] trap invalid opcode ip:7f3c1e6316be sp:7ffea26b61c0 error:0 in libgnutls.so.30.31.0[7f3c1e50f000+129000] Also, git clone is not working as well. $ git clone --depth=1 https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests Cloning into 'autotest-client-tests'... error: git-remote-https died of signal 4 dmesg: [ 806.072080] traps: git-remote-http[2561] trap invalid opcode ip:7fa2e7dac44a sp:7ffed6796480 error:0 in libgnutls.so.30.31.0[7fa2e7c85000+129000] libgnutls30 version:3.7.3-4ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2031093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039747] Re: snd_intel_dsp_driver_probe page fault on linux 6.2
** Also affects: linux-hwe-6.8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2039747 Title: snd_intel_dsp_driver_probe page fault on linux 6.2 Status in linux-hwe-6.2 package in Ubuntu: New Status in linux-hwe-6.8 package in Ubuntu: New Bug description: Workaround snd_intel_dspcfg.dsp_driver=1 allows sound output, did not investigate further. Saw some upstream work mentioning "DSPless" mode that sounds like this might become relevant on 6.5 again. Recent 6.5 report where DSP detect worked, but sound did not: LP: #2039320 Note that kvm_intel was loaded, also: /sys/class/firmware-attributes/thinklmi/attributes/KernelDMAProtection/current_value:Enable /sys/class/firmware-attributes/thinklmi/attributes/MicrophoneAccess/current_value:Disable /sys/class/firmware-attributes/thinklmi/attributes/IntegratedAudioAccess/current_value:Enable /sys/class/firmware-attributes/thinklmi/attributes/SGXControl/current_value:Disable (in case some tool refuses parsing the dmesg cutout: I left the inserted "rmi4_smbus" message untouched) DMAR: IOMMU enabled SMT: disabled microcode: Microcode Update Driver: v2.2. [..] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 BUG: unable to handle page fault for address: a412796b5325 #PF: supervisor read access in kernel mode #PF: error_code(0x) - not-present page PGD 10067 P4D 10067 PUD 0 Oops: [#1] PREEMPT SMP NOPTI CPU: 1 PID: 698 Comm: systemd-udevd Not tainted 6.2.0-36-generic #37~22.04.1-Ubuntu Hardware name: LENOVO 20S5GE/20S5GE, BIOS N2XET39W (1.29 ) 07/25/2023 RIP: 0010:intel_nhlt_has_endpoint_type+0x2a/0x60 [snd_intel_dspcfg] Code: 0f 1f 44 00 00 55 48 89 e5 48 85 ff 74 35 48 8d 47 25 0f b6 7f 24 85 ff 74 29 31 d2 eb 0c 8b 08 83 c2 01 48 01 c8 39 fa 74 19 <40> 38 70 04 75 ee b8 01 00 00 00 5d> RSP: 0018:a41200b778e0 EFLAGS: 00010297 RAX: a412796b5321 RBX: 889c8187d810 RCX: 796802fc RDX: 0001 RSI: 0002 RDI: 00a7 RBP: a41200b778e0 R08: R09: R10: R11: R12: a41200035000 R13: 02c8 R14: 889c819530d0 R15: c137c4b0 FS: 7f3ddea9d8c0() GS:889fce48() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: a412796b5325 CR3: 000103d1e003 CR4: 003706e0 Call Trace: ? show_regs+0x72/0x90 ? __die+0x25/0x80 ? page_fault_oops+0x79/0x190 ? search_exception_tables+0x67/0x80 ? kernelmode_fixup_or_oops+0xb2/0x140 ? __bad_area_nosemaphore+0x1a5/0x2e0 ? bad_area_nosemaphore+0x16/0x30 ? do_kern_addr_fault+0x7b/0xa0 ? exc_page_fault+0x10f/0x1b0 ? asm_exc_page_fault+0x27/0x30 ? intel_nhlt_has_endpoint_type+0x2a/0x60 [snd_intel_dspcfg] snd_intel_dsp_driver_probe.part.0+0x232/0x2a0 [snd_intel_dspcfg] snd_intel_dsp_driver_probe+0x38/0x70 [snd_intel_dspcfg] azx_probe+0x22d/0x4e0 [snd_hda_intel] local_pci_probe+0x48/0xb0 pci_call_probe+0x55/0x190 pci_device_probe+0x84/0x120 really_probe+0x1ea/0x450 __driver_probe_device+0x8a/0x190 driver_probe_device+0x23/0xd0 __driver_attach+0x10f/0x220 ? __pfx___driver_attach+0x10/0x10 bus_for_each_dev+0x80/0xe0 driver_attach+0x1e/0x30 bus_add_driver+0x152/0x250 driver_register+0x83/0x160 ? __pfx_init_module+0x10/0x10 [snd_hda_intel] __pci_register_driver+0x68/0x80 azx_driver_init+0x23/0xff0 [snd_hda_intel] do_one_initcall+0x46/0x240 ? kmalloc_trace+0x2a/0xb0 do_init_module+0x52/0x240 load_module+0xb96/0xd60 ? kernel_read_file+0x25c/0x2b0 __do_sys_finit_module+0xcc/0x150 ? __do_sys_finit_module+0xcc/0x150 __x64_sys_finit_module+0x18/0x30 do_syscall_64+0x59/0x90 ? exit_to_user_mode_prepare+0x3b/0xd0 ? syscall_exit_to_user_mode+0x38/0x60 ? do_syscall_64+0x69/0x90 ? exit_to_user_mode_prepare+0x3b/0xd0 ? syscall_exit_to_user_mode+0x38/0x60 ? do_syscall_64+0x69/0x90 ? do_syscall_64+0x69/0x90 ? do_syscall_64+0x69/0x90 ? do_syscall_64+0x69/0x90 entry_SYSCALL_64_after_hwframe+0x73/0xdd RIP: 0033:0x7f3dde91ea7d Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d> RSP: 002b:7ffe1ebf2a98 EFLAGS: 0246 ORIG_RAX: 0139 RAX: ffda RBX: 5654c0d70fe0 RCX: 7f3dde91ea7d RDX: RSI: 7f3ddeb5c441 RDI: 0013 RBP: 0002 R08: R09: 0002 R10: 0013 R11: 0246 R12: 7f3ddeb5c441 R13: 5654c0c26000 R14: 0068 R15: 5654c0d65bb0 Modules lin
[Kernel-packages] [Bug 2039747] Re: snd_intel_dsp_driver_probe page fault on linux 6.2
Similar device on linux-image-generic-hwe-22.04 ~> linux-
modules-6.8.0-40-generic
# dmidecode | grep 'Family: T'
Family: ThinkPad T14 Gen 1
# grep -rH .
/sys/class/firmware-attributes/thinklmi/attributes/{MicrophoneAccess,IntegratedAudioAccess,SGXControl,KernelDMAProtection}/current_value
/sys/class/firmware-attributes/thinklmi/attributes/MicrophoneAccess/current_value:Disable
/sys/class/firmware-attributes/thinklmi/attributes/IntegratedAudioAccess/current_value:Enable
/sys/class/firmware-attributes/thinklmi/attributes/SGXControl/current_value:Disable
/sys/class/firmware-attributes/thinklmi/attributes/KernelDMAProtection/current_value:Enable
# dmesg
DMAR-IR: IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1
SMT: disabled
microcode: Current revision: 0x00fc
microcode: Updated early from: 0x00f8
[..]
snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info
0x040380
BUG: unable to handle page fault for address: a3e28c9e353f
#PF: supervisor read access in kernel mode
#PF: error_code(0x) - not-present page
PGD 10067 P4D 10067 PUD 0
Oops: [#1] PREEMPT SMP NOPTI
CPU: 1 PID: 750 Comm: systemd-udevd Not tainted 6.8.0-40-generic
#40~22.04.3-Ubuntu
Hardware name: LENOVO 20S1S4RB2E/20S1S4RB2E, BIOS N2XET40W (1.30 ) 10/31/2023
RIP: 0010:intel_nhlt_has_endpoint_type+0x2b/0x60 [snd_intel_dspcfg]
Code: 1f 44 00 00 55 48 89 e5 48 85 ff 74 36 48 8d 47 25 0f b6 7f 24 40 84 ff
74 29 31 d2 eb 0c 8b 08 83 c2 01 48 01 c8 39 fa 74 19 <40> 38 70 04 75 ee b8 01
00 00 00 5d 31 d2 31 c9 31 f6 31 ff c3 cc
RSP: 0018:a3e1c06975c8 EFLAGS: 00010297
RAX: a3e28c9e353b RBX: a3e1c0035000 RCX: cc9ae516
RDX: 0001 RSI: 0002 RDI: 0086
RBP: a3e1c06975c8 R08: R09:
R10: R11: R12: 8e8d82028000
R13: 0003 R14: 0002 R15: c135e4c8
FS: 7b56ce03a8c0() GS:8e90cc28() knlGS:
CS: 0010 DS: ES: CR0: 80050033
CR2: a3e28c9e353f CR3: 00010eae8003 CR4: 003706f0
DR0: DR1: DR2:
DR3: DR6: fffe0ff0 DR7: 0400
Call Trace:
? show_regs+0x6d/0x80
? __die+0x24/0x80
? page_fault_oops+0x99/0x1b0
? kernelmode_fixup_or_oops.constprop.0+0x69/0x90
? __bad_area_nosemaphore+0x19d/0x2c0
? bad_area_nosemaphore+0x16/0x30
? do_kern_addr_fault+0x7b/0xa0
? exc_page_fault+0x10d/0x1b0
? asm_exc_page_fault+0x27/0x30
? intel_nhlt_has_endpoint_type+0x2b/0x60 [snd_intel_dspcfg]
snd_intel_dsp_driver_probe+0x32b/0x3e0 [snd_intel_dspcfg]
azx_probe+0x2d9/0x830 [snd_hda_intel]
? __get_random_u32_below+0x17/0x70
? radix_tree_iter_tag_clear+0x12/0x20
? idr_alloc_u32+0xaa/0xf0
? idr_alloc_cyclic+0x54/0xc0
? __kernfs_new_node+0x18f/0x220
? kmalloc_trace+0x139/0x360
local_pci_probe+0x44/0xb0
pci_call_probe+0x55/0x1a0
pci_device_probe+0x84/0x120
really_probe+0x1c9/0x430
__driver_probe_device+0x8c/0x190
driver_probe_device+0x24/0xd0
__driver_attach+0x10b/0x210
? __pfx___driver_attach+0x10/0x10
bus_for_each_dev+0x8a/0xf0
driver_attach+0x1e/0x30
bus_add_driver+0x156/0x260
driver_register+0x5e/0x130
? __pfx_azx_driver_init+0x10/0x10 [snd_hda_intel]
__pci_register_driver+0x5e/0x70
azx_driver_init+0x23/0xff0 [snd_hda_intel]
do_one_initcall+0x5b/0x340
do_init_module+0x97/0x290
load_module+0xb85/0xcd0
? security_kernel_post_read_file+0x75/0x90
init_module_from_file+0x96/0x100
? init_module_from_file+0x96/0x100
idempotent_init_module+0x11c/0x2b0
__x64_sys_finit_module+0x64/0xd0
x64_sys_call+0x169c/0x24b0
do_syscall_64+0x81/0x170
? syscall_exit_to_user_mode+0x89/0x260
? do_syscall_64+0x8d/0x170
? putname+0x5b/0x80
? do_sys_openat2+0x9f/0xe0
? __x64_sys_openat+0x6c/0xa0
? syscall_exit_to_user_mode+0x89/0x260
? do_syscall_64+0x8d/0x170
? do_syscall_64+0x8d/0x170
? do_syscall_64+0x8d/0x170
? irqentry_exit+0x43/0x50
? clear_bhb_loop+0x15/0x70
? clear_bhb_loop+0x15/0x70
? clear_bhb_loop+0x15/0x70
entry_SYSCALL_64_after_hwframe+0x78/0x80
RIP: 0033:0x7b56cdf1e88d
Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48
89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01
c3 48 8b 0d 73 b5 0f 00 f7 d8 64 89 01 48
RSP: 002b:7ffc3d886228 EFLAGS: 0246 ORIG_RAX: 0139
RAX: ffda RBX: 5b15c3b7f090 RCX: 7b56cdf1e88d
RDX: RSI: 7b56ce25f441 RDI: 0014
RBP: 0002 R08: R09: 0002
R10: 0014 R11: 0246 R12: 7b56ce25f441
R13: 5b15c3a44eb0 R14: 0068 R15: 5b15c3b80190
Modules linked in: snd_hda_intel(+) mac80211 snd_intel_dspcfg intel_cstate
libarc4 snd_intel_sdw_acpi snd_seq_midi rmi_smbus(+) snd_seq_midi_event
snd_hda_codec rmi_core processor_thermal_device_pci_legacy snd_hda_core
snd_rawmidi vid
[Kernel-packages] [Bug 2077416] Re: error in audit_log_object_context
** Description changed: Patch "UBUNTU: SAUCE: apparmor4.0.0 [42/76]: Stacking v38: Audit: Add record for multiple object contexts" - see LP: #2028253 - emits a new kernel error: "error in audit_log_object_context" Could use some explanation, and likely workarounds in whatever software (update, possibly?) is triggering it. https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=hwe-6.8-next&id=dac9a8cf860b2859065e2bdf049c8c7b1404c7be Saw it on Ubuntu 22.04 + Linux 6.5; this report mentions 24.04: https://github.com/linux-audit/audit-userspace/issues/378 - edit: correlation: systems seeing this error had the snap firefox - running at the time. + edit: correlation: systems seeing this error had the snap firefox running at the time. + see LP: #2069464 for a reliable reproducer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2077416 Title: error in audit_log_object_context Status in linux package in Ubuntu: New Bug description: Patch "UBUNTU: SAUCE: apparmor4.0.0 [42/76]: Stacking v38: Audit: Add record for multiple object contexts" - see LP: #2028253 - emits a new kernel error: "error in audit_log_object_context" Could use some explanation, and likely workarounds in whatever software (update, possibly?) is triggering it. https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy/commit/?h=hwe-6.8-next&id=dac9a8cf860b2859065e2bdf049c8c7b1404c7be Saw it on Ubuntu 22.04 + Linux 6.5; this report mentions 24.04: https://github.com/linux-audit/audit-userspace/issues/378 edit: correlation: systems seeing this error had the snap firefox running at the time. see LP: #2069464 for a reliable reproducer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2104282] Re: iptables incompatibility
upstream break: 0bfcb7b71e735560077a42847f69597ec7dcc326 netfilter: xtables: avoid NFPROTO_UNSPEC where needed Upstream fix: 306ed1728e8438caed30332e1ab46b28c25fe3d8 netfilter: xtables: fix typo causing some targets not to load on IPv6 Sample error message: ip6tables-restore v1.8.7 (nf_tables): unknown option "--nflog-group" (came here to add the missing keywords - search does not find this bug affecting NFLOG TRACE MARK targets) ** Summary changed: - iptables incompatibility + iptables NFLOG TRACE MARK incompatibility -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2104282 Title: iptables NFLOG TRACE MARK incompatibility Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: Fix Committed Bug description: After upgrading to linux-image-6.8.0-56-generic my RKE2 based kubernetes cluster on Ubuntu 24.04.2 LTS started having some problems. The kubeproxy pods started crashlooping with an error that said "Failed to execute iptables-restore" err=https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2104282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2105997] Re: Android instance can not access network once kernel is upgraded to 6.8.0-57.59~22.04.1
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2104282
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2104134
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2091990
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2105997
Title:
Android instance can not access network once kernel is upgraded to
6.8.0-57.59~22.04.1
Status in linux package in Ubuntu:
New
Bug description:
Anbox Cloud enables people to run LXC-based Android instances to
provide a generic AOSP experience in the cloud. After the 6.8 HWE
kernel was updated to 6.8.0-57.59, Android containers can no longer
access the network.
```
root@test0:~# anbox-shell ping -c 1 192.168.250.1
connect: Network is unreachable
```
We observed the following errors from the IptablesRestoreController component
in Android, which manages both IPv4 and IPv6 rules.
```
root@test0:~# anbox-shell logcat -s IptablesRestoreController
- beginning of main
04-01 12:29:48.03691 171 E IptablesRestoreController: iptables error:
04-01 12:29:48.03691 171 E IptablesRestoreController: --- COMMAND
---
04-01 12:29:48.03691 171 E IptablesRestoreController: *mangle
04-01 12:29:48.03691 171 E IptablesRestoreController: -A
routectrl_mangle_INPUT -i eth0 -j MARK --set-mark 0x30064/0xffef
04-01 12:29:48.03691 171 E IptablesRestoreController: COMMIT
04-01 12:29:48.03691 171 E IptablesRestoreController: --- ERROR
---
04-01 12:29:48.03691 171 E IptablesRestoreController: ip6tables-restore
v1.8.7 (legacy): unknown option "--set-mark"
04-01 12:29:48.03691 171 E IptablesRestoreController: Error occurred at
line: 2
04-01 12:29:48.03691 171 E IptablesRestoreController: Try
`ip6tables-restore -h' or 'ip6tables-restore --help' for more information.
```
During our testing, things started breaking with kernel 6.8.0-56.58.1.
We confirmed that after downgrading the kernel to 6.8.0-55.57.1,
things worked again.
The underlying issue has been discussed over [1]
```
This is caused by 0bfcb7b71e73 ("netfilter: xtables: avoid NFPROTO_UNSPEC
where needed") and a fix is already in the works:
https://lore.kernel.org/all/20241019-xtables-typos-v2-1-6b8b1735d...@0upti.me/
For now downgrading the kernel or patching it with the above should fix the
issue, although I'd expect the issue to be fixed with the next stable kernel
```
We've seen that the fix("netfilter: xtables: fix typo causing some
targets not to load on IPv6") has been included in the 6.8.0-58.60
kernel [2] and can confirm that after upgrading the kernel to
6.8.0-58.60, the issue is resolved, and network access from the
Android container works fine.
```
$ anbox-shell ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=34.4 ms
```
Meanwhile when testing the cloud flavor kernels,
```
$ uname -r
6.8.0-1024-aws
$ anbox-shell ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=34.4 ms
```
So far, cloud flavor kernels have not been affected by the issue.
However, our concern is that after the kernel, which includes commit
0bfcb7b71e73, rolls out to the public cloud, it may affect Anbox Cloud
environments deployed on the cloud.
Could you please share the timeline for the release of the 6.8.0-58.60
kernel? According to the discourse post[3], is it targeted for early
May? We need to determine what actions we can take to minimize the
impact on our customers as much as possible.
Thanks!
[1]
https://github.com/tailscale/tailscale/issues/13863#issuecomment-2424752914
[2] https://launchpad.net/ubuntu/+source/linux/6.8.0-58.60
[3] https://discourse.ubuntu.com/t/the-2025-03-17-sru-cycle-started/57903
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2105997/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
