Intel Wireless 7260 - bluetooth drops from USB bus almost immediately after connecting a device on the lastest firmware

[krzys_h]

The bluetooth in my Intel Wireless 7260 on my Thinkpad W541 resets almost immediately after a device connects. This is seen in dmesg as the device disconnecting and reconnecting to the USB bus with no other error messages, like this:

[603851.305788] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013
[603851.305827] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
[603851.443776] Bluetooth: hci0: unexpected event for opcode 0xfc2f
[603851.460922] Bluetooth: hci0: Intel BT fw patch 0x2a completed & activated
[603871.948430] usb 3-11: USB disconnect, device number 36
[603872.273696] usb 3-11: new full-speed USB device number 37 using xhci_hcd
[603872.422912] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01
[603872.422916] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[603872.437854] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013
[603872.437873] Bluetooth: hci0: Intel device is already patched. patch num: 2a
[603894.932755] input: JBL TUNE700BT (AVRCP) as /devices/virtual/input/input113
[603898.742664] usb 3-11: USB disconnect, device number 37
[603899.057916] usb 3-11: new full-speed USB device number 38 using xhci_hcd
[603899.211235] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01
[603899.211241] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[603899.226972] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013
[603899.226988] Bluetooth: hci0: Intel device is already patched. patch num: 2a
[603909.785396] input: JBL TUNE700BT (AVRCP) as /devices/virtual/input/input114
[603914.565733] usb 3-11: USB disconnect, device number 38
[603916.905954] usb 3-11: new full-speed USB device number 39 using xhci_hcd
[603917.055128] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01
[603917.055147] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[603917.071869] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013
[603917.071877] Bluetooth: hci0: Intel device is already patched. patch num: 2a

This has been a problem ever since I got this laptop, but recently I managed to fix it by downgrading the ibt firmware. I downgraded the /lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq file to this version https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq?id=fb328183532ffc7a1a54e84fb53467e275a95b79 and after that all problems stopped.

System info:

$ lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04
$ apt-cache policy linux-firmware
linux-firmware:
  Installed: 20220329.git681281e4-0ubuntu3.12
  Candidate: 20220329.git681281e4-0ubuntu3.12
  Version table:
 *** 20220329.git681281e4-0ubuntu3.12 500
        500 http://pl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
        500 http://pl.archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu jammy-security/main i386 Packages
        100 /var/lib/dpkg/status
     20220329.git681281e4-0ubuntu1 500
        500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
        500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages
$ lspci -vvvv
(see attachment)
$ lsusb -vvvvv
(see attachment)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: krzys_h 1511 F.... pulseaudio
 /dev/snd/controlC2: krzys_h 1511 F.... pulseaudio
 /dev/snd/controlC0: krzys_h 1511 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Dependencies: firmware-sof-signed 2.0-1ubuntu4.1
DistroRelease: Ubuntu 22.04
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-28 (3346 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: LENOVO 20EGS2G300
Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 [modified: lib/firmware/intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq]
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-71-generic root=UUID=4270eaa2-2664-4fb3-9d5f-f24328454960 ro rootflags=subvol=@ splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-71.78-generic 5.15.92
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-71-generic N/A
 linux-backports-modules-5.15.0-71-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.12
Tags: jammy
Uname: Linux 5.15.0-71-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-07-29 (273 days ago)
UserGroups: adm bluetooth cdrom dialout dip docker input libvirt lpadmin lxd plugdev sambashare sudo vboxusers wireshark
_MarkForUpload: True
dmi.bios.date: 08/23/2019
dmi.bios.release: 2.40
dmi.bios.vendor: LENOVO
dmi.bios.version: GNET92WW (2.40 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EGS2G300
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.15
dmi.modalias: dmi:bvnLENOVO:bvrGNET92WW(2.40):bd08/23/2019:br2.40:efr1.15:svnLENOVO:pn20EGS2G300:pvrThinkPadW541:rvnLENOVO:rn20EGS2G300:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20EG:
dmi.product.family: ThinkPad W541
dmi.product.name: 20EGS2G300
dmi.product.sku: LENOVO_MT_20EG
dmi.product.version: ThinkPad W541
dmi.sys.vendor: LENOVO

[Juerg Haefliger (juergh)]

Please run 'apport-collect 2017877' which will collect some more system information and attach it to this bug.

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[krzys_h (krzys-hal)]

apport information

[Launchpad Janitor (janitor)]

[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.]

[krzys_h (krzys-hal)]

The issue still exists for me, just recently the file somehow got reverted after an upgrade and I had to do my patch again to get bluetooth back. I added apport information as requested a long time ago.

[Juerg Haefliger (juergh)]

Sorry, missed the updates to this bug. Can you post the dmesg from when you're able to connect successfully (with the reverted fw)?

[krzys_h (krzys-hal)]

I'm pretty sure that the dmesg from apport ends with me replacing the firmware after which the issues stop, but here is a fresh one I took right now from a clean boot with the reverted fw. I don't think there is anything notable to see, really (except that "USB disconnect" obviously no longer happens a few seconds after establishing the connection)

[krzys_h (krzys-hal)]

During a recent system update the linux-firmware package updated again removing my manual fix - the issue still exists in 20220329.git681281e4-0ubuntu3.17

(commenting mostly to keep the issue from expiring again)

[Juerg Haefliger (juergh)]

Relevant log entries:

[ 14.405083] Bluetooth: Core ver 2.22
[ 14.405115] NET: Registered PF_BLUETOOTH protocol family
[ 14.405116] Bluetooth: HCI device and connection manager initialized
[ 14.405120] Bluetooth: HCI socket layer initialized
[ 14.405121] Bluetooth: L2CAP socket layer initialized
[ 14.405124] Bluetooth: SCO socket layer initialized
[ 14.442194] usbcore: registered new interface driver btusb
[ 14.454369] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013
[ 14.456943] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
[ 14.531540] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 14.531543] Bluetooth: BNEP filters: protocol multicast
[ 14.531546] Bluetooth: BNEP socket layer initialized
[ 14.603335] Bluetooth: hci0: unexpected event for opcode 0xfc2f
[ 14.619356] Bluetooth: hci0: Intel BT fw patch 0x2a completed & activated
[ 14.674486] NET: Registered PF_ALG protocol family
[ 14.699195] Bluetooth: RFCOMM TTY layer initialized
[ 14.699203] Bluetooth: RFCOMM socket layer initialized
[ 14.699208] Bluetooth: RFCOMM ver 1.11

[ 80.399089] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 80.399099] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 80.399101] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 80.399103] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 80.399105] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 80.399106] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 80.399108] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 80.399110] Bluetooth: hci0: SCO packet for unknown connection handle 0
[ 99.657119] usb 3-11: USB disconnect, device number 4
[ 99.701466] Bluetooth: hci0: setting interface failed (19)
[ 100.029214] usb 3-11: new full-speed USB device number 7 using xhci_hcd
[ 100.182436] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01
[ 100.182443] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 100.198003] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013
[ 100.198009] Bluetooth: hci0: Intel device is already patched. patch num: 2a

[ 172.057057] usb 3-11: USB disconnect, device number 7
[ 172.407869] usb 3-11: new full-speed USB device number 8 using xhci_hcd
[ 172.557024] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01
[ 172.557029] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 172.572730] Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 1 week 45 2013
[ 172.572737] Bluetooth: hci0: Intel device is already patched. patch num: 2a

[ 189.598594] Bluetooth: hci0: Ignoring error of Inquiry Cancel command

[ 196.210563] usb 3-11: USB disconnect, device number 8
[ 196.210829] Bluetooth: hci0: failed to restart LE scan: status 31
[ 196.523336] usb 3-11: new full-speed USB device number 9 using xhci_hcd
[ 196.676506] usb 3-11: New USB device found, idVendor=8087, idProduct=07dc, bcdDevice= 0.01
[ 196.676511] usb 3-11: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 196.6915...

[Juerg Haefliger (juergh)]

Can you check if this kernel commandline makes a difference with the new/broken firmware?

enable_autosuspend=0

[krzys_h (krzys-hal)]

I finally had some time to test this - no, this kernel argument doesn't seem to change anything.