[Bug 1884813] Re: gvfs truncates files in ftp and ftps
** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #488 https://gitlab.gnome.org/GNOME/gvfs/-/issues/488 ** Also affects: gvfs via https://gitlab.gnome.org/GNOME/gvfs/-/issues/488 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884813 Title: gvfs truncates files in ftp and ftps To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1884813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907814] [NEW] This is not an official Ubuntu package. (but it was, yesterday!)
Public bug reported: This is a special case of Bug 559345 somewhere between a question and a request for better/more discoverable error message/documentation. In apport, because thats what people encountering bugs are going to use. In USN, because the one thing worse than no security notices is incorrect advice. In the package changelog, because reverts are confusing enough already. Proposed fix, among others: Add two URLs to the apport error messages. One to the relevant "https://changelogs.ubuntu.com/"; site which apt should still know, package in Relaase or not, which hopefully by then includes a note about a package rebuild to clarify the revert. And another one to any relevant "https://ubuntu.com/security/notices/?details=package"; site, if you are able to keep the search URL stable long enough for that to reliably present a list of related USNs. Background: `ubuntu-bug linux` will not let me report the kernel regression I ran into.. because the package went AWOL (linux-image-5.8.0-31-generic, linux-image-5.4.0-56-generic, .. as announced from https://ubuntu.com/security/notices/USN-4658-1) Since I might now have two tentatively non-reproducible versions, one reproducible in between and presumably one upcoming that re-introduces the potentially responsible security backports, bisecting will be much easier with some knowledge of the order of backports applied. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907814 Title: This is not an official Ubuntu package. (but it was, yesterday!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1907814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907761 Title: vanishing kernel 5.4.0-56-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1907761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907761 Title: vanishing kernel 5.4.0-56-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1907761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907814] Re: This is not an official Ubuntu package. (but it was, yesterday!)
** Description changed: This is a special case of Bug 559345 somewhere between a question and a request for better/more discoverable error message/documentation. In apport, because thats what people encountering bugs are going to use. In USN, because the one thing worse than no security notices is incorrect advice. In the package changelog, because reverts are confusing enough already. Proposed fix, among others: Add two URLs to the apport error messages. One to the relevant "https://changelogs.ubuntu.com/"; site which apt should still know, package in Relaase or not, which hopefully by then includes a note about a package rebuild to clarify the revert. And another one to any relevant "https://ubuntu.com/security/notices/?details=package"; site, if you are able to keep the search URL stable long enough for that to reliably present a list of related USNs. - Background: `ubuntu-bug linux` will not let me report the kernel regression I ran into.. because the package went AWOL (linux-image-5.8.0-31-generic, linux-image-5.4.0-56-generic, .. as announced from https://ubuntu.com/security/notices/USN-4658-1) + Background: `ubuntu-bug linux` will not let me report the kernel regression I ran into.. because the package went AWOL (linux-image-5.8.0-31-generic, linux-image-5.4.0-56-generic, .. see Bug 1907761) Since I might now have two tentatively non-reproducible versions, one reproducible in between and presumably one upcoming that re-introduces the potentially responsible security backports, bisecting will be much easier with some knowledge of the order of backports applied. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907814 Title: This is not an official Ubuntu package. (but it was, yesterday!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1907814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907761 Title: vanishing kernel 5.4.0-56-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1907761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
[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
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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', '/
[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
[Bug 1908423] Re: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive
The workaround of using "performance" cpufreq governor only appears fully effective if applied from system boot. On 5.4 kernels I can just disable the ondemand.service to keep performance governor active. On 5.8 kernels I would need to switch back from an apparently changed default. The kernel cmdline param cpufreq.default_governor is not available until 5.9. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908423 Title: 5.4.0-58-generic: Raspberry Pi 3 arm64 occasionally unresponsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1908423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975545] [NEW] firefox on xwayland unusable after gnome autostart
Public bug reported: Early starts of firefox on gnome on wayland on Ubuntu 20.04.4 are unusable. Early meaning directly after session start from gdm. If I put firefox.desktop into ~/.config/autostart/, firefox will start as expected, successfully load my homepage (as evidenced in server logs), but fail to display windows decoration or contents or react on input. The space occupied by the window will be either black, matching last shown pixels in the place (background, other windows) or alternate between such with varying flicker frequency. For avoidance of ambiguity, the mode affected by the bug is windowProtocol=xwayland (as in about:support) The bug can be worked around, either method is sufficient on its own: a) forcing windowProtocol=wayland through environment MOZ_ENABLE_WAYLAND=1 b) starting firefox later, through a prepended sleep 10 call Mostly for documenting the workarounds, I understand that this might not be worth fixing as firefox snap approaches similar quality, see also #1970884 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: wayland -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975545 Title: firefox on xwayland unusable after gnome autostart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1975545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2017447] Re: chromium installs cupsd snap
Reproducible, plausibly dangerous, and not mentioned in the "install" section of the man page. Sure, if one knows that canonical-published snaps can trigger installation of 3rd-party-published snaps despite specifically disabling the system-wide "APT::Install-Recommends" setting, one can act accordingly. But how would users even learn that snap, when solely instructed to install a non-privileged browser, also decides to enable a privileged network daemon? One that certainly has a high risk of exposing additional RCE bugs, the threat level of which in the snap scenario is however not obvious from documentation like https://ubuntu.com/security/cves?q=&package=cups -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2017447 Title: chromium installs cupsd snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2017447/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077416 Title: error in audit_log_object_context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077416 Title: error in audit_log_object_context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2021956] Re: crash cups-proxyd
From 22.04, no printers (LP: #2017447): 2024-06-12 16:15:04.871 kernel cups-proxyd[1716]: segfault at 18 ip 5ab34f1b1d75 sp 7fff18534040 error 4 in cups-proxyd[5ab34f1ae000+7000] likely on CPU 1 (core 1, socket 0) 2024-06-12 16:15:04.871+02 kernel Code: 83 3d ee b2 00 00 00 41 54 55 48 89 fd 53 0f 85 f4 00 00 00 48 8d 1d 69 3d 00 00 48 63 45 1c 48 89 df 48 c1 e0 05 48 03 45 08 <48> 8b 50 18 8b 70 14 e8 0f d0 ff ff 44 8b 65 18 48 89 c7 45 85 e4 2024-06-12 16:15:40.830 snap.cups.cupsd.service cups.cupsd[3630]: ==> Shutting down cups-browsed first 2024-06-12 16:15:40.830 snap.cups.cupsd.service cups.cupsd[3659]: /snap/cups/1047/scripts/stop-cupsd: 15: /snap/cups/1047/stop-cups-browsed: not found 2024-06-12 16:15:40.833 init.scope systemd[1]: snap.cups.cupsd.service: Control process exited, code=exited, status=127/n/a 2024-06-12 16:15:40.899 init.scope systemd[1]: snap.cups.cupsd.service: Failed with result 'exit-code'. 2024-06-12 16:15:41.000 init.scope systemd[1]: snap.cups.cups-browsed.service: Main process exited, code=exited, status=143/n/a 2024-06-12 16:15:41.013 init.scope systemd[1]: snap.cups.cups-browsed.service: Failed with result 'exit-code'. 2024-06-12 16:15:53.858 kernel cups-proxyd[4275]: segfault at 18 ip 562d38300d75 sp 7ffe3755adc0 error 4 in cups-proxyd[562d382fd000+7000] likely on CPU 0 (core 0, socket 0) 2024-06-12 16:15:53.859 kernel Code: 83 3d ee b2 00 00 00 41 54 55 48 89 fd 53 0f 85 f4 00 00 00 48 8d 1d 69 3d 00 00 48 63 45 1c 48 89 df 48 c1 e0 05 48 03 45 08 <48> 8b 50 18 8b 70 14 e8 0f d0 ff ff 44 8b 65 18 48 89 c7 45 85 e4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2021956 Title: crash cups-proxyd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2021956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2039747 Title: snd_intel_dsp_driver_probe page fault on linux 6.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2039747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2077416 Title: error in audit_log_object_context To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2091304] [NEW] depends: libblockdev-crypto3 means fwupd library requirements pull in bunch of autorun services
Public bug reported: Could the requirements please be split in a more precise way between shared libraries (essentially free, save for libsystemd0 bonus features) and stuff running (not free)? After udisks2 > libblockdev-crypto3 > libvolume-key1 > gnupg > gpg- agent+dirmngr is a Required chain (LP: #1757321) and fwupd refuses to work with the ESP location without consulting udisks2 (https://github.com/fwupd/fwupd/issues/6911) the less than ideal result is that installing functional fwupd pollutes user sessions (dirmngr.service gpg-agent.service gpg-agent.socket gpg-agent-ssh.socket gpg-agent-extra.socket gpg-agent-browser.socket) even though none of that is needed. ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2091304 Title: depends: libblockdev-crypto3 means fwupd library requirements pull in bunch of autorun services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2091304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
