[Bug 198993] New: Intel Bluetooth 8260: Spurious wake events prevent from staying suspended in s2idle state on Dell Latitude 7275

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

            Bug ID: 198993
           Summary: Intel Bluetooth 8260: Spurious wake events prevent
                    from staying suspended in s2idle state on Dell
                    Latitude 7275
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.15rc8 4.14 4.13
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@xxxxxxxxxxxxxxx
          Reporter: jerome.debretagne@xxxxxxxxx
        Regression: No

Attempting to suspend a Dell Latitude 7275 in s2idle state doesn't work, as the
system wakes up right away / just after a few seconds.

Looking at the default output of /proc/acpi/wakeup, very few entries are
enabled:

   $ cat /proc/acpi/wakeup | grep enabled
   XHC    S0    *enabled   pci:0000:00:14.0
   LID0   S3    *enabled   platform:PNP0C0D:00
   PBTN   S3    *enabled   platform:PNP0C0C:00

Disabling the XHC entry makes the system suspend properly and reliably as a
quick workaround, with the following command:

   # echo XHC > /proc/acpi/wakeup

Investigating a bit more by re-enabling the above XHC entry, the culprit seems
to be Bluetooth:
- switching off Bluetooth before suspend renders suspend stable (in my case
from the Gnome Settings) 
- enabling the Bluetooth radio brings back the spurious wake events right away.
Having Bluetooth devices actually connected or not doesn't change this
behavior.  

I don't see any output in the system logs mentioning this wake-up event so I
don't know which logs would be useful.

Here are some info from dmesg:

$ cat dmesg.txt | grep Bluetooth
[    3.949315] Bluetooth: Core ver 2.22
[    3.949327] Bluetooth: HCI device and connection manager initialized
[    3.949330] Bluetooth: HCI socket layer initialized
[    3.949332] Bluetooth: L2CAP socket layer initialized
[    3.949338] Bluetooth: SCO socket layer initialized
[    3.982814] Bluetooth: hci0: Firmware revision 0.0 build 95 week 37 2016
[    4.254340] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.254342] Bluetooth: BNEP filters: protocol multicast
[    4.254346] Bluetooth: BNEP socket layer initialized
[    9.525978] Bluetooth: RFCOMM TTY layer initialized
[    9.525987] Bluetooth: RFCOMM socket layer initialized
[    9.525992] Bluetooth: RFCOMM ver 1.11
[   14.950895] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   14.950909] Bluetooth: HIDP socket layer initialized

and some more info about the system itself: Dell Latitude 7275 is a 2-in-1
detachable laptop with an Intel Core-M processor (6th gen "Skylake"). There is
a similar consumer product branded XPS 12 (9250). The combo Wi-Fi / Bluetooth
chipset is the AC 8260 from Intel.

$ cat dmesg.txt | grep 8260
[    3.936492] iwlwifi 0000:6d:00.0: Detected Intel(R) Dual Band Wireless AC
8260, REV=0x208

I'm attaching a dmesg output, lspci and the content of /proc/acpi/wakeup. Let
me know which other inputs would be useful to investigate this issue.

Thanks,
Jérôme

-- 
You are receiving this mail because:
You are the assignee for the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux