Skip to contentSkip to conversation

New: Intel AX211 Bluetooth hci0 hardware error 0x0c with HID/HOG failures on 6.19.14-zen

Bug 221426 [email protected] 1 participant 9 messages Apr 27 – Apr 28 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=221426

            Bug ID: 221426
           Summary: Intel AX211 Bluetooth hci0 hardware error 0x0c with
                    HID/HOG failures on 6.19.14-zen
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Created attachment 309973
--> https://bugzilla.kernel.org/attachment.cgi?id=309973&action=edit
Log highlights

# AX211 Bluetooth HID instability report

## Summary
Intel AX211 Bluetooth on this system intermittently fails with kernel hardware error 0x0c and repeated BlueZ HOG profile failures. User-facing symptom is that BLE mouse and keyboard become difficult or impossible to connect while Chrome is open; closing Chrome often allows reconnect.

This appears to be a kernel or controller stability problem, potentially amplified by power management settings and high USB activity.

## Environment
- Distro: ArchLinux rolling
- Kernel: 6.19.14-zen1-1-zen
- Bluetooth controller: Intel AX211 Bluetooth (USB ID 8087:0033)
- Devices affected: Logitech M720 mouse, Logitech K850 keyboard (BLE HID)

## Reproduction
1. Boot system normally.
2. Ensure Bluetooth service is active.
3. Open Chrome and use system normally.
4. Attempt to connect or keep connected BLE keyboard and mouse.
5. Observe failures, reconnect loops, or failed writes.
6. Close Chrome and retry; connection usually succeeds.

## Expected behavior
BLE mouse and keyboard should remain stable regardless of Chrome state.

## Actual behavior
BLE HID profile operation intermittently fails; reconnect loops occur and controller errors are logged.

## High signal evidence
From kernel log:

Bluetooth: hci0: Hardware error 0x0c
Bluetooth: hci0: Retrieving Intel exception info failed (-16)

From bluetooth service log:

profiles/input/hog-lib.c:output_written_cb() Write output report failed:
Request attribute has encountered an unlikely error
Wrong size of start discovery return parameters

Power-management related state on this host:

/sys/module/btusb/parameters/enable_autosuspend=Y /sys/module/usbcore/parameters/autosuspend=2

## Attachments
- System snapshot: ax211-bt-system-2026-04-27.txt
- Log highlights: ax211-bt-logs-2026-04-27.txt

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#1 lore raw

[Bug 221426] Intel AX211 Bluetooth hci0 hardware error 0x0c with HID/HOG failures on 6.19.14-zen

https://bugzilla.kernel.org/show_bug.cgi?id=221426

--- Comment #1 from Cristian Cocos ([email protected]) --- Created attachment 309974
--> https://bugzilla.kernel.org/attachment.cgi?id=309974&action=edit
System snapshot

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#2 lore raw

[Bug 221426] Intel AX211 Bluetooth hci0 hardware error 0x0c with HID/HOG failures on 6.19.14-zen

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=221426

Paul Menzel ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |pmenzel+bugzilla.kernel.org
                   |                            |@molgen.mpg.de

--- Comment #2 from Paul Menzel ([email protected]) --- Thank you for your report. Do you know if it’s a regression, that means, did it work with earlier Linux versions?

What firmware is used?

The BlueZ issue template has some more commands helping to collect things aiding in debugging.

[1]: https://github.com/bluez/bluez/tree/master/.github/ISSUE_TEMPLATE

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#3 lore raw

[Bug 221426] Intel AX211 Bluetooth hci0 hardware error 0x0c with HID/HOG failures on 6.19.14-zen

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=221426

--- Comment #3 from Cristian Cocos ([email protected]) --- (In reply to Paul Menzel from comment #2)

Quoted 2 lines

Thank you for your report. Do you know if it’s a regression, that means, did it work with earlier Linux versions?

I do not recall this issue's happening with the previous Linux kernel (6.19.13), hence very likely no regression.

Quoted 1 line

What firmware is used?

BlueZ 5.86, AX211 firmware 202-5.26

C

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#4 lore raw

[Bug 221426] Intel AX211 Bluetooth hci0 hardware error 0x0c with HID/HOG failures on 6.19.14-zen

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=221426

--- Comment #4 from Paul Menzel ([email protected]) --- (In reply to Cristian Cocos from comment #3)

Quoted 7 lines

(In reply to Paul Menzel from comment #2)

Quoted 1 line

Thank you for your report. Do you know if it’s a regression, that means,

did

Quoted 1 line

it work with earlier Linux versions?

I do not recall this issue's happening with the previous Linux kernel (6.19.13), hence very likely no regression.

Sorry, that is a contradiction, if I am not mistaken. Which not/no is wrong? ;-)

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#5 lore raw

[Bug 221426] Intel AX211 Bluetooth hci0 hardware error 0x0c with HID/HOG failures on 6.19.14-zen

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=221426

--- Comment #5 from Cristian Cocos ([email protected]) --- (In reply to Paul Menzel from comment #4)

Quoted 6 lines

(In reply to Cristian Cocos from comment #3)

Quoted 2 lines

I do not recall this issue's happening with the previous Linux kernel (6.19.13), hence very likely no regression.

Sorry, that is a contradiction, if I am not mistaken. Which not/no is wrong? ;-)

This phenomenon did NOT happen with the previous kernel version (6.19.13). I am not familiar with the "regression" jargon: I take it this counts as a ... "regression"? If so, please excuse my ignorance, and feel free to ignore my previous post.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#6 lore raw

[Bug 221426] Intel AX211 Bluetooth hci0 hardware error 0x0c with HID/HOG failures on 6.19.14-zen

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=221426

Luiz Von Dentz ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #6 from Luiz Von Dentz ([email protected]) --- (In reply to Paul Menzel from comment #2)

Quoted 10 lines

Thank you for your report. Do you know if it’s a regression, that means, did it work with earlier Linux versions?

What firmware is used?

The BlueZ issue template has some more commands helping to collect things aiding in debugging.

[1]: https://github.com/bluez/bluez/tree/master/.github/ISSUE_TEMPLATE

It might be a good idea to file the issue directly in github if there is a btmon trace then btsnoop-analyzer is used to analyze it, that said I suspect this is firmware related if it is really generating a hardware error.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#7 lore raw

[Bug 221426] Intel AX211 Bluetooth hci0 hardware error 0x0c with HID/HOG failures on 6.19.14-zen

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=221426

Paul Menzel ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #7 from Paul Menzel ([email protected]) --- (In reply to Cristian Cocos from comment #5)

Quoted 5 lines

(In reply to Paul Menzel from comment #4)

Quoted 4 lines

(In reply to Cristian Cocos from comment #3)

Quoted 2 lines

I do not recall this issue's happening with the previous Linux kernel (6.19.13), hence very likely no regression.

Quoted 8 lines
Quoted 1 line

Sorry, that is a contradiction, if I am not mistaken. Which not/no is

wrong?

Quoted 1 line

;-)

This phenomenon did NOT happen with the previous kernel version (6.19.13). I am not familiar with the "regression" jargon: I take it this counts as a ... "regression"? If so, please excuse my ignorance, and feel free to ignore my previous post.

No problem, I should have been more clear. Yes, a regression is that a new problem was introduced. And actually that is a good thing, as you can find the commit introducing the problem. The Linux kernel has a guide how to find that commit via bisection [1]. It’s also something the user, that means you, could do to help fixing the issue.

[1]:
https://www.kernel.org/doc/html/latest/admin-guide/reporting-regressions.html

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#8 lore raw

[Bug 221426] Intel AX211 Bluetooth hci0 hardware error 0x0c with HID/HOG failures on 6.19.14-zen

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=221426

--- Comment #8 from The Linux kernel's regression tracker (Thorsten Leemhuis) ([email protected]) --- (In reply to Paul Menzel from comment #7)

BTW, thx for CCing me

Quoted 1 line

https://www.kernel.org/doc/html/latest/admin-guide/reporting-regressions.html

The most detailed guide on bisection is:
https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html

Best follow that, as it will check latest mainline, which is important, as 6.19.y is already EOL. It will also ensure the problem happens on a vanilla kernel, as -zen kernels are heavily patched (see
https://github.com/zen-kernel/zen-kernel/wiki/Detailed-Feature-List ) and thus inadequate for upstream reporting.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.