Public bug reported:

TITLE
Intel AX211 Bluetooth firmware download fails with -38 on 7.0.0-29-generic
(regression; works on 7.0.0-28-generic)

PACKAGE
linux-image-7.0.0-29-generic 7.0.0-29.29

SUMMARY
After upgrading to kernel 7.0.0-29-generic, the Intel AX211 Bluetooth
controller fails to complete firmware download and the adapter never
registers. The same hardware, with the same firmware file and the same
firmware version, initialises successfully on 7.0.0-28-generic. This is a
kernel regression - no firmware or userspace package changed between the
working and failing boots.

SYSTEM
  Ubuntu:          26.04 LTS (resolute), 26.04
  Machine:         Framework Laptop 12 (13th Gen Intel Core), system version A5
  BIOS:            03.07
  CPU:             13th Gen Intel(R) Core(TM) i5-1334U
  WiFi/BT combo:   Intel Corporation Raptor Lake PCH CNVi WiFi [8086:51f1] (rev 
01)
  Bluetooth:       Bus 003 Device 003: ID 8087:0033 Intel Corp. AX211 Bluetooth

VERSIONS
  linux-image-7.0.0-28-generic     7.0.0-28.28                      (works)
  linux-image-7.0.0-29-generic     7.0.0-29.29                      (fails)
  linux-firmware-intel-wireless    20260319.git217ca6e4-0ubuntu2.1  (unchanged)
  bluez                            5.85-4ubuntu0.1                  (unchanged)

  Firmware blob:      intel/ibt-0040-0041.sfi
  Firmware Version:   202-5.26
  Bootloader:         timestamp 2019.40 buildtype 1 build 38

STEPS TO REPRODUCE
  1. Boot 7.0.0-29-generic on the hardware above.
  2. Run: bluetoothctl list

EXPECTED
The adapter is listed and hci0 registers.

ACTUAL
No adapter. /sys/class/bluetooth/ is empty. bluetoothd runs normally and
rfkill reports no blocks, but there is no Bluetooth rfkill entry at all.
Critically, after the failed download and reset the controller disappears
from the USB bus entirely - "lsusb -d 8087:" returns nothing - so
"modprobe -r btusb && modprobe btusb" cannot recover it. A reboot is
required.

KERNEL LOG - FAILING, 7.0.0-29-generic
  [23.558753] Bluetooth: hci0: Device revision is 0
  [23.558771] Bluetooth: hci0: Secure boot is enabled
  [23.558832] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [23.558849] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
  [23.558864] Bluetooth: hci0: DSM reset method type: 0x00
  [23.558877] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
  [23.558892] Bluetooth: hci0: Boot Address: 0x100800
  [23.558907] Bluetooth: hci0: Firmware Version: 202-5.26
  [25.145022] Bluetooth: hci0: Failed to send firmware data (-38)
  [25.145077] Bluetooth: hci0: Intel reset sent to retry FW download
  [27.333110] Bluetooth: hci0: Failed to read MSFT supported features (-110)

KERNEL LOG - WORKING, 7.0.0-28-generic
  [30.770032] Bluetooth: hci0: Device revision is 0
  [30.770093] Bluetooth: hci0: Secure boot is enabled
  [30.770147] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
  [30.770157] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1 build 38
  [30.770163] Bluetooth: hci0: DSM reset method type: 0x00
  [30.775014] Bluetooth: hci0: Found device firmware: intel/ibt-0040-0041.sfi
  [30.775067] Bluetooth: hci0: Boot Address: 0x100800
  [30.775083] Bluetooth: hci0: Firmware Version: 202-5.26
  [32.425062] Bluetooth: hci0: Waiting for firmware download to complete
  [32.425119] Bluetooth: hci0: Firmware loaded in 1611992 usecs
  [32.425137] Bluetooth: hci0: Waiting for device to boot
  [32.444024] Bluetooth: hci0: Device booted in 17760 usecs
  [32.448827] Bluetooth: hci0: Found Intel DDC parameters: 
intel/ibt-0040-0041.ddc
  [32.452015] Bluetooth: hci0: Applying Intel DDC parameters completed

The two boots are identical through "Firmware Version: 202-5.26", then
diverge: -28 proceeds to "Waiting for firmware download to complete",
while -29 returns -38 from the send path.

NOTES THAT MAY HELP TRIAGE
  * Not a timeout difference. -28 succeeds after ~1.61 s of download; -29
    fails after ~1.59 s. Nearly identical elapsed time, so this does not
    look like a shortened timeout.
  * -38 is ENOSYS, which suggests the download path may be attempting an
    operation this controller's bootloader does not implement, rather than
    a transfer error. Note the relatively old bootloader (2019.40 build 38)
    and DSM reset method type: 0x00.
  * Firmware ruled out: linux-firmware-intel-wireless was last modified on
    this system 2026-07-10, a month before the failure, and was not part of
    the upgrade that introduced -29. "dpkg -V linux-firmware-intel-wireless"
    reports clean checksums.
  * The "Firmware loaded in ~1.6 s" figure is slow in absolute terms, which
    may indicate this controller sits near a tolerance boundary.

WORKAROUND
Boot 7.0.0-28-generic.

ATTACHMENTS
  dmesg-7.0.0-29-failing.txt   full kernel log of the failing boot
  dmesg-7.0.0-28-working.txt   full kernel log of the working boot

ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-7.0.0-28-generic 7.0.0-28.28
ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12
Uname: Linux 7.0.0-28-generic x86_64
ApportVersion: 2.34.1-0ubuntu0.1
Architecture: amd64
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  ron-smth   4581 F.... wireplumber
 /dev/snd/seq:        ron-smth   4561 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 12 14:14:45 2026
InstallationDate: Installed on 2025-09-11 (335 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
MachineType: Framework Laptop 12 (13th Gen Intel Core)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-28-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash mem_sleep_default=deep 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-05-23 (82 days ago)
dmi.bios.date: 02/10/2026
dmi.bios.release: 3.7
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.07
dmi.board.asset.tag: *
dmi.board.name: FRAPMACP05
dmi.board.vendor: Framework
dmi.board.version: A5
dmi.chassis.asset.tag: FRAPDACPA55292000W
dmi.chassis.type: 31
dmi.chassis.vendor: Framework
dmi.chassis.version: A5
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.07:bd02/10/2026:br3.7:svnFramework:pnLaptop12(13thGenIntelCore):pvrA5:rvnFramework:rnFRAPMACP05:rvrA5:cvnFramework:ct31:cvrA5:skuFRAPDACP05:pfaLaptop12:
dmi.product.family: Laptop 12
dmi.product.name: Laptop 12 (13th Gen Intel Core)
dmi.product.sku: FRAPDACP05
dmi.product.version: A5
dmi.sys.vendor: Framework

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug resolute wayland-session

** Attachment added: "dmesg-7.0.0-29-failing.txt"
   
https://bugs.launchpad.net/bugs/2163365/+attachment/5991616/+files/dmesg-7.0.0-29-failing.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2163365

Title:
  bluetooth

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163365/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to