[Bug 209527] New: motherboard bluetooth fails to initialize after resume

[bugzilla-daemon@bugzilla.kernel.org]

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

            Bug ID: 209527
           Summary: motherboard bluetooth fails to initialize after resume
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.6.19
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: low
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: mikolajczyk.mateusz@gmail.com
        Regression: No

I am using asrock h470m-itx/ac which has a built-in bluetooth device. the board
itself works quite perfectly, however it has problem which occurs randomly when
I suspend the motherboard (it manifests itself once per several suspends).
After hitting the spacebar to resume the computer, the board either does not
start at all, or it starts, however POST time is significantly long - that's
when I know that the problem starts. after POST messages dissapear, the kernel
boots as usual and then at lightdm greeter I am unable to use my mouse and
keyboard (they are both USB devices). I have to wait for a moment (usually 2
minutes) at which point in time I can log in and my blutooth is disabled. The
only way to restore proper behavior of the motherboard is to shutdown the PC,
completely disable bluetooth in BIOS, boot, then shutdown and enable bluetooth
again. when I did `lsmod` I noticed these modules:

```
btbcm                  20480  1 btusb
btintel                28672  1 btusb
```

which would explain why I am unable to use the usb devices when the bug occurs
- as if the bluetooth would be somehow virtually connected as an USB device on
the motherboard ? lsusb confirms this theory (I think):

Bus 001 Device 007: ID 8087:0aa7 Intel Corp. Wireless-AC 3168 Bluetooth

I am certain that the system log would contain some useful information, however
I don't know where I would be able to find it since I believe the logs are now
inside systemd. I would be more than happy to provide some additional
information, it's just that I don't know where to start.

kindest regards,
toudi

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