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

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

[bugzilla-daemon]

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: linux-bluetooth@vger.kernel.org
          Reporter: cristi@ieee.org
        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

-- 
You may reply to this email to add a comment.

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

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

[bugzilla-daemon]

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

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

-- 
You may reply to this email to add a comment.

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

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

[bugzilla-daemon]

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

Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pmenzel+bugzilla.kernel.org
                   |                            |@molgen.mpg.de

--- Comment #2 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
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

-- 
You may reply to this email to add a comment.

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

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

[bugzilla-daemon]

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

--- Comment #3 from Cristian Cocos (cristi@ieee.org) ---
(In reply to Paul Menzel from comment #2)
> 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.

> What firmware is used?

BlueZ 5.86, AX211 firmware 202-5.26

C

-- 
You may reply to this email to add a comment.

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

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

[bugzilla-daemon]

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

--- Comment #4 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
(In reply to Cristian Cocos from comment #3)
> (In reply to Paul Menzel from comment #2)
> > 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.

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

-- 
You may reply to this email to add a comment.

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

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

[bugzilla-daemon]

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

--- Comment #5 from Cristian Cocos (cristi@ieee.org) ---
(In reply to Paul Menzel from comment #4)
> (In reply to Cristian Cocos from comment #3)
> > 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.

-- 
You may reply to this email to add a comment.

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

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

[bugzilla-daemon]

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

Luiz Von Dentz (luiz.dentz@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |luiz.dentz@gmail.com

--- Comment #6 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
(In reply to Paul Menzel from comment #2)
> 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.

-- 
You may reply to this email to add a comment.

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

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

[bugzilla-daemon]

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

Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |regressions@leemhuis.info

--- Comment #7 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
(In reply to Cristian Cocos from comment #5)
> (In reply to Paul Menzel from comment #4)
> > (In reply to Cristian Cocos from comment #3)
> > > 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.

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

-- 
You may reply to this email to add a comment.

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