[Bug 2146517] Re: ov08x40 module mounted upside down on a certain DELL platforms

This bug is awaiting verification that the linux-oem-6.17/6.17.0-1019.19 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-oem-6.17' to 'verification-done- noble-linux-oem-6.17'. If the problem still exists, change the tag 'verification-needed-noble-linux-oem-6.17' to 'verification-failed- noble-linux-oem-6.17'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-oem-6.17-v2 verification-needed-noble-linux-oem-6.17 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2146517 Title: ov08x40 module mounted upside down on a certain DELL platforms Status in ipu6-drivers package in Ubuntu: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-6.17 package in Ubuntu: Invalid Status in ipu6-drivers source package in Noble: Won't Fix Status in linux source package in Noble: Won't Fix Status in linux-oem-6.17 source package in Noble: Fix Committed Status in ipu6-drivers source package in Questing: Won't Fix Status in linux source package in Questing: Won't Fix Status in linux-oem-6.17 source package in Questing: Invalid Status in ipu6-drivers source package in Resolute: In Progress Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [SRU Justification] [Impact] Camera streaming gives upside-down image because the hardware module is mounted rotated physically. [Fix] Proposed fix in https://github.com/intel/ipu6-drivers/pull/432, which has been merged into tag 20260327. [Test Plan] 1. Install the kernel from -proposed pocket along with linux-modules-{ipu6,ipu7,usbio,vision}-<variant> meta packages. 2. Start camera streaming and check if it's still upside-down. [Where problems could occur] We had switched to in-tree ov08x40 in bug 2137700, but in order not to patch in-tree camera sensor drivers that may be used in other embedded systems, the core driver fix is landed back in the dkms instead. This follows we may suffer from the lack of upstream updates from now on. [Other Info] This is only mandatory for OEM platforms that shipped with an inverted module running linux-oem-6.17 and on. Nominate for ipu6-drivers/resolute, which is taken to be built along with linux- oem-6.17/noble. ========== original bug report ========== Proposed fix in https://github.com/intel/ipu6-drivers/pull/432/, which requires updates in the dkms and in the in-tree kernel ipu-bridge driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2146517/+subscriptions

[Bug 2148595] Re: resolute-amd64-uefi 7.0.0-14-generic gfs2 oopses

Launchpad has imported 6 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=221374. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2026-04-16T17:09:50+00:00 colin.i.king wrote: Null ptr deference in: RIP: 0010:gfs2_trans_add_revoke+0x2b/0x50 [gfs2] How to reproduce: Using Ubuntu resolute with Linux 7.0 (Linux resolute-amd64-uefi 7.0.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Mon Apr 13 11:09:53 UTC 2026 x86_64 GNU/Linux) Using an AMD64 QEMU VM, 8GB RAM, 24 CPUs on a 10GB virtual disk with 1 partition: sudo apt install gfs2-utils sudo mkfs.gfs2 /dev/vdb1 -p lock_nolock sudo mount /dev/vdb1 /mnt sudo mkdir /mnt/test sudo chmod 777 /mnt/test/ and then with the current version of stress-ng: git clone https://github.com/ColinIanKing/stress-ng cd stress-ng make clean make -j $(nproc) cd stress-ng ./stress-ng --temp-path /mnt/test --chattr 8 -t 30 in another console wait 30 seconds, type dmesg and you see the following kernel splat: [ 70.910532] gfs2: GFS2 installed [ 70.911169] gfs2: fsid=vdb1: Trying to join cluster "lock_nolock", "vdb1" [ 70.911172] gfs2: fsid=vdb1: Now mounting FS (format 1802)... [ 70.912437] gfs2: fsid=vdb1.0: journal 0 mapped with 1 extents in 0ms [ 70.912533] gfs2: fsid=vdb1.0: jid=0, already locked for use [ 70.912535] gfs2: fsid=vdb1.0: jid=0: Looking at journal... [ 70.925816] gfs2: fsid=vdb1.0: jid=0: Journal head lookup took 13ms [ 70.925839] gfs2: fsid=vdb1.0: jid=0: Done [ 70.925848] gfs2: fsid=vdb1.0: first mount done, others may mount [ 129.723242] BUG: kernel NULL pointer dereference, address: 0000000000000018 [ 129.723262] #PF: supervisor write access in kernel mode [ 129.723268] #PF: error_code(0x0002) - not-present page [ 129.723275] PGD 0 P4D 0 [ 129.723280] Oops: Oops: 0002 [#1] SMP NOPTI [ 129.723287] CPU: 6 UID: 1000 PID: 1996 Comm: stress-ng-chatt Not tainted 7.0.0-14-generic #14-Ubuntu PREEMPT(lazy) [ 129.723298] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 2025.02-8+deb13u1 11/08/2025 [ 129.723307] RIP: 0010:gfs2_trans_add_revoke+0x2b/0x50 [gfs2] [ 129.723336] Code: 1f 44 00 00 48 8b 56 18 48 8d 46 18 48 39 c2 75 34 55 65 48 8b 05 6d 81 2e e0 48 89 e5 53 48 8b 98 70 0e 00 00 e8 c5 e6 fd ff <f0> 80 4b 18 02 83 43 30 01 48 8b 5d f8 c9 31 c0 31 d2 31 f6 31 ff [ 129.723352] RSP: 0018:ffffcd7c015e3800 EFLAGS: 00010246 [ 129.723358] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 [ 129.723365] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 [ 129.723372] RBP: ffffcd7c015e3808 R08: 0000000000000000 R09: 0000000000000000 [ 129.723378] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 [ 129.723385] R13: ffff8d5789156d00 R14: fffff5e7c496cc00 R15: 0000000000000000 [ 129.723392] FS: 00007f7f188bab00(0000) GS:ffff8d585af00000(0000) knlGS:0000000000000000 [ 129.723399] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 129.723405] CR2: 0000000000000018 CR3: 0000000107b58001 CR4: 0000000000772ef0 [ 129.723414] PKRU: 55555554 [ 129.723418] Call Trace: [ 129.723422] <TASK> [ 129.723428] gfs2_remove_from_journal+0x6b/0x210 [gfs2] [ 129.723448] ? _raw_spin_unlock+0xe/0x40 [ 129.723473] gfs2_invalidate_folio+0x103/0x240 [gfs2] [ 129.723491] truncate_cleanup_folio+0xb3/0xe0 [ 129.723498] truncate_inode_pages_range+0x13c/0x560 [ 129.723506] truncate_inode_pages+0x15/0x30 [ 129.723511] do_gfs2_set_flags+0x13d/0x240 [gfs2] [ 129.723529] ? gfs2_holder_uninit+0x1f/0x40 [gfs2] [ 129.723546] ? gfs2_fileattr_set+0xb4/0x200 [gfs2] [ 129.723564] gfs2_fileattr_set+0xb4/0x200 [gfs2] [ 129.723581] ? fileattr_set_prepare+0x47/0x170 [ 129.723587] ? vfs_fileattr_get+0x4b/0x70 [ 129.723593] vfs_fileattr_set+0x101/0x1e0 [ 129.723599] ioctl_setflags+0xa6/0xc0 [ 129.723603] do_vfs_ioctl+0x21a/0x860 [ 129.723609] ? hook_file_ioctl+0x10/0x20 [ 129.723615] __x64_sys_ioctl+0x81/0x100 [ 129.723621] x64_sys_call+0x103b/0x2390 [ 129.723627] do_syscall_64+0x115/0x5a0 [ 129.723634] ? ksys_write+0x71/0xf0 [ 129.723640] ? arch_exit_to_user_mode_prepare.isra.0+0xc5/0xe0 [ 129.723647] ? do_syscall_64+0x150/0x5a0 [ 129.723653] ? __x64_sys_ioctl+0x81/0x100 [ 129.723658] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 [ 129.723664] ? do_syscall_64+0x150/0x5a0 [ 129.723826] ? do_syscall_64+0x150/0x5a0 [ 129.723984] ? arch_exit_to_user_mode_prepare.isra.0+0xc5/0xe0 [ 129.724134] ? do_syscall_64+0x150/0x5a0 [ 129.724280] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 129.724424] RIP: 0033:0x7f7f18332cbd [ 129.724567] Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00 [ 129.724880] RSP: 002b:00007fff9a20be10 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 129.725038] RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f7f18332cbd [ 129.725193] RDX: 00007fff9a20bea8 RSI: 0000000040086602 RDI: 0000000000000004 [ 129.725346] RBP: 00007fff9a20be60 R08: 0000000000000000 R09: 0000000000000000 [ 129.725492] R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff9a20c020 [ 129.725642] R13: 0000000000000004 R14: 00000000208bc0ff R15: 00007f7f1844e3c8 [ 129.725800] </TASK> Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148595/comments/1 ------------------------------------------------------------------------ On 2026-04-16T21:58:19+00:00 colin.i.king wrote: Also reported at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148595 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148595/comments/4 ------------------------------------------------------------------------ On 2026-04-16T21:59:43+00:00 colin.i.king wrote: This is not a regression for 7.0, it also occurs with the ubuntu questing 6.17.0-9-generic kernel too Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148595/comments/5 ------------------------------------------------------------------------ On 2026-04-17T11:12:26+00:00 andyp wrote: It looks like the null pointer deref was fixed in commit f4e4c4e6acdc20a9065064dd164db52e2e0d44ad "gfs2: fix address space truncation during withdraw" which was merged in the current merge window, but I'm still getting a hang with this test so that will need looking at. Thanks. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148595/comments/6 ------------------------------------------------------------------------ On 2026-04-17T12:56:40+00:00 andyp wrote: Created attachment 309884 Hang logs Attaching the logs from testing the master branch at 43cfbdda5af60ffc6272a7b8c5c37d1d0a181ca9 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148595/comments/7 ------------------------------------------------------------------------ On 2026-04-17T13:26:00+00:00 agruenba wrote: This is with chattr +j files (data journaling). We are looking at a number of data journaling related bugs at the moment. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148595/comments/8 ** Changed in: linux Status: Unknown => In Progress ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148595 Title: resolute-amd64-uefi 7.0.0-14-generic gfs2 oopses Status in Linux: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: How to reproduce: Using an AMD64 QEMU VM, 8GB RAM, 24 CPUs on a 10GB virtual disk with 1 partition: sudo apt install gfs2-utils sudo mkfs.gfs2 /dev/vdb1 -p lock_nolock sudo mount /dev/vdb1 /mnt sudo mkdir /mnt/test sudo chmod 777 /mnt/test/ and then with the current version of stress-ng: git clone https://github.com/ColinIanKing/stress-ng cd stress-ng make clean make -j $(nproc) ./stress-ng --temp-path /mnt/test --chattr 8 -t 30 in another console wait 30 seconds, type dmesg and you see the following kernel splat: [ 70.910532] gfs2: GFS2 installed [ 70.911169] gfs2: fsid=vdb1: Trying to join cluster "lock_nolock", "vdb1" [ 70.911172] gfs2: fsid=vdb1: Now mounting FS (format 1802)... [ 70.912437] gfs2: fsid=vdb1.0: journal 0 mapped with 1 extents in 0ms [ 70.912533] gfs2: fsid=vdb1.0: jid=0, already locked for use [ 70.912535] gfs2: fsid=vdb1.0: jid=0: Looking at journal... [ 70.925816] gfs2: fsid=vdb1.0: jid=0: Journal head lookup took 13ms [ 70.925839] gfs2: fsid=vdb1.0: jid=0: Done [ 70.925848] gfs2: fsid=vdb1.0: first mount done, others may mount [ 129.723242] BUG: kernel NULL pointer dereference, address: 0000000000000018 [ 129.723262] #PF: supervisor write access in kernel mode [ 129.723268] #PF: error_code(0x0002) - not-present page [ 129.723275] PGD 0 P4D 0 [ 129.723280] Oops: Oops: 0002 [#1] SMP NOPTI [ 129.723287] CPU: 6 UID: 1000 PID: 1996 Comm: stress-ng-chatt Not tainted 7.0.0-14-generic #14-Ubuntu PREEMPT(lazy) [ 129.723298] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 2025.02-8+deb13u1 11/08/2025 [ 129.723307] RIP: 0010:gfs2_trans_add_revoke+0x2b/0x50 [gfs2] [ 129.723336] Code: 1f 44 00 00 48 8b 56 18 48 8d 46 18 48 39 c2 75 34 55 65 48 8b 05 6d 81 2e e0 48 89 e5 53 48 8b 98 70 0e 00 00 e8 c5 e6 fd ff <f0> 80 4b 18 02 83 43 30 01 48 8b 5d f8 c9 31 c0 31 d2 31 f6 31 ff [ 129.723352] RSP: 0018:ffffcd7c015e3800 EFLAGS: 00010246 [ 129.723358] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 [ 129.723365] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 [ 129.723372] RBP: ffffcd7c015e3808 R08: 0000000000000000 R09: 0000000000000000 [ 129.723378] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000 [ 129.723385] R13: ffff8d5789156d00 R14: fffff5e7c496cc00 R15: 0000000000000000 [ 129.723392] FS: 00007f7f188bab00(0000) GS:ffff8d585af00000(0000) knlGS:0000000000000000 [ 129.723399] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 129.723405] CR2: 0000000000000018 CR3: 0000000107b58001 CR4: 0000000000772ef0 [ 129.723414] PKRU: 55555554 [ 129.723418] Call Trace: [ 129.723422] <TASK> [ 129.723428] gfs2_remove_from_journal+0x6b/0x210 [gfs2] [ 129.723448] ? _raw_spin_unlock+0xe/0x40 [ 129.723473] gfs2_invalidate_folio+0x103/0x240 [gfs2] [ 129.723491] truncate_cleanup_folio+0xb3/0xe0 [ 129.723498] truncate_inode_pages_range+0x13c/0x560 [ 129.723506] truncate_inode_pages+0x15/0x30 [ 129.723511] do_gfs2_set_flags+0x13d/0x240 [gfs2] [ 129.723529] ? gfs2_holder_uninit+0x1f/0x40 [gfs2] [ 129.723546] ? gfs2_fileattr_set+0xb4/0x200 [gfs2] [ 129.723564] gfs2_fileattr_set+0xb4/0x200 [gfs2] [ 129.723581] ? fileattr_set_prepare+0x47/0x170 [ 129.723587] ? vfs_fileattr_get+0x4b/0x70 [ 129.723593] vfs_fileattr_set+0x101/0x1e0 [ 129.723599] ioctl_setflags+0xa6/0xc0 [ 129.723603] do_vfs_ioctl+0x21a/0x860 [ 129.723609] ? hook_file_ioctl+0x10/0x20 [ 129.723615] __x64_sys_ioctl+0x81/0x100 [ 129.723621] x64_sys_call+0x103b/0x2390 [ 129.723627] do_syscall_64+0x115/0x5a0 [ 129.723634] ? ksys_write+0x71/0xf0 [ 129.723640] ? arch_exit_to_user_mode_prepare.isra.0+0xc5/0xe0 [ 129.723647] ? do_syscall_64+0x150/0x5a0 [ 129.723653] ? __x64_sys_ioctl+0x81/0x100 [ 129.723658] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 [ 129.723664] ? do_syscall_64+0x150/0x5a0 [ 129.723826] ? do_syscall_64+0x150/0x5a0 [ 129.723984] ? arch_exit_to_user_mode_prepare.isra.0+0xc5/0xe0 [ 129.724134] ? do_syscall_64+0x150/0x5a0 [ 129.724280] entry_SYSCALL_64_after_hwframe+0x76/0x7e [ 129.724424] RIP: 0033:0x7f7f18332cbd [ 129.724567] Code: 04 25 28 00 00 00 48 89 45 c8 31 c0 48 8d 45 10 c7 45 b0 10 00 00 00 48 89 45 b8 48 8d 45 d0 48 89 45 c0 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 1a 48 8b 45 c8 64 48 2b 04 25 28 00 00 00 [ 129.724880] RSP: 002b:00007fff9a20be10 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 [ 129.725038] RAX: ffffffffffffffda RBX: 0000000000000004 RCX: 00007f7f18332cbd [ 129.725193] RDX: 00007fff9a20bea8 RSI: 0000000040086602 RDI: 0000000000000004 [ 129.725346] RBP: 00007fff9a20be60 R08: 0000000000000000 R09: 0000000000000000 [ 129.725492] R10: 0000000000000000 R11: 0000000000000246 R12: 00007fff9a20c020 [ 129.725642] R13: 0000000000000004 R14: 00000000208bc0ff R15: 00007f7f1844e3c8 [ 129.725800] </TASK> To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2148595/+subscriptions

[Bug 2148718] [NEW] intel-ipu7 / intel-ipu7-isys modules are shipped unsigned in latest Resolute kernels, breaking Secure Boot systems

You have been subscribed to a public bug: Affects: Ubuntu 26.04 (Resolute Raccoon) --- Description: On kernel 7.0.0-13 and 7.0.0-14, the webcam stopped working on my XPS 13 9350 Lunar Lake laptop (sensor: OV02C10) with Secure Boot enabled. The intel-ipu7 and intel-ipu7-isys modules are shipped unsigned, so the kernel refuses to load them under Secure Boot. --- Expected: Staging modules are signed by the Ubuntu kernel build and should load successfully with Secure Boot enabled. Actual: Webcam is non-functional on Secure Boot systems unless modules are manually MOK-signed. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-bug resolute -- intel-ipu7 / intel-ipu7-isys modules are shipped unsigned in latest Resolute kernels, breaking Secure Boot systems https://bugs.launchpad.net/bugs/2148718 You received this bug notification because you are subscribed to linux in Ubuntu.

[Bug 2148089] ProcCpuinfo.txt

apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2148089/+attachment/5962141/+files/ProcCpuinfo.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148089 Title: MediaTek MT7925 Bluetooth (0489:e111) not auto-bound by btusb on kernel 6.17 Status in linux package in Ubuntu: Incomplete Bug description: Distribution: Linux Mint 22.3 (based on Ubuntu 24.04 Noble) Kernel: 6.17.0-20-generic Hardware: MediaTek MT7925 Bluetooth (USB ID 0489:e111, Foxconn) Issue: Bluetooth device is detected in lsusb but is not automatically bound by the btusb driver. Symptoms: - bluetoothctl list may be empty OR controller shows Powered: no - Bluetooth does not turn on automatically - Manual intervention required after every boot Workaround: echo "0489 e111" > /sys/bus/usb/drivers/btusb/new_id Persistent workaround: udev rule to bind device and power on Bluetooth Expected: Device should be automatically recognized and bound by btusb without manual steps. This appears to be a missing device ID in the btusb driver for USB ID 0489:e111. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 22.3 InstallationDate: Installed on 2026-03-29 (19 days ago) InstallationMedia: Linux Mint 22.3 "Zena" - Release amd64 20260108 MachineType: LENOVO 83NX Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-20-generic root=UUID=7e7b4a7a-6660-4846-8578-967140758e52 ro quiet splash ProcVersionSignature: Ubuntu 6.17.0-20.20~24.04.1-generic 6.17.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.17.0-20-generic N/A linux-backports-modules-6.17.0-20-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.26 Tags: zena Uname: Linux 6.17.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/04/2025 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: Q6CN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 5 16IAX10 dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnLENOVO:bvrQ6CN31WW:bd11/04/2025:br1.31:efr1.30:svnLENOVO:pn83NX:pvrLegion516IAX10:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion516IAX10:skuLENOVO_MT_83NX_BU_idea_FM_Legion516IAX10: dmi.product.family: Legion 5 16IAX10 dmi.product.name: 83NX dmi.product.sku: LENOVO_MT_83NX_BU_idea_FM_Legion 5 16IAX10 dmi.product.version: Legion 5 16IAX10 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 22.3 InstallationDate: Installed on 2026-03-29 (19 days ago) InstallationMedia: Linux Mint 22.3 "Zena" - Release amd64 20260108 MachineType: LENOVO 83NX Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 LANGUAGE=en_US PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-20-generic root=UUID=7e7b4a7a-6660-4846-8578-967140758e52 ro quiet splash ProcVersionSignature: Ubuntu 6.17.0-20.20~24.04.1-generic 6.17.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.17.0-20-generic N/A linux-backports-modules-6.17.0-20-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.26 Tags: zena Uname: Linux 6.17.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/04/2025 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: Q6CN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 5 16IAX10 dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnLENOVO:bvrQ6CN31WW:bd11/04/2025:br1.31:efr1.30:svnLENOVO:pn83NX:pvrLegion516IAX10:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegion516IAX10:skuLENOVO_MT_83NX_BU_idea_FM_Legion516IAX10: dmi.product.family: Legion 5 16IAX10 dmi.product.name: 83NX dmi.product.sku: LENOVO_MT_83NX_BU_idea_FM_Legion 5 16IAX10 dmi.product.version: Legion 5 16IAX10 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148089/+subscriptions

[Bug 2148662] [NEW] firewire fw_device_workfn [firewire_core]

