Adding version.log as requested by the kernel bug guidelines. ** Attachment added: "version.log (proc/version_signature + lsb_release -rd + apt-cache policy)" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173885/+attachment/6016719/+files/version.log -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2173885 Title: 7.0.0-43-generic: NULL-pointer page fault in lruvec_stat_mod_folio() during munmap (folio_remove_rmap_ptes -> zap_pte_range), 4 panics in 10 days Status in linux package in Ubuntu: New Bug description: ## Summary Since this machine moved to 7.0.0-42/-43 it has hit a kernel panic 4 times in 10 days (~1 in every 10 boots). Each time the kernel Oopses instantly (Ubuntu's `panic_on_oops=1`), kdump writes a vmcore and the machine reboots. Two different MM/folio code paths are involved. Dumps present in `/var/crash`: `202610311135`, `202611010006`, `202611041154`, `202611101949`. ## Latest Oops (2026-11-10 19:45:52 +0800, uptime 91 s, kernel 7.0.0-43-generic) ``` BUG: unable to handle page fault for address: 000000000002a200 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 1455aa067 P4D 1455aa067 PUD 1455a9067 PMD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 1 UID: 1000 PID: 2913 Comm: Thread-1 (get_m Tainted: G OE 7.0.0-43-generic #43-Ubuntu PREEMPT(lazy) Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: Dell Inc. Precision 5760/0T7J1J, BIOS 1.39.0 03/31/2026 RIP: 0010:lruvec_stat_mod_folio+0x50/0x100 Code: 1c c5 a0 e9 5f a5 e8 cf d1 c7 ff 49 8b 54 24 38 48 89 d0 48 83 e0 f8 83 e2 02 74 04 48 8b 40 10 49 63 d5 48 85 c0 74 63 66 90 <48> 63 8b 00 a2 02 00 4c 8b a4 c8 80 06 00 00 49 83 c4 40 49 3b 9c RSP: 0018:ffffd196ccf7f6f0 EFLAGS: 00010286 RAX: ffff8a2a0816a1c0 RBX: 0000000000000000 RCX: ffff8a2d7260b200 RDX: ffffffffffffffff RSI: 0000000000000011 RDI: fffff27119138640 R13: 00000000ffffffff R14: 0000000000000011 R15: fffff27119138640 CR2: 000000000002a200 Call Trace: <TASK> folio_remove_rmap_ptes+0x41/0x270 zap_present_ptes.constprop.0+0x290/0x750 zap_pte_range+0x1f5/0x780 zap_pmd_range.isra.0+0xce/0x250 unmap_page_range+0x23a/0x3d0 unmap_single_vma+0x96/0x110 unmap_vmas+0xa5/0x180 unmap_region+0xa4/0x110 vms_complete_munmap_vmas+0x1f7/0x280 do_vmi_align_munmap+0x185/0x210 do_vmi_munmap+0xd1/0x1b0 __vm_munmap+0xc1/0x190 __x64_sys_munmap+0x1b/0x30 x64_sys_call+0x22a3/0x2390 do_syscall_64+0x105/0x580 entry_SYSCALL_64_after_hwframe+0x76/0x7e </TASK> ``` Reading of the registers: `RBX=0` and the faulting instruction is `movslq 0x2a200(%rbx),%rcx`, i.e. a NULL base plus a member offset that matches `struct mem_cgroup`; `memcg` obtained from the folio was NULL while the path still dereferenced it. `R13=0xffffffff` (−1) is the stat delta (`-nr_pages` for a single page). The `folio` pointer itself (`R15=fffff27119138640`) is a vmemmap address, so this looks like rmap accounting on a folio that is not charged to any memcg (device-private / special mapping), reached through the plain `munmap()` → `zap_pte_range()` path. The faulting task is a Python thread (`Thread-1 (get_model)`) of a local FunASR STT daemon; the `munmap()` being torn down is a ~928 MB region (`RSI=0x39f3e000`), i.e. it happens while that daemon loads model weights right after boot. The nvidia modules are loaded (taint OE), but no nvidia frame appears anywhere in the stack. ## Earlier panic on the same kernel family (2026-10-31 11:35) ``` RIP: 0010:detach_extent_buffer_folio+0x19 [btrfs] CR2=0x0000200000000018 eb->folios[i] garbage btree_release_folio → filemap_release_folio → shrink_folio_list → balance_pgdat → kswapd ``` So within 10 days two different folio/rmap/reclaim code paths died. Both look like mm regressions rather than hardware (no MCE, no I/O errors, no thermal events in dmesg; memory test not run yet, but the two signatures are in different subsystems). ## System - Ubuntu 26.04 (resolute), `7.0.0-43-generic` (7.0.14 base), 16 threads, 61 GiB RAM, 16 GiB zram - Dell Precision 5760, BIOS 1.39.0 - root on btrfs (`space_cache=v2`, `discard=async`, single device, 712 GiB used / 236 GiB free) - nvidia 595.99.02 (OOT, tainted), virtualbox 7.2.6 - Reproducible only statistically: ~1 panic per 10 boots, always during heavy allocation/free right after boot (FunASR model loading) or during kswapd reclaim ## Why I cannot bisect downwards `7.0.0-31-generic` (installed) boots, but DisplayPort-MST outputs are dead on it: KWin enumerates `eDP-1`, `DP-9`, `DP-11` (the two external monitors sit on i915 DP-MST), windows are placed on the MST outputs and the screens stay black. So 7.0.0-31 is not usable here as a control. ## Secondary issue `kdump-tools` logs `The kernel version is not supported. The makedumpfile operation may be incomplete.` while saving the vmcore (makedumpfile in the kdump initrd is older than the 7.0 kernel). dmesg extraction still works; the compressed dump is 872 MB. ## Questions / request 1. Is this a known regression in 7.0.0-42/-43 (folio/rmap accounting, `lruvec_stat_mod_folio`)? 2. Is there a fix in `-proposed` I can test? 3. I can provide the full dmesg, `/proc/vmcore`-derived dump (872 MB) or run any debug kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173885/+subscriptions
вторник
[Bug 2173885] Re: 7.0.0-43-generic: NULL-pointer page fault in lruvec_stat_mod_folio() during munmap (folio_remove_rmap_ptes -> zap_pte_range), 4 panics in 10 days
Test comment (will be edited): logging system info next. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2173885 Title: 7.0.0-43-generic: NULL-pointer page fault in lruvec_stat_mod_folio() during munmap (folio_remove_rmap_ptes -> zap_pte_range), 4 panics in 10 days Status in linux package in Ubuntu: New Bug description: ## Summary Since this machine moved to 7.0.0-42/-43 it has hit a kernel panic 4 times in 10 days (~1 in every 10 boots). Each time the kernel Oopses instantly (Ubuntu's `panic_on_oops=1`), kdump writes a vmcore and the machine reboots. Two different MM/folio code paths are involved. Dumps present in `/var/crash`: `202610311135`, `202611010006`, `202611041154`, `202611101949`. ## Latest Oops (2026-11-10 19:45:52 +0800, uptime 91 s, kernel 7.0.0-43-generic) ``` BUG: unable to handle page fault for address: 000000000002a200 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 1455aa067 P4D 1455aa067 PUD 1455a9067 PMD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 1 UID: 1000 PID: 2913 Comm: Thread-1 (get_m Tainted: G OE 7.0.0-43-generic #43-Ubuntu PREEMPT(lazy) Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: Dell Inc. Precision 5760/0T7J1J, BIOS 1.39.0 03/31/2026 RIP: 0010:lruvec_stat_mod_folio+0x50/0x100 Code: 1c c5 a0 e9 5f a5 e8 cf d1 c7 ff 49 8b 54 24 38 48 89 d0 48 83 e0 f8 83 e2 02 74 04 48 8b 40 10 49 63 d5 48 85 c0 74 63 66 90 <48> 63 8b 00 a2 02 00 4c 8b a4 c8 80 06 00 00 49 83 c4 40 49 3b 9c RSP: 0018:ffffd196ccf7f6f0 EFLAGS: 00010286 RAX: ffff8a2a0816a1c0 RBX: 0000000000000000 RCX: ffff8a2d7260b200 RDX: ffffffffffffffff RSI: 0000000000000011 RDI: fffff27119138640 R13: 00000000ffffffff R14: 0000000000000011 R15: fffff27119138640 CR2: 000000000002a200 Call Trace: <TASK> folio_remove_rmap_ptes+0x41/0x270 zap_present_ptes.constprop.0+0x290/0x750 zap_pte_range+0x1f5/0x780 zap_pmd_range.isra.0+0xce/0x250 unmap_page_range+0x23a/0x3d0 unmap_single_vma+0x96/0x110 unmap_vmas+0xa5/0x180 unmap_region+0xa4/0x110 vms_complete_munmap_vmas+0x1f7/0x280 do_vmi_align_munmap+0x185/0x210 do_vmi_munmap+0xd1/0x1b0 __vm_munmap+0xc1/0x190 __x64_sys_munmap+0x1b/0x30 x64_sys_call+0x22a3/0x2390 do_syscall_64+0x105/0x580 entry_SYSCALL_64_after_hwframe+0x76/0x7e </TASK> ``` Reading of the registers: `RBX=0` and the faulting instruction is `movslq 0x2a200(%rbx),%rcx`, i.e. a NULL base plus a member offset that matches `struct mem_cgroup`; `memcg` obtained from the folio was NULL while the path still dereferenced it. `R13=0xffffffff` (−1) is the stat delta (`-nr_pages` for a single page). The `folio` pointer itself (`R15=fffff27119138640`) is a vmemmap address, so this looks like rmap accounting on a folio that is not charged to any memcg (device-private / special mapping), reached through the plain `munmap()` → `zap_pte_range()` path. The faulting task is a Python thread (`Thread-1 (get_model)`) of a local FunASR STT daemon; the `munmap()` being torn down is a ~928 MB region (`RSI=0x39f3e000`), i.e. it happens while that daemon loads model weights right after boot. The nvidia modules are loaded (taint OE), but no nvidia frame appears anywhere in the stack. ## Earlier panic on the same kernel family (2026-10-31 11:35) ``` RIP: 0010:detach_extent_buffer_folio+0x19 [btrfs] CR2=0x0000200000000018 eb->folios[i] garbage btree_release_folio → filemap_release_folio → shrink_folio_list → balance_pgdat → kswapd ``` So within 10 days two different folio/rmap/reclaim code paths died. Both look like mm regressions rather than hardware (no MCE, no I/O errors, no thermal events in dmesg; memory test not run yet, but the two signatures are in different subsystems). ## System - Ubuntu 26.04 (resolute), `7.0.0-43-generic` (7.0.14 base), 16 threads, 61 GiB RAM, 16 GiB zram - Dell Precision 5760, BIOS 1.39.0 - root on btrfs (`space_cache=v2`, `discard=async`, single device, 712 GiB used / 236 GiB free) - nvidia 595.99.02 (OOT, tainted), virtualbox 7.2.6 - Reproducible only statistically: ~1 panic per 10 boots, always during heavy allocation/free right after boot (FunASR model loading) or during kswapd reclaim ## Why I cannot bisect downwards `7.0.0-31-generic` (installed) boots, but DisplayPort-MST outputs are dead on it: KWin enumerates `eDP-1`, `DP-9`, `DP-11` (the two external monitors sit on i915 DP-MST), windows are placed on the MST outputs and the screens stay black. So 7.0.0-31 is not usable here as a control. ## Secondary issue `kdump-tools` logs `The kernel version is not supported. The makedumpfile operation may be incomplete.` while saving the vmcore (makedumpfile in the kdump initrd is older than the 7.0 kernel). dmesg extraction still works; the compressed dump is 872 MB. ## Questions / request 1. Is this a known regression in 7.0.0-42/-43 (folio/rmap accounting, `lruvec_stat_mod_folio`)? 2. Is there a fix in `-proposed` I can test? 3. I can provide the full dmesg, `/proc/vmcore`-derived dump (872 MB) or run any debug kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173885/+subscriptions
[Bug 2169304] Re: Regression: systemd-shutdown hangs for 60s at fwupd.shutdown hook under kernel 7.3 (ASUS X580GD)
Confirmed shutdown hook is gone. Can no longer cause issues. test@test-SUT:~$ apt policy fwupd fwupd: Installed: 2.1.6-3ubuntu4~26.04.1 Candidate: 2.1.6-3ubuntu4~26.04.1 Version table: *** 2.1.6-3ubuntu4~26.04.1 100 100 http://archive.ubuntu.com/ubuntu resolute-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.1.1-1ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu resolute-updates/main amd64 Packages 2.1.1-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu resolute/main amd64 Packages test@test-SUT:~$ dpkg -L fwupd | grep shutdown test@test-SUT:~$ ** Tags removed: verification-needed-resolute ** Tags added: verification-done-resolute -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2169304 Title: Regression: systemd-shutdown hangs for 60s at fwupd.shutdown hook under kernel 7.3 (ASUS X580GD) Status in fwupd package in Ubuntu: Fix Released Status in linux package in Ubuntu: Won't Fix Status in fwupd source package in Resolute: Fix Committed Status in linux source package in Resolute: Won't Fix Status in fwupd source package in Stonking: Fix Released Status in linux source package in Stonking: Won't Fix Bug description: [Impact] * fwupd ships a systemd-shutdown hook that runs `fwupdtool activate` very late in shutdown. On some hardware this blocks until a hard 60-second I/O timeout, delaying every shutdown/reboot. This is easily mistaken for a kernel/systemd hang (see this bug, originally filed against linux). * This upload removes the fwupd.shutdown hook entirely (data/fwupd.shutdown.in, its install rule, and the spec %files entry). Delayed activation at shutdown is no longer recommended upstream; devices are activated via the normal daemon/CLI paths instead. Removing the hook removes the only code path that could block shutdown. [Test Plan] 1. Confirm /usr/lib/systemd/system-shutdown/fwupd.shutdown exists before the update, and is gone after upgrading from -proposed. 2. Reboot/shut down a few times and confirm no added delay. 3. Confirm fwupdmgr get-devices/get-updates still work normally. Reporter syldeb35 already confirmed via a PPA build that the hang is gone (comment #8). [Where problems could occur] * A device relying on activation happening specifically at shutdown (rather than next daemon start/boot, or explicit fwupdmgr activate) would have that activation delayed by one cycle, not lost. * Packaging: the hook file simply stops being shipped; no maintainer-script logic depends on it. * Low risk: this deletes a rarely-used, already-discouraged code path with no changes to core daemon/plugin/activation logic. [Other Info] * Upstream fix: fwupd commit f295aead0 "Remove fwupd.shutdown delayed activation". * linux (Ubuntu) is Won't Fix — root cause and fix are in fwupd, not the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/2169304/+subscriptions
понедельник
[Bug 2170572] Re: linux-image-7.0.0-38-generic randomly freezes Lenovo Legion 5
This bug is awaiting verification that the linux/7.3.0-11.12 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-stonking-linux' to 'verification-done-stonking- linux'. If the problem still exists, change the tag 'verification- needed-stonking-linux' to 'verification-failed-stonking-linux'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-stonking-linux-v2 verification-needed-stonking-linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2170572 Title: linux-image-7.0.0-38-generic randomly freezes Lenovo Legion 5 Status in linux package in Ubuntu: Invalid Status in linux source package in Resolute: Fix Committed Status in linux source package in Stonking: Fix Committed Bug description: == SRU Justification == -- Impact An apparmor change in v7.2 caused a NULL pointer validation in some cases. At least one of those happens in a critical section leaving a held lock behind. Which in the end causes the kernel to hang. -- Fix A fix to this was recently released upstream. It would at some point get pulled via stable updates but given the severity of the bug should be given priority. commit 4de32fd05ce9 Author: Maxime Bélair <maxime.belair@canonical.com> Date: Mon Aug 24 17:58:02 2026 +0200 apparmor: fix NULL ctx->peer derefs in unix socket ctx updates -- Test case This seems to require certain HW/setup to happen. And even then might need several restarts. -- Regression potential Anywhere within the area of apparmor controlled socket access. --- original description --- An unattended upgrade from the 7.0.0-31-generic kernel to the 7.0.0-38-generic kernel started causing random freezes on my Lenovo Legion 5 15IAX10 laptop, reverting back to 7.0.0-34-generic seems to fix my issues. I was able to switch to a tty and take a photo (attached), it seems like a kernel bug where CPU is stuck on a spin lock waiting for something. ``` $ grep -C 2 -i "linux-image" /var/log/apt/history.log Start-Date: 2026-10-08 09:10:45 Commandline: /usr/bin/unattended-upgrade Install: linux-modules-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic), linux-image-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic), linux-headers-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic), linux-tools-7.0.0-38:amd64 (7.0.0-38.38, automatic), linux-headers-7.0.0-38:amd64 (7.0.0-38.38, automatic), linux-tools-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic), linux-main-modules-zfs-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic) Upgrade: linux-generic-hwe-24.04:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-image-generic-hwe-26.04:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-tools-common:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-headers-generic:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-perf:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-headers-generic-hwe-26.04:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-generic-hwe-26.04:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-generic:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-image-generic:amd64 (7.0.0-34.34, 7.0.0-38.38), bpftool:amd64 (7.7.0+7.0.0-34.34, 7.7.0+7.0.0-38.38), linux-libc-dev:amd64 (7.0.0-34.34, 7.0.0-38.38) End-Date: 2026-10-08 09:11:28 -- Start-Date: 2026-10-08 09:12:00 Commandline: /usr/bin/unattended-upgrade Remove: linux-image-7.0.0-31-generic:amd64 (7.0.0-31.31), linux-modules-7.0.0-31-generic:amd64 (7.0.0-31.31), linux-main-modules-zfs-7.0.0-31-generic:amd64 (7.0.0-31.31+2) End-Date: 2026-10-08 09:12:06 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170572/+subscriptions
[Bug 2173815] [NEW] CSR8510 USB Bluetooth dongle (0a12:0001) silently hangs after BLE mouse reconnect on 7.0 kernels; fine on 6.8
Public bug reported: TITLE: [regression] CSR8510 USB Bluetooth dongle (0a12:0001) silently hangs after BLE mouse reconnect on 7.0 kernels; fine on 6.8 DESCRIPTION: Summary ------- Since upgrading to Ubuntu 26.04 (kernel 7.0), a CSR8510-based USB Bluetooth dongle stops working after a Bluetooth LE mouse sleeps and reconnects. The adapter stays "powered" and the mouse stays "Connected: yes" in bluetoothctl, but no input arrives, its uhid input device disappears, and new connections fail. Nothing is logged in dmesg or the bluetoothd journal when this happens. Only physically unplugging and replugging the dongle recovers it. Restarting bluetoothd or disconnecting/reconnecting the device does not. Booting the older 6.8 kernel with the same 26.04 userspace (same BlueZ, same dongle, same mouse) avoids the problem completely. Regression evidence ------------------- - 6.8.0-101-generic: 13 days uptime (Oct 27 - Nov 9), 20 mouse sleep/reconnect cycles, zero dongle hangs. - 7.0.0-38-generic: hung roughly daily (Oct 5 - Oct 27); dongle had to be re-plugged 8 times in one boot. - 7.0.0-42-generic: hung within ~50 minutes of boot (Nov 9). Disabling USB autosuspend (btusb enable_autosuspend=0, confirmed active, power/control=on) did NOT help on 7.0.0-38. Hardware -------- - Machine: HP EliteDesk 800 G3 DM 65W - Dongle: TP-Link UB400 (CSR8510) lsusb: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) bcdDevice=88.91, no USB manufacturer/product strings dmesg: "Bluetooth: hci0: CSR: Setting up dongle with HCI ver=6 rev=22bb" "Bluetooth: hci0: LMP ver=6 subver=22bb; manufacturer=10" "Bluetooth: hci0: unexpected event for opcode 0x0000" (at every setup) Driver: btusb (both interfaces) - Mouse: generic "BT5.0 Mouse", BLE HID-over-GATT Modalias usb:v000Ep3412d0400, appearance 0x03c2 Software -------- - Ubuntu 26.04.1 LTS (resolute) - bluez 5.85-4ubuntu0.4 - Bad: linux-image-7.0.0-38-generic, linux-image-7.0.0-42-generic (7.0.0-42.42) - Good: linux-image-6.8.0-101-generic (6.8.0-101.101) Steps to reproduce ------------------ 1. Boot a 7.0 kernel with a CSR8510 dongle and pair a BLE mouse. 2. Leave the mouse idle until it sleeps (minutes to hours). 3. Move the mouse to wake it. Expected: mouse reconnects (as on 6.8). Actual: mouse does nothing; dongle is unresponsive until replugged. No kernel or bluetoothd errors are logged. Notes ----- Possibly related: reports of CSR 0a12:0001 breakage in btusb_setup_csr() on 7.0.x / 7.1.x upstream (CachyOS and Arch forums), although those show "Opcode ... failed: -110" at setup, which does not appear here: setup succeeds and the hang happens later. A btmon capture of the hang can be provided on request. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-42-generic 7.0.0-42.42 ProcVersionSignature: Ubuntu 7.0.0-42.42-generic 7.0.14 Uname: Linux 7.0.0-42-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: jerry 2825 F.... wireplumber /dev/snd/controlC1: jerry 2825 F.... wireplumber /dev/snd/controlC0: jerry 2825 F.... wireplumber /dev/snd/seq: jerry 2816 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 9 16:44:49 2026 InstallationDate: Installed on 2024-02-11 (1003 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP EliteDesk 800 G3 DM 65W ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-42-generic root=UUID=a397f20c-1215-48ea-af0b-fc85938b0709 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-06 (35 days ago) dmi.bios.date: 05/21/2018 dmi.bios.release: 2.19 dmi.bios.vendor: HP dmi.bios.version: P21 Ver. 02.19 dmi.board.name: 829A dmi.board.vendor: HP dmi.board.version: KBC Version 06.21 dmi.chassis.type: 35 dmi.chassis.vendor: HP dmi.ec.firmware.release: 6.33 dmi.modalias: dmi:bvnHP:bvrP21Ver.02.19:bd05/21/2018:br2.19:efr6.33:svnHP:pnHPEliteDesk800G3DM65W:pvr:rvnHP:rn829A:rvrKBCVersion06.21:cvnHP:ct35:cvr:skuY3A18AV:pfa103C_53307FHPEliteDesk: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G3 DM 65W dmi.product.sku: Y3A18AV dmi.sys.vendor: HP ** 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/2173815 Title: CSR8510 USB Bluetooth dongle (0a12:0001) silently hangs after BLE mouse reconnect on 7.0 kernels; fine on 6.8 Status in linux package in Ubuntu: New Bug description: TITLE: [regression] CSR8510 USB Bluetooth dongle (0a12:0001) silently hangs after BLE mouse reconnect on 7.0 kernels; fine on 6.8 DESCRIPTION: Summary ------- Since upgrading to Ubuntu 26.04 (kernel 7.0), a CSR8510-based USB Bluetooth dongle stops working after a Bluetooth LE mouse sleeps and reconnects. The adapter stays "powered" and the mouse stays "Connected: yes" in bluetoothctl, but no input arrives, its uhid input device disappears, and new connections fail. Nothing is logged in dmesg or the bluetoothd journal when this happens. Only physically unplugging and replugging the dongle recovers it. Restarting bluetoothd or disconnecting/reconnecting the device does not. Booting the older 6.8 kernel with the same 26.04 userspace (same BlueZ, same dongle, same mouse) avoids the problem completely. Regression evidence ------------------- - 6.8.0-101-generic: 13 days uptime (Oct 27 - Nov 9), 20 mouse sleep/reconnect cycles, zero dongle hangs. - 7.0.0-38-generic: hung roughly daily (Oct 5 - Oct 27); dongle had to be re-plugged 8 times in one boot. - 7.0.0-42-generic: hung within ~50 minutes of boot (Nov 9). Disabling USB autosuspend (btusb enable_autosuspend=0, confirmed active, power/control=on) did NOT help on 7.0.0-38. Hardware -------- - Machine: HP EliteDesk 800 G3 DM 65W - Dongle: TP-Link UB400 (CSR8510) lsusb: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) bcdDevice=88.91, no USB manufacturer/product strings dmesg: "Bluetooth: hci0: CSR: Setting up dongle with HCI ver=6 rev=22bb" "Bluetooth: hci0: LMP ver=6 subver=22bb; manufacturer=10" "Bluetooth: hci0: unexpected event for opcode 0x0000" (at every setup) Driver: btusb (both interfaces) - Mouse: generic "BT5.0 Mouse", BLE HID-over-GATT Modalias usb:v000Ep3412d0400, appearance 0x03c2 Software -------- - Ubuntu 26.04.1 LTS (resolute) - bluez 5.85-4ubuntu0.4 - Bad: linux-image-7.0.0-38-generic, linux-image-7.0.0-42-generic (7.0.0-42.42) - Good: linux-image-6.8.0-101-generic (6.8.0-101.101) Steps to reproduce ------------------ 1. Boot a 7.0 kernel with a CSR8510 dongle and pair a BLE mouse. 2. Leave the mouse idle until it sleeps (minutes to hours). 3. Move the mouse to wake it. Expected: mouse reconnects (as on 6.8). Actual: mouse does nothing; dongle is unresponsive until replugged. No kernel or bluetoothd errors are logged. Notes ----- Possibly related: reports of CSR 0a12:0001 breakage in btusb_setup_csr() on 7.0.x / 7.1.x upstream (CachyOS and Arch forums), although those show "Opcode ... failed: -110" at setup, which does not appear here: setup succeeds and the hang happens later. A btmon capture of the hang can be provided on request. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-42-generic 7.0.0-42.42 ProcVersionSignature: Ubuntu 7.0.0-42.42-generic 7.0.14 Uname: Linux 7.0.0-42-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: jerry 2825 F.... wireplumber /dev/snd/controlC1: jerry 2825 F.... wireplumber /dev/snd/controlC0: jerry 2825 F.... wireplumber /dev/snd/seq: jerry 2816 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 9 16:44:49 2026 InstallationDate: Installed on 2024-02-11 (1003 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: HP HP EliteDesk 800 G3 DM 65W ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-42-generic root=UUID=a397f20c-1215-48ea-af0b-fc85938b0709 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-06 (35 days ago) dmi.bios.date: 05/21/2018 dmi.bios.release: 2.19 dmi.bios.vendor: HP dmi.bios.version: P21 Ver. 02.19 dmi.board.name: 829A dmi.board.vendor: HP dmi.board.version: KBC Version 06.21 dmi.chassis.type: 35 dmi.chassis.vendor: HP dmi.ec.firmware.release: 6.33 dmi.modalias: dmi:bvnHP:bvrP21Ver.02.19:bd05/21/2018:br2.19:efr6.33:svnHP:pnHPEliteDesk800G3DM65W:pvr:rvnHP:rn829A:rvrKBCVersion06.21:cvnHP:ct35:cvr:skuY3A18AV:pfa103C_53307FHPEliteDesk: dmi.product.family: 103C_53307F HP EliteDesk dmi.product.name: HP EliteDesk 800 G3 DM 65W dmi.product.sku: Y3A18AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173815/+subscriptions
[Bug 2173709] Re: ath9k_htc AR9271 USB Wi-Fi fails to come up on 6.8.0-149 ("Message too long"), works on 6.8.0-139
Daniel I am only seeing 7.0.0-44 in proposed for resolute and not noble at this time -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2173709 Title: ath9k_htc AR9271 USB Wi-Fi fails to come up on 6.8.0-149 ("Message too long"), works on 6.8.0-139 Status in linux package in Ubuntu: Confirmed Bug description: Hardware: Atheros AR9271 USB Wi-Fi adapter (ath9k_htc, firmware htc_9271-1.4.0.fw), Ubuntu 24.04.5, 2014 Mac Mini. On 6.8.0-139-generic the adapter works normally. On 6.8.0-149-generic the firmware loads ("HTC initialized with 33 credits", "FW Version: 1.4") but the interface cannot be brought up: ip link set <iface> up returns "RTNETLINK answers: Message too long", and wpa_supplicant fails with "Could not set interface flags (UP): Message too long" / "Failed to initialize driver interface". An earlier attempt also produced a kernel oops in the driver. The only ath9k changes in 6.8.0-149.149 are "wifi: ath9k: reject short WMI command responses" (CVE-2026-98828) and "wifi: ath9k_htc: bound TX aggregation to MAX_TX_BUF_SIZE". I suspect one of these is rejecting replies from the AR9271 firmware. Not yet tested on 6.8.0-146–148. This is a regression: users have to choose between a working adapter and the CVE-2026-98432 fix, which is only in 149. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139 ProcVersionSignature: Ubuntu 6.8.0-139.139-generic 6.8.12 Uname: Linux 6.8.0-139-generic x86_64 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-139-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Nov 8 22:36:43 2026 InstallationDate: Installed on 2025-10-01 (403 days ago) InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: Apple Inc. Macmini7,1 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-139-generic root=UUID=af466c7b-6c14-44fc-9013-df78fcb3b3f5 ro RelatedPackageVersions: linux-restricted-modules-6.8.0-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 01/13/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 478.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-35C5E08120C7EEAF dmi.board.vendor: Apple Inc. dmi.board.version: Macmini7,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-35C5E08120C7EEAF dmi.modalias: dmi:bvnAppleInc.:bvr478.0.0.0.0:bd01/13/2023:br0.1:svnAppleInc.:pnMacmini7,1:pvr1.0:rvnAppleInc.:rnMac-35C5E08120C7EEAF:rvrMacmini7,1:cvnAppleInc.:ct10:cvrMac-35C5E08120C7EEAF:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: Macmini7,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173709/+subscriptions
[Bug 2111569] Re: No sound via HDMI on older Nvidia card (using nouveau driver)
Reopened as the original information that was requested was given, but neither the requester nor the reporter returned this to the "New" or "Confirmed" state. I have marked it "Confirmed" as it affects multiple users. ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2111569 Title: No sound via HDMI on older Nvidia card (using nouveau driver) Status in linux package in Ubuntu: Confirmed Bug description: My Nvidia card is model GT710. This also happens on a GT 610 card. Both cards are no longer supported by official Nvidia drivers but for a media centre PC they are perfectly fine. Ubuntu 22.04 - video and sound work fine Ubuntu 24.04 - video works but sound does not I am not a very technical user but so far my tests with changing the kernel (in both 22.04 and 24.04) have concluded the following: kernel 6.6.63 and below - sound works well over HDMI kernel 6.7.0 and above - no sound over HDMI I've tried to report this as a kernel bug but I get redirected to Ubuntu, then in the Ubuntu bugs place I have been redirected here. I am managing to use 24.04 successfully at the moment by using an old kernel but this is not ideal. Please help. Many thanks (reported in December 2024 at https://discourse.ubuntu.com/t/no-hdmi-sound-with-older-nvidia-card-nouveau-driver/51540 but with no solution) --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2012-01-21 (4883 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: System manufacturer System Product Name NonfreeKernelModules: lkp_Ubuntu_6_8_0_49_49_generic_112 Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 6.8.0-49.49-generic 6.8.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Tags: noble Uname: Linux 6.8.0-49-generic x86_64 UpgradeStatus: Upgraded to noble on 2024-11-25 (191 days ago) UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare _MarkForUpload: True dmi.bios.date: 10/17/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2011 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A68HM-PLUS 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.:bvr2011:bd10/17/2018:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA68HM-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2012-12-24T00:28:29.410569 mtime.conffile..etc.init.d.apport: 2024-07-22T15:59:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2111569/+subscriptions
[Bug 2173784] Re: ThinkPad T480: intermittent BAT1 capacity collapse (20.03 Wh to 4.98 Wh) after reboot with 7.0.0-43-generic
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2173784 Title: ThinkPad T480: intermittent BAT1 capacity collapse (20.03 Wh to 4.98 Wh) after reboot with 7.0.0-43-generic Status in linux package in Ubuntu: New Bug description: Ubuntu package: linux Suggested title: ThinkPad T480: intermittent BAT1 capacity collapse (20.03 Wh to 4.98 Wh) after reboot with 7.0.0-43-generic System: Lenovo ThinkPad T480, machine type 20L6SARA00 BIOS N24ET81W (1.56), EC N24HT37W Ubuntu/Kubuntu, x86_64 Battery BAT0: SMP 01AV421, internal, design capacity 24.00 Wh Battery BAT1: Celxpert 01AV424, removable, design capacity 24.05 Wh Charge thresholds for both batteries: start 76%, stop 80% Observed issue: On 2026-11-08 at 16:41 CET, BAT1 was discharging normally at 76% with energy_now=15.32 Wh and energy_full=20.03 Wh. After rebooting into 7.0.0-43-generic, a subsequent measurement at 16:53 showed BAT1 status=Not charging, capacity=0%, energy_now=0 Wh, energy_full=4.98 Wh, while BAT0 was discharging. The external battery did not provide power in that state. With AC connected, BAT1 was subsequently reported as Charging at approximately 3.994 W, but its reported energy_full remained 4.98 Wh at that time. On 2026-11-09, after running 7.0.0-42-generic, BAT1 again reported plausible capacity (energy_full=18.29 Wh, energy_now=14.58 Wh, 80%). The user observed BAT1 charging and discharging while using 7.0.0-42-generic. At 18:05 CET with AC disconnected, BAT0 was discharging at 7.876 W while BAT1 remained at 80% and 0 W. A second measurement 25 seconds later showed the same selection. At 18:12 CET after rebooting back into 7.0.0-43-generic without AC, BAT1 still reported energy_full=18.29 Wh, energy_now=14.58 Wh, capacity=80%, status=Not charging, power_now=0. BAT0 was discharging at 9.303 W. Thus the capacity collapse did NOT recur during this reboot. Both batteries were detected by ACPI, and thinkpad_acpi registered both charge thresholds without obvious errors in the filtered kernel log. Expected behavior: BAT1 should retain a consistent, plausible full-charge capacity across reboots and should be available to discharge when selected by the ThinkPad embedded controller. Actual behavior: Intermittent BAT1 capacity reporting collapse to 4.98 Wh/0% after a reboot into 7.0.0-43-generic, with the battery temporarily unavailable for discharge. The failure is not reproducible on every boot. The discharge order of BAT0/BAT1 is controlled by the embedded controller, so BAT1 reporting 0 W while BAT0 discharges is not by itself evidence of failure. Regression status: Possible regression between 7.0.0-42-generic and 7.0.0-43-generic; NOT conclusively established. Other factors, including EC/battery gauge state, may be involved. A later boot into 7.0.0-43-generic did not reproduce the capacity drop. Package history on 2026-11-09: OpenJDK 25 JRE, FreeRDP-related packages, and libnfs14 were updated. No kernel or obvious power-management package update was recorded on that date. Evidence logs: === VOR HERUNTERFAHREN === 2026-11-08T16:41:44+01:00 [BAT0] manufacturer=SMP model_name=01AV421 present=1 status=Not charging capacity=90 energy_now=17570000 energy_full=19630000 energy_full_design=24000000 cycle_count=122 [BAT1] manufacturer=Celxpert model_name=01AV424 present=1 status=Discharging capacity=76 energy_now=15320000 energy_full=20030000 energy_full_design=24050000 cycle_count=107 === NACH NEUSTART === 2026-11-08T16:53:11+01:00 2026-11-08 16:43:58 [BAT0] manufacturer=SMP model_name=01AV421 present=1 status=Discharging capacity=83 energy_now=16290000 energy_full=19630000 energy_full_design=24000000 cycle_count=122 [BAT1] manufacturer=Celxpert model_name=01AV424 present=1 status=Not charging capacity=0 energy_now=0 energy_full=4980000 energy_full_design=24050000 cycle_count=107 [AC] online=0 === NETZTEIL IM LAUFENDEN BETRIEB ANGESCHLOSSEN === 2026-11-08T16:56:19+01:00 [AC] online=1 [BAT0] status=Not charging capacity=80 energy_now=15800000 energy_full=19630000 energy_full_design=24000000 power_now=0 voltage_now=11931000 [BAT1] status=Charging capacity=0 energy_now=10000 energy_full=4980000 energy_full_design=24050000 power_now=3994000 voltage_now=12254000 ===== BASELINE BEFORE BOOTING NEW KERNEL ===== 2026-11-09T18:04:24+01:00 Linux T480 7.0.0-42-generic #42-Ubuntu SMP PREEMPT_DYNAMIC Thu Oct 15 08:06:44 UTC 2026 x86_64 GNU/Linux --- uptime --- 18:04:24 up 37 min, 1 user, load average: 0,46, 0,43, 0,30 --- power supplies --- [AC] online=1 [BAT0] manufacturer=SMP model_name=01AV421 serial_number= 4130 present=1 status=Not charging capacity=77 energy_now=16000000 energy_full=20710000 energy_full_design=24000000 power_now=0 voltage_now=12090000 cycle_count=123 charge_control_start_threshold=76 charge_control_end_threshold=80 [BAT1] manufacturer=Celxpert model_name=01AV424 serial_number= 2418 present=1 status=Not charging capacity=80 energy_now=14580000 energy_full=18290000 energy_full_design=24050000 power_now=0 voltage_now=12219000 cycle_count=108 charge_control_start_threshold=76 charge_control_end_threshold=80 --- installed kernel images --- /boot/vmlinuz-7.0.0-15-generic /boot/vmlinuz-7.0.0-22-generic /boot/vmlinuz-7.0.0-27-generic /boot/vmlinuz-7.0.0-28-generic /boot/vmlinuz-7.0.0-29-generic /boot/vmlinuz-7.0.0-30-generic /boot/vmlinuz-7.0.0-31-generic /boot/vmlinuz-7.0.0-34-generic /boot/vmlinuz-7.0.0-38-generic /boot/vmlinuz-7.0.0-42-generic /boot/vmlinuz-7.0.0-43-generic --- battery-related kernel log --- Nov 09 17:26:46 T480 kernel: ACPI: battery: Slot [BAT0] (battery present) Nov 09 17:26:46 T480 kernel: ACPI: battery: Slot [BAT1] (battery present) Nov 09 17:26:48 T480 kernel: thinkpad_acpi: ThinkPad ACPI Extras v0.26 Nov 09 17:26:48 T480 kernel: thinkpad_acpi: http://ibm-acpi.sf.net/ Nov 09 17:26:48 T480 kernel: thinkpad_acpi: ThinkPad BIOS N24ET81W (1.56 ), EC N24HT37W Nov 09 17:26:48 T480 kernel: thinkpad_acpi: Lenovo ThinkPad T480, model 20L6SARA00 Nov 09 17:26:48 T480 kernel: thinkpad_acpi: radio switch found; radios are enabled Nov 09 17:26:48 T480 kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver Nov 09 17:26:48 T480 kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... Nov 09 17:26:48 T480 kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked Nov 09 17:26:48 T480 kernel: thinkpad_acpi: battery 2 registered (start 76, stop 80, behaviours: 0xb) Nov 09 17:26:48 T480 kernel: thinkpad_acpi: battery 1 registered (start 76, stop 80, behaviours: 0xb) Nov 09 17:26:48 T480 kernel: ACPI: battery: new hook: ThinkPad Battery Extension Nov 09 17:26:48 T480 kernel: input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input8 ===== END BASELINE ===== ===== AC DISCONNECTED: SAMPLE 1 ===== 2026-11-09T18:05:47+01:00 7.0.0-42-generic [AC] online=0 [BAT0] status=Discharging capacity=77 energy_now=15960000 energy_full=20710000 power_now=7876000 voltage_now=11686000 [BAT1] status=Not charging capacity=80 energy_now=14580000 energy_full=18290000 power_now=0 voltage_now=12214000 ===== AC DISCONNECTED: SAMPLE 2 (+25s) ===== 2026-11-09T18:06:12+01:00 7.0.0-42-generic [AC] online=0 [BAT0] status=Discharging capacity=77 energy_now=15890000 energy_full=20710000 power_now=8886000 voltage_now=11739000 [BAT1] status=Not charging capacity=80 energy_now=14580000 energy_full=18290000 power_now=0 voltage_now=12214000 ===== AFTER REBOOT: NEW KERNEL ===== 2026-11-09T18:12:27+01:00 Linux T480 7.0.0-43-generic #43-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 23 13:25:25 UTC 2026 x86_64 GNU/Linux 18:12:27 up 1 min, 1 user, load average: 1,43, 0,55, 0,20 [AC] online=0 [BAT0] manufacturer=SMP model_name=01AV421 serial_number= 4130 present=1 status=Discharging capacity=71 energy_now=14780000 energy_full=20710000 energy_full_design=24000000 power_now=9303000 voltage_now=11209000 cycle_count=123 charge_control_start_threshold=76 charge_control_end_threshold=80 [BAT1] manufacturer=Celxpert model_name=01AV424 serial_number= 2418 present=1 status=Not charging capacity=80 energy_now=14580000 energy_full=18290000 energy_full_design=24050000 power_now=0 voltage_now=12214000 cycle_count=108 charge_control_start_threshold=76 charge_control_end_threshold=80 --- relevant kernel messages --- Nov 09 18:10:38 T480 kernel: ACPI: battery: Slot [BAT1] (battery present) Nov 09 18:10:38 T480 kernel: ACPI: battery: Slot [BAT0] (battery present) Nov 09 18:10:39 T480 kernel: thinkpad_acpi: ThinkPad ACPI Extras v0.26 Nov 09 18:10:39 T480 kernel: thinkpad_acpi: http://ibm-acpi.sf.net/ Nov 09 18:10:39 T480 kernel: thinkpad_acpi: ThinkPad BIOS N24ET81W (1.56 ), EC N24HT37W Nov 09 18:10:39 T480 kernel: thinkpad_acpi: Lenovo ThinkPad T480, model 20L6SARA00 Nov 09 18:10:39 T480 kernel: thinkpad_acpi: radio switch found; radios are enabled Nov 09 18:10:39 T480 kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver Nov 09 18:10:39 T480 kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... Nov 09 18:10:39 T480 kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked Nov 09 18:10:39 T480 kernel: thinkpad_acpi: battery 1 registered (start 76, stop 80, behaviours: 0xb) Nov 09 18:10:39 T480 kernel: thinkpad_acpi: battery 2 registered (start 76, stop 80, behaviours: 0xb) Nov 09 18:10:39 T480 kernel: ACPI: battery: new hook: ThinkPad Battery Extension Nov 09 18:10:39 T480 kernel: input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input6 ===== END AFTER REBOOT ===== ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: klaus 2637 F.... wireplumber /dev/snd/seq: klaus 2633 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Nov 9 18:21:58 2026 InstallationDate: Installed on 2026-04-28 (195 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) MachineType: LENOVO 20L6SARA00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-7.0.0-43-generic root=UUID=c333d985-1c81-4f31-a2cc-67a7e1ffb212 ro rootflags=subvol=@ quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2025 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET81W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6SARA00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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.22 dmi.modalias: dmi:bvnLENOVO:bvrN24ET81W(1.56):bd09/06/2025:br1.56:efr1.22:svnLENOVO:pn20L6SARA00:pvrThinkPadT480:rvnLENOVO:rn20L6SARA00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L6_BU_Think_FM_ThinkPadT480:pfaThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6SARA00 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173784/+subscriptions
[Bug 2173787] Re: Failure to suspend due to bluetooth btintel_pcie
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2173787 Title: Failure to suspend due to bluetooth btintel_pcie Status in linux package in Ubuntu: New Bug description: Hi, I have been experiencing failures to suspend the (Lunar Lake-based Intel) laptop due to bluetooth issues. 2026-11-09T02:41:40.095514+00:00 efortune systemd[1]: Reached target sleep.target - Sleep. 2026-11-09T02:41:40.097895+00:00 efortune systemd[1]: Starting systemd-suspend.service - System Suspend... 2026-11-09T02:41:40.129293+00:00 efortune systemd[1]: session-c5.scope: Unit now frozen-by-parent. 2026-11-09T02:41:40.129497+00:00 efortune systemd[1]: user-1002.slice: Unit now frozen-by-parent. 2026-11-09T02:41:40.129595+00:00 efortune systemd[1]: user@1002.service: Unit now frozen-by-parent. 2026-11-09T02:41:40.129648+00:00 efortune systemd[1]: user@1000.service: Unit now frozen-by-parent. 2026-11-09T02:41:40.129705+00:00 efortune systemd[1]: user.slice: Unit now frozen. 2026-11-09T02:41:40.129762+00:00 efortune systemd[1]: user-1000.slice: Unit now frozen-by-parent. 2026-11-09T02:41:40.129819+00:00 efortune systemd[1]: session-2.scope: Unit now frozen-by-parent. 2026-11-09T02:41:40.130373+00:00 efortune systemd-sleep[302392]: Successfully froze unit 'user.slice'. 2026-11-09T02:41:40.143002+00:00 efortune systemd-sleep[302392]: Performing sleep operation 'suspend'... 2026-11-09T02:41:40.143277+00:00 efortune kernel: PM: suspend entry (s2idle) 2026-11-09T02:41:40.151279+00:00 efortune kernel: Filesystems sync: 0.007 seconds 2026-11-09T02:41:40.666313+00:00 efortune kernel: Bluetooth: hci0: Timeout (500 ms) on tx completion 2026-11-09T02:41:40.666348+00:00 efortune kernel: Bluetooth: hci0: Failed to send frame (-62) 2026-11-09T02:41:40.666351+00:00 efortune kernel: Bluetooth: hci0: sending frame failed (-62) 2026-11-09T02:41:40.666353+00:00 efortune kernel: Bluetooth: hci0: Opcode 0x2042 failed: -62 2026-11-09T02:41:40.666354+00:00 efortune kernel: Bluetooth: hci0: Unable to disable scanning: -62 2026-11-09T02:41:42.487470+00:00 efortune kernel: Freezing user space processes 2026-11-09T02:41:42.487515+00:00 efortune kernel: Freezing user space processes completed (elapsed 0.017 seconds) 2026-11-09T02:41:42.487516+00:00 efortune kernel: OOM killer disabled. 2026-11-09T02:41:42.487518+00:00 efortune kernel: Freezing remaining freezable tasks 2026-11-09T02:41:42.487519+00:00 efortune kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds) 2026-11-09T02:41:42.487520+00:00 efortune kernel: printk: Suspending console(s) (use no_console_suspend to debug) 2026-11-09T02:41:42.487521+00:00 efortune kernel: Bluetooth: hci0: Timeout (200 ms) on alive interrupt for D2 entry, retry count 0 2026-11-09T02:41:42.487522+00:00 efortune kernel: Bluetooth: hci0: Timeout (200 ms) on alive interrupt for D2 entry, retry count 1 2026-11-09T02:41:42.487523+00:00 efortune kernel: Bluetooth: hci0: Timeout (200 ms) on alive interrupt for D2 entry, retry count 2 2026-11-09T02:41:42.487524+00:00 efortune kernel: btintel_pcie 0000:00:14.7: PM: pci_pm_suspend(): btintel_pcie_suspend [btintel_pcie] returns -16 2026-11-09T02:41:42.487525+00:00 efortune kernel: btintel_pcie 0000:00:14.7: PM: dpm_run_callback(): pci_pm_suspend returns -16 2026-11-09T02:41:42.487526+00:00 efortune kernel: btintel_pcie 0000:00:14.7: PM: failed to suspend async: error -16 2026-11-09T02:41:42.487528+00:00 efortune kernel: PM: Some devices failed to suspend, or early wake event detected 2026-11-09T02:41:42.487529+00:00 efortune kernel: intel_pmc_ssram_telemetry 0000:00:14.2: enabling device (0000 -> 0002) 2026-11-09T02:41:42.487530+00:00 efortune kernel: nvme nvme0: 8/0/0 default/read/poll queues If I remove the bluetooth modules (rmmod btintel bluetooth btintel_pcie ), i can suspend without issues. From what I can see there is a kernel issue: https://bugzilla.kernel.org/show_bug.cgi?id=221481 but it has no resolution. Thanks, Sergey PS I don't think I need to include extra info here, but I am talking about ubuntu 26.04.1 with 7.0.0-43-generic kernel ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: koposov 8670 F.... pipewire koposov 8676 F.... wireplumber /dev/snd/seq: koposov 8670 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 9 18:02:42 2026 InstallationDate: Installed on 2026-04-01 (222 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: LENOVO 21NS00MMUK ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=e74f9dd5-fd08-4ed9-8858-517f051cb7c9 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-10 (152 days ago) dmi.bios.date: 08/12/2026 dmi.bios.release: 1.48 dmi.bios.vendor: LENOVO dmi.bios.version: N4BET78W (1.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 21NS00MMUK dmi.board.vendor: LENOVO dmi.board.version: SDK0T76576 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.41 dmi.modalias: dmi:bvnLENOVO:bvrN4BET78W(1.48):bd08/12/2026:br1.48:efr1.41:svnLENOVO:pn21NS00MMUK:pvrThinkPadX1CarbonGen13:rvnLENOVO:rn21NS00MMUK:rvrSDK0T76576WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21NS_BU_Think_FM_ThinkPadX1CarbonGen13:pfaThinkPadX1CarbonGen13: dmi.product.family: ThinkPad X1 Carbon Gen 13 dmi.product.name: 21NS00MMUK dmi.product.sku: LENOVO_MT_21NS_BU_Think_FM_ThinkPad X1 Carbon Gen 13 dmi.product.version: ThinkPad X1 Carbon Gen 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173787/+subscriptions
воскресенье
[Bug 2173709] Re: ath9k_htc AR9271 USB Wi-Fi fails to come up on 6.8.0-149 ("Message too long"), works on 6.8.0-139
** Attachment added: "Crash log 149" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173709/+attachment/6016162/+files/kernel-6.8.0-149-oops.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2173709 Title: ath9k_htc AR9271 USB Wi-Fi fails to come up on 6.8.0-149 ("Message too long"), works on 6.8.0-139 Status in linux package in Ubuntu: New Bug description: Hardware: Atheros AR9271 USB Wi-Fi adapter (ath9k_htc, firmware htc_9271-1.4.0.fw), Ubuntu 24.04.5, 2014 Mac Mini. On 6.8.0-139-generic the adapter works normally. On 6.8.0-149-generic the firmware loads ("HTC initialized with 33 credits", "FW Version: 1.4") but the interface cannot be brought up: ip link set <iface> up returns "RTNETLINK answers: Message too long", and wpa_supplicant fails with "Could not set interface flags (UP): Message too long" / "Failed to initialize driver interface". An earlier attempt also produced a kernel oops in the driver. The only ath9k changes in 6.8.0-149.149 are "wifi: ath9k: reject short WMI command responses" (CVE-2026-98828) and "wifi: ath9k_htc: bound TX aggregation to MAX_TX_BUF_SIZE". I suspect one of these is rejecting replies from the AR9271 firmware. Not yet tested on 6.8.0-146–148. This is a regression: users have to choose between a working adapter and the CVE-2026-98432 fix, which is only in 149. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139 ProcVersionSignature: Ubuntu 6.8.0-139.139-generic 6.8.12 Uname: Linux 6.8.0-139-generic x86_64 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-139-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Nov 8 22:36:43 2026 InstallationDate: Installed on 2025-10-01 (403 days ago) InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: Apple Inc. Macmini7,1 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-139-generic root=UUID=af466c7b-6c14-44fc-9013-df78fcb3b3f5 ro RelatedPackageVersions: linux-restricted-modules-6.8.0-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 01/13/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 478.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-35C5E08120C7EEAF dmi.board.vendor: Apple Inc. dmi.board.version: Macmini7,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-35C5E08120C7EEAF dmi.modalias: dmi:bvnAppleInc.:bvr478.0.0.0.0:bd01/13/2023:br0.1:svnAppleInc.:pnMacmini7,1:pvr1.0:rvnAppleInc.:rnMac-35C5E08120C7EEAF:rvrMacmini7,1:cvnAppleInc.:ct10:cvrMac-35C5E08120C7EEAF:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: Macmini7,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173709/+subscriptions
[Bug 2173709] Re: ath9k_htc AR9271 USB Wi-Fi fails to come up on 6.8.0-149 ("Message too long"), works on 6.8.0-139
The wl module is Broadcom STA for the unused built-in Wi-Fi (wlp2s0). The failing device is the separate USB AR9271 on ath9k_htc. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2173709 Title: ath9k_htc AR9271 USB Wi-Fi fails to come up on 6.8.0-149 ("Message too long"), works on 6.8.0-139 Status in linux package in Ubuntu: New Bug description: Hardware: Atheros AR9271 USB Wi-Fi adapter (ath9k_htc, firmware htc_9271-1.4.0.fw), Ubuntu 24.04.5, 2014 Mac Mini. On 6.8.0-139-generic the adapter works normally. On 6.8.0-149-generic the firmware loads ("HTC initialized with 33 credits", "FW Version: 1.4") but the interface cannot be brought up: ip link set <iface> up returns "RTNETLINK answers: Message too long", and wpa_supplicant fails with "Could not set interface flags (UP): Message too long" / "Failed to initialize driver interface". An earlier attempt also produced a kernel oops in the driver. The only ath9k changes in 6.8.0-149.149 are "wifi: ath9k: reject short WMI command responses" (CVE-2026-98828) and "wifi: ath9k_htc: bound TX aggregation to MAX_TX_BUF_SIZE". I suspect one of these is rejecting replies from the AR9271 firmware. Not yet tested on 6.8.0-146–148. This is a regression: users have to choose between a working adapter and the CVE-2026-98432 fix, which is only in 149. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139 ProcVersionSignature: Ubuntu 6.8.0-139.139-generic 6.8.12 Uname: Linux 6.8.0-139-generic x86_64 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-139-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Nov 8 22:36:43 2026 InstallationDate: Installed on 2025-10-01 (403 days ago) InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: Apple Inc. Macmini7,1 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-139-generic root=UUID=af466c7b-6c14-44fc-9013-df78fcb3b3f5 ro RelatedPackageVersions: linux-restricted-modules-6.8.0-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 01/13/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 478.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-35C5E08120C7EEAF dmi.board.vendor: Apple Inc. dmi.board.version: Macmini7,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-35C5E08120C7EEAF dmi.modalias: dmi:bvnAppleInc.:bvr478.0.0.0.0:bd01/13/2023:br0.1:svnAppleInc.:pnMacmini7,1:pvr1.0:rvnAppleInc.:rnMac-35C5E08120C7EEAF:rvrMacmini7,1:cvnAppleInc.:ct10:cvrMac-35C5E08120C7EEAF:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: Macmini7,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173709/+subscriptions
[Bug 2173709] [NEW] ath9k_htc AR9271 USB Wi-Fi fails to come up on 6.8.0-149 ("Message too long"), works on 6.8.0-139
Public bug reported: Hardware: Atheros AR9271 USB Wi-Fi adapter (ath9k_htc, firmware htc_9271-1.4.0.fw), Ubuntu 24.04.5, 2014 Mac Mini. On 6.8.0-139-generic the adapter works normally. On 6.8.0-149-generic the firmware loads ("HTC initialized with 33 credits", "FW Version: 1.4") but the interface cannot be brought up: ip link set <iface> up returns "RTNETLINK answers: Message too long", and wpa_supplicant fails with "Could not set interface flags (UP): Message too long" / "Failed to initialize driver interface". An earlier attempt also produced a kernel oops in the driver. The only ath9k changes in 6.8.0-149.149 are "wifi: ath9k: reject short WMI command responses" (CVE-2026-98828) and "wifi: ath9k_htc: bound TX aggregation to MAX_TX_BUF_SIZE". I suspect one of these is rejecting replies from the AR9271 firmware. Not yet tested on 6.8.0-146–148. This is a regression: users have to choose between a working adapter and the CVE-2026-98432 fix, which is only in 149. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139 ProcVersionSignature: Ubuntu 6.8.0-139.139-generic 6.8.12 Uname: Linux 6.8.0-139-generic x86_64 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-139-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Nov 8 22:36:43 2026 InstallationDate: Installed on 2025-10-01 (403 days ago) InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: Apple Inc. Macmini7,1 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-139-generic root=UUID=af466c7b-6c14-44fc-9013-df78fcb3b3f5 ro RelatedPackageVersions: linux-restricted-modules-6.8.0-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 01/13/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 478.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-35C5E08120C7EEAF dmi.board.vendor: Apple Inc. dmi.board.version: Macmini7,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-35C5E08120C7EEAF dmi.modalias: dmi:bvnAppleInc.:bvr478.0.0.0.0:bd01/13/2023:br0.1:svnAppleInc.:pnMacmini7,1:pvr1.0:rvnAppleInc.:rnMac-35C5E08120C7EEAF:rvrMacmini7,1:cvnAppleInc.:ct10:cvrMac-35C5E08120C7EEAF:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: Macmini7,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2173709 Title: ath9k_htc AR9271 USB Wi-Fi fails to come up on 6.8.0-149 ("Message too long"), works on 6.8.0-139 Status in linux package in Ubuntu: New Bug description: Hardware: Atheros AR9271 USB Wi-Fi adapter (ath9k_htc, firmware htc_9271-1.4.0.fw), Ubuntu 24.04.5, 2014 Mac Mini. On 6.8.0-139-generic the adapter works normally. On 6.8.0-149-generic the firmware loads ("HTC initialized with 33 credits", "FW Version: 1.4") but the interface cannot be brought up: ip link set <iface> up returns "RTNETLINK answers: Message too long", and wpa_supplicant fails with "Could not set interface flags (UP): Message too long" / "Failed to initialize driver interface". An earlier attempt also produced a kernel oops in the driver. The only ath9k changes in 6.8.0-149.149 are "wifi: ath9k: reject short WMI command responses" (CVE-2026-98828) and "wifi: ath9k_htc: bound TX aggregation to MAX_TX_BUF_SIZE". I suspect one of these is rejecting replies from the AR9271 firmware. Not yet tested on 6.8.0-146–148. This is a regression: users have to choose between a working adapter and the CVE-2026-98432 fix, which is only in 149. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-139-generic 6.8.0-139.139 ProcVersionSignature: Ubuntu 6.8.0-139.139-generic 6.8.12 Uname: Linux 6.8.0-139-generic x86_64 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.8.0-139-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Nov 8 22:36:43 2026 InstallationDate: Installed on 2025-10-01 (403 days ago) InstallationMedia: Ubuntu-Server 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: Apple Inc. Macmini7,1 ProcEnviron: LANG=en_GB.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-139-generic root=UUID=af466c7b-6c14-44fc-9013-df78fcb3b3f5 ro RelatedPackageVersions: linux-restricted-modules-6.8.0-139-generic N/A linux-backports-modules-6.8.0-139-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 01/13/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 478.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-35C5E08120C7EEAF dmi.board.vendor: Apple Inc. dmi.board.version: Macmini7,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-35C5E08120C7EEAF dmi.modalias: dmi:bvnAppleInc.:bvr478.0.0.0.0:bd01/13/2023:br0.1:svnAppleInc.:pnMacmini7,1:pvr1.0:rvnAppleInc.:rnMac-35C5E08120C7EEAF:rvrMacmini7,1:cvnAppleInc.:ct10:cvrMac-35C5E08120C7EEAF:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: Macmini7,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173709/+subscriptions
[Bug 2172229] Re: AppArmor: profile attachment fails for diff-encoded xmatch DFAs (leftmatch_fb ignores MATCH_FLAG_DIFF_ENCODE) - firefox profile never attaches
Also affected on 26.04, kernel 7.0.0-43-generic, apparmor 5.0.2-0ubuntu1~26.04.1, Firefox deb from ppa:mozillateam. Please nominate for Resolute. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172229 Title: AppArmor: profile attachment fails for diff-encoded xmatch DFAs (leftmatch_fb ignores MATCH_FLAG_DIFF_ENCODE) - firefox profile never attaches Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Profiles whose attachment pattern compiles to a differentially encoded DFA never attach. The exec stays "unconfined", and because no conflict is involved, nothing is audited. Visible example: /etc/apparmor.d/firefox (from the apparmor package) profile firefox /{usr/lib/firefox{,-esr,-beta,-devedition,-nightly},opt/firefox}/firefox{,-esr,-bin} flags=(unconfined) { userns, ... } never attaches to /usr/lib/firefox/firefox-bin (Firefox .deb from packages.mozilla.org). Firefox therefore runs unconfined and is moved to unprivileged_userns, which denies CAP_SYS_ADMIN. Its content sandbox loses user-namespace isolation: apparmor="AUDIT" operation="userns_create" info="Userns create - transitioning profile" profile="unconfined" comm="firefox-bin" target="unprivileged_userns" execpath="/usr/lib/firefox/firefox-bin" apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" comm="firefox-bin" capability=21 capname="sys_admin" ps -eo label,args shows "unconfined" for every firefox-bin process, although "firefox (unconfined)" is loaded. [Cause] security/apparmor/match.c: leftmatch_fb(), used by aa_dfa_leftmatch() and therefore by find_attach(), takes the default transition as if (check[pos] == state) state = next[pos]; else state = def[state]; and moves on to the next input character. It does not handle MATCH_FLAG_DIFF_ENCODE. match_char(), used by aa_dfa_match() for file rules, does: for a diff-encoded state it follows def[state] and retries the SAME character. apparmor_parser emits diff-encoded DFAs by default whenever the kernel advertises policy/diff_encode (it does), so larger attachment patterns end in a non-accepting state. File rules are not affected, since they go through match_char(). Simple attachments (plain paths, "/a/{b,c}/x", "/a/x{,-y}", "/{,usr/}{,s}bin/unix_chkpwd") still attach. Larger or nested alternations fail. [Test case] The attached aa-repro.sh (run as root) loads the firefox profile's attachment pattern, relocated to a scratch directory, twice: once with default options and once with "-O no-diff-encode". It then executes a copy of dash under each path and prints /proc/$$/attr/current. Expected: enc -> repro_enc (unconfined) noenc -> repro_noenc (unconfined) Actual: enc -> unconfined noenc -> repro_noenc (unconfined) The two profiles differ only in diff encoding. Reproduced on the stock 7.0.0-38-generic kernel (output attached as repro- output-7.0.0-38-generic.txt). Further confirmation: Ubuntu's real firefox profile does not attach, while a copy with the simpler attachment /usr/lib/firefox/firefox{,-bin} does. [Workarounds] - Set "Optimize=no-diff-encode" in /etc/apparmor/parser.conf and reload all profiles. - Alternatively, add a local profile with a simpler attachment, e.g. /usr/lib/firefox/firefox{,-bin}. [Suggested fix - untested] In leftmatch_fb(), compute the input byte first (c = equiv[(u8) *str++] or (u8) *str++), then replace the open-coded transition with match_char(state, def, base, next, check, c), as aa_dfa_match() does. The is_loop() history and longest-left count logic should then be reviewed for diff-encoded default chains. Upstream report: https://gitlab.com/apparmor/apparmor- kernel/-/work_items/8 [Environment] Ubuntu 26.04.1 LTS (resolute) linux-image-7.0.0-38-generic 7.0.0-38.38 (/proc/version_signature: Ubuntu 7.0.0-38.38-generic 7.0.14) apparmor / libapparmor1 5.0.2-0ubuntu1~26.04.1 firefox 158.0.1~build1 (packages.mozilla.org) /sys/kernel/security/apparmor/features/policy/diff_encode: yes --- ProblemType: Bug ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: invarianz 1478 F.... wireplumber /dev/snd/controlC1: invarianz 1478 F.... wireplumber /dev/snd/seq: invarianz 1454 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 InstallationDate: Installed on 2026-06-27 (121 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 30DH00H7GE Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-38-generic root=UUID=3c69bedc-0154-4019-a8e3-99860442ddb8 ro quiet splash ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 RebootRequiredPkgs: Error: path contained symlinks. Tags: resolute wayland-session Uname: Linux 7.0.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sudo users _MarkForUpload: True dmi.bios.date: 03/21/2025 dmi.bios.release: 1.94 dmi.bios.vendor: LENOVO dmi.bios.version: S08KT5EA dmi.board.name: 1048 dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN 3305348596304 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrS08KT5EA:bd03/21/2025:br1.94:efr1.12:svnLENOVO:pn30DH00H7GE:pvrThinkStationP340:rvnLENOVO:rn1048:rvrSDK0T08861WIN3305348596304:cvnLENOVO:ct3:cvrNone:skuLENOVO_MT_30DH_BU_Think_FM_ThinkStationP340:pfaThinkStationP340: dmi.product.family: ThinkStation P340 dmi.product.name: 30DH00H7GE dmi.product.sku: LENOVO_MT_30DH_BU_Think_FM_ThinkStation P340 dmi.product.version: ThinkStation P340 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172229/+subscriptions