** Attachment added: "crash-20260715-dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160457/+attachment/5982104/+files/crash-20260715-dmesg.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160457 Title: Kernel panic in srso_safe_ret / kick_ilb during sched_tick on AMD Ryzen 7 4800U (Zen2) Status in linux package in Ubuntu: New Bug description: DESCRIPTION: == Summary == Repeated kernel panics on AMD Ryzen 7 4800U (Renoir/Zen2) triggered by the SRSO (Speculative Return Stack Overflow) mitigation interacting with the scheduler tick path. The system crashes every 1-11 days with no user-space trigger. Crashes occur in both linux-image-7.0.0-22-generic and linux-image-7.0.0-27-generic. Workaround: processor.max_cstate=1 (preventing deep C-states avoids the crash path). == Hardware == - System: AZW (Beelink) SER Mini PC - CPU: AMD Ryzen 7 4800U with Radeon Graphics (Zen2 / Renoir) - Microcode: 0x0860010d (updated from 0x08600106 at boot) - GPU: AMD Renoir [Radeon Vega Series] (integrated, amdgpu driver) - RAM: 16GB DDR4 - BIOS: SER_V1.14_P3C6M43_B_Link (03/24/2022) — latest available for this model - NVMe storage == Software == - Ubuntu 26.04 LTS (fresh install on 2026-05-26) - Kernel: 7.0.0-22-generic and 7.0.0-27-generic (both affected) - amd64-microcode: 3.20251202.1ubuntu2 - linux-firmware: 20260319.git217ca6e4.1ubuntu - Boot params: quiet splash crashkernel=... - Active mitigation: srso_return_thunk (confirmed via dmesg) - NOPTI active == Crash #1 — 2026-07-10 (kernel 7.0.0-27) == Oops: invalid opcode: 0000 [#1] SMP NOPTI CPU: 0 UID: 0 PID: 0 Comm: swapper/0 RIP: 0010:srso_safe_ret+0x0/0x20 Call Trace: <IRQ> sched_tick+0x48/0x280 update_process_times+0xa0/0xe0 tick_nohz_handler+0x96/0x1a0 __hrtimer_run_queues+0x10c/0x270 hrtimer_interrupt+0x104/0x250 __sysvec_apic_timer_interrupt+0x58/0x150 sysvec_apic_timer_interrupt+0x9a/0xd0 </IRQ> <TASK> asm_sysvec_apic_timer_interrupt+0x1b/0x20 RIP: 0010:cpuidle_enter_state+0xca/0x700 cpuidle_enter+0x30/0x50 cpuidle_idle_call+0x16b/0x1f0 do_idle+0x94/0xf0 </TASK> == Crash #2 — 2026-07-12 (kernel 7.0.0-27) == BUG: unable to handle page fault for address: ffffffff99053b04 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD bc447067 P4D bc447067 PUD bc448063 PMD 0 Oops: Oops: 0002 [#1] SMP NOPTI CPU: 0 UID: 1000 PID: 2680076 Comm: curl RIP: 0010:kick_ilb+0x6e/0x180 Call Trace: <TASK> kick_ilb+0x52/0x180 nohz_balancer_kick+0x92/0x2d0 sched_balance_trigger+0x4c/0x90 sched_tick+0xf9/0x280 update_process_times+0xa0/0xe0 tick_nohz_handler+0x96/0x1a0 __hrtimer_run_queues+0x10c/0x270 hrtimer_interrupt+0x104/0x250 __sysvec_apic_timer_interrupt+0x58/0x150 sysvec_apic_timer_interrupt+0x44/0xd0 asm_sysvec_apic_timer_interrupt+0x1b/0x20 </TASK> == Additional context == - amdgpu driver logs "dm_irq_work_func [amdgpu] hogged CPU for >13333us" 35+ times per boot, suggesting IRQ pressure on the scheduler tick path. - Both crashes occur on CPU 0 during timer interrupt → sched_tick. - Crash #1 is an invalid opcode in the SRSO safe_ret thunk itself. - Crash #2 is a page fault in kick_ilb writing to an unmapped kernel address (PMD 0), suggesting corrupted per-cpu data or text patching issue in the SRSO path. - The system was stable for 14 days once (when amdgpu initialized without errors). - Full kdump vmcores are available in /var/crash/ for all crashes. == Crash frequency == 6+ crashes since 2026-05-29, intervals ranging from 1.5 to 11 days. No specific user-space trigger identified — crashes happen during idle or light workloads (cron jobs, curl). == Workaround == Adding processor.max_cstate=1 to kernel boot parameters prevents the CPU from entering deep C-states where the crash occurs. This confirms the interaction between cpuidle exit path, SRSO return thunks, and sched_tick. == Possible root cause == The SRSO mitigation (srso_return_thunk / srso_safe_ret) appears to have a bug in the text patching or in the interaction with the scheduler's nohz/idle balancer on AMD Zen2 processors when exiting deep C-states. The amdgpu driver hogging the CPU in interrupt context likely increases the probability of hitting the race condition. == Kdump files == /var/crash/202607101059/ — Crash #1 (srso_safe_ret) /var/crash/202607120124/ — Crash #2 (kick_ilb) Both contain full vmcore dumps and dmesg extracts. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: gdm-greeter 2490 F.... wireplumber /dev/snd/controlC0: gdm-greeter 2490 F.... wireplumber /dev/snd/seq: gdm-greeter 2474 F.... pipewire CasperMD5CheckResult: unknown Date: Sun Jul 12 12:34:59 2026 InstallationDate: Installed on 2026-05-26 (47 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp2s0Link: Not connected. MachineType: AZW SER ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=screen-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=3cc618bf-7287-4c56-86b6-9ddbfe59a14a 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: 03/24/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: SER_V1.14_P3C6M43_B_Link dmi.board.asset.tag: Default string dmi.board.name: SER dmi.board.vendor: AZW dmi.board.version: V01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: AZW dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrSER_V1.14_P3C6M43_B_Link:bd03/24/2022:br5.16:svnAZW:pnSER:pvrDefaultstring:rvnAZW:rnSER:rvrV01:cvnAZW:ct35:cvrDefaultstring:skuSKU4:pfaSER: dmi.product.family: SER dmi.product.name: SER dmi.product.sku: SKU4 dmi.product.version: Default string dmi.sys.vendor: AZW To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160457/+subscriptions
среда
[Bug 1117804] Re: ausearch doesn't show AppArmor denial messages
Debdiff for Resolute ** Patch added: "lp1117804-resolute-3.debdiff" https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1117804/+attachment/5982102/+files/lp1117804-resolute-3.debdiff -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1117804 Title: ausearch doesn't show AppArmor denial messages Status in AppArmor: Confirmed Status in audit package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Status in audit source package in Jammy: In Progress Status in audit source package in Noble: In Progress Status in audit source package in Questing: Won't Fix Status in audit source package in Resolute: In Progress Status in audit source package in Stonking: In Progress Bug description: [ Impact ] * The following command should display all AppArmor AVC events: `ausearch --message AVC`; however, it doesn't work: ``` yachie@virtual:/etc/apparmor.d$ ausearch --message AVC <no matches> ``` * Users currently must inspect `/var/log/audit.log` to find the missing AppArmor AVC events: ``` yachie@virtual:/etc/apparmor.d$ sudo cat /var/log/audit.log type=AVC msg=audit(1774470501.870:1117918): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/proc/2009624/cmdline" pid=106062 comm="in:imuxsock" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 FSUID="root" OUID="root" type=AVC msg=audit(1774470501.927:1117919): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/proc/2009636/cmdline" pid=106062 comm="in:imuxsock" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 FSUID="root" OUID="root" ``` * The root cause is that `ausearch` is checking for a `tclass` field in the AppArmor events, because AppArmor is using event id `1400` (assigned to SELinux) instead of `1500`. * AppArmor events don't have a `tclass` field, so `ausearch` treats every AppArmor event as 'malformed' and hides them. We can reveal the 'malformed' events with the `--debug` flag: ``` yachie@virtual:~$ ausearch --message AVC --debug ( ... a ton of unrelated events ... ) Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.176:616): apparmor="AUDIT" operation="change_onexec" class="file" info="change_profile unprivileged unconfined converted to stacking" profile="unconfined" name="lsb_release" pid=5443 comm="aa-exec" Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:617): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/nsswitch.conf" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:618): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/passwd" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:619): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/bash.bashrc" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:620): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/home/yachie/.bashrc" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:621): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/home/yachie/.bash_history" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:622): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/home/yachie/.bash_history" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:623): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/inputrc" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 <no matches> ``` * This bug makes `auditd` very difficult to use on Ubuntu: having the `auditd` package installed hides AVC events from the kernel log AND `ausearch` doesn't reveal them, making AppArmor events seemingly vanish unless you know where to look. [ Test plan ] # Install the relevant packages 1. sudo apt install apparmor auditd # Run the reproducer 2. aa-exec --profile=lsb_release bash # generates a ton of denials; see below: ``` root@jammy-vm:~# aa-exec --profile lsb_release bash bash: /etc/bash.bashrc: Permission denied bash: /root/.bashrc: Permission denied bash-5.1# exit ``` # Run `ausearch` and search for AVC events 3. ausearch --message AVC 3a. Unpatched package output (fail): ``` root@jammy-vm:~# ausearch --message AVC <no matches> ``` 3b. Patched package output (success): ``` root@jammy-vm:~# ausearch --message AVC ---- time->Tue Jul 14 21:03:18 2026 type=PROCTITLE msg=audit(1784062998.789:100): proctitle="bash" type=SYSCALL msg=audit(1784062998.789:100): arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=7f6a7274c150 a2=80000 a3=0 items=0 ppid=562 pid=3449 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=4294967295 comm="bash" exe="/usr/bin/bash" subj=lsb_release key=(null) type=AVC msg=audit(1784062998.789:100): apparmor="DENIED" operation="open" profile="lsb_release" name="/etc/nsswitch.conf" pid=3449 comm="bash" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 ---- time->Tue Jul 14 21:03:18 2026 type=PROCTITLE msg=audit(1784062998.789:101): proctitle="bash" type=SYSCALL msg=audit(1784062998.789:101): arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=7f6a7274c2ac a2=80000 a3=0 items=0 ppid=562 pid=3449 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=4294967295 comm="bash" exe="/usr/bin/bash" subj=lsb_release key=(null) type=AVC msg=audit(1784062998.789:101): apparmor="DENIED" operation="open" profile="lsb_release" name="/etc/passwd" pid=3449 comm="bash" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 ---- ( ...continues ) ``` [ Where problems could occur ] * Currently, all AppArmor events are treated as 'malformed' SELinux events when they are actually well-formed AppArmor events. * This patch modifies the filtration behavior of `ausearch` by making the `tclass` field optional, thus making AppArmor events be treated as well-formed SELinux events. * The regression risk with this patch is such that potentially well- formed events will be hidden by `ausearch` unintentionally, or truly malformed events will be allowed past the filter. * One major caveat is that regressions with respect to actual SELinux events are difficult to test on Ubuntu; some malformed SELinux events would potentially be allowed through the filter with this patch, or well-formed SELinux events hidden. This patch essentially trades correctness in the SELinux case for correctness in the AppArmor case. [ Other info ] * Debian likely doesn't want this patch, as Debian officially won't be making any changes until upstream does [3]. * Upstream `audit` can't move the AppArmor event id to the `1500` range any time soon. AppArmor was moved to the `1400` range to align with the Linux kernel LSM infrastructure [2]. * This patch comes from SUSE; they've been carrying it for well over a decade [4], and they seem to still be carrying it even after switching to SELinux by default [5]. Targeted releases: All currently supported releases and all releases moving forward until AppArmor moves back to the `1500` event range or Ubuntu switches to SELinux by default. [1] Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726 [2] AA using 1400 reason: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726#39 [3] Debian `wontfix` closure: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726#88 [4] SUSE KB: https://support.scc.suse.com/s/kb/audit-log-file-that-has-the-apparmor-AVC-entries-that-ausearch-can-t-read-1583239408721?language=en_US [5] SUSE Patch: https://build.opensuse.org/projects/security/packages/audit/files/audit-ausearch-do-not-require-tclass.patch [ Original bug (for posterity after over a decade) ] The following command should display all AVC denials: ausearch -m avc However, it doesn't work with AppArmor denials. Here's a quick test case to generate a denial, search for it with ausearch, and see that no messages are displayed: $ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current cat: /proc/self/attr/current: Permission denied $ sudo ausearch -m avc -c cat <no matches> ausearch claims that there are no matches, but there's a matching audit message if you look in audit.log: type=AVC msg=audit(1360193426.539:64): apparmor="DENIED" operation="open" parent=8253 profile="/usr/sbin/tcpdump" name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1117804/+subscriptions
[Bug 1117804] Re: ausearch doesn't show AppArmor denial messages
Debdiff for Noble. The maintainer was already set to Ubuntu Developers for this version. ** Patch added: "lp1117804-noble-3.debdiff" https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1117804/+attachment/5982101/+files/lp1117804-noble-3.debdiff -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1117804 Title: ausearch doesn't show AppArmor denial messages Status in AppArmor: Confirmed Status in audit package in Ubuntu: In Progress Status in linux package in Ubuntu: Invalid Status in audit source package in Jammy: In Progress Status in audit source package in Noble: In Progress Status in audit source package in Questing: Won't Fix Status in audit source package in Resolute: In Progress Status in audit source package in Stonking: In Progress Bug description: [ Impact ] * The following command should display all AppArmor AVC events: `ausearch --message AVC`; however, it doesn't work: ``` yachie@virtual:/etc/apparmor.d$ ausearch --message AVC <no matches> ``` * Users currently must inspect `/var/log/audit.log` to find the missing AppArmor AVC events: ``` yachie@virtual:/etc/apparmor.d$ sudo cat /var/log/audit.log type=AVC msg=audit(1774470501.870:1117918): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/proc/2009624/cmdline" pid=106062 comm="in:imuxsock" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 FSUID="root" OUID="root" type=AVC msg=audit(1774470501.927:1117919): apparmor="DENIED" operation="open" class="file" profile="rsyslogd" name="/proc/2009636/cmdline" pid=106062 comm="in:imuxsock" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 FSUID="root" OUID="root" ``` * The root cause is that `ausearch` is checking for a `tclass` field in the AppArmor events, because AppArmor is using event id `1400` (assigned to SELinux) instead of `1500`. * AppArmor events don't have a `tclass` field, so `ausearch` treats every AppArmor event as 'malformed' and hides them. We can reveal the 'malformed' events with the `--debug` flag: ``` yachie@virtual:~$ ausearch --message AVC --debug ( ... a ton of unrelated events ... ) Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.176:616): apparmor="AUDIT" operation="change_onexec" class="file" info="change_profile unprivileged unconfined converted to stacking" profile="unconfined" name="lsb_release" pid=5443 comm="aa-exec" Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:617): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/nsswitch.conf" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:618): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/passwd" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:619): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/bash.bashrc" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:620): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/home/yachie/.bashrc" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:621): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/home/yachie/.bash_history" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:622): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/home/yachie/.bash_history" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Malformed event skipped, rc=9. type=AVC msg=audit(1776888566.177:623): apparmor="DENIED" operation="open" class="file" profile="lsb_release" name="/etc/inputrc" pid=5443 comm="bash" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 <no matches> ``` * This bug makes `auditd` very difficult to use on Ubuntu: having the `auditd` package installed hides AVC events from the kernel log AND `ausearch` doesn't reveal them, making AppArmor events seemingly vanish unless you know where to look. [ Test plan ] # Install the relevant packages 1. sudo apt install apparmor auditd # Run the reproducer 2. aa-exec --profile=lsb_release bash # generates a ton of denials; see below: ``` root@jammy-vm:~# aa-exec --profile lsb_release bash bash: /etc/bash.bashrc: Permission denied bash: /root/.bashrc: Permission denied bash-5.1# exit ``` # Run `ausearch` and search for AVC events 3. ausearch --message AVC 3a. Unpatched package output (fail): ``` root@jammy-vm:~# ausearch --message AVC <no matches> ``` 3b. Patched package output (success): ``` root@jammy-vm:~# ausearch --message AVC ---- time->Tue Jul 14 21:03:18 2026 type=PROCTITLE msg=audit(1784062998.789:100): proctitle="bash" type=SYSCALL msg=audit(1784062998.789:100): arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=7f6a7274c150 a2=80000 a3=0 items=0 ppid=562 pid=3449 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=4294967295 comm="bash" exe="/usr/bin/bash" subj=lsb_release key=(null) type=AVC msg=audit(1784062998.789:100): apparmor="DENIED" operation="open" profile="lsb_release" name="/etc/nsswitch.conf" pid=3449 comm="bash" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 ---- time->Tue Jul 14 21:03:18 2026 type=PROCTITLE msg=audit(1784062998.789:101): proctitle="bash" type=SYSCALL msg=audit(1784062998.789:101): arch=c000003e syscall=257 success=no exit=-13 a0=ffffff9c a1=7f6a7274c2ac a2=80000 a3=0 items=0 ppid=562 pid=3449 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts0 ses=4294967295 comm="bash" exe="/usr/bin/bash" subj=lsb_release key=(null) type=AVC msg=audit(1784062998.789:101): apparmor="DENIED" operation="open" profile="lsb_release" name="/etc/passwd" pid=3449 comm="bash" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 ---- ( ...continues ) ``` [ Where problems could occur ] * Currently, all AppArmor events are treated as 'malformed' SELinux events when they are actually well-formed AppArmor events. * This patch modifies the filtration behavior of `ausearch` by making the `tclass` field optional, thus making AppArmor events be treated as well-formed SELinux events. * The regression risk with this patch is such that potentially well- formed events will be hidden by `ausearch` unintentionally, or truly malformed events will be allowed past the filter. * One major caveat is that regressions with respect to actual SELinux events are difficult to test on Ubuntu; some malformed SELinux events would potentially be allowed through the filter with this patch, or well-formed SELinux events hidden. This patch essentially trades correctness in the SELinux case for correctness in the AppArmor case. [ Other info ] * Debian likely doesn't want this patch, as Debian officially won't be making any changes until upstream does [3]. * Upstream `audit` can't move the AppArmor event id to the `1500` range any time soon. AppArmor was moved to the `1400` range to align with the Linux kernel LSM infrastructure [2]. * This patch comes from SUSE; they've been carrying it for well over a decade [4], and they seem to still be carrying it even after switching to SELinux by default [5]. Targeted releases: All currently supported releases and all releases moving forward until AppArmor moves back to the `1500` event range or Ubuntu switches to SELinux by default. [1] Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726 [2] AA using 1400 reason: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726#39 [3] Debian `wontfix` closure: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726#88 [4] SUSE KB: https://support.scc.suse.com/s/kb/audit-log-file-that-has-the-apparmor-AVC-entries-that-ausearch-can-t-read-1583239408721?language=en_US [5] SUSE Patch: https://build.opensuse.org/projects/security/packages/audit/files/audit-ausearch-do-not-require-tclass.patch [ Original bug (for posterity after over a decade) ] The following command should display all AVC denials: ausearch -m avc However, it doesn't work with AppArmor denials. Here's a quick test case to generate a denial, search for it with ausearch, and see that no messages are displayed: $ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current cat: /proc/self/attr/current: Permission denied $ sudo ausearch -m avc -c cat <no matches> ausearch claims that there are no matches, but there's a matching audit message if you look in audit.log: type=AVC msg=audit(1360193426.539:64): apparmor="DENIED" operation="open" parent=8253 profile="/usr/sbin/tcpdump" name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1117804/+subscriptions
Re: [Bug 2160452] Re: Touchpad broke after updating linux kernel to 7.0.0-27-generic
Here it is. I wasn't paying attention and I think I could use the touchpad earlier while on the 7.0.0-27 kernel, but now I'm definitely on the 7.0.0-27 kernel and it doesn't work. On 7/13/26 21:30, Alice C. Munduruca wrote: > Hey Elias, thanks for sending in this bug report, > > Could you connect a mouse and re-send the kernel logs from 7.0.0-27? The > follow command will produce a log files in your Downloads folder which > can then be attached here. > > $ sudo dmesg > ~/Downloads/dmesg.log > > This will help us understand why the kernel cannot detect your touchpad > device. > > ** Changed in: linux (Ubuntu) > Status: New => Incomplete > ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/2160452/+attachment/5982041/+files/dmesg.log -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160452 Title: Touchpad broke after updating linux kernel to 7.0.0-27-generic Status in linux package in Ubuntu: Incomplete Bug description: Hi, After updating the linux kernel from 7.0.0-22-generic to 7.0.0-27-generic the touchpad completely stopped working. I tried restarting the drivers (i2c_hid_api driver), and rebooting my computer, without success. I booted back in ubuntu using the 7.0.0-22-generic kernel and it worked again. OS version: Ubuntu 26.04 LTS, firmware version E16V1IMS.112 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-22-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: heart 3714 F.... wireplumber /dev/snd/controlC1: heart 3714 F.... wireplumber /dev/snd/seq: heart 3698 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 12 15:40:46 2026 InstallationDate: Installed on 2026-05-05 (68 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Micro-Star International Co., Ltd. GS66 Stealth 10SF ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-kitty ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-22-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro rootflags=subvol=@ quiet splash intel_iommu=on iommu=pt 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: 11/19/2020 dmi.bios.release: 1.18 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16V1IMS.112 dmi.board.asset.tag: Default string dmi.board.name: MS-16V1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16V1IMS.112:bd11/19/2020:br1.18:svnMicro-StarInternationalCo.,Ltd.:pnGS66Stealth10SF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16V1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16V1.1:pfaGS: dmi.product.family: GS dmi.product.name: GS66 Stealth 10SF dmi.product.sku: 16V1.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160452/+subscriptions
[Bug 2152688] Re: iwlwifi failed to handle oversized command 0xC05
Thanks for your contribution! It seems that this change was already uploaded to the archive as `backport-iwlwifi-dkms 1:0~103.14434-gitdf6b5bf4-0ubuntu3.26.04.2`, so there is nothing left to sponsor here. Cleaning up the queue by unsubscribing ~ubuntu-sponsors. https://launchpad.net/ubuntu/+source/backport-iwlwifi- dkms/1:0~103.14434-gitdf6b5bf4-0ubuntu3.26.04.2 -- This is an automated initial review of sponsoring requests. If this review seems wrong, please report it at https://bugs.launchpad.net/ubuntu-sponsoring -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152688 Title: iwlwifi failed to handle oversized command 0xC05 Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-hwe-7.0 package in Ubuntu: Invalid Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux-oem-7.0 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Noble: Invalid Status in linux source package in Noble: Invalid Status in linux-hwe-7.0 source package in Noble: Triaged Status in linux-oem-6.17 source package in Noble: Incomplete Status in linux-oem-7.0 source package in Noble: Invalid Status in backport-iwlwifi-dkms source package in Questing: Invalid Status in linux source package in Questing: Invalid Status in linux-hwe-7.0 source package in Questing: Invalid Status in linux-oem-6.17 source package in Questing: Invalid Status in linux-oem-7.0 source package in Questing: Invalid Status in backport-iwlwifi-dkms source package in Resolute: Fix Released Status in linux source package in Resolute: In Progress Status in linux-hwe-7.0 source package in Resolute: Invalid Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux-oem-7.0 source package in Resolute: Fix Released Status in backport-iwlwifi-dkms source package in Stonking: Fix Released Status in linux source package in Stonking: In Progress Status in linux-hwe-7.0 source package in Stonking: Invalid Status in linux-oem-6.17 source package in Stonking: Invalid Status in linux-oem-7.0 source package in Stonking: Invalid Bug description: [SRU Justification] [Impact] With Intel AX211 wireless module installed on Intel Wildcat Lake platform, kernel warning with following errors are found at loading iwlwifi driver: ``` kernel: iwlwifi 0000:00:14.3: Error sending UNKNOWN: enqueue_hcmd failed: -22 kernel: iwlwifi 0000:00:14.3: failed to send MCC_ALLOWED_AP_TYPE_CMD (-22) ``` This are found in mainline kernels 7.0+ as they are the kernel versions for WCL support, as well as backport-iwlwifi core102, 103, 104 and 105. backport-iwlwifi master branch HEAD has been partially patched, but incomplete. [Fix] For backport-iwlwifi-dkms, in the master branch HEAD it has commit 5a3d01a7ea635 ("[BUGFIX] wifi: iwlwifi: mvm: avoid oversized UATS command copy"), which is incomplete that Intel gives an additional patch titled "wifi: iwlwifi: mvm: don't map the stack to DMA". These two patches combined equal to https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi- next.git/commit/?h=fixes&id=e0c121d545134af886b28c4c26d91abf5dd39c17 ("wifi: iwlwifi: mvm: avoid oversized UATS command copy"). However the later breaks builds against kernel < 7.0 and therefore it takes additional backport related to kmalloc_obj family from commit 4862faa9c3dd ("Merge remote-tracking branch 'auto/master'"). Later, it's found to cause another PHC register failure warning on kernels >= 7.0, and it takes backports related to settime64 from another commit 5076fafb8e33 ("Merge remote-tracking branch 'auto/master'"). For the linux kernel in-tree iwlwifi driver, Intel proposed a fix https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi- next.git/commit/?h=fixes&id=e0c121d545134af886b28c4c26d91abf5dd39c17 ("wifi: iwlwifi: mvm: avoid oversized UATS command copy") that is already in linux-next. While v7.0 has already commit 81d90d93d22ca ("wifi: iwlwifi: Implement settime64 as stub for MVM/MLD PTP") that fixes the PHC register problem, no additional fix is needed. [Test Plan] There are 4 cases: * linux-unstable-7.1/stonking * linux-generic-7.0/resolute * linux-oem-7.0/resolute * backport-iwlwifi-dkms/stoking - tested against linux-unstable-7.1/stonking * backport-iwlwifi-dkms/resolute - tested against linux-generic-7.0/resolute, linux-oem-7.0/resolute and linux-oem-6.17/noble To test kernel packages: 1. Install kernels from corresponding -proposed pocket. 2. Boot from some Intel Wildcat Lake platforms with an Intel AX211 wireless module installed. Here I use Intel WCL-U RVP. 3. The dmesg should gives no error but probe iwlwifi kernel module successfully. To test backport-iwlwifi-dkms packages: 1. Boot the testing kernel from some Intel Wildcat Lake platforms with an Intel AX211 wireless module installed. Here I use Intel WCL-U RVP. 2. Install kernels from corresponding -proposed pocket. 3. The corresponding kernel modules should be built automatically by dpkg triggers. Use `dkms status` to list built kernel versions. 4. Reboot into the same kernel. The dmesg should gives no error but probe iwlwifi kernel module successfully. [Where problems could occur] This changes the way that command object is handled using IWL_HCMD_DFL_NOCOPY to avoid buffer size checking. It doesn't really change runtime behavior or anything else. [Other Info] The patches for backport-iwlwifi-dkms are meant to be superseded by the ones in the master branch, so I did not cherry-pick the one from linux-next instead. Nominate backport-iwlwifi-dkms Resolute and Stonking, because they are versions with WCL support. Nominate linux/{Q,R}, linux-oem-7.0, linux-oem-6.17, because they are either 7.0 kernels or uses backport-iwlwifi-dkms/R. ========== original bug report ========== May 04 13:33:52 ubuntu-202603-38491 kernel: ------------[ cut here ]------------ May 04 13:33:52 ubuntu-202603-38491 kernel: Command UNKNOWN (0xc05) is too large (348 bytes) May 04 13:33:52 ubuntu-202603-38491 kernel: WARNING: CPU: 4 PID: 995 at drivers/net/wireless/intel/iwlwifi/pcie/gen1_2/tx-gen2.c:1278 iwl_pcie_gen2_enqueue_hcmd+0x7ea/0xf10 [iwlwifi] May 04 13:33:52 ubuntu-202603-38491 kernel: Modules linked in: snd_soc_sof_sdw snd_sof_probes snd_soc_intel_hda_dsp_common qrtr snd_soc_rt722_sdca regmap_sdw_mbq snd_hda_codec_intelhdmi snd_soc_dmic bnep snd_hda_intel snd_sof_pci_intel_ptl snd_sof_pci_intel_lnl snd_sof_pci_intel_mtl snd_sof_intel_hda_generic soundwire_intel snd_sof_intel_hda_sdw_bpt snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda_mlink snd_sof_intel_hda snd_hda_codec_hdmi soundwire_cadence snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_hda_ext_core snd_hda_codec snd_hda_core snd_intel_dspcfg snd_intel_sdw_acpi snd_soc_acpi_intel_match snd_soc_acpi_intel_sdca_quirks soundwire_generic_allocation snd_soc_sdw_utils snd_soc_acpi snd_hwdep intel_uncore_frequency soundwire_bus intel_uncore_frequency_common snd_soc_sdca x86_pkg_temp_thermal snd_soc_core intel_powerclamp snd_compress coretemp ac97_bus snd_pcm_dmaengine snd_pcm kvm_intel snd_seq_midi dell_pc snd_ctl_led snd_seq_midi_event mei_gsc_proxy intel_rapl_msr binfmt_misc snd_rawmidi kvm xe uvcvideo dell_laptop May 04 13:33:52 ubuntu-202603-38491 kernel: snd_seq irqbypass videobuf2_vmalloc iwlmvm(O) uvc gpu_sched processor_thermal_device_pci videobuf2_memops polyval_clmulni btusb drm_gpuvm ghash_clmulni_intel videobuf2_v4l2 processor_thermal_device btrtl processor_thermal_wt_hint videobuf2_common aesni_intel dell_wmi drm_gpusvm_helper snd_seq_device platform_temperature_control mac80211(O) btintel drm_buddy dell_smbios snd_timer drm_ttm_helper processor_thermal_soc_slider btbcm videodev processor_thermal_rfim ttm btmtk dcdbas nls_iso8859_1 bluetooth libarc4 dell_wmi_ddv dell_wmi_sysman(+) dell_smm_hwmon mc firmware_attributes_class drm_exec iwlwifi(O) processor_thermal_rapl snd intel_rapl_common i2c_i801 processor_thermal_wt_req drm_suballoc_helper dell_wmi_descriptor wmi_bmof i2c_smbus processor_thermal_power_floor soundcore mei_me drm_display_helper processor_thermal_mbox crc8 i2c_mux mei cfg80211(O) cec intel_vpu rc_core iwlwifi_compat(O) intel_pmc_core platform_profile i2c_algo_bit igen6_edac pmt_telemetry int3403_thermal int340x_thermal_zone May 04 13:33:52 ubuntu-202603-38491 kernel: pmt_discovery pmt_class int3400_thermal intel_pmc_ssram_telemetry acpi_thermal_rel intel_vsec acpi_tad intel_hid sparse_keymap acpi_pad joydev input_leds serio_raw mac_hid sch_fq_codel msr parport_pc ppdev lp parport nvme_fabrics efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 linear uas usb_storage ucsi_acpi hid_multitouch typec_ucsi hid_generic typec nvme psmouse video intel_lpss_pci nvme_core e1000e nvme_keyring intel_lpss nvme_auth idma64 thunderbolt i2c_hid_acpi i2c_hid hid wmi pinctrl_intel_platform May 04 13:33:52 ubuntu-202603-38491 kernel: CPU: 4 UID: 0 PID: 995 Comm: NetworkManager Tainted: G O 6.17.0-1020-oem #20-Ubuntu PREEMPT(voluntary) May 04 13:33:52 ubuntu-202603-38491 kernel: Tainted: [O]=OOT_MODULE May 04 13:33:52 ubuntu-202603-38491 kernel: Hardware name: Dell Inc. Dell Pro 3 16 P316260/, BIOS 2.0.1 04/16/2026 May 04 13:33:52 ubuntu-202603-38491 kernel: RIP: 0010:iwl_pcie_gen2_enqueue_hcmd+0x7ea/0xf10 [iwlwifi] May 04 13:33:52 ubuntu-202603-38491 kernel: Code: ff ff ff 8b 5b 28 4c 89 e7 89 4d b0 89 de e8 dd 1f fd ff 8b 4d b0 89 da 48 c7 c7 d0 b2 d4 c0 48 89 c6 0f b7 c9 e8 c6 d8 68 f8 <0f> 0b c7 45 a4 ea ff ff ff e9 da fe ff ff 48 8b b5 48 ff ff ff 0f May 04 13:33:52 ubuntu-202603-38491 kernel: RSP: 0018:ffffd57e53ab2fc8 EFLAGS: 00010246 May 04 13:33:52 ubuntu-202603-38491 kernel: RAX: 0000000000000000 RBX: 0000000000000c05 RCX: 0000000000000000 May 04 13:33:52 ubuntu-202603-38491 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 May 04 13:33:52 ubuntu-202603-38491 kernel: RBP: ffffd57e53ab30a8 R08: 0000000000000000 R09: 0000000000000000 May 04 13:33:52 ubuntu-202603-38491 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff8ef75ec60028 May 04 13:33:52 ubuntu-202603-38491 kernel: R13: 000000000000015c R14: 0000000000000c05 R15: 0000000000000001 May 04 13:33:52 ubuntu-202603-38491 kernel: FS: 0000789de8915580(0000) GS:ffff8efb03a6a000(0000) knlGS:0000000000000000 May 04 13:33:52 ubuntu-202603-38491 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 04 13:33:52 ubuntu-202603-38491 kernel: CR2: 00005bc50ada15f0 CR3: 000000012051d004 CR4: 0000000000f72ef0 May 04 13:33:52 ubuntu-202603-38491 kernel: PKRU: 55555554 May 04 13:33:52 ubuntu-202603-38491 kernel: Call Trace: May 04 13:33:52 ubuntu-202603-38491 kernel: <TASK> May 04 13:33:52 ubuntu-202603-38491 kernel: ? __wait_for_common+0x14d/0x180 May 04 13:33:52 ubuntu-202603-38491 kernel: ? __pfx_schedule_timeout+0x10/0x10 May 04 13:33:52 ubuntu-202603-38491 kernel: ? bsearch+0x58/0x90 May 04 13:33:52 ubuntu-202603-38491 kernel: iwl_trans_pcie_send_hcmd+0x15b/0x470 [iwlwifi] May 04 13:33:52 ubuntu-202603-38491 kernel: iwl_trans_send_cmd+0x57/0xe0 [iwlwifi] May 04 13:33:52 ubuntu-202603-38491 kernel: iwl_mvm_send_cmd_pdu+0x53/0xa0 [iwlmvm] May 04 13:33:52 ubuntu-202603-38491 kernel: iwl_mvm_uats_init+0x162/0x1d0 [iwlmvm] May 04 13:33:52 ubuntu-202603-38491 kernel: iwl_mvm_up+0xa03/0xe80 [iwlmvm] May 04 13:33:52 ubuntu-202603-38491 kernel: __iwl_mvm_mac_start+0x227/0x2c0 [iwlmvm] May 04 13:33:52 ubuntu-202603-38491 kernel: ? __iwl_mvm_mac_start+0x227/0x2c0 [iwlmvm] May 04 13:33:52 ubuntu-202603-38491 kernel: iwl_mvm_mac_start+0x81/0x120 [iwlmvm] May 04 13:33:52 ubuntu-202603-38491 kernel: drv_start+0x52/0x120 [mac80211] May 04 13:33:52 ubuntu-202603-38491 kernel: ieee80211_do_open+0x333/0x800 [mac80211] May 04 13:33:52 ubuntu-202603-38491 kernel: ieee80211_open+0x6e/0xa0 [mac80211] May 04 13:33:52 ubuntu-202603-38491 kernel: __dev_open+0x136/0x300 May 04 13:33:52 ubuntu-202603-38491 kernel: __dev_change_flags+0x1b9/0x230 May 04 13:33:52 ubuntu-202603-38491 kernel: netif_change_flags+0x27/0x80 May 04 13:33:52 ubuntu-202603-38491 kernel: do_setlink.isra.0+0xb7c/0xea0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? _raw_spin_lock_irqsave+0xe/0x20 May 04 13:33:52 ubuntu-202603-38491 kernel: ? skb_queue_tail+0x48/0x60 May 04 13:33:52 ubuntu-202603-38491 kernel: ? sock_def_readable+0x52/0xe0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? __netlink_sendskb+0x6a/0x90 May 04 13:33:52 ubuntu-202603-38491 kernel: ? netlink_unicast+0x35a/0x3e0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? __alloc_skb+0xd9/0x1b0 May 04 13:33:52 ubuntu-202603-38491 kernel: __rtnl_newlink+0x2ea/0x3c0 May 04 13:33:52 ubuntu-202603-38491 kernel: rtnl_newlink+0x4ad/0x910 May 04 13:33:52 ubuntu-202603-38491 kernel: ? __check_object_size.part.0+0x72/0x150 May 04 13:33:52 ubuntu-202603-38491 kernel: ? security_capable+0x44/0x80 May 04 13:33:52 ubuntu-202603-38491 kernel: ? __pfx_rtnl_newlink+0x10/0x10 May 04 13:33:52 ubuntu-202603-38491 kernel: rtnetlink_rcv_msg+0x37b/0x450 May 04 13:33:52 ubuntu-202603-38491 kernel: ? inode_set_ctime_to_ts+0x32/0xb0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? __pfx_rtnetlink_rcv_msg+0x10/0x10 May 04 13:33:52 ubuntu-202603-38491 kernel: netlink_rcv_skb+0x59/0x110 May 04 13:33:52 ubuntu-202603-38491 kernel: rtnetlink_rcv+0x15/0x30 May 04 13:33:52 ubuntu-202603-38491 kernel: netlink_unicast+0x28a/0x3e0 May 04 13:33:52 ubuntu-202603-38491 kernel: netlink_sendmsg+0x214/0x470 May 04 13:33:52 ubuntu-202603-38491 kernel: ____sys_sendmsg+0x36f/0x3e0 May 04 13:33:52 ubuntu-202603-38491 kernel: ___sys_sendmsg+0x99/0xf0 May 04 13:33:52 ubuntu-202603-38491 kernel: __sys_sendmsg+0x8c/0x100 May 04 13:33:52 ubuntu-202603-38491 kernel: __x64_sys_sendmsg+0x1d/0x30 May 04 13:33:52 ubuntu-202603-38491 kernel: x64_sys_call+0x237b/0x2680 May 04 13:33:52 ubuntu-202603-38491 kernel: do_syscall_64+0x80/0x910 May 04 13:33:52 ubuntu-202603-38491 kernel: ? fput_close_sync+0x3d/0xa0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? __x64_sys_close+0x3e/0x90 May 04 13:33:52 ubuntu-202603-38491 kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? do_syscall_64+0xb6/0x910 May 04 13:33:52 ubuntu-202603-38491 kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? do_syscall_64+0xb6/0x910 May 04 13:33:52 ubuntu-202603-38491 kernel: ? proc_sys_write+0x13/0x20 May 04 13:33:52 ubuntu-202603-38491 kernel: ? vfs_write+0x29b/0x480 May 04 13:33:52 ubuntu-202603-38491 kernel: ? ksys_write+0xdb/0xf0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? do_syscall_64+0xb6/0x910 May 04 13:33:52 ubuntu-202603-38491 kernel: ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 May 04 13:33:52 ubuntu-202603-38491 kernel: ? do_syscall_64+0xb6/0x910 May 04 13:33:52 ubuntu-202603-38491 kernel: ? irqentry_exit+0x43/0x50 May 04 13:33:52 ubuntu-202603-38491 kernel: ? exc_page_fault+0x90/0x1b0 May 04 13:33:52 ubuntu-202603-38491 kernel: entry_SYSCALL_64_after_hwframe+0x76/0x7e May 04 13:33:52 ubuntu-202603-38491 kernel: RIP: 0033:0x789de952c06b May 04 13:33:52 ubuntu-202603-38491 kernel: Code: 48 89 e5 48 83 ec 20 89 55 ec 48 89 75 f0 89 7d f8 e8 f9 c4 f6 ff 8b 55 ec 48 8b 75 f0 41 89 c0 8b 7d f8 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 2d 44 89 c7 48 89 45 f8 e8 51 c5 f6 ff 48 8b May 04 13:33:52 ubuntu-202603-38491 kernel: RSP: 002b:00007fffd89c9080 EFLAGS: 00000293 ORIG_RAX: 000000000000002e May 04 13:33:52 ubuntu-202603-38491 kernel: RAX: ffffffffffffffda RBX: 00006220d400e430 RCX: 0000789de952c06b May 04 13:33:52 ubuntu-202603-38491 kernel: RDX: 0000000000000000 RSI: 00007fffd89c90c0 RDI: 000000000000000d May 04 13:33:52 ubuntu-202603-38491 kernel: RBP: 00007fffd89c90a0 R08: 0000000000000000 R09: 0000000000000000 May 04 13:33:52 ubuntu-202603-38491 kernel: R10: 0000000000000000 R11: 0000000000000293 R12: 000000000000000e May 04 13:33:52 ubuntu-202603-38491 kernel: R13: 00006220d400e430 R14: 0000000000000001 R15: 0000000000000000 May 04 13:33:52 ubuntu-202603-38491 kernel: </TASK> May 04 13:33:52 ubuntu-202603-38491 kernel: ---[ end trace 0000000000000000 ]--- May 04 13:33:52 ubuntu-202603-38491 kernel: iwlwifi 0000:00:14.3: Error sending UNKNOWN: enqueue_hcmd failed: -22 May 04 13:33:52 ubuntu-202603-38491 kernel: iwlwifi 0000:00:14.3: failed to send MCC_ALLOWED_AP_TYPE_CMD (-22) --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1522 F.... pipewire ubuntu 1527 F.... wireplumber /dev/snd/seq: ubuntu 1522 F.... pipewire CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.standard.hotfix.manifest ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg CasperMD5CheckResult: fail DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for Dell # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-noble-oem-24.04d-proposed-20260427-100 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2026-04-30 (15 days ago) InstallationMedia: Ubuntu OEM 24.04.4 LTS "Noble Numbat" - Release amd64 (20260423) IwConfig: lo no wireless extensions. enp0s31f6 no wireless extensions. wlp0s20f3 no wireless extensions. MachineType: Dell Inc. Dell Pro 3 16 P316260 Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1020-oem root=UUID=ad40f208-dcb5-4e8e-96c2-c4bb5ebdb23c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.17.0-1020.20-oem 6.17.13 RelatedPackageVersions: linux-restricted-modules-6.17.0-1020-oem N/A linux-backports-modules-6.17.0-1020-oem N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 Tags: noble Uname: Linux 6.17.0-1020-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/16/2026 dmi.bios.release: 2.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.0 dmi.modalias: dmi:bvnDellInc.:bvr2.0.1:bd04/16/2026:br2.0:efr1.0:svnDellInc.:pnDellPro316P316260:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0DF5: dmi.product.family: Dell Pro Laptops dmi.product.name: Dell Pro 3 16 P316260 dmi.product.sku: 0DF5 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/2152688/+subscriptions
[Bug 2029214] Re: pinctrl_emmitsburg module on L-6.2 cause failure to test_095_kernel_symbols_missing_proc_modules in ubuntu_qrt_kernel_security
** Description changed: - Issue found with 6.2.0-26-generic on node grumman from Intel SDP cloud. + Issue for pinctrl_cannonlake module found on: + * intel-server:joliet + * intel-server:mahgo + * intel-ibm-server:manta - Looks like this pinctrl_emmitsburg module does not match the requirement - of test_095_kernel_symbols_missing_proc_modules test in - ubuntu_qrt_kernel_security. + Test log: + ====================================================================== + FAIL: test_095_kernel_symbols_missing_proc_modules (__main__.KernelSecurityTest) + kernel addresses in /proc/modules are zeroed out + ---------------------------------------------------------------------- + Traceback (most recent call last): + File "/var/tmp/qa-regression-testing/scripts/test-kernel-security.py", line 1450, in test_095_kernel_symbols_missing_proc_modules + self._check_pK_files(self._095_kernel_symbols_missing_proc_modules, expected=expected) + File "/var/tmp/qa-regression-testing/scripts/test-kernel-security.py", line 1308, in _check_pK_files + test_function(expected_restricted) + File "/var/tmp/qa-regression-testing/scripts/test-kernel-security.py", line 1348, in _095_kernel_symbols_missing_proc_modules + self.assertTrue(os.path.exists(module_path), + AssertionError: False is not true : Module text section /sys/module/pinctrl_cannonlake/sections/.text does not exist + + + And issue for pinctrl_emmitsburg found on: + * `grumman` from Intel SDP cloud. Test failed with: - $ sudo python3 ./test-kernel-security.py -v KernelSecurityTest.test_095_kernel_symbols_missing_proc_modules + KernelSecurityTest.test_095_kernel_symbols_missing_proc_modules Running test: './test-kernel-security.py' distro: 'Ubuntu 23.04' kernel: '6.2.0-26.26 (Ubuntu 6.2.0-26.26-generic 6.2.13)' arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu') test_095_kernel_symbols_missing_proc_modules (__main__.KernelSecurityTest.test_095_kernel_symbols_missing_proc_modules) kernel addresses in /proc/modules are zeroed out ... (In 4.15+, /proc/modules always zeroed for users) FAIL ====================================================================== FAIL: test_095_kernel_symbols_missing_proc_modules (__main__.KernelSecurityTest.test_095_kernel_symbols_missing_proc_modules) kernel addresses in /proc/modules are zeroed out ---------------------------------------------------------------------- Traceback (most recent call last): - File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 1431, in test_095_kernel_symbols_missing_proc_modules - self._check_pK_files(self._095_kernel_symbols_missing_proc_modules, expected=expected) - File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 1289, in _check_pK_files - test_function(expected_restricted) - File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 1329, in _095_kernel_symbols_missing_proc_modules - self.assertTrue(os.path.exists(module_path), + File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 1431, in test_095_kernel_symbols_missing_proc_modules + self._check_pK_files(self._095_kernel_symbols_missing_proc_modules, expected=expected) + File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 1289, in _check_pK_files + test_function(expected_restricted) + File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 1329, in _095_kernel_symbols_missing_proc_modules + self.assertTrue(os.path.exists(module_path), AssertionError: False is not true : Module text section /sys/module/pinctrl_emmitsburg/sections/.text does not exist ---------------------------------------------------------------------- Ran 1 test in 0.048s FAILED (failures=1) + + + Looks like these modules do not match the requirement of test_095_kernel_symbols_missing_proc_modules test in ubuntu_qrt_kernel_security. + ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26 ProcVersionSignature: User Name 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.2.0-26-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: maas CloudName: maas CloudPlatform: maas CloudSerial: 20230524 CloudSubPlatform: seed-dir (http://192.168.102.22:5248/MAAS/metadata/) CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Aug 1 09:04:34 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: - /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 10000M - /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M - |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/7p, 480M + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 10000M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M + |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/7p, 480M MachineType: Intel Corporation ArcherCity ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=77d6e516-5dd8-4983-9afa-013505099591 ro apparmor=1 RelatedPackageVersions: - linux-restricted-modules-6.2.0-26-generic N/A - linux-backports-modules-6.2.0-26-generic N/A - linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.2 + linux-restricted-modules-6.2.0-26-generic N/A + linux-backports-modules-6.2.0-26-generic N/A + linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: - + dmi.bios.date: 02/26/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: EGSDCRB1.SYS.0100.D09.2302261433 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: ArcherCity dmi.board.vendor: Intel Corporation dmi.board.version: .......... dmi.chassis.asset.tag: .................... dmi.chassis.type: 23 dmi.chassis.vendor: ............................... dmi.chassis.version: .................. dmi.modalias: dmi:bvnIntelCorporation:bvrEGSDCRB1.SYS.0100.D09.2302261433:bd02/26/2023:svnIntelCorporation:pnArcherCity:pvr....................:rvnIntelCorporation:rnArcherCity:rvr..........:cvn...............................:ct23:cvr..................:skuSKUNumber: dmi.product.family: Family dmi.product.name: ArcherCity dmi.product.sku: SKU Number dmi.product.version: .................... dmi.sys.vendor: Intel Corporation ** Tags added: 5.15 jammy ** Summary changed: - pinctrl_emmitsburg module on L-6.2 cause failure to test_095_kernel_symbols_missing_proc_modules in ubuntu_qrt_kernel_security + pinctrl_cannonlake and pinctrl_emmitsburg module cause failure to test_095_kernel_symbols_missing_proc_modules in ubuntu_qrt_kernel_security -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2029214 Title: pinctrl_cannonlake and pinctrl_emmitsburg module cause failure to test_095_kernel_symbols_missing_proc_modules in ubuntu_qrt_kernel_security Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Lunar: Won't Fix Bug description: Issue for pinctrl_cannonlake module found on: * intel-server:joliet * intel-server:mahgo * intel-ibm-server:manta Test log: ====================================================================== FAIL: test_095_kernel_symbols_missing_proc_modules (__main__.KernelSecurityTest) kernel addresses in /proc/modules are zeroed out ---------------------------------------------------------------------- Traceback (most recent call last): File "/var/tmp/qa-regression-testing/scripts/test-kernel-security.py", line 1450, in test_095_kernel_symbols_missing_proc_modules self._check_pK_files(self._095_kernel_symbols_missing_proc_modules, expected=expected) File "/var/tmp/qa-regression-testing/scripts/test-kernel-security.py", line 1308, in _check_pK_files test_function(expected_restricted) File "/var/tmp/qa-regression-testing/scripts/test-kernel-security.py", line 1348, in _095_kernel_symbols_missing_proc_modules self.assertTrue(os.path.exists(module_path), AssertionError: False is not true : Module text section /sys/module/pinctrl_cannonlake/sections/.text does not exist And issue for pinctrl_emmitsburg found on: * `grumman` from Intel SDP cloud. Test failed with: KernelSecurityTest.test_095_kernel_symbols_missing_proc_modules Running test: './test-kernel-security.py' distro: 'Ubuntu 23.04' kernel: '6.2.0-26.26 (Ubuntu 6.2.0-26.26-generic 6.2.13)' arch: 'amd64' init: 'systemd' uid: 0/0 SUDO_USER: 'ubuntu') test_095_kernel_symbols_missing_proc_modules (__main__.KernelSecurityTest.test_095_kernel_symbols_missing_proc_modules) kernel addresses in /proc/modules are zeroed out ... (In 4.15+, /proc/modules always zeroed for users) FAIL ====================================================================== FAIL: test_095_kernel_symbols_missing_proc_modules (__main__.KernelSecurityTest.test_095_kernel_symbols_missing_proc_modules) kernel addresses in /proc/modules are zeroed out ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 1431, in test_095_kernel_symbols_missing_proc_modules self._check_pK_files(self._095_kernel_symbols_missing_proc_modules, expected=expected) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 1289, in _check_pK_files test_function(expected_restricted) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/./test-kernel-security.py", line 1329, in _095_kernel_symbols_missing_proc_modules self.assertTrue(os.path.exists(module_path), AssertionError: False is not true : Module text section /sys/module/pinctrl_emmitsburg/sections/.text does not exist ---------------------------------------------------------------------- Ran 1 test in 0.048s FAILED (failures=1) Looks like these modules do not match the requirement of test_095_kernel_symbols_missing_proc_modules test in ubuntu_qrt_kernel_security. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26 ProcVersionSignature: User Name 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.2.0-26-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: maas CloudName: maas CloudPlatform: maas CloudSerial: 20230524 CloudSubPlatform: seed-dir (http://192.168.102.22:5248/MAAS/metadata/) CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Aug 1 09:04:34 2023 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 10000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 11: Dev 2, If 0, Class=Hub, Driver=hub/7p, 480M MachineType: Intel Corporation ArcherCity ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=77d6e516-5dd8-4983-9afa-013505099591 ro apparmor=1 RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 02/26/2023 dmi.bios.vendor: Intel Corporation dmi.bios.version: EGSDCRB1.SYS.0100.D09.2302261433 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: ArcherCity dmi.board.vendor: Intel Corporation dmi.board.version: .......... dmi.chassis.asset.tag: .................... dmi.chassis.type: 23 dmi.chassis.vendor: ............................... dmi.chassis.version: .................. dmi.modalias: dmi:bvnIntelCorporation:bvrEGSDCRB1.SYS.0100.D09.2302261433:bd02/26/2023:svnIntelCorporation:pnArcherCity:pvr....................:rvnIntelCorporation:rnArcherCity:rvr..........:cvn...............................:ct23:cvr..................:skuSKUNumber: dmi.product.family: Family dmi.product.name: ArcherCity dmi.product.sku: SKU Number dmi.product.version: .................... dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029214/+subscriptions
[Bug 2160707] [NEW] USB timeout : error ehci-pci 110 on probe
Public bug reported: migration from ubuntu 25.10 (kernel 6) to 26.04 (kernel 7) USB mouse and keyboard lost on kernel 7. Booting from kernel 6 OK. Suspecting aggressive timeout limit H61 chipset with 2 separated USB : USB 2.0 EHCI (00:1a.0 / 00:1d.0) dmesg broken kernel / last reboot ➜ ~ journalctl -k -b -1 | grep -iE "usb|xhci|ehci|hid" pci 0000:00:1a.0: quirk_usb_early_handoff+0x0/0x180 took 15857 usecs pci 0000:00:1d.0: quirk_usb_early_handoff+0x0/0x180 took 637663 usecs ehci-pci 0000:00:1d.0: USB bus 3 deregistered ehci-pci 0000:00:1a.0: EHCI Host Controller ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 3 ehci-pci 0000:00:1a.0: debug port 2 ehci-pci 0000:00:1d.0: init 0000:00:1d.0 fail, -110 ehci-pci 0000:00:1d.0: probe with driver ehci-pci failed with error -110 ehci-pci 0000:00:1a.0: irq 23, io mem 0xf7407000 ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 6.14.0-37.37-generic 6.14.11 Uname: Linux 6.14.0-37-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: wil 4230 F.... wireplumber /dev/snd/controlC1: wil 4230 F.... wireplumber /dev/snd/seq: wil 4220 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 15 14:04:01 2026 InstallationDate: Installed on 2021-04-20 (1912 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwDevWlp3s0Link: Not connected. MachineType: ASUSTeK Computer INC. CM6330_CM6630_CM6730_CM6830_M11AA-8 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.14.0-37-generic root=UUID=eb22bd69-70bb-4034-b49a-0def5551424c ro quiet splash usbcore.autosuspend=-1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-07-09 (6 days ago) dmi.bios.date: 01/08/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0904 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM6330_CM6630_CM6730_CM6830_M11AA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0904:bd01/08/2014:br4.6:svnASUSTeKComputerINC.:pnCM6330_CM6630_CM6730_CM6830_M11AA-8:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6330_CM6630_CM6730_CM6830_M11AA:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: Desktop dmi.product.name: CM6330_CM6630_CM6730_CM6830_M11AA-8 dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160707 Title: USB timeout : error ehci-pci 110 on probe Status in linux package in Ubuntu: New Bug description: migration from ubuntu 25.10 (kernel 6) to 26.04 (kernel 7) USB mouse and keyboard lost on kernel 7. Booting from kernel 6 OK. Suspecting aggressive timeout limit H61 chipset with 2 separated USB : USB 2.0 EHCI (00:1a.0 / 00:1d.0) dmesg broken kernel / last reboot ➜ ~ journalctl -k -b -1 | grep -iE "usb|xhci|ehci|hid" pci 0000:00:1a.0: quirk_usb_early_handoff+0x0/0x180 took 15857 usecs pci 0000:00:1d.0: quirk_usb_early_handoff+0x0/0x180 took 637663 usecs ehci-pci 0000:00:1d.0: USB bus 3 deregistered ehci-pci 0000:00:1a.0: EHCI Host Controller ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 3 ehci-pci 0000:00:1a.0: debug port 2 ehci-pci 0000:00:1d.0: init 0000:00:1d.0 fail, -110 ehci-pci 0000:00:1d.0: probe with driver ehci-pci failed with error -110 ehci-pci 0000:00:1a.0: irq 23, io mem 0xf7407000 ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00 ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 6.14.0-37.37-generic 6.14.11 Uname: Linux 6.14.0-37-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: wil 4230 F.... wireplumber /dev/snd/controlC1: wil 4230 F.... wireplumber /dev/snd/seq: wil 4220 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 15 14:04:01 2026 InstallationDate: Installed on 2021-04-20 (1912 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwDevWlp3s0Link: Not connected. MachineType: ASUSTeK Computer INC. CM6330_CM6630_CM6730_CM6830_M11AA-8 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.14.0-37-generic root=UUID=eb22bd69-70bb-4034-b49a-0def5551424c ro quiet splash usbcore.autosuspend=-1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-07-09 (6 days ago) dmi.bios.date: 01/08/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0904 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM6330_CM6630_CM6730_CM6830_M11AA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0904:bd01/08/2014:br4.6:svnASUSTeKComputerINC.:pnCM6330_CM6630_CM6730_CM6830_M11AA-8:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6330_CM6630_CM6730_CM6830_M11AA:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: Desktop dmi.product.name: CM6330_CM6630_CM6730_CM6830_M11AA-8 dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160707/+subscriptions
[Bug 2160704] [NEW] AMD-Vi "Completion-Wait loop timed out" IOMMU hang → full system freeze on 6.8.0-134; regression vs 6.8.0-124 (Ryzen 7 PRO 5850U)
Public bug reported: [Impact] On linux-image-6.8.0-134-generic the AMD IOMMU (AMD-Vi) begins logging "AMD-Vi: Completion-Wait loop timed out" within hours of boot, and the machine then hard-freezes every 3-6 days requiring a physical power cycle: no SSH, dead console, no clean shutdown recorded. The final kernel log line before each freeze is that AMD-Vi timeout. This is a REGRESSION. The immediately prior kernel, 6.8.0-124-generic, is completely clean on the same hardware and identical workload. [Regression evidence: count of "Completion-Wait loop timed out" per boot] 6.8.0-124-generic (Jun 17 -> Jul 4, 17 days) : 0 occurrences, stable 6.8.0-134-generic (Jul 5 -> Jul 11) : 83 occurrences, ended in hard freeze 6.8.0-134-generic (Jul 11 -> Jul 14) : 43 occurrences, ended in hard freeze 6.8.0-134-generic (current boot) : 1 occurrence ~18 min after boot The errors begin a few hours after booting -134 and accumulate until lockup. [Hardware] - Beelink SER5 mini PC - AMD Ryzen 7 PRO 5850U (Cezanne, integrated Radeon Vega / RENOIR amdgpu) - 32 GB RAM, BIOS dated 2024-09-06 - No VFIO / PCI passthrough. No custom kernel command line. - IOMMU default config: "Default domain type: Translated", "DMA domain TLB invalidation policy: lazy mode". [Ruled out] Not OOM (memory healthy, systemd-oomd inactive, zero OOM kills), not disk, not thermal (the thermal_zone0 read failure appears on the good -124 boots too). [Steps to reproduce] 1. Boot 6.8.0-134-generic on the above hardware. 2. Run a normal container / desktop workload (rootless podman, amdgpu active). 3. Within hours "AMD-Vi: Completion-Wait loop timed out" appears in dmesg; within 3-6 days the machine freezes hard. [Expected] No IOMMU completion-wait timeouts and no freeze, as on 6.8.0-124-generic. [Workaround] Reverting to 6.8.0-124-generic eliminates the errors entirely. "amd_iommu=off" is expected to also work (no passthrough in use). [Request] Please bisect the AMD IOMMU changes between 6.8.0-124 and 6.8.0-134, or advise if this is a known regression with a fix in flight. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update ** Attachment added: "Kernel log, 6.8.0-134 boot of Jul 11-14 that ended in a hard freeze — AMD-Vi Completion-Wait timeouts throughout; final kernel line is the timeout." https://bugs.launchpad.net/bugs/2160704/+attachment/5981991/+files/dooku-amdvi-134-prev.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160704 Title: AMD-Vi "Completion-Wait loop timed out" IOMMU hang → full system freeze on 6.8.0-134; regression vs 6.8.0-124 (Ryzen 7 PRO 5850U) Status in linux package in Ubuntu: New Bug description: [Impact] On linux-image-6.8.0-134-generic the AMD IOMMU (AMD-Vi) begins logging "AMD-Vi: Completion-Wait loop timed out" within hours of boot, and the machine then hard-freezes every 3-6 days requiring a physical power cycle: no SSH, dead console, no clean shutdown recorded. The final kernel log line before each freeze is that AMD-Vi timeout. This is a REGRESSION. The immediately prior kernel, 6.8.0-124-generic, is completely clean on the same hardware and identical workload. [Regression evidence: count of "Completion-Wait loop timed out" per boot] 6.8.0-124-generic (Jun 17 -> Jul 4, 17 days) : 0 occurrences, stable 6.8.0-134-generic (Jul 5 -> Jul 11) : 83 occurrences, ended in hard freeze 6.8.0-134-generic (Jul 11 -> Jul 14) : 43 occurrences, ended in hard freeze 6.8.0-134-generic (current boot) : 1 occurrence ~18 min after boot The errors begin a few hours after booting -134 and accumulate until lockup. [Hardware] - Beelink SER5 mini PC - AMD Ryzen 7 PRO 5850U (Cezanne, integrated Radeon Vega / RENOIR amdgpu) - 32 GB RAM, BIOS dated 2024-09-06 - No VFIO / PCI passthrough. No custom kernel command line. - IOMMU default config: "Default domain type: Translated", "DMA domain TLB invalidation policy: lazy mode". [Ruled out] Not OOM (memory healthy, systemd-oomd inactive, zero OOM kills), not disk, not thermal (the thermal_zone0 read failure appears on the good -124 boots too). [Steps to reproduce] 1. Boot 6.8.0-134-generic on the above hardware. 2. Run a normal container / desktop workload (rootless podman, amdgpu active). 3. Within hours "AMD-Vi: Completion-Wait loop timed out" appears in dmesg; within 3-6 days the machine freezes hard. [Expected] No IOMMU completion-wait timeouts and no freeze, as on 6.8.0-124-generic. [Workaround] Reverting to 6.8.0-124-generic eliminates the errors entirely. "amd_iommu=off" is expected to also work (no passthrough in use). [Request] Please bisect the AMD IOMMU changes between 6.8.0-124 and 6.8.0-134, or advise if this is a known regression with a fix in flight. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160704/+subscriptions
[Bug 2160699] [NEW] Thunderbolt: pre-backport v7.2-rc1 refactor to oem-7.0 to avoid future conflicts
Public bug reported: [Impact] The oem-7.0 thunderbolt driver is based on an older tree. Upstream heavily refactored the driver in v7.2-rc1 (NHI struct split, XDomain lifetime and locking rework, path/tunnel allocation changes, plus new USB4STREAM and ConfigFS support). The v7.1 line also carries XDomain property-parser hardening that prevents out-of-bounds reads on malformed XDomain property data (Fixes: cdae7...). If we don't sync the driver first, every future fix we need to backport from v7.2-rc1 or later (security hardening, device quirks, stability fixes) will fail to apply or will conflict badly against the old tree. Backporting the whole refactor now keeps the driver aligned with upstream so later fixes land cleanly. This batch also closes a real gap: without the v7.1 XDomain bounds-check commits, a peer sending oversized or malformed property packets can trigger out-of-bounds reads in tb_property_parse_dir() and the XDomain response copy paths. [Fix] Preemptively backport the thunderbolt refactor plus hardening that landed in v7.1 and v7.2-rc1. Scope: 50 commits total. - 47 are direct upstream backports (10 from v7.1, 37 from v7.2-rc1). - 3 are local adjustments needed to land the series on this tree: * UBUNTU: [Config] Add annotations USB4_{STREAM,CONFIGFS} (enables the two new features; USB4_STREAM=n, USB4_CONFIGFS=m) * UBUNTU: SAUCE: thunderbolt: Fix tb_pci_rescan_work after Move pci_device out of tb_nhi (fixes a reference broken by the NHI struct move) * thunderbolt: Add tb_property_merge_dir() (backported with a forward- declaration conflict resolved against this tree's "Cap recursion depth" change; marked (backported from commit ...) instead of cherry-picked) Key structural upstream changes (all from v7.2-rc1 unless noted): - NHI: Move pci_device out of tb_nhi, Separate out common NHI bits, Require nhi->ops be valid, more descriptive probe errors. - XDomain lifetime/locking: remove from bus without holding tb->lock, keep XDomain reference during a service, add xd->removing guard for delayed work (use-after-free fix), keep domain reference during hotplug. - Path/tunnel: Activate path hops source->destination, tunnel allocation simplification, kzalloc_flex() for tb_path, dma_port flex alloc, improve multi-display DP tunnel allocation. - Router/probe: Read NVM version before quirks, verify Router Ready / Config Ready bits, increase notification + config-ready timeouts, verify PCIe adapter detect state, lane-bonding logging and USB4 v2 bonding fixes. - New features: USB4STREAM, ConfigFS, tb_ring_flush(), service-driver interrupt throttling + own properties. - Hardening (v7.1): validate XDomain request packet size, clamp/limit response copy, bound root directory to block size, reject zero-length property entries. - CLx: disable CLx on Titan Ridge devices with old firmware (v7.1). Upstream versions confirmed via `git tag --contains <hash>`: v7.1 for the 10 hardening/flex/CLx commits v7.2-rc1 for the 37 refactor/feature commits No Launchpad bug is attached yet; this is a proactive driver sync. A tracking bug should be opened for the SRU. [Test Plan] Build the kernel with the new config and verify basic + stressed thunderbolt behavior on a TB3/TB4 capable machine. 1) Build and install; confirm the new options took: $ grep -E 'CONFIG_USB4_(STREAM|CONFIGFS)' /boot/config-$(uname -r) Expect CONFIG_USB4_CONFIGFS=m and CONFIG_USB4_STREAM not set. 2) Cold boot, check the controller enumerates with no errors: $ sudo dmesg | grep -i thunderbolt Expect clean "thunderbolt ... detected" / router enumeration; no WARN/OOPS. 3) Hotplug a Thunderbolt dock/device, then unplug: $ boltctl list $ sudo dmesg | tail Expect the device to appear on plug and disappear on unplug; no kernel error. Repeat plug/unplug 10 times. 4) Connect an external display through the dock (DP tunnel): Expect the display to come up; no "failed to activate path" in dmesg. 5) Suspend/resume with a device plugged: $ sudo rtcwake -m mem -s 20 After resume, boltctl list should still show the device; no oops. 6) (If two TB hosts available) thunderbolt-net: $ sudo modprobe thunderbolt-net Bring up the link and ping across; no crash in tb_service / XDomain paths. Without the series: future v7.2-rc1+ fixes can't be cleanly backported; the v7.1 XDomain parser hardening is also missing (OOB-read exposure). With the series: driver enumerates, tunnels, hotplugs, suspends, and networks as above. [Where problems could occur] This touches core thunderbolt driver structures, so a regression would show up in the thunderbolt driver itself. - NHI rework (Move pci_device out of tb_nhi, common NHI bits, require nhi->ops): if pdev/ops handling is wrong, the driver may fail to probe on some controllers, or tb_pci_rescan_work could deref a stale pointer. dmesg would show a probe failure or NULL deref. - XDomain lifetime/locking (xd->removing, ref during service, remove without tb->lock): if reference counting or the lock guard is wrong, a device disconnect could hit a use-after-free or hang the workqueue. thunderbolt-net and service-based tunnels are the most exposed. - Path/tunnel allocation (kzalloc_flex, allocation simplification, activate hops src->dst): a mistake could fail DP or PCIe tunnel setup ("failed to activate path") or misconfigure hop credits. - CLx on Titan Ridge (v7.1): if the firmware-version condition is inverted, CLx could stay disabled (lower power savings) or get enabled on old firmware and break router enumeration. - USB4STREAM / ConfigFS (new, off by default except ConfigFS=m): if the new module teardown is wrong, rmmod thunderbolt or configfs unmount could oops. - Suspend/resume (tb_domain_release wait, root_switch = NULL on stop): if wrong, resume could hang or oops during domain teardown. [Other Info] - This is a proactive driver sync, not a fix for a single reported failure. - Targets oem-7.0 (Resolute 26.04) only. - 47 commits are upstream (v7.1 / v7.2-rc1); 3 are local (config, SAUCE NHI fixup, manually resolved tb_property_merge_dir backport). - The v7.2-rc1 refactor is the same code that will be in the 7.2 stable kernel; this keeps oem-7.0 aligned so later stable fixes apply cleanly. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-7.0 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Resolute) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-7.0 (Ubuntu Resolute) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Also affects: linux-oem-7.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux-oem-7.0 (Ubuntu Resolute) Importance: Undecided Status: New ** Changed in: linux-oem-7.0 (Ubuntu Resolute) Status: New => In Progress ** Changed in: linux (Ubuntu Resolute) Status: New => Won't Fix ** Changed in: linux-oem-7.0 (Ubuntu Resolute) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160699 Title: Thunderbolt: pre-backport v7.2-rc1 refactor to oem-7.0 to avoid future conflicts Status in linux package in Ubuntu: New Status in linux-oem-7.0 package in Ubuntu: New Status in linux source package in Resolute: Won't Fix Status in linux-oem-7.0 source package in Resolute: In Progress Bug description: [Impact] The oem-7.0 thunderbolt driver is based on an older tree. Upstream heavily refactored the driver in v7.2-rc1 (NHI struct split, XDomain lifetime and locking rework, path/tunnel allocation changes, plus new USB4STREAM and ConfigFS support). The v7.1 line also carries XDomain property-parser hardening that prevents out-of-bounds reads on malformed XDomain property data (Fixes: cdae7...). If we don't sync the driver first, every future fix we need to backport from v7.2-rc1 or later (security hardening, device quirks, stability fixes) will fail to apply or will conflict badly against the old tree. Backporting the whole refactor now keeps the driver aligned with upstream so later fixes land cleanly. This batch also closes a real gap: without the v7.1 XDomain bounds-check commits, a peer sending oversized or malformed property packets can trigger out-of-bounds reads in tb_property_parse_dir() and the XDomain response copy paths. [Fix] Preemptively backport the thunderbolt refactor plus hardening that landed in v7.1 and v7.2-rc1. Scope: 50 commits total. - 47 are direct upstream backports (10 from v7.1, 37 from v7.2-rc1). - 3 are local adjustments needed to land the series on this tree: * UBUNTU: [Config] Add annotations USB4_{STREAM,CONFIGFS} (enables the two new features; USB4_STREAM=n, USB4_CONFIGFS=m) * UBUNTU: SAUCE: thunderbolt: Fix tb_pci_rescan_work after Move pci_device out of tb_nhi (fixes a reference broken by the NHI struct move) * thunderbolt: Add tb_property_merge_dir() (backported with a forward- declaration conflict resolved against this tree's "Cap recursion depth" change; marked (backported from commit ...) instead of cherry-picked) Key structural upstream changes (all from v7.2-rc1 unless noted): - NHI: Move pci_device out of tb_nhi, Separate out common NHI bits, Require nhi->ops be valid, more descriptive probe errors. - XDomain lifetime/locking: remove from bus without holding tb->lock, keep XDomain reference during a service, add xd->removing guard for delayed work (use-after-free fix), keep domain reference during hotplug. - Path/tunnel: Activate path hops source->destination, tunnel allocation simplification, kzalloc_flex() for tb_path, dma_port flex alloc, improve multi-display DP tunnel allocation. - Router/probe: Read NVM version before quirks, verify Router Ready / Config Ready bits, increase notification + config-ready timeouts, verify PCIe adapter detect state, lane-bonding logging and USB4 v2 bonding fixes. - New features: USB4STREAM, ConfigFS, tb_ring_flush(), service-driver interrupt throttling + own properties. - Hardening (v7.1): validate XDomain request packet size, clamp/limit response copy, bound root directory to block size, reject zero-length property entries. - CLx: disable CLx on Titan Ridge devices with old firmware (v7.1). Upstream versions confirmed via `git tag --contains <hash>`: v7.1 for the 10 hardening/flex/CLx commits v7.2-rc1 for the 37 refactor/feature commits No Launchpad bug is attached yet; this is a proactive driver sync. A tracking bug should be opened for the SRU. [Test Plan] Build the kernel with the new config and verify basic + stressed thunderbolt behavior on a TB3/TB4 capable machine. 1) Build and install; confirm the new options took: $ grep -E 'CONFIG_USB4_(STREAM|CONFIGFS)' /boot/config-$(uname -r) Expect CONFIG_USB4_CONFIGFS=m and CONFIG_USB4_STREAM not set. 2) Cold boot, check the controller enumerates with no errors: $ sudo dmesg | grep -i thunderbolt Expect clean "thunderbolt ... detected" / router enumeration; no WARN/OOPS. 3) Hotplug a Thunderbolt dock/device, then unplug: $ boltctl list $ sudo dmesg | tail Expect the device to appear on plug and disappear on unplug; no kernel error. Repeat plug/unplug 10 times. 4) Connect an external display through the dock (DP tunnel): Expect the display to come up; no "failed to activate path" in dmesg. 5) Suspend/resume with a device plugged: $ sudo rtcwake -m mem -s 20 After resume, boltctl list should still show the device; no oops. 6) (If two TB hosts available) thunderbolt-net: $ sudo modprobe thunderbolt-net Bring up the link and ping across; no crash in tb_service / XDomain paths. Without the series: future v7.2-rc1+ fixes can't be cleanly backported; the v7.1 XDomain parser hardening is also missing (OOB-read exposure). With the series: driver enumerates, tunnels, hotplugs, suspends, and networks as above. [Where problems could occur] This touches core thunderbolt driver structures, so a regression would show up in the thunderbolt driver itself. - NHI rework (Move pci_device out of tb_nhi, common NHI bits, require nhi->ops): if pdev/ops handling is wrong, the driver may fail to probe on some controllers, or tb_pci_rescan_work could deref a stale pointer. dmesg would show a probe failure or NULL deref. - XDomain lifetime/locking (xd->removing, ref during service, remove without tb->lock): if reference counting or the lock guard is wrong, a device disconnect could hit a use-after-free or hang the workqueue. thunderbolt-net and service-based tunnels are the most exposed. - Path/tunnel allocation (kzalloc_flex, allocation simplification, activate hops src->dst): a mistake could fail DP or PCIe tunnel setup ("failed to activate path") or misconfigure hop credits. - CLx on Titan Ridge (v7.1): if the firmware-version condition is inverted, CLx could stay disabled (lower power savings) or get enabled on old firmware and break router enumeration. - USB4STREAM / ConfigFS (new, off by default except ConfigFS=m): if the new module teardown is wrong, rmmod thunderbolt or configfs unmount could oops. - Suspend/resume (tb_domain_release wait, root_switch = NULL on stop): if wrong, resume could hang or oops during domain teardown. [Other Info] - This is a proactive driver sync, not a fix for a single reported failure. - Targets oem-7.0 (Resolute 26.04) only. - 47 commits are upstream (v7.1 / v7.2-rc1); 3 are local (config, SAUCE NHI fixup, manually resolved tb_property_merge_dir backport). - The v7.2-rc1 refactor is the same code that will be in the 7.2 stable kernel; this keeps oem-7.0 aligned so later stable fixes apply cleanly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160699/+subscriptions
вторник
[Bug 2160619] Re: amdgpu: DP MST via Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock fails at boot and trigger_hpd_mst_set causes kernel oops
** Description changed: - On a Lenovo laptop with AMD Rembrandt / Radeon 680M, external monitors connected through a Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock often stay dark when the system is booted while already docked. Kernel logs show repeated USB enumeration failures on the dock path, Thunderbolt dock connect/disconnect, amdgpu DP AUX/DPCD/MST link failures, and a warning in dcn31_program_compbuf_size. A manual MST reprobe via /sys/kernel/debug/dri/0000:33:00.0/amdgpu_dm_trigger_hpd_mst caused a reproducible amdgpu kernel oops in trigger_hpd_mst_set. - ``` - - ## Reproduction steps to paste - - ```text - 1. Connect the laptop to a Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock with two external DP monitors attached. - 2. Boot the machine while already docked. - 3. Observe that the external monitors sometimes remain dark. - 4. Check kernel logs for repeated usb 8-1 enumeration failures, Thunderbolt disconnects, and amdgpu MST / AUX / DPCD errors. - - Additional diagnostic reproduction: - 5. When the docked displays are in a working MST state, write "1" to /sys/kernel/debug/dri/0000:33:00.0/amdgpu_dm_trigger_hpd_mst. - 6. Observe a kernel oops in trigger_hpd_mst_set [amdgpu]. - ``` - - ## Expected result - - ```text - The dock should enumerate cleanly during boot, both external monitors should come up reliably, and an MST hotplug reprobe should not crash the kernel. - ``` - - ## Actual result - - ```text - During docked boot, the dock path repeatedly fails USB enumeration, Thunderbolt disconnects after appearing, amdgpu DP MST link setup fails, and the external monitors may remain dark. A manual MST reprobe can trigger a kernel oops in amdgpu. - ``` - - ## High-signal details to include - - - Kernel: `7.0.0-27-generic` - - GPU: `AMD Rembrandt / Radeon 680M` - - BIOS: `R22ET81W (1.51)`, `2026-04-10` - - Dock: `Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock` - - No dock firmware update was offered by `fwupdmgr` - - No system firmware or EC update was pending - - ## Key log lines to mention - - These are the most important patterns: - amdgpu ... [drm] DPIA AUX failed on 0x2c0(1), error 7 - thunderbolt 0-2: device disconnected - amdgpu ... [drm] *ERROR* dpcd_set_link_settings ... - amdgpu ... [drm] *ERROR* Sending link address failed with -5 - WARNING: ... dcn31_program_compbuf_size - [drm:trigger_hpd_mst_set [amdgpu]] *ERROR* DM_MST: Failed to detect dc link! - BUG: unable to handle page fault ... - RIP: trigger_hpd_mst_set+0x13b/0x1b0 [amdgpu] - ``` - - ## Files prepared locally - - - Main report: [UBUNTU_BUGREPORT_DP_DOCK_MST.md](/home/tstocke/gitlab.ethz.ch/eth-config-tool/UBUNTU_BUGREPORT_DP_DOCK_MST.md) - - Filing guide: [UBUNTU_BUGREPORT_DP_DOCK_MST_FILING.md](/home/tstocke/gitlab.ethz.ch/eth-config-tool/UBUNTU_BUGREPORT_DP_DOCK_MST_FILING.md) - - ## Suggested filing workflow - - Run: - - ```bash - ubuntu-bug linux - ``` - - Then in the bug text: - - 1. Use the bug title from this file. - 2. Paste the short summary. - 3. Paste the reproduction steps. - 4. Paste expected and actual result. - 5. Attach or paste the contents of `UBUNTU_BUGREPORT_DP_DOCK_MST.md`. - - ## Optional extra attachments - - If Apport does not automatically gather enough information, attach the output of: - - ```bash - uname -a - journalctl -b -k - sudo lspci -nnk - sudo fwupdmgr get-devices - sudo fwupdmgr get-updates - sudo boltctl list - sudo cat /sys/kernel/debug/dri/0000:33:00.0/amdgpu_mst_topology - ``` - - ## Note - - The `trigger_hpd_mst_set` reprobe was used only as a diagnostic step. It should not be treated as a safe workaround, because it caused a kernel oops on this system. - ```text - usb 8-1: Device not responding to setup address - usb 8-1: device not accepting address ..., error -71 - thunderbolt 0-2: Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock + On a Lenovo laptop with AMD Rembrandt / Radeon 680M, external monitors + connected through a Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock + often stay dark when the system is booted while already docked. Kernel + logs show repeated USB enumeration failures on the dock path, + Thunderbolt dock connect/disconnect, amdgpu DP AUX/DPCD/MST link + failures, and a warning in dcn31_program_compbuf_size. A manual MST + reprobe via /sys/kernel/debug/dri/0000:33:00.0/amdgpu_dm_trigger_hpd_mst + caused a reproducible amdgpu kernel oops in trigger_hpd_mst_set. + + ## Reproduction steps + + 1. Connect the laptop to a Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock with two external DP monitors attached. + 2. Boot the machine while already docked. + 3. Observe that the external monitors sometimes remain dark. + 4. Check kernel logs for repeated usb 8-1 enumeration failures, Thunderbolt disconnects, and amdgpu MST / AUX / DPCD errors. + + Additional diagnostic reproduction: + 5. When the docked displays are in a working MST state, write "1" to /sys/kernel/debug/dri/0000:33:00.0/amdgpu_dm_trigger_hpd_mst. + 6. Observe a kernel oops in trigger_hpd_mst_set [amdgpu]. + + ## Expected result + + The dock should enumerate cleanly during boot, both external monitors + should come up reliably, and an MST hotplug reprobe should not crash the + kernel. + + + ## Actual result + + During docked boot, the dock path repeatedly fails USB enumeration, + Thunderbolt disconnects after appearing, amdgpu DP MST link setup fails, + and the external monitors may remain dark. A manual MST reprobe can + trigger a kernel oops in amdgpu. + + + ## High-signal details to include + + - Kernel: `7.0.0-27-generic` + - GPU: `AMD Rembrandt / Radeon 680M` + - BIOS: `R22ET81W (1.51)`, `2026-04-10` + - Dock: `Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock` + - No dock firmware update was offered by `fwupdmgr` + - No system firmware or EC update was pending + + ## Key log lines to mention + + These are the most important patterns: + amdgpu ... [drm] DPIA AUX failed on 0x2c0(1), error 7 + thunderbolt 0-2: device disconnected + amdgpu ... [drm] *ERROR* dpcd_set_link_settings ... + amdgpu ... [drm] *ERROR* Sending link address failed with -5 + WARNING: ... dcn31_program_compbuf_size + [drm:trigger_hpd_mst_set [amdgpu]] *ERROR* DM_MST: Failed to detect dc link! + BUG: unable to handle page fault ... + RIP: trigger_hpd_mst_set+0x13b/0x1b0 [amdgpu] + + + ## Note + + The `trigger_hpd_mst_set` reprobe was used only as a diagnostic step. It + should not be treated as a safe workaround, because it caused a kernel + oops on this system. + + usb 8-1: Device not responding to setup address + usb 8-1: device not accepting address ..., error -71 + thunderbolt 0-2: Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 14 14:58:10 2026 InstallationDate: Installed on 2025-03-12 (489 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: LENOVO 21CRS08P00 ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm - XDG_RUNTIME_DIR=<set> + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm + XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-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: Upgraded to resolute on 2026-05-08 (67 days ago) dmi.bios.date: 04/10/2026 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: R22ET81W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CRS08P00 dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrR22ET81W(1.51):bd04/10/2026:br1.51:efr1.33:svnLENOVO:pn21CRS08P00:pvrThinkPadT14sGen3:rvnLENOVO:rn21CRS08P00:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CR_BU_Think_FM_ThinkPadT14sGen3:pfaThinkPadT14sGen3: dmi.product.family: ThinkPad T14s Gen 3 dmi.product.name: 21CRS08P00 dmi.product.sku: LENOVO_MT_21CR_BU_Think_FM_ThinkPad T14s Gen 3 dmi.product.version: ThinkPad T14s Gen 3 dmi.sys.vendor: LENOVO -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160619 Title: amdgpu: DP MST via Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock fails at boot and trigger_hpd_mst_set causes kernel oops Status in linux package in Ubuntu: New Bug description: On a Lenovo laptop with AMD Rembrandt / Radeon 680M, external monitors connected through a Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock often stay dark when the system is booted while already docked. Kernel logs show repeated USB enumeration failures on the dock path, Thunderbolt dock connect/disconnect, amdgpu DP AUX/DPCD/MST link failures, and a warning in dcn31_program_compbuf_size. A manual MST reprobe via /sys/kernel/debug/dri/0000:33:00.0/amdgpu_dm_trigger_hpd_mst caused a reproducible amdgpu kernel oops in trigger_hpd_mst_set. ## Reproduction steps 1. Connect the laptop to a Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock with two external DP monitors attached. 2. Boot the machine while already docked. 3. Observe that the external monitors sometimes remain dark. 4. Check kernel logs for repeated usb 8-1 enumeration failures, Thunderbolt disconnects, and amdgpu MST / AUX / DPCD errors. Additional diagnostic reproduction: 5. When the docked displays are in a working MST state, write "1" to /sys/kernel/debug/dri/0000:33:00.0/amdgpu_dm_trigger_hpd_mst. 6. Observe a kernel oops in trigger_hpd_mst_set [amdgpu]. ## Expected result The dock should enumerate cleanly during boot, both external monitors should come up reliably, and an MST hotplug reprobe should not crash the kernel. ## Actual result During docked boot, the dock path repeatedly fails USB enumeration, Thunderbolt disconnects after appearing, amdgpu DP MST link setup fails, and the external monitors may remain dark. A manual MST reprobe can trigger a kernel oops in amdgpu. ## High-signal details to include - Kernel: `7.0.0-27-generic` - GPU: `AMD Rembrandt / Radeon 680M` - BIOS: `R22ET81W (1.51)`, `2026-04-10` - Dock: `Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock` - No dock firmware update was offered by `fwupdmgr` - No system firmware or EC update was pending ## Key log lines to mention These are the most important patterns: amdgpu ... [drm] DPIA AUX failed on 0x2c0(1), error 7 thunderbolt 0-2: device disconnected amdgpu ... [drm] *ERROR* dpcd_set_link_settings ... amdgpu ... [drm] *ERROR* Sending link address failed with -5 WARNING: ... dcn31_program_compbuf_size [drm:trigger_hpd_mst_set [amdgpu]] *ERROR* DM_MST: Failed to detect dc link! BUG: unable to handle page fault ... RIP: trigger_hpd_mst_set+0x13b/0x1b0 [amdgpu] ## Note The `trigger_hpd_mst_set` reprobe was used only as a diagnostic step. It should not be treated as a safe workaround, because it caused a kernel oops on this system. usb 8-1: Device not responding to setup address usb 8-1: device not accepting address ..., error -71 thunderbolt 0-2: Lenovo ThinkPad Universal Thunderbolt 4 Smart Dock ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 14 14:58:10 2026 InstallationDate: Installed on 2025-03-12 (489 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: LENOVO 21CRS08P00 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-27-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: Upgraded to resolute on 2026-05-08 (67 days ago) dmi.bios.date: 04/10/2026 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: R22ET81W (1.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CRS08P00 dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrR22ET81W(1.51):bd04/10/2026:br1.51:efr1.33:svnLENOVO:pn21CRS08P00:pvrThinkPadT14sGen3:rvnLENOVO:rn21CRS08P00:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CR_BU_Think_FM_ThinkPadT14sGen3:pfaThinkPadT14sGen3: dmi.product.family: ThinkPad T14s Gen 3 dmi.product.name: 21CRS08P00 dmi.product.sku: LENOVO_MT_21CR_BU_Think_FM_ThinkPad T14s Gen 3 dmi.product.version: ThinkPad T14s Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160619/+subscriptions