public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 211121] New: Bluetooth not working after suspend
Date: Sun, 10 Jan 2021 17:15:37 +0000	[thread overview]
Message-ID: <bug-211121-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 211121
           Summary: Bluetooth not working after suspend
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.11.0-051100rc2-generic
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: aymang.abdallah@gmail.com
        Regression: No

Hi,

The bluetooth with device RLT8821CE stops working after resume from suspend (S3
cycle). It requires restarting the laptop to work again. I noticed that lsusb
and rfkill list shows hci0 device after booting, but when waking up from
suspend, hci0 no longer shows in rfkill, and is not listed in lsusb.

rfkill list

1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no


dmesg | grep -i bluetooth

[    1.456943] usb 1-10: Product: Bluetooth Radio
[    1.608363] Bluetooth: Core ver 2.22
[    1.608400] Bluetooth: HCI device and connection manager initialized
[    1.608404] Bluetooth: HCI socket layer initialized
[    1.608408] Bluetooth: L2CAP socket layer initialized
[    1.608412] Bluetooth: SCO socket layer initialized
[    1.622244] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000c
lmp_ver=0a lmp_subver=8822
[    1.623042] Bluetooth: hci0: RTL: rom_version status=0 version=3
[    1.623045] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_fw.bin
[    1.625528] Bluetooth: hci0: RTL: loading rtl_bt/rtl8822cu_config.bin
[    1.625643] Bluetooth: hci0: RTL: cfg_sz 6, total sz 31422
[    1.779046] Bluetooth: hci0: RTL: fw version 0x09993aa1
[    2.457853] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    2.457860] Bluetooth: BNEP filters: protocol multicast
[    2.457867] Bluetooth: BNEP socket layer initialized
[   10.739657] Bluetooth: RFCOMM TTY layer initialized
[   10.739667] Bluetooth: RFCOMM socket layer initialized
[   10.739673] Bluetooth: RFCOMM ver 1.11


lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Laptop is HP 14-dq1059wm running Ubuntu 20.04

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

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

                 reply	other threads:[~2021-01-10 17:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-211121-62941@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox