rokejulianlockhart
September 25, 2025, 4:35pm
9
@fuzzyhalo , my Sony Group Corporation WH-1000 XM5s also frequently disconnect. However, I see “Bluetooth: hci0: Invalid exception type 03” regardless, so you may have conflated multiple problems.
To demonstrate, I see that this has been occurring since at least +2023. It provides evidence to support the undermentioned, since firmware so rarely updates:
opened 09:00PM - 27 Mar 24 UTC
closed 03:06PM - 12 Apr 24 UTC
Now that firmware 53617 landed for my BE200NGW card and finally added cis-centra… l/peripheral support, I am trying to make LE Audio work with my LE Audio enabled Sony WF-1000XM5 earbuds (which work almost perfectly with my Android phone & tablet). However, this just does not seem to work. I have tried this on various combinations of:
- Linux kernel: 6.8.1, 6.8.2 & latest 6.9 master (962490525cffee6270422206c9d5bdb12d472c2b) with latest bluetooth-next (db4597cc88b2621706dc39a7363e61f4e7734425) merged into it
- bluez 5.73 & latest master (41d6c4e1c)
- pipewire/wireplumber: stable & latest git versions
```
~ $ sudo journalctl -b | grep -iE 'blue|hci0|ibt|be200'
bře 27 21:34:17 box kernel: Bluetooth: Core ver 2.22
bře 27 21:34:17 box kernel: NET: Registered PF_BLUETOOTH protocol family
bře 27 21:34:17 box kernel: Bluetooth: HCI device and connection manager initialized
bře 27 21:34:17 box kernel: Bluetooth: HCI socket layer initialized
bře 27 21:34:17 box kernel: Bluetooth: L2CAP socket layer initialized
bře 27 21:34:17 box kernel: Bluetooth: SCO socket layer initialized
bře 27 21:34:17 box kernel: Bluetooth: hci0: Firmware timestamp 2024.8 buildtype 1 build 53617
bře 27 21:34:17 box kernel: Bluetooth: hci0: Firmware SHA1: 0x7c7b67b9
bře 27 21:34:17 box kernel: Bluetooth: hci0: No support for _PRR ACPI method
bře 27 21:34:17 box kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0291-0291.sfi
bře 27 21:34:17 box kernel: Bluetooth: hci0: Boot Address: 0x100800
bře 27 21:34:17 box kernel: Bluetooth: hci0: Firmware Version: 113-8.24
bře 27 21:34:17 box kernel: Bluetooth: hci0: Firmware already loaded
bře 27 21:34:17 box kernel: Bluetooth: hci0: Fseq status: Success (0x00)
bře 27 21:34:17 box kernel: Bluetooth: hci0: Fseq executed: 00.00.04.157
bře 27 21:34:17 box kernel: Bluetooth: hci0: Fseq BT Top: 00.00.04.157
bře 27 21:34:22 box systemd[1]: Starting Bluetooth service...
bře 27 21:34:22 box bluetoothd[1325]: Bluetooth daemon 5.73
bře 27 21:34:22 box systemd[1]: Started Bluetooth service.
bře 27 21:34:22 box systemd[1]: Reached target Bluetooth Support.
bře 27 21:34:22 box bluetoothd[1325]: Excluding (cli) a2dp
bře 27 21:34:22 box bluetoothd[1325]: Excluding (cli) vcp
bře 27 21:34:22 box bluetoothd[1325]: Bluetooth management interface 1.22 initialized
bře 27 21:34:22 box bluetoothd[1325]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
bře 27 21:34:22 box bluetoothd[1325]: Battery Provider Manager created
bře 27 21:34:22 box kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
bře 27 21:34:22 box kernel: Bluetooth: BNEP filters: protocol multicast
bře 27 21:34:22 box kernel: Bluetooth: BNEP socket layer initialized
bře 27 21:34:22 box kernel: Bluetooth: MGMT ver 1.22
bře 27 21:34:22 box kernel: Bluetooth: ISO socket layer initialized
bře 27 21:34:22 box bluetoothd[1325]: profiles/audio/avrcp.c:avrcp_controller_server_probe() Unable to register AVRCP service record
bře 27 21:34:22 box bluetoothd[1325]: avrcp-controller: Operation not permitted (1)
bře 27 21:34:22 box bluetoothd[1325]: profiles/audio/avrcp.c:avrcp_target_server_probe() Unable to register AVRCP target service record
bře 27 21:34:22 box bluetoothd[1325]: audio-avrcp-target: Operation not permitted (1)
bře 27 21:34:22 box bluetoothd[1325]: Failed to clear UUIDs: Failed (0x03)
bře 27 21:34:22 box bluetoothd[1325]: Adv Monitor Manager created with supported features:0x00000001, enabled features:0x00000001, max number of supported monitors:32, max number of supported patterns:16
bře 27 21:34:35 box bluetoothd[1325]: Path / reserved for Adv Monitor app :1.17
bře 27 21:35:11 box kernel: Bluetooth: hci0: Invalid exception type 03
bře 27 21:35:11 box systemd[1566]: Reached target Bluetooth.
bře 27 21:35:16 box kernel: Bluetooth: hci0: Invalid exception type 03
bře 27 21:35:16 box bluetoothd[1325]: profiles/battery/battery.c:parse_battery_level() Trying to update an unregistered battery
bře 27 21:35:24 box bluetoothd[1325]: profiles/battery/battery.c:parse_battery_level() Trying to update an unregistered battery
bře 27 21:35:55 box bluetoothd[1325]: Adv Monitor app :1.17 disconnected from D-Bus
bře 27 21:36:27 box bluetoothd[1325]: src/profile.c:ext_register_record() Failed to register service record
bře 27 21:36:27 box bluetoothd[1325]: src/profile.c:ext_register_record() Failed to register service record
bře 27 21:36:27 box kernel: Bluetooth: RFCOMM TTY layer initialized
bře 27 21:36:27 box kernel: Bluetooth: RFCOMM socket layer initialized
bře 27 21:36:27 box kernel: Bluetooth: RFCOMM ver 1.11
bře 27 21:36:28 box systemd[1566]: Starting Bluetooth OBEX service...
bře 27 21:36:28 box systemd[1566]: Started Bluetooth OBEX service.
bře 27 21:36:28 box bluetoothd[1325]: src/profile.c:ext_register_record() Failed to register service record
bře 27 21:36:28 box bluetoothd[1325]: src/profile.c:ext_register_record() Failed to register service record
bře 27 21:36:28 box bluetoothd[1325]: src/profile.c:ext_register_record() Failed to register service record
bře 27 21:36:28 box bluetoothd[1325]: src/profile.c:ext_register_record() Failed to register service record
bře 27 21:36:28 box bluetoothd[1325]: src/profile.c:ext_register_record() Failed to register service record
bře 27 21:36:28 box bluetoothd[1325]: src/profile.c:ext_register_record() Failed to register service record
bře 27 21:36:28 box bluetoothd[1325]: src/profile.c:ext_register_record() Failed to register service record
bře 27 21:39:40 box kernel: Bluetooth: hci0: Invalid exception type 04
bře 27 21:39:40 box kernel: Bluetooth: hci0: Invalid exception type 04
```
Am I attempting something unsupported yet? I get Invalid exception type 03 after pairing, 04 after disconnecting. Also of note is the 'No support for _PRR ACPI method', 'Failed to reset Adv Monitors: Failed (0x03)' and 'Failed to clear UUIDs: Failed (0x03)' errors. I have disabled classic stack, so there are errors linked to that, but that is normal.
However, we may be in luck, for the kernel may have been very recently updated to work around this, if I’ve understood its context correctly: