All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 210141] New: Bluetooth device rtw_8822ce is lost after suspend to RAM
Date: Wed, 11 Nov 2020 00:47:39 +0000	[thread overview]
Message-ID: <bug-210141-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 210141
           Summary: Bluetooth device rtw_8822ce is lost after suspend to
                    RAM
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.9.7
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: funtoos@yahoo.com
        Regression: No

This is on an HP 14" laptop model: HP 14-dq1xxx with rtw_8822ce driver drives
the wifi and bluetooth.

So, everything works fine until I suspend to RAM. After waking from suspend,
the bluetooth adapter just disappears. I can see in the 'dmesg' the USB device
gets disconnected but no reason is mentioned.

Before suspend:

[    6.937836] usb 1-10: new full-speed USB device number 5 using xhci_hcd
[    7.065627] usb 1-10: New USB device found, idVendor=0bda, idProduct=b00c,
bcdDevice= 0.00
[    7.065630] usb 1-10: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[    7.065632] usb 1-10: Product: Bluetooth Radio 
[    7.065633] usb 1-10: Manufacturer: Realtek

After resume, it is gone:

[  329.512699] Restarting tasks ... done.
[  329.515898] usb 1-10: USB disconnect, device number 5
[  329.585469] PM: suspend exit
[  329.585559] elogind-daemon[7406]: System resumed.

# lspci
00:00.0 Host bridge: Intel Corporation Device 8a02 (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics G1 (Ice
Lake) (rev 07)
00:04.0 Signal processing controller: Intel Corporation Device 8a03 (rev 03)
00:14.0 USB controller: Intel Corporation Ice Lake-LP USB 3.1 xHCI Host
Controller (rev 30)
00:14.2 RAM memory: Intel Corporation Device 34ef (rev 30)
00:15.0 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO
I2C Controller #0 (rev 30)
00:15.1 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP Serial IO
I2C Controller #1 (rev 30)
00:16.0 Communication controller: Intel Corporation Management Engine Interface
(rev 30)
00:17.0 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller
[RAID mode] (rev 30)
00:1c.0 PCI bridge: Intel Corporation Device 34bf (rev 30)
00:1f.0 ISA bridge: Intel Corporation Ice Lake-LP LPC Controller (rev 30)
00:1f.3 Audio device: Intel Corporation Smart Sound Technology Audio Controller
(rev 30)
00:1f.4 SMBus: Intel Corporation Ice Lake-LP SMBus Controller (rev 30)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Ice Lake-LP SPI
Controller (rev 30)
01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac
PCIe Wireless Network Adapter

# lsusb
Bus 002 Device 002: ID 05e3:0626 Genesys Logic, Inc. USB3.1 Hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera
Bus 001 Device 008: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 007: ID 413c:2011 Dell Computer Corp. Multimedia Pro Keyboard
Bus 001 Device 006: ID 413c:1005 Dell Computer Corp. Multimedia Pro Keyboard
Hub
Bus 001 Device 004: ID 0c45:64ab Microdia Integrated Camera
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Device 5 is gone from lsusb.

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

             reply	other threads:[~2020-11-11  0:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-11  0:47 bugzilla-daemon [this message]
2020-12-09 17:18 ` [Bug 210141] Bluetooth device driven by rtw_8822ce is lost after suspend to RAM bugzilla-daemon
2021-02-03 15:31 ` bugzilla-daemon
2021-12-07 18:21 ` bugzilla-daemon

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-210141-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.