[Bug 215589] New: Random bluetooth dropout after sleep.

[Bug 215589] New: Random bluetooth dropout after sleep.

[bugzilla-daemon]

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

            Bug ID: 215589
           Summary: Random bluetooth dropout after sleep.
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.16.8-zen1-1-zen
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: rodomar705@protonmail.com
        Regression: No

Created attachment 300430
  --> https://bugzilla.kernel.org/attachment.cgi?id=300430&action=edit
ATA SCSI trace failing randomly

After the previous issue of AX210 bluetooth issues after warm reboots I got
another problem; after the system sleep and get woken up from it, the bluetooth
adapter stop completely to respond to the host, other times it will connect to
my bluetooth mouse for a few seconds and then the bluetooth subsystem locks up
randomly. Sometimes when it works and then stop working I see this message in
the dmesg log:

[ 9248.324043] hid-generic 0005:0A5C:4503.0009: input,hidraw1: BLUETOOTH HID
v1.29 Mouse [TeckNet BM308] on xx:xx:xx:xx:xx:xx
[ 9259.970320] pcieport 0000:00:08.1: PME: Spurious native interrupt!
[ 9276.881203] pcieport 0000:00:08.1: PME: Spurious native interrupt!
[ 9277.137263] usb 3-4: reset full-speed USB device number 2 using xhci_hcd
...
[ 9997.610527] Bluetooth: hci0: command 0x0405 tx timeout
[10041.455285] Bluetooth: hci0: command 0x0408 tx timeout
[10082.421187] Bluetooth: hci0: command 0x0408 tx timeout
[10127.484049] Bluetooth: hci0: command 0x0408 tx timeout
...
[10143.614676] Bluetooth: hci0: command 0x0c1a tx timeout
[10143.614686] Bluetooth: hci0: Timed out waiting for suspend events
[10143.614693] Bluetooth: hci0: No way to reset. Ignoring and continuing
[10143.614697] Bluetooth: hci0: Suspend timeout bit: 4
[10143.614700] Bluetooth: hci0: Suspend timeout bit: 6
[10143.614703] Bluetooth: hci0: Suspend timeout bit: 9
[10143.614730] Bluetooth: hci0: Suspend notifier action (3) failed: -110

To fix this problem I usually put the laptop to sleep and wake it up again
Today however I was greeted with this error multiple times:

see ata_scsi_trace.txt

This laptop doesn't have a SATA port, but I guess the error comes from the
probing of the chipset non connected port? Why it crashes though?

Then this error is printed:

[10151.146976] ata2: failed stop FIS RX (-16)
[10151.148212] ata1: failed stop FIS RX (-16)

And then multiple new errors coming from a function called list (but it seems
that the caller is the bluetooth subsystem):

see list_stack_trace.txt

Then the bluetooth subsystem 4 times:

see bluetooth_stack_trace.txt

Finally after a sleep wake cycle again this was printed again:

see double_stack_trace.txt.

In this last case, however, the bluetooth works perfectly fine, after 3 cycles.

I don't really get what's happening here, frankly.

If you need more information on this, just ask.

Marco.

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

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

[Bug 215589] Random bluetooth dropout after sleep.

[bugzilla-daemon]

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

--- Comment #2 from Marco (rodomar705@protonmail.com) ---
Created attachment 300432
  --> https://bugzilla.kernel.org/attachment.cgi?id=300432&action=edit
List stack trace

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

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

[Bug 215589] Random bluetooth dropout after sleep.

[bugzilla-daemon]

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

Marco (rodomar705@protonmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #4 from Marco (rodomar705@protonmail.com) ---
It was my fault, coming from a non deleted DSDT override from my previous
testing from bluetooth related issues. Sorry for the noise.

Marco.

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

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