Skip to contentSkip to conversation

New: hci0: unexpected event for opcode 0xfc2f

Bug 215189 [email protected] 2 participants 3 messages Dec 1, 2021 – Nov 27, 2022 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

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

            Bug ID: 215189
           Summary: hci0: unexpected event for opcode 0xfc2f
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.16-rc1
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

Created attachment 299811
--> https://bugzilla.kernel.org/attachment.cgi?id=299811&action=edit
Linux 5.16-rc1 messages (output of dmesg)

On a Dell Latitude E7520 with

Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface

running Debian sid/unstable, Linux 5.16-rc1 (but has so with older versions too) logs

    [   46.423662] Bluetooth: hci0: unexpected event for opcode 0xfc2f

when starting (or when resuming).

The WWW contains several reports of this issue:

1. https://debianforum.de/forum/viewtopic.php?t=174717
2.
https://askubuntu.com/questions/1179883/how-to-solve-256966901-bluetooth-hclo-unexpected-event-for-opcode-0xfc2f-mes
3. https://bugzilla.redhat.com/show_bug.cgi?id=1576865#c15

*[5.2.0-rcx] Bluetooth: hci0: unexpected event for opcode* [1] claims it was introduced by commit f80c5dad7b64 (Bluetooth: Ignore CC events not matching the last HCI command).

Marcel also analyzed the problem [2]:

Quoted 18 lines

so this is the culprit command.

< HCI Command: Intel Write BD Data (0x3f|0x002f) plen 80

        Address: 00:00:00:00:00:00 (OUI 00-00-00)
        ...
Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

      Intel Write BD Data (0x3f|0x002f) ncmd 1
        Status: Success (0x00)
Quoted 1 line

HCI Event: Vendor (0xff) plen 2

      Intel Write BD Data Complete (0x19)
        Status: Success (0x00)

There is actually nothing wrong with it and the firmware bseq file clearly says that it is expecting a command status followed by the vendor event. The driver however for simplicity reasons is using __hci_cmd_sync_ev and just waiting for the vendor event since the command status doesn’t offer any useful information in the success case.

Quoted 4 lines

Now I think that in the case of __hci_cmd_sync_ev with an extra event expected, we should not print this error when receiving the command status since that is clearly a valid response. How to achieve that, I don’t know yet. Maybe Joao Paulo has an idea.

I can’t find any responses from Joao Paulo though.

[1]: https://www.spinics.net/lists/kernel/msg3151547.html
[2]: https://www.spinics.net/lists/kernel/msg3153203.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.
#1 lore raw

[Bug 215189] hci0: unexpected event for opcode 0xfc2f

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

[email protected] changed:

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

--- Comment #2 from [email protected] ---
I am suffering from this issue as well. It wouldn’t be so bad except that the message gets printed out to tty1 and messes up my login console on wake from sleep.

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 215189] hci0: unexpected event for opcode 0xfc2f

In reply to [email protected]

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

Rijnhard Hessel ([email protected]) changed:

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

--- Comment #3 from Rijnhard Hessel ([email protected]) --- Forgive me if this isn't related but also seeing the same message with

Bus 001 Device 003: ID 8087:07dc Intel Corp. Bluetooth wireless interface

System:
Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
Machine:
Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
serial: <superuser required>
Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: <superuser required>

    UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015

Also the side track also seeing a lot of other issues around powering on the adapter after a suspend resume cycle (quite a few over the web, on launchpad etc)

so was wondering if it could be related.

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.