Public bug reported: [ 247.143126] INFO: task kworker/0:0:9 blocked for more than 122 seconds. [ 247.143145] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 247.143149] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 247.143153] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 247.143163] Workqueue: firewire fw_device_workfn [firewire_core] [ 247.143210] Call Trace: [ 247.143215] <TASK> [ 247.143220] __schedule+0x2ed/0x7c0 [ 247.143233] schedule+0x27/0x90 [ 247.143239] schedule_timeout+0xcf/0x110 [ 247.143247] wait_for_completion+0x82/0x160 [ 247.143253] fw_run_transaction+0xed/0x130 [firewire_core] [ 247.143288] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 247.143322] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 247.143355] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 247.143388] read_rom+0x64/0xb0 [firewire_core] [ 247.143421] read_config_rom+0x9f/0x440 [firewire_core] [ 247.143454] ? psi_task_switch+0x17e/0x390 [ 247.143462] fw_device_init+0x48/0x470 [firewire_core] [ 247.143495] fw_device_workfn+0x12/0x20 [firewire_core] [ 247.143527] process_one_work+0x18e/0x370 [ 247.143535] worker_thread+0x317/0x450 [ 247.143541] ? __pfx_worker_thread+0x10/0x10 [ 247.143547] kthread+0x10b/0x220 [ 247.143552] ? __pfx_kthread+0x10/0x10 [ 247.143557] ret_from_fork+0x134/0x150 [ 247.143562] ? __pfx_kthread+0x10/0x10 [ 247.143567] ret_from_fork_asm+0x1a/0x30 [ 247.143575] </TASK> [ 370.022713] INFO: task kworker/0:0:9 blocked for more than 245 seconds. [ 370.022733] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 370.022738] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 370.022741] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 370.022751] Workqueue: firewire fw_device_workfn [firewire_core] [ 370.022798] Call Trace: [ 370.022802] <TASK> [ 370.022807] __schedule+0x2ed/0x7c0 [ 370.022819] schedule+0x27/0x90 [ 370.022826] schedule_timeout+0xcf/0x110 [ 370.022833] wait_for_completion+0x82/0x160 [ 370.022839] fw_run_transaction+0xed/0x130 [firewire_core] [ 370.022874] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 370.022908] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 370.022941] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 370.022975] read_rom+0x64/0xb0 [firewire_core] [ 370.023008] read_config_rom+0x9f/0x440 [firewire_core] [ 370.023041] ? psi_task_switch+0x17e/0x390 [ 370.023049] fw_device_init+0x48/0x470 [firewire_core] [ 370.023082] fw_device_workfn+0x12/0x20 [firewire_core] [ 370.023114] process_one_work+0x18e/0x370 [ 370.023122] worker_thread+0x317/0x450 [ 370.023128] ? __pfx_worker_thread+0x10/0x10 [ 370.023134] kthread+0x10b/0x220 [ 370.023139] ? __pfx_kthread+0x10/0x10 [ 370.023144] ret_from_fork+0x134/0x150 [ 370.023149] ? __pfx_kthread+0x10/0x10 [ 370.023154] ret_from_fork_asm+0x1a/0x30 [ 370.023161] </TASK> [ 465.208692] perf: interrupt took too long (2518 > 2500), lowering kernel.perf_event_max_sample_rate to 79000 [ 492.900268] INFO: task kworker/0:0:9 blocked for more than 368 seconds. [ 492.900287] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 492.900292] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 492.900296] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 492.900306] Workqueue: firewire fw_device_workfn [firewire_core] [ 492.900354] Call Trace: [ 492.900358] <TASK> [ 492.900364] __schedule+0x2ed/0x7c0 [ 492.900377] schedule+0x27/0x90 [ 492.900383] schedule_timeout+0xcf/0x110 [ 492.900391] wait_for_completion+0x82/0x160 [ 492.900397] fw_run_transaction+0xed/0x130 [firewire_core] [ 492.900432] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 492.900466] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 492.900499] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 492.900533] read_rom+0x64/0xb0 [firewire_core] [ 492.900566] read_config_rom+0x9f/0x440 [firewire_core] [ 492.900599] ? psi_task_switch+0x17e/0x390 [ 492.900607] fw_device_init+0x48/0x470 [firewire_core] [ 492.900641] fw_device_workfn+0x12/0x20 [firewire_core] [ 492.900673] process_one_work+0x18e/0x370 [ 492.900681] worker_thread+0x317/0x450 [ 492.900688] ? __pfx_worker_thread+0x10/0x10 [ 492.900694] kthread+0x10b/0x220 [ 492.900699] ? __pfx_kthread+0x10/0x10 [ 492.900704] ret_from_fork+0x134/0x150 [ 492.900709] ? __pfx_kthread+0x10/0x10 [ 492.900714] ret_from_fork_asm+0x1a/0x30 [ 492.900722] </TASK> [ 615.779806] INFO: task kworker/0:0:9 blocked for more than 491 seconds. [ 615.779837] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 615.779841] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 615.779844] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 615.779853] Workqueue: firewire fw_device_workfn [firewire_core] [ 615.779937] Call Trace: [ 615.779942] <TASK> [ 615.779949] __schedule+0x2ed/0x7c0 [ 615.779964] schedule+0x27/0x90 [ 615.779968] schedule_timeout+0xcf/0x110 [ 615.779975] wait_for_completion+0x82/0x160 [ 615.779979] fw_run_transaction+0xed/0x130 [firewire_core] [ 615.780004] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 615.780028] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 615.780051] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 615.780074] read_rom+0x64/0xb0 [firewire_core] [ 615.780097] read_config_rom+0x9f/0x440 [firewire_core] [ 615.780120] ? psi_task_switch+0x17e/0x390 [ 615.780127] fw_device_init+0x48/0x470 [firewire_core] [ 615.780151] fw_device_workfn+0x12/0x20 [firewire_core] [ 615.780173] process_one_work+0x18e/0x370 [ 615.780181] worker_thread+0x317/0x450 [ 615.780185] ? __pfx_worker_thread+0x10/0x10 [ 615.780189] kthread+0x10b/0x220 [ 615.780194] ? __pfx_kthread+0x10/0x10 [ 615.780198] ret_from_fork+0x134/0x150 [ 615.780202] ? __pfx_kthread+0x10/0x10 [ 615.780205] ret_from_fork_asm+0x1a/0x30 [ 615.780213] </TASK> [ 738.657061] INFO: task kworker/0:0:9 blocked for more than 614 seconds. [ 738.657079] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 738.657084] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 738.657087] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 738.657097] Workqueue: firewire fw_device_workfn [firewire_core] [ 738.657142] Call Trace: [ 738.657146] <TASK> [ 738.657151] __schedule+0x2ed/0x7c0 [ 738.657163] schedule+0x27/0x90 [ 738.657170] schedule_timeout+0xcf/0x110 [ 738.657177] wait_for_completion+0x82/0x160 [ 738.657183] fw_run_transaction+0xed/0x130 [firewire_core] [ 738.657218] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 738.657252] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 738.657285] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 738.657318] read_rom+0x64/0xb0 [firewire_core] [ 738.657351] read_config_rom+0x9f/0x440 [firewire_core] [ 738.657383] ? psi_task_switch+0x17e/0x390 [ 738.657391] fw_device_init+0x48/0x470 [firewire_core] [ 738.657425] fw_device_workfn+0x12/0x20 [firewire_core] [ 738.657457] process_one_work+0x18e/0x370 [ 738.657465] worker_thread+0x317/0x450 [ 738.657471] ? __pfx_worker_thread+0x10/0x10 [ 738.657477] kthread+0x10b/0x220 [ 738.657482] ? __pfx_kthread+0x10/0x10 [ 738.657487] ret_from_fork+0x134/0x150 [ 738.657492] ? __pfx_kthread+0x10/0x10 [ 738.657497] ret_from_fork_asm+0x1a/0x30 [ 738.657504] </TASK> [ 845.725853] perf: interrupt took too long (3153 > 3147), lowering kernel.perf_event_max_sample_rate to 63000 [ 861.535406] INFO: task kworker/0:0:9 blocked for more than 737 seconds. [ 861.535425] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 861.535430] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 861.535434] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 861.535443] Workqueue: firewire fw_device_workfn [firewire_core] [ 861.535490] Call Trace: [ 861.535494] <TASK> [ 861.535499] __schedule+0x2ed/0x7c0 [ 861.535511] schedule+0x27/0x90 [ 861.535518] schedule_timeout+0xcf/0x110 [ 861.535525] wait_for_completion+0x82/0x160 [ 861.535531] fw_run_transaction+0xed/0x130 [firewire_core] [ 861.535566] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 861.535599] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 861.535632] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 861.535665] read_rom+0x64/0xb0 [firewire_core] [ 861.535699] read_config_rom+0x9f/0x440 [firewire_core] [ 861.535731] ? psi_task_switch+0x17e/0x390 [ 861.535739] fw_device_init+0x48/0x470 [firewire_core] [ 861.535773] fw_device_workfn+0x12/0x20 [firewire_core] [ 861.535805] process_one_work+0x18e/0x370 [ 861.535812] worker_thread+0x317/0x450 [ 861.535818] ? __pfx_worker_thread+0x10/0x10 [ 861.535824] kthread+0x10b/0x220 [ 861.535830] ? __pfx_kthread+0x10/0x10 [ 861.535835] ret_from_fork+0x134/0x150 [ 861.535839] ? __pfx_kthread+0x10/0x10 [ 861.535844] ret_from_fork_asm+0x1a/0x30 [ 861.535852] </TASK> [ 984.413795] INFO: task kworker/0:0:9 blocked for more than 860 seconds. [ 984.413813] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 984.413817] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 984.413821] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 984.413830] Workqueue: firewire fw_device_workfn [firewire_core] [ 984.413879] Call Trace: [ 984.413883] <TASK> [ 984.413889] __schedule+0x2ed/0x7c0 [ 984.413901] schedule+0x27/0x90 [ 984.413907] schedule_timeout+0xcf/0x110 [ 984.413915] wait_for_completion+0x82/0x160 [ 984.413921] fw_run_transaction+0xed/0x130 [firewire_core] [ 984.413956] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 984.413989] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 984.414022] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 984.414055] read_rom+0x64/0xb0 [firewire_core] [ 984.414089] read_config_rom+0x9f/0x440 [firewire_core] [ 984.414127] ? psi_task_switch+0x17e/0x390 [ 984.414135] fw_device_init+0x48/0x470 [firewire_core] [ 984.414169] fw_device_workfn+0x12/0x20 [firewire_core] [ 984.414202] process_one_work+0x18e/0x370 [ 984.414210] worker_thread+0x317/0x450 [ 984.414216] ? __pfx_worker_thread+0x10/0x10 [ 984.414222] kthread+0x10b/0x220 [ 984.414228] ? __pfx_kthread+0x10/0x10 [ 984.414233] ret_from_fork+0x134/0x150 [ 984.414237] ? __pfx_kthread+0x10/0x10 [ 984.414242] ret_from_fork_asm+0x1a/0x30 [ 984.414250] </TASK> [ 1107.292039] INFO: task kworker/0:0:9 blocked for more than 983 seconds. [ 1107.292055] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 1107.292058] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1107.292061] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 1107.292068] Workqueue: firewire fw_device_workfn [firewire_core] [ 1107.292107] Call Trace: [ 1107.292110] <TASK> [ 1107.292114] __schedule+0x2ed/0x7c0 [ 1107.292123] schedule+0x27/0x90 [ 1107.292127] schedule_timeout+0xcf/0x110 [ 1107.292132] wait_for_completion+0x82/0x160 [ 1107.292137] fw_run_transaction+0xed/0x130 [firewire_core] [ 1107.292160] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 1107.292183] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 1107.292205] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 1107.292227] read_rom+0x64/0xb0 [firewire_core] [ 1107.292249] read_config_rom+0x9f/0x440 [firewire_core] [ 1107.292271] ? psi_task_switch+0x17e/0x390 [ 1107.292277] fw_device_init+0x48/0x470 [firewire_core] [ 1107.292299] fw_device_workfn+0x12/0x20 [firewire_core] [ 1107.292321] process_one_work+0x18e/0x370 [ 1107.292326] worker_thread+0x317/0x450 [ 1107.292330] ? __pfx_worker_thread+0x10/0x10 [ 1107.292334] kthread+0x10b/0x220 [ 1107.292338] ? __pfx_kthread+0x10/0x10 [ 1107.292342] ret_from_fork+0x134/0x150 [ 1107.292345] ? __pfx_kthread+0x10/0x10 [ 1107.292348] ret_from_fork_asm+0x1a/0x30 [ 1107.292354] </TASK> [ 1230.171464] INFO: task kworker/0:0:9 blocked for more than 1105 seconds. [ 1230.171489] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 1230.171492] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1230.171495] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 1230.171504] Workqueue: firewire fw_device_workfn [firewire_core] [ 1230.171573] Call Trace: [ 1230.171578] <TASK> [ 1230.171584] __schedule+0x2ed/0x7c0 [ 1230.171597] schedule+0x27/0x90 [ 1230.171602] schedule_timeout+0xcf/0x110 [ 1230.171610] wait_for_completion+0x82/0x160 [ 1230.171615] fw_run_transaction+0xed/0x130 [firewire_core] [ 1230.171639] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 1230.171661] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 1230.171684] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 1230.171706] read_rom+0x64/0xb0 [firewire_core] [ 1230.171728] read_config_rom+0x9f/0x440 [firewire_core] [ 1230.171750] ? psi_task_switch+0x17e/0x390 [ 1230.171758] fw_device_init+0x48/0x470 [firewire_core] [ 1230.171781] fw_device_workfn+0x12/0x20 [firewire_core] [ 1230.171802] process_one_work+0x18e/0x370 [ 1230.171809] worker_thread+0x317/0x450 [ 1230.171813] ? __pfx_worker_thread+0x10/0x10 [ 1230.171817] kthread+0x10b/0x220 [ 1230.171822] ? __pfx_kthread+0x10/0x10 [ 1230.171825] ret_from_fork+0x134/0x150 [ 1230.171830] ? __pfx_kthread+0x10/0x10 [ 1230.171833] ret_from_fork_asm+0x1a/0x30 [ 1230.171839] </TASK> [ 1353.048685] INFO: task kworker/0:0:9 blocked for more than 1228 seconds. [ 1353.048702] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 1353.048707] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1353.048710] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 1353.048720] Workqueue: firewire fw_device_workfn [firewire_core] [ 1353.048765] Call Trace: [ 1353.048768] <TASK> [ 1353.048774] __schedule+0x2ed/0x7c0 [ 1353.048786] schedule+0x27/0x90 [ 1353.048792] schedule_timeout+0xcf/0x110 [ 1353.048799] wait_for_completion+0x82/0x160 [ 1353.048805] fw_run_transaction+0xed/0x130 [firewire_core] [ 1353.048840] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 1353.048874] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 1353.048907] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 1353.048940] read_rom+0x64/0xb0 [firewire_core] [ 1353.048973] read_config_rom+0x9f/0x440 [firewire_core] [ 1353.049006] ? psi_task_switch+0x17e/0x390 [ 1353.049014] fw_device_init+0x48/0x470 [firewire_core] [ 1353.049047] fw_device_workfn+0x12/0x20 [firewire_core] [ 1353.049079] process_one_work+0x18e/0x370 [ 1353.049087] worker_thread+0x317/0x450 [ 1353.049093] ? __pfx_worker_thread+0x10/0x10 [ 1353.049099] kthread+0x10b/0x220 [ 1353.049104] ? __pfx_kthread+0x10/0x10 [ 1353.049109] ret_from_fork+0x134/0x150 [ 1353.049114] ? __pfx_kthread+0x10/0x10 [ 1353.049119] ret_from_fork_asm+0x1a/0x30 [ 1353.049126] </TASK> [ 1353.049129] Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings ProblemType: Bug DistroRelease: Ubuntu 25.10 Package: linux-image-6.17.0-20-generic 6.17.0-20.20 ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13 Uname: Linux 6.17.0-20-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: js1 1905 F.... wireplumber /dev/snd/controlC1: js1 1905 F.... wireplumber /dev/snd/seq: js1 1884 F.... pipewire CasperMD5CheckResult: unknown Date: Fri Apr 17 08:30:03 2026 InstallationDate: Installed on 2018-12-10 (2685 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-20-generic root=UUID=591ea17a-5ac6-4e8b-adb3-75a3dab238d5 ro irqpoll cryptdevice=UUID=6416a2a8-8a76-44df-8d5f-9c465982298a:luks-6416a2a8-8a76-44df-8d5f-9c465982298a root=/dev/mapper/luks-6416a2a8-8a76-44df-8d5f-9c465982298a resume=/dev/mapper/luks-6416a2a8-8a76-44df-8d5f-9c465982298a ipv6.disable=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: firmware-sof N/A linux-firmware 20250901.git993ff19b-0ubuntu1.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2007 dmi.bios.release: 0.0 dmi.bios.vendor: Intel Corp. dmi.bios.version: BX97520J.86A.2674.2007.0315.1546 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D975XBX2 dmi.board.vendor: Intel Corporation dmi.board.version: AAD53350-507 dmi.chassis.type: 2 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBX97520J.86A.2674.2007.0315.1546:bd03/15/2007:br0.0:efr0.0:svn:pn:pvr:rvnIntelCorporation:rnD975XBX2:rvrAAD53350-507:cvn:ct2:cvr:sku: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug questing -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148662 Title: firewire fw_device_workfn [firewire_core] Status in linux package in Ubuntu: New Bug description: [ 247.143126] INFO: task kworker/0:0:9 blocked for more than 122 seconds. [ 247.143145] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 247.143149] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 247.143153] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 247.143163] Workqueue: firewire fw_device_workfn [firewire_core] [ 247.143210] Call Trace: [ 247.143215] <TASK> [ 247.143220] __schedule+0x2ed/0x7c0 [ 247.143233] schedule+0x27/0x90 [ 247.143239] schedule_timeout+0xcf/0x110 [ 247.143247] wait_for_completion+0x82/0x160 [ 247.143253] fw_run_transaction+0xed/0x130 [firewire_core] [ 247.143288] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 247.143322] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 247.143355] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 247.143388] read_rom+0x64/0xb0 [firewire_core] [ 247.143421] read_config_rom+0x9f/0x440 [firewire_core] [ 247.143454] ? psi_task_switch+0x17e/0x390 [ 247.143462] fw_device_init+0x48/0x470 [firewire_core] [ 247.143495] fw_device_workfn+0x12/0x20 [firewire_core] [ 247.143527] process_one_work+0x18e/0x370 [ 247.143535] worker_thread+0x317/0x450 [ 247.143541] ? __pfx_worker_thread+0x10/0x10 [ 247.143547] kthread+0x10b/0x220 [ 247.143552] ? __pfx_kthread+0x10/0x10 [ 247.143557] ret_from_fork+0x134/0x150 [ 247.143562] ? __pfx_kthread+0x10/0x10 [ 247.143567] ret_from_fork_asm+0x1a/0x30 [ 247.143575] </TASK> [ 370.022713] INFO: task kworker/0:0:9 blocked for more than 245 seconds. [ 370.022733] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 370.022738] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 370.022741] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 370.022751] Workqueue: firewire fw_device_workfn [firewire_core] [ 370.022798] Call Trace: [ 370.022802] <TASK> [ 370.022807] __schedule+0x2ed/0x7c0 [ 370.022819] schedule+0x27/0x90 [ 370.022826] schedule_timeout+0xcf/0x110 [ 370.022833] wait_for_completion+0x82/0x160 [ 370.022839] fw_run_transaction+0xed/0x130 [firewire_core] [ 370.022874] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 370.022908] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 370.022941] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 370.022975] read_rom+0x64/0xb0 [firewire_core] [ 370.023008] read_config_rom+0x9f/0x440 [firewire_core] [ 370.023041] ? psi_task_switch+0x17e/0x390 [ 370.023049] fw_device_init+0x48/0x470 [firewire_core] [ 370.023082] fw_device_workfn+0x12/0x20 [firewire_core] [ 370.023114] process_one_work+0x18e/0x370 [ 370.023122] worker_thread+0x317/0x450 [ 370.023128] ? __pfx_worker_thread+0x10/0x10 [ 370.023134] kthread+0x10b/0x220 [ 370.023139] ? __pfx_kthread+0x10/0x10 [ 370.023144] ret_from_fork+0x134/0x150 [ 370.023149] ? __pfx_kthread+0x10/0x10 [ 370.023154] ret_from_fork_asm+0x1a/0x30 [ 370.023161] </TASK> [ 465.208692] perf: interrupt took too long (2518 > 2500), lowering kernel.perf_event_max_sample_rate to 79000 [ 492.900268] INFO: task kworker/0:0:9 blocked for more than 368 seconds. [ 492.900287] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 492.900292] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 492.900296] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 492.900306] Workqueue: firewire fw_device_workfn [firewire_core] [ 492.900354] Call Trace: [ 492.900358] <TASK> [ 492.900364] __schedule+0x2ed/0x7c0 [ 492.900377] schedule+0x27/0x90 [ 492.900383] schedule_timeout+0xcf/0x110 [ 492.900391] wait_for_completion+0x82/0x160 [ 492.900397] fw_run_transaction+0xed/0x130 [firewire_core] [ 492.900432] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 492.900466] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 492.900499] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 492.900533] read_rom+0x64/0xb0 [firewire_core] [ 492.900566] read_config_rom+0x9f/0x440 [firewire_core] [ 492.900599] ? psi_task_switch+0x17e/0x390 [ 492.900607] fw_device_init+0x48/0x470 [firewire_core] [ 492.900641] fw_device_workfn+0x12/0x20 [firewire_core] [ 492.900673] process_one_work+0x18e/0x370 [ 492.900681] worker_thread+0x317/0x450 [ 492.900688] ? __pfx_worker_thread+0x10/0x10 [ 492.900694] kthread+0x10b/0x220 [ 492.900699] ? __pfx_kthread+0x10/0x10 [ 492.900704] ret_from_fork+0x134/0x150 [ 492.900709] ? __pfx_kthread+0x10/0x10 [ 492.900714] ret_from_fork_asm+0x1a/0x30 [ 492.900722] </TASK> [ 615.779806] INFO: task kworker/0:0:9 blocked for more than 491 seconds. [ 615.779837] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 615.779841] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 615.779844] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 615.779853] Workqueue: firewire fw_device_workfn [firewire_core] [ 615.779937] Call Trace: [ 615.779942] <TASK> [ 615.779949] __schedule+0x2ed/0x7c0 [ 615.779964] schedule+0x27/0x90 [ 615.779968] schedule_timeout+0xcf/0x110 [ 615.779975] wait_for_completion+0x82/0x160 [ 615.779979] fw_run_transaction+0xed/0x130 [firewire_core] [ 615.780004] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 615.780028] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 615.780051] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 615.780074] read_rom+0x64/0xb0 [firewire_core] [ 615.780097] read_config_rom+0x9f/0x440 [firewire_core] [ 615.780120] ? psi_task_switch+0x17e/0x390 [ 615.780127] fw_device_init+0x48/0x470 [firewire_core] [ 615.780151] fw_device_workfn+0x12/0x20 [firewire_core] [ 615.780173] process_one_work+0x18e/0x370 [ 615.780181] worker_thread+0x317/0x450 [ 615.780185] ? __pfx_worker_thread+0x10/0x10 [ 615.780189] kthread+0x10b/0x220 [ 615.780194] ? __pfx_kthread+0x10/0x10 [ 615.780198] ret_from_fork+0x134/0x150 [ 615.780202] ? __pfx_kthread+0x10/0x10 [ 615.780205] ret_from_fork_asm+0x1a/0x30 [ 615.780213] </TASK> [ 738.657061] INFO: task kworker/0:0:9 blocked for more than 614 seconds. [ 738.657079] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 738.657084] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 738.657087] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 738.657097] Workqueue: firewire fw_device_workfn [firewire_core] [ 738.657142] Call Trace: [ 738.657146] <TASK> [ 738.657151] __schedule+0x2ed/0x7c0 [ 738.657163] schedule+0x27/0x90 [ 738.657170] schedule_timeout+0xcf/0x110 [ 738.657177] wait_for_completion+0x82/0x160 [ 738.657183] fw_run_transaction+0xed/0x130 [firewire_core] [ 738.657218] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 738.657252] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 738.657285] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 738.657318] read_rom+0x64/0xb0 [firewire_core] [ 738.657351] read_config_rom+0x9f/0x440 [firewire_core] [ 738.657383] ? psi_task_switch+0x17e/0x390 [ 738.657391] fw_device_init+0x48/0x470 [firewire_core] [ 738.657425] fw_device_workfn+0x12/0x20 [firewire_core] [ 738.657457] process_one_work+0x18e/0x370 [ 738.657465] worker_thread+0x317/0x450 [ 738.657471] ? __pfx_worker_thread+0x10/0x10 [ 738.657477] kthread+0x10b/0x220 [ 738.657482] ? __pfx_kthread+0x10/0x10 [ 738.657487] ret_from_fork+0x134/0x150 [ 738.657492] ? __pfx_kthread+0x10/0x10 [ 738.657497] ret_from_fork_asm+0x1a/0x30 [ 738.657504] </TASK> [ 845.725853] perf: interrupt took too long (3153 > 3147), lowering kernel.perf_event_max_sample_rate to 63000 [ 861.535406] INFO: task kworker/0:0:9 blocked for more than 737 seconds. [ 861.535425] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 861.535430] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 861.535434] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 861.535443] Workqueue: firewire fw_device_workfn [firewire_core] [ 861.535490] Call Trace: [ 861.535494] <TASK> [ 861.535499] __schedule+0x2ed/0x7c0 [ 861.535511] schedule+0x27/0x90 [ 861.535518] schedule_timeout+0xcf/0x110 [ 861.535525] wait_for_completion+0x82/0x160 [ 861.535531] fw_run_transaction+0xed/0x130 [firewire_core] [ 861.535566] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 861.535599] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 861.535632] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 861.535665] read_rom+0x64/0xb0 [firewire_core] [ 861.535699] read_config_rom+0x9f/0x440 [firewire_core] [ 861.535731] ? psi_task_switch+0x17e/0x390 [ 861.535739] fw_device_init+0x48/0x470 [firewire_core] [ 861.535773] fw_device_workfn+0x12/0x20 [firewire_core] [ 861.535805] process_one_work+0x18e/0x370 [ 861.535812] worker_thread+0x317/0x450 [ 861.535818] ? __pfx_worker_thread+0x10/0x10 [ 861.535824] kthread+0x10b/0x220 [ 861.535830] ? __pfx_kthread+0x10/0x10 [ 861.535835] ret_from_fork+0x134/0x150 [ 861.535839] ? __pfx_kthread+0x10/0x10 [ 861.535844] ret_from_fork_asm+0x1a/0x30 [ 861.535852] </TASK> [ 984.413795] INFO: task kworker/0:0:9 blocked for more than 860 seconds. [ 984.413813] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 984.413817] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 984.413821] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 984.413830] Workqueue: firewire fw_device_workfn [firewire_core] [ 984.413879] Call Trace: [ 984.413883] <TASK> [ 984.413889] __schedule+0x2ed/0x7c0 [ 984.413901] schedule+0x27/0x90 [ 984.413907] schedule_timeout+0xcf/0x110 [ 984.413915] wait_for_completion+0x82/0x160 [ 984.413921] fw_run_transaction+0xed/0x130 [firewire_core] [ 984.413956] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 984.413989] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 984.414022] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 984.414055] read_rom+0x64/0xb0 [firewire_core] [ 984.414089] read_config_rom+0x9f/0x440 [firewire_core] [ 984.414127] ? psi_task_switch+0x17e/0x390 [ 984.414135] fw_device_init+0x48/0x470 [firewire_core] [ 984.414169] fw_device_workfn+0x12/0x20 [firewire_core] [ 984.414202] process_one_work+0x18e/0x370 [ 984.414210] worker_thread+0x317/0x450 [ 984.414216] ? __pfx_worker_thread+0x10/0x10 [ 984.414222] kthread+0x10b/0x220 [ 984.414228] ? __pfx_kthread+0x10/0x10 [ 984.414233] ret_from_fork+0x134/0x150 [ 984.414237] ? __pfx_kthread+0x10/0x10 [ 984.414242] ret_from_fork_asm+0x1a/0x30 [ 984.414250] </TASK> [ 1107.292039] INFO: task kworker/0:0:9 blocked for more than 983 seconds. [ 1107.292055] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 1107.292058] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1107.292061] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 1107.292068] Workqueue: firewire fw_device_workfn [firewire_core] [ 1107.292107] Call Trace: [ 1107.292110] <TASK> [ 1107.292114] __schedule+0x2ed/0x7c0 [ 1107.292123] schedule+0x27/0x90 [ 1107.292127] schedule_timeout+0xcf/0x110 [ 1107.292132] wait_for_completion+0x82/0x160 [ 1107.292137] fw_run_transaction+0xed/0x130 [firewire_core] [ 1107.292160] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 1107.292183] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 1107.292205] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 1107.292227] read_rom+0x64/0xb0 [firewire_core] [ 1107.292249] read_config_rom+0x9f/0x440 [firewire_core] [ 1107.292271] ? psi_task_switch+0x17e/0x390 [ 1107.292277] fw_device_init+0x48/0x470 [firewire_core] [ 1107.292299] fw_device_workfn+0x12/0x20 [firewire_core] [ 1107.292321] process_one_work+0x18e/0x370 [ 1107.292326] worker_thread+0x317/0x450 [ 1107.292330] ? __pfx_worker_thread+0x10/0x10 [ 1107.292334] kthread+0x10b/0x220 [ 1107.292338] ? __pfx_kthread+0x10/0x10 [ 1107.292342] ret_from_fork+0x134/0x150 [ 1107.292345] ? __pfx_kthread+0x10/0x10 [ 1107.292348] ret_from_fork_asm+0x1a/0x30 [ 1107.292354] </TASK> [ 1230.171464] INFO: task kworker/0:0:9 blocked for more than 1105 seconds. [ 1230.171489] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 1230.171492] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1230.171495] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 1230.171504] Workqueue: firewire fw_device_workfn [firewire_core] [ 1230.171573] Call Trace: [ 1230.171578] <TASK> [ 1230.171584] __schedule+0x2ed/0x7c0 [ 1230.171597] schedule+0x27/0x90 [ 1230.171602] schedule_timeout+0xcf/0x110 [ 1230.171610] wait_for_completion+0x82/0x160 [ 1230.171615] fw_run_transaction+0xed/0x130 [firewire_core] [ 1230.171639] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 1230.171661] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 1230.171684] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 1230.171706] read_rom+0x64/0xb0 [firewire_core] [ 1230.171728] read_config_rom+0x9f/0x440 [firewire_core] [ 1230.171750] ? psi_task_switch+0x17e/0x390 [ 1230.171758] fw_device_init+0x48/0x470 [firewire_core] [ 1230.171781] fw_device_workfn+0x12/0x20 [firewire_core] [ 1230.171802] process_one_work+0x18e/0x370 [ 1230.171809] worker_thread+0x317/0x450 [ 1230.171813] ? __pfx_worker_thread+0x10/0x10 [ 1230.171817] kthread+0x10b/0x220 [ 1230.171822] ? __pfx_kthread+0x10/0x10 [ 1230.171825] ret_from_fork+0x134/0x150 [ 1230.171830] ? __pfx_kthread+0x10/0x10 [ 1230.171833] ret_from_fork_asm+0x1a/0x30 [ 1230.171839] </TASK> [ 1353.048685] INFO: task kworker/0:0:9 blocked for more than 1228 seconds. [ 1353.048702] Tainted: G S 6.17.0-20-generic #20-Ubuntu [ 1353.048707] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 1353.048710] task:kworker/0:0 state:D stack:0 pid:9 tgid:9 ppid:2 task_flags:0x4208060 flags:0x00004000 [ 1353.048720] Workqueue: firewire fw_device_workfn [firewire_core] [ 1353.048765] Call Trace: [ 1353.048768] <TASK> [ 1353.048774] __schedule+0x2ed/0x7c0 [ 1353.048786] schedule+0x27/0x90 [ 1353.048792] schedule_timeout+0xcf/0x110 [ 1353.048799] wait_for_completion+0x82/0x160 [ 1353.048805] fw_run_transaction+0xed/0x130 [firewire_core] [ 1353.048840] ? __pfx_split_transaction_timeout_callback+0x10/0x10 [firewire_core] [ 1353.048874] ? __pfx_transmit_complete_callback+0x10/0x10 [firewire_core] [ 1353.048907] ? __pfx_transaction_callback+0x10/0x10 [firewire_core] [ 1353.048940] read_rom+0x64/0xb0 [firewire_core] [ 1353.048973] read_config_rom+0x9f/0x440 [firewire_core] [ 1353.049006] ? psi_task_switch+0x17e/0x390 [ 1353.049014] fw_device_init+0x48/0x470 [firewire_core] [ 1353.049047] fw_device_workfn+0x12/0x20 [firewire_core] [ 1353.049079] process_one_work+0x18e/0x370 [ 1353.049087] worker_thread+0x317/0x450 [ 1353.049093] ? __pfx_worker_thread+0x10/0x10 [ 1353.049099] kthread+0x10b/0x220 [ 1353.049104] ? __pfx_kthread+0x10/0x10 [ 1353.049109] ret_from_fork+0x134/0x150 [ 1353.049114] ? __pfx_kthread+0x10/0x10 [ 1353.049119] ret_from_fork_asm+0x1a/0x30 [ 1353.049126] </TASK> [ 1353.049129] Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings ProblemType: Bug DistroRelease: Ubuntu 25.10 Package: linux-image-6.17.0-20-generic 6.17.0-20.20 ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13 Uname: Linux 6.17.0-20-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: js1 1905 F.... wireplumber /dev/snd/controlC1: js1 1905 F.... wireplumber /dev/snd/seq: js1 1884 F.... pipewire CasperMD5CheckResult: unknown Date: Fri Apr 17 08:30:03 2026 InstallationDate: Installed on 2018-12-10 (2685 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-20-generic root=UUID=591ea17a-5ac6-4e8b-adb3-75a3dab238d5 ro irqpoll cryptdevice=UUID=6416a2a8-8a76-44df-8d5f-9c465982298a:luks-6416a2a8-8a76-44df-8d5f-9c465982298a root=/dev/mapper/luks-6416a2a8-8a76-44df-8d5f-9c465982298a resume=/dev/mapper/luks-6416a2a8-8a76-44df-8d5f-9c465982298a ipv6.disable=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: firmware-sof N/A linux-firmware 20250901.git993ff19b-0ubuntu1.9 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/15/2007 dmi.bios.release: 0.0 dmi.bios.vendor: Intel Corp. dmi.bios.version: BX97520J.86A.2674.2007.0315.1546 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D975XBX2 dmi.board.vendor: Intel Corporation dmi.board.version: AAD53350-507 dmi.chassis.type: 2 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBX97520J.86A.2674.2007.0315.1546:bd03/15/2007:br0.0:efr0.0:svn:pn:pvr:rvnIntelCorporation:rnD975XBX2:rvrAAD53350-507:cvn:ct2:cvr:sku: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148662/+subscriptions

[Bug 2148348] [NEW] Mainline kernel 7.0 .deb fails to install: invalid run-parts usage in maintainer scripts

Public bug reported: The mainline kernel package linux-image-unsigned-7.0.0-070000-generic fails to install because its maintainer scripts use an invalid run-parts invocation. The scripts incorrectly call: run-parts --report --exit-on-error --arg=$version \ --arg=$image_path /etc/kernel/<hook>.d /usr/share/kernel/<hook>.d run-parts only accepts a single directory argument. Passing multiple directories causes: run-parts: missing operand This breaks dpkg during: - preinst - postinst - postrm and leaves the package in a broken or half-installed state. Additionally, postinst dynamically generates a trigger script with the same invalid run-parts usage, causing repeated failures even after reinstall attempts. --- Fix: Each run-parts call must be split into two separate calls, one per directory. ### preinst fix Replace: if [ -d /etc/kernel/preinst.d ] || [ -d /usr/share/kernel/preinst.d ]; then DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error --arg=$version \ --arg=$image_path /etc/kernel/preinst.d /usr/share/kernel/preinst.d fi With: if [ -d /etc/kernel/preinst.d ]; then DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error \ --arg=$version --arg=$image_path /etc/kernel/preinst.d fi if [ -d /usr/share/kernel/preinst.d ]; then DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error \ --arg=$version --arg=$image_path /usr/share/kernel/preinst.d fi --- ### postinst fix (trigger generation) Replace: cat - >/usr/lib/linux/triggers/$version <<EOF DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error --arg=$version \ --arg=$image_path /etc/kernel/postinst.d /usr/share/kernel/postinst.d EOF With: cat > /usr/lib/linux/triggers/$version <<EOF #!/bin/sh set -e if [ -d /etc/kernel/postinst.d ]; then DEB_MAINT_PARAMS="\$*" run-parts --report --exit-on-error \ --arg=$version --arg=$image_path /etc/kernel/postinst.d fi if [ -d /usr/share/kernel/postinst.d ]; then DEB_MAINT_PARAMS="\$*" run-parts --report --exit-on-error \ --arg=$version --arg=$image_path /usr/share/kernel/postinst.d fi EOF chmod +x /usr/lib/linux/triggers/$version --- ### postrm fix Replace: DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error --arg=$version \ --arg=$image_path /etc/kernel/postrm.d /usr/share/kernel/postrm.d With: if [ -d /etc/kernel/postrm.d ]; then DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error \ --arg=$version --arg=$image_path /etc/kernel/postrm.d fi if [ -d /usr/share/kernel/postrm.d ]; then DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error \ --arg=$version --arg=$image_path /usr/share/kernel/postrm.d fi --- Impact: - Prevents dpkg install failures - Allows initramfs and bootloader hooks to run correctly - Stops broken trigger scripts from being generated After applying these fixes to all affected scripts, the kernel installs and configures successfully. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-7.0 kernel-bug mainline-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148348 Title: Mainline kernel 7.0 .deb fails to install: invalid run-parts usage in maintainer scripts Status in linux package in Ubuntu: New Bug description: The mainline kernel package linux-image-unsigned-7.0.0-070000-generic fails to install because its maintainer scripts use an invalid run-parts invocation. The scripts incorrectly call: run-parts --report --exit-on-error --arg=$version \ --arg=$image_path /etc/kernel/<hook>.d /usr/share/kernel/<hook>.d run-parts only accepts a single directory argument. Passing multiple directories causes: run-parts: missing operand This breaks dpkg during: - preinst - postinst - postrm and leaves the package in a broken or half-installed state. Additionally, postinst dynamically generates a trigger script with the same invalid run-parts usage, causing repeated failures even after reinstall attempts. --- Fix: Each run-parts call must be split into two separate calls, one per directory. ### preinst fix Replace: if [ -d /etc/kernel/preinst.d ] || [ -d /usr/share/kernel/preinst.d ]; then DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error --arg=$version \ --arg=$image_path /etc/kernel/preinst.d /usr/share/kernel/preinst.d fi With: if [ -d /etc/kernel/preinst.d ]; then DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error \ --arg=$version --arg=$image_path /etc/kernel/preinst.d fi if [ -d /usr/share/kernel/preinst.d ]; then DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error \ --arg=$version --arg=$image_path /usr/share/kernel/preinst.d fi --- ### postinst fix (trigger generation) Replace: cat - >/usr/lib/linux/triggers/$version <<EOF DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error --arg=$version \ --arg=$image_path /etc/kernel/postinst.d /usr/share/kernel/postinst.d EOF With: cat > /usr/lib/linux/triggers/$version <<EOF #!/bin/sh set -e if [ -d /etc/kernel/postinst.d ]; then DEB_MAINT_PARAMS="\$*" run-parts --report --exit-on-error \ --arg=$version --arg=$image_path /etc/kernel/postinst.d fi if [ -d /usr/share/kernel/postinst.d ]; then DEB_MAINT_PARAMS="\$*" run-parts --report --exit-on-error \ --arg=$version --arg=$image_path /usr/share/kernel/postinst.d fi EOF chmod +x /usr/lib/linux/triggers/$version --- ### postrm fix Replace: DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error --arg=$version \ --arg=$image_path /etc/kernel/postrm.d /usr/share/kernel/postrm.d With: if [ -d /etc/kernel/postrm.d ]; then DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error \ --arg=$version --arg=$image_path /etc/kernel/postrm.d fi if [ -d /usr/share/kernel/postrm.d ]; then DEB_MAINT_PARAMS="$*" run-parts --report --exit-on-error \ --arg=$version --arg=$image_path /usr/share/kernel/postrm.d fi --- Impact: - Prevents dpkg install failures - Allows initramfs and bootloader hooks to run correctly - Stops broken trigger scripts from being generated After applying these fixes to all affected scripts, the kernel installs and configures successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148348/+subscriptions

[Bug 2148714] [NEW] Noble update: upstream stable patchset 2026-04-17

Public bug reported: 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: upstream stable patchset 2026-04-17 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148714 Title: Noble update: upstream stable patchset 2026-04-17 Status in linux package in Ubuntu: Confirmed Status in linux source package in Noble: New 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: upstream stable patchset 2026-04-17 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148714/+subscriptions

[Bug 2148636] Re: backport Intel iwlwifi core102 support from linux-next to linux/resolute 7.0.

DKMS (dkms-3.2.2) make.log for backport-iwlwifi/0~103.14434-gitdf6b5bf4 for kernel 7.0.0-2014-generic (x86_64) ...... CC [M] net/wireless/sysfs.o net/wireless/sysfs.c:176:22: error: initialization of 'const struct ns_common * (*)(const struct device *)' from incompatible pointer type 'const void * (*)(const stru ct device *)' [-Wincompatible-pointer-types] 176 | .namespace = wiphy_namespace, | ^~~~~~~~~~~~~~~ net/wireless/sysfs.c:176:22: note: (near initialization for 'ieee80211_class.namespace') net/wireless/sysfs.c:163:20: note: 'wiphy_namespace' declared here 163 | static const void *wiphy_namespace(__ns_const struct device *d) | ^~~~~~~~~~~~~~~ make[7]: *** [/usr/src/linux-headers-7.0.0-2014-generic/scripts/Makefile.build:289: net/wireless/sysfs.o] Error 1 ** Attachment added: "dkms-build-failure_backport-iwlwifi.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148636/+attachment/5962108/+files/dkms-build-failure_backport-iwlwifi.log -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148636 Title: backport Intel iwlwifi core102 support from linux-next to linux/resolute 7.0. Status in linux package in Ubuntu: Incomplete Status in linux source package in Resolute: Incomplete Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148636/+subscriptions

[Bug 2147137] Re: rocblas-test crashes with hipErrorIllegalAddress(700)

** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2147137 Title: rocblas-test crashes with hipErrorIllegalAddress(700) Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in rocblas package in Ubuntu: Triaged Bug description: The built-in test suite for rocblas is crashing repeatably with memory access errors, usually a hipError 700 which translates to hipErrorIllegalAddress. ## Reproducing The entire test suite does not cause problems, the easiest way to get this crash to manifest is to use './rocblas-test --gtest_filter=*trsm_batched*' ## Debug information When run through gdb, '/usr/libexec/rocm/librocblas5-tests/rocblas- test --gtest_filter=*trsm_batched*' generates the following output and backtrace: Query device success: there are 1 devices ------------------------------------------------------------------------------- Device ID 0 : AMD Radeon Pro W7900 gfx1100 with 48.3 GB memory, max. SCLK 1760 MHz, max. MCLK 1124 MHz, memoryBusWidth 48 Bytes, compute capability 11.0 maxGridDimX 2147483647, sharedMemPerBlock 65.5 KB, maxThreadsPerBlock 1024, warpSize 32 ------------------------------------------------------------------------------- info: parsing of test data may take a couple minutes before any test output appears... Note: Google Test filter = *trsm_batched* [==========] Running 13969 tests from 3 test suites. [----------] Global test environment set-up. [----------] 11916 tests from _/trsm_batched [New Thread 0x7ffe641af6c0 (LWP 1407327)] [New Thread 0x7ffcea7ff6c0 (LWP 1407328)] [Thread 0x7ffcea7ff6c0 (LWP 1407328) exited] Signal 0x7ffce2d05900 time stamps may be invalid. clients/common/../include/blas3/testing_trsm_batched.hpp:546: Failure Expected equality of these values:   hXorB_1.transfer_from(dXorB)     Which is: 700   hipSuccess     Which is: 0 Error: hipMemcpy post-guard copy failure. clients/gtest/../include/d_vector.hpp:165: Failure Expected equality of these values:   memcmp(host.data(), m_guard, m_guard_len)     Which is: -203   0 clients/gtest/../include/d_vector.hpp:190: Failure Expected equality of these values:   (hipFree)(d)     Which is: 700   hipSuccess     Which is: 0 clients/gtest/../include/device_batch_matrix.hpp:391: Failure Expected equality of these values:   (hipFree)(tmp_device_data)     Which is: 700   hipSuccess     Which is: 0 Error: hipMemcpy post-guard copy failure. clients/gtest/../include/d_vector.hpp:165: Failure Expected equality of these values:   memcmp(host.data(), m_guard, m_guard_len)     Which is: -203   0 Error: hipMemcpy pre-guard copy failure. clients/gtest/../include/d_vector.hpp:175: Failure Expected equality of these values:   memcmp(host.data(), m_guard, m_guard_len)     Which is: -203   0 clients/gtest/../include/d_vector.hpp:190: Failure Expected equality of these values:   (hipFree)(d)     Which is: 700   hipSuccess     Which is: 0 clients/gtest/../include/device_batch_matrix.hpp:391: Failure Expected equality of these values:   (hipFree)(tmp_device_data)     Which is: 700   hipSuccess     Which is: 0 rocBLAS error retreiving the device (deviceID: 32767) Thread 1 "rocblas-test" received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=<optimized out>, signo=6, no_tid=0) at ./nptl/pthread_kill.c:44 warning: 44 ./nptl/pthread_kill.c: No such file or directory (gdb) bt #0 __pthread_kill_implementation (threadid=<optimized out>, signo=6, no_tid=0) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (threadid=<optimized out>, signo=6) at ./nptl/pthread_kill.c:89 #2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=6) at ./nptl/pthread_kill.c:100 #3 0x00007fffebc2fb7e in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x00007fffebc128ec in __GI_abort () at ./stdlib/abort.c:77 #5 0x00007fffeead5477 in rocblas_abort () at /usr/src/rocblas-7.1.0-1ubuntu4/library/src/rocblas_ostream.cpp:81 #6 0x00007fffeeace40e in _rocblas_handle::~_rocblas_handle (this=<optimized out>) at /usr/src/rocblas-7.1.0-1ubuntu4/library/src/include/rocblas_ostream.hpp:537 #7 0x00007fffeead2cd3 in rocblas_destroy_handle (handle=0x5555d5bbcfd0) at /usr/src/rocblas-7.1.0-1ubuntu4/library/src/rocblas_auxiliary.cpp:230 #8 0x000055555818e5ad in rocblas_local_handle::~rocblas_local_handle (this=0x7fffffffdad8) at /usr/src/rocblas-7.1.0-1ubuntu4/clients/common/client_utility.cpp:519 #9 0x0000555557a2ec84 in testing_trsm_batched<double> (arg=...) at /usr/src/rocblas-7.1.0-1ubuntu4/clients/common/../include/blas3/testing_trsm_batched.hpp:775 #10 0x000055555819e7b5 in std::function<void()>::operator() (this=0x7fffffffdc90) at /usr/lib/gcc/x86_64-linux-gnu/16/../../../../include/c++/16/bits/std_function.h:581 #11 catch_signals_and_exceptions_as_failures (test=..., set_alarm=true) at /usr/src/rocblas-7.1.0-1ubuntu4/clients/common/gtest_helpers.cpp:199 #12 0x0000555555c374c5 in (anonymous namespace)::trsm_batched_blas3_tensile_Test::TestBody (this=<optimized out>) at /usr/src/rocblas-7.1.0-1ubuntu4/clients/gtest/blas3/trsm_gtest.cpp:201 #13 0x00005555581fb6c7 in void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) () #14 0x00005555581e0dae in testing::Test::Run() () #15 0x00005555581e0f35 in testing::TestInfo::Run() () #16 0x00005555581ebd47 in testing::TestSuite::Run() () #17 0x00005555581f0ebc in testing::internal::UnitTestImpl::RunAllTests() () #18 0x00005555581fbd27 in bool testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) () #19 0x00005555581e0fca in testing::UnitTest::Run() () #20 0x000055555587efc9 in RUN_ALL_TESTS () at /usr/include/gtest/gtest.h:2334 #21 main (argc=1, argv=0x7fffffffe458) at /usr/src/rocblas-7.1.0-1ubuntu4/clients/gtest/rocblas_gtest_main.cpp:344 ## versions and affected HW Arch: amd64 Tested version: rocblas 7.1.0-1ubuntu4 AMD gpu ISAs tested: gfx1100, gfx1101, gfx1201 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2147137/+subscriptions

[Bug 2148694] [NEW] LG Gram 16U70Q: Brightness keys send no ACPI signal on 6.8.0-110, worked on 6.8.0-38

Public bug reported: On LG Gram 16U70Q-G laptop, the brightness keys (increase/decrease) do not generate any ACPI events under kernel 6.8.0-110-generic. Under kernel 6.8.0-38-generic the same keys work correctly. Steps to reproduce: 1. Boot kernel 6.8.0-110-generic 2. Run: acpi_listen 3. Press brightness up or down key 4. No output is generated Expected behavior: acpi_listen should output events like: video/brightnessdown BRTDN 00000087 00000000 System info: - Laptop: LG Gram 16U70Q-G-AR36G - OS: Linux Mint 22.3 Cinnamon - Working kernel: 6.8.0-38-generic - Broken kernels: 6.8.0-107-generic, 6.8.0-110-generic - Backlight device: amdgpu_bl1 (AMD GPU) - No acpi_backlight parameters set in working kernel ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148694 Title: LG Gram 16U70Q: Brightness keys send no ACPI signal on 6.8.0-110, worked on 6.8.0-38 Status in linux package in Ubuntu: New Bug description: On LG Gram 16U70Q-G laptop, the brightness keys (increase/decrease) do not generate any ACPI events under kernel 6.8.0-110-generic. Under kernel 6.8.0-38-generic the same keys work correctly. Steps to reproduce: 1. Boot kernel 6.8.0-110-generic 2. Run: acpi_listen 3. Press brightness up or down key 4. No output is generated Expected behavior: acpi_listen should output events like: video/brightnessdown BRTDN 00000087 00000000 System info: - Laptop: LG Gram 16U70Q-G-AR36G - OS: Linux Mint 22.3 Cinnamon - Working kernel: 6.8.0-38-generic - Broken kernels: 6.8.0-107-generic, 6.8.0-110-generic - Backlight device: amdgpu_bl1 (AMD GPU) - No acpi_backlight parameters set in working kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148694/+subscriptions

[Bug 2148567] Re: HP Zbook Ultra G1a - Bluetooth Not Working

This device was freshly installed with 26.04 beta, so we didn't get a chance to test it with a 6.14, 6.17, or 6.19 kernel. This laptop is certified with 24.04, with the 6.14.0-1008-oem kernel. However, any patches in that oem kernel should be in the 26.04 kernel already, at least in theory. https://ubuntu.com/certified/202411-36033 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2148567 Title: HP Zbook Ultra G1a - Bluetooth Not Working Status in linux package in Ubuntu: Incomplete Status in linux source package in Resolute: Incomplete Bug description: When clicking on the Bluetooth icon, 3 dots appear as if it is thinking, but Bluetooth never enables. The button remains grey. On rare occasions it works, but most of the time this happens. I have seen no indicating as to why it works some times and not others. When clicking the Bluetooth button, nothing is logged in kern.log either. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 09:52:54 2026 InstallationDate: Installed on 2026-03-10 (37 days ago) InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260308) MachineType: HP HP ZBook Ultra G1a 14 inch Mobile Workstation PC ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/19/2026 dmi.bios.release: 4.5 dmi.bios.vendor: HP dmi.bios.version: X89 Ver. 01.04.05 dmi.board.name: 8D01 dmi.board.vendor: HP dmi.board.version: KBC Version 35.33.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 53.51 dmi.modalias: dmi:bvnHP:bvrX89Ver.01.04.05:bd01/19/2026:br4.5:efr53.51:svnHP:pnHPZBookUltraG1a14inchMobileWorkstationPC:pvrSBKPFV3:rvnHP:rn8D01:rvrKBCVersion35.33.00:cvnHP:ct10:cvr:skuBF6U5UT#ABA:pfa103C_5336ANHPZBook: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook Ultra G1a 14 inch Mobile Workstation PC dmi.product.sku: BF6U5UT#ABA dmi.product.version: SBKPFV3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2148567/+subscriptions

[Bug 2067644] Re: containers in ubuntu_ltp_stable and cve-2018-18955 in ubuntu_ltp_cve fail on Noble

As Juerg wrote on 2024-05-31, this issue is indeed caused by the AppArmor configuration. ```sh $ apt download apparmor Get:1 http://au.archive.ubuntu.com/ubuntu noble-updates/main amd64 apparmor amd64 4.0.1really4.0.1-0ubuntu0.24.04.6 [639 kB] Fetched 639 kB in 0s (5137 kB/s) $ mkdir aa $ dpkg -x apparmor_4.0.1really4.0.1-0ubuntu0.24.04.6_amd64.deb aa $ cd aa aa$ find . -name "*.conf" ./usr/lib/sysctl.d/10-apparmor.conf ./etc/apparmor/parser.conf aa$ cat ./usr/lib/sysctl.d/10-apparmor.conf # AppArmor restrictions of unprivileged user namespaces # Allows to restrict the use of unprivileged user namespaces to applications # which have an AppArmor profile loaded which specifies the userns # permission. All other applications (whether confined by AppArmor or not) will # be denied the use of unprivileged user namespaces. # # See # https://gitlab.com/apparmor/apparmor/-/wikis/unprivileged_userns_restriction # # If it is desired to disable this restriction, it is preferable to create an # additional file named /etc/sysctl.d/20-apparmor.conf which will override this # current file and sets this value to 0 rather than editing this current file kernel.apparmor_restrict_unprivileged_userns = 1 ``` -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2067644 Title: containers in ubuntu_ltp_stable and cve-2018-18955 in ubuntu_ltp_cve fail on Noble Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: Both the containers test in ubuntu_ltp_stable and cve-2018-18955 in ubuntu_ltp_cve fail with a similar error on Noble. This happens on multiple noble kernels, including generic, realtime, and ibm. The following error references a commit, but these kernels have that commit applied. The errors are as follows: containers in ubuntu_ltp_stable: 18189 13:55:14 DEBUG| [stdout] userns08.c:80: TBROK: setgid(0) failed: EPERM (1) 18190 13:55:14 DEBUG| [stdout] 18191 13:55:14 DEBUG| [stdout] HINT: You _MAY_ be missing kernel fixes: 18192 13:55:14 DEBUG| [stdout] 18193 13:55:14 DEBUG| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d2f007dbe7e4 cve-2018-18955 in ubuntu_ltp_cve: 40826 userns08.c:80: TBROK: setgid(0) failed: EPERM (1) 40827 40828 HINT: You _MAY_ be missing kernel fixes: 40829 40830 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d2f007dbe7e4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2067644/+subscriptions

[Bug 2144530] Re: Regression on Acer Nitro AN17-41: amdgpu DC/DMUB fails to light up internal eDP and Radeon-routed USB-C/DP outputs on Ubuntu 26.04 / kernel 6.19, while Ubuntu 24.04.4 live works

** Also affects: linux-firmware-amd-graphics (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: Triaged => Invalid ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: Invalid ** Also affects: linux-firmware (Ubuntu Resolute) Importance: Undecided Assignee: Leo Lin (0xff07) Status: Invalid ** Also affects: linux-firmware-amd-graphics (Ubuntu Resolute) Importance: Undecided Status: New ** Changed in: linux-firmware-amd-graphics (Ubuntu Resolute) Status: New => Fix Committed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2144530 Title: Regression on Acer Nitro AN17-41: amdgpu DC/DMUB fails to light up internal eDP and Radeon-routed USB-C/DP outputs on Ubuntu 26.04 / kernel 6.19, while Ubuntu 24.04.4 live works Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware-amd-graphics package in Ubuntu: Fix Committed Status in linux source package in Resolute: Invalid Status in linux-firmware source package in Resolute: Invalid Status in linux-firmware-amd-graphics source package in Resolute: Fix Committed Bug description: [ Impact ] here’s a regression reported by community in 1e2c1534: https://gitlab.freedesktop.org/drm/amd/-/work_items/5143#note_3411517 The last known good version is 43c969c1, and there’s a revert happening in upstream: https://gitlab.freedesktop.org/drm/amd/-/work_items/5143#note_3418637 [ Fix ] Cherry-pick the following revert commit: - d3a8c25 (amdgpu: Revert Yellow Carp DMUB fw to 0x4000045) Firmware in Noble and Questing currently doesn't include the bad version. Only Resolute needs this. [ Test ] Install the firmware package including this revert and boot. The display should light up normally. [ Where the problem could occur] Whatever was introduce after commit 43c969c1 would be reverted. Also, there's an ongoing SRU in Q and N to update the very same file in LP:#2147396. If it happens that they need firmware after commit 43c969c1 to fix the issue, then one of those 2 issues will likely not get fixed. ================= ORIGINAL DESCRIPTION ================= Problem summary =============== On an Acer Nitro AN17-41 laptop, Ubuntu 26.04 development branch with kernel 6.19.0-9-generic fails to display video when the internal panel and/or external USB-C display output are owned by the AMD iGPU. This appears to be a regression or behavior change in the newer Linux graphics stack, because the same machine and same monitor path work under: - Windows 11 - Ubuntu 24.04.4 live ISO The machine has: - Acer Nitro AN17-41 - BIOS V1.25 - AMD Rembrandt / Radeon 680M iGPU (1002:1681) - NVIDIA GeForce RTX 4050 Mobile / Max-Q dGPU (10de:28e1) I collected logs over SSH from another device in the failing cases because the machine was still alive even when both displays were black. Observed behavior on Ubuntu 26.04 / kernel 6.19 ================================================ When AMD owns the display outputs, the system boots but the displays stay black. This affects: - the internal eDP panel - an external monitor connected through the USB-C / DP output routed to Radeon The logs repeatedly show amdgpu DC / DMUB failures such as: - "Failed to enable ASSR" - "No reply for DMUB command: status=3" - "DMCUB error - collecting diagnostic data" - "Error queueing DMUB command: status=2" - "enabling link ... failed: 15" In the failing cases, DRM can still detect AMD-owned outputs as connected and enabled, but they remain black. Environment =========== OS: - Ubuntu 26.04 (Resolute Raccoon development branch) Kernel: - 6.19.0-9-generic Secure Boot: - enabled Hardware: - Acer Nitro AN17-41 - BIOS V1.25 - AMD Radeon 680M iGPU - NVIDIA RTX 4050 Mobile dGPU Regression evidence =================== I now have a working Linux control case on the same laptop and same physical USB-C monitor path. Tested with: - Ubuntu 24.04.4 LTS live ISO Results on Ubuntu 24.04.4: 1. Auto / hybrid mode:    - internal panel works    - external monitor connected to the Radeon-routed USB-C/DP output also works 2. NVIDIA GPU Only mode:    - internal panel works    - the same external monitor on the Radeon-routed USB-C/DP output also works in my test In both Ubuntu 24.04.4 test cases, the displays light up normally and I do not see the repeated amdgpu DC/DMUB failure pattern that appears on Ubuntu 26.04 / kernel 6.19. This strongly suggests: - the hardware is capable of driving both outputs under Linux - the Radeon-routed USB-C output is not fundamentally broken on this laptop - the issue is more likely a regression or missing quirk in the newer graphics/kernel stack used in Ubuntu 26.04 Additional control evidence =========================== The same USB-C monitor connected to the Radeon-routed USB-C output also works in Windows 11 when switching to Extend mode with Win+P. This further suggests that the physical hardware path is functional, and that the failing configuration is specific to the newer Linux graphics stack. What works ========== 1. NVIDIA GPU Only mode in firmware / BIOS on Ubuntu 26.04:    - the internal laptop panel works 2. Windows 11:    - the USB-C monitor connected to the Radeon-routed USB-C output works in Extend mode 3. Ubuntu 24.04.4 live ISO:    - Auto / hybrid mode works    - internal panel works    - Radeon-routed USB-C/DP external monitor works    - NVIDIA GPU Only mode also worked in my test, including the same USB-C monitor What does not work ================== On Ubuntu 26.04 / kernel 6.19: 1. Hybrid / normal mode:    - if the internal panel is owned by AMD, the panel stays black 2. AMD-only test:    - booting with      module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm    - internal eDP stays black    - external USB-C/DP monitor routed to Radeon also stays black This strongly suggests the issue is not caused by nvidia-drm handoff or by both DRM stacks loading together. How to reproduce ================ Case A: Hybrid / normal mode on Ubuntu 26.04 1. Boot Ubuntu 26.04 on Acer Nitro AN17-41. 2. Let the machine use its normal hybrid graphics routing. 3. If the internal panel is owned by AMD, the panel remains black. Case B: AMD-only test on Ubuntu 26.04 1. Boot with:    module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm 2. Connect an external monitor to the USB-C / DP output routed to Radeon before power-on. 3. Boot Ubuntu. 4. Result: both the internal panel and the external USB-C display remain black, although the system is alive and reachable over SSH. Case C: Verbose DRM logging on Ubuntu 26.04 1. Boot with:    drm.debug=0x1e log_buf_len=4M module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm 2. Result: same black screens, with detailed DRM / amdgpu logging showing DMUB / ASSR / link enable failures. Expected result =============== When AMD owns the internal eDP panel and/or Radeon-routed USB-C/DP output, the displays should light up normally and the system should reach a visible graphical session. Actual result ============= The system boots, but the displays stay black. Logs indicate failures in amdgpu DC / DMUB while trying to bring up AMD-owned display links. Important log patterns ====================== Examples consistently seen in the affected Ubuntu 26.04 boots: - "Skipping amdgpu DM backlight registration" - "Failed to get EDID from ACPI: -19" (seen in verbose DRM logging) - "boot timing validation failed ..." - "Failed to enable ASSR" - "No reply for DMUB command: status=3" - "DMCUB error - collecting diagnostic data" - "Error queueing DMUB command: status=2" - "enabling link 0 failed: 15" - "enabling link 2 failed: 15" Why I think this is a kernel/amdgpu issue ========================================= The issue reproduces when NVIDIA modules are blacklisted, so it does not appear to depend on nvidia-drm being active. The internal panel and the Radeon-routed external USB-C/DP output can both be detected as connected/enabled by DRM, but they still remain black. The same hardware and same USB-C path work: - on Windows 11 - on Ubuntu 24.04.4 live ISO This makes it look like an amdgpu DC / DMUB / link bring-up failure in the newer Ubuntu 26.04 graphics stack, rather than: - a simple EDID-not-found case - a generic Optimus/MUX problem - a pure backlight-only issue - a userspace / compositor-only issue - a fundamental hardware limitation of the laptop Tests already performed ======================= On Ubuntu 26.04: 1. Normal hybrid boot    - black internal display when AMD owns it 2. NVIDIA GPU Only mode    - internal panel works 3. AMD-only boot with:    module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm    - both internal eDP and Radeon-routed USB-C/DP stayed black 4. Verbose DRM boot with:    drm.debug=0x1e log_buf_len=4M    - same failure, more detailed DMUB / ASSR / link logs 5. Test with:    amdgpu.sg_display=0    - no improvement 6. Test with:    amdgpu.abmlevel=0    - no improvement On Ubuntu 24.04.4 live ISO: 7. Auto / hybrid mode    - internal panel works    - Radeon-routed USB-C/DP external monitor works 8. NVIDIA GPU Only mode    - internal panel works    - the same Radeon-routed USB-C/DP external monitor also worked in my test Attachments =========== I am attaching log bundles from these scenarios: - gpu-badboot4-nvidiablacklist.zip - gpu-badboot5-nvidiablacklistamdusbc.zip - gpu-badboot6-nvidiablacklistamdusbcdbg.zip - gpu-goodboot7-nvidiaonly-w-usbc-radeon.zip - gpu-badboot8-sgzero.zip - gpu-badboot9-abmzero.zip - gpu-goodboot10-u24044.zip - gpu-goodboot11-u24045.zip These include: - journalctl / dmesg output - DRM connector status and enabled state - lspci / module state - backlight info - EDID decode output - verbose DRM logs where applicable I can reproduce this reliably and I can collect additional logs over SSH because the machine stays alive even when both displays are black. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-6.19.0-9-generic 6.19.0-9.9 ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5 Uname: Linux 6.19.0-9-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC2: denixx 6079 F.... wireplumber  /dev/snd/controlC0: denixx 6079 F.... wireplumber  /dev/snd/controlC1: denixx 6079 F.... wireplumber  /dev/snd/seq: denixx 6059 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 16 08:26:28 2026 InstallationDate: Installed on 2026-03-15 (1 days ago) InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260313) IwDevWlp4s0Link: Not connected. MachineType: Acer Nitro AN17-41 ProcEnviron:  LANG=uk_UA.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color ProcFB:  0 amdgpudrmfb  1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.19.0-9-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2024 dmi.bios.release: 1.25 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Spacia_PEH dmi.board.vendor: RB dmi.board.version: V1.25 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000: dmi.product.family: Acer Nitro 17 dmi.product.name: Nitro AN17-41 dmi.product.sku: 0000000000000000 dmi.product.version: V1.25 dmi.sys.vendor: Acer --- ProblemType: Bug ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC2: ubuntu 4446 F.... wireplumber  /dev/snd/controlC0: ubuntu 4446 F.... wireplumber  /dev/snd/controlC1: ubuntu 4446 F.... wireplumber  /dev/snd/seq: ubuntu 4430 F.... pipewire CasperMD5CheckResult: pass CasperVersion: 26.04.0 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 IwDevWlp4s0Link: Not connected. LiveMediaBuild: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260316) MachineType: Acer Nitro AN17-41 NonfreeKernelModules: zfs Package: linux (not installed) ProcEnviron:  LANG=C.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB:  0 amdgpudrmfb  1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5 Tags: resolute wayland-session Uname: Linux 6.19.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 09/18/2024 dmi.bios.release: 1.25 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Spacia_PEH dmi.board.vendor: RB dmi.board.version: V1.25 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000: dmi.product.family: Acer Nitro 17 dmi.product.name: Nitro AN17-41 dmi.product.sku: 0000000000000000 dmi.product.version: V1.25 dmi.sys.vendor: Acer --- ProblemType: Bug ApportVersion: 2.33.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse:  USER PID ACCESS COMMAND  /dev/snd/controlC2: ubuntu 4386 F.... wireplumber  /dev/snd/controlC0: ubuntu 4386 F.... wireplumber  /dev/snd/controlC1: ubuntu 4386 F.... wireplumber  /dev/snd/seq: ubuntu 4370 F.... pipewire CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CasperVersion: 26.04.1 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 IwDevWlp4s0Link: Not connected. LiveMediaBuild: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260322) MachineType: Acer Nitro AN17-41 NonfreeKernelModules: zfs Package: linux (not installed) ProcEnviron:  LANG=C.UTF-8  PATH=(custom, no user)  SHELL=/bin/bash  TERM=xterm-256color  XDG_RUNTIME_DIR=<set> ProcFB:  0 amdgpudrmfb  1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash drm.debug=0x1e log_buf_len=4M ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3 Tags: resolute wayland-session Uname: Linux 7.0.0-7-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 09/18/2024 dmi.bios.release: 1.25 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.25 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Spacia_PEH dmi.board.vendor: RB dmi.board.version: V1.25 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:pfaAcerNitro17: dmi.product.family: Acer Nitro 17 dmi.product.name: Nitro AN17-41 dmi.product.sku: 0000000000000000 dmi.product.version: V1.25 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+subscriptions