Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1028:0310] BT advertising packet wakes up the system from S3 and suspend-to-idle

Bug #1839124 reported by Shih-Yuan Lee
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OEM Priority Project
Triaged
High
Unassigned
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

A generic issue which happens on Intel BT(8087:0aaa) and Atheros BT(0cf3:e005)(0cf3:e007).
Once the system has paired with BT4 devices(disconnected), the system will be waken up randomly from S3/s2idle while receiving advertising packet from any random BT4 devices in the environment which are even not paired/connected.

By removing all previously paired BT4 devices(disconnected) from BT menu can fix this issue.

The advertising packet could be none connectable undirected or connectable undirected.

And the BT4 devices we found can reproduce this issue are
1. Microsoft Surface 1678
2. Logitech K375s
3. Microsoft Designer Mouse
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: u 1539 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2019-08-06 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications
 Bus 001 Device 002: ID 0bda:5658 Realtek Semiconductor Corp. Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 3300
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.2.0-8-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
RelatedPackageVersions:
 linux-restricted-modules-5.2.0-8-generic N/A
 linux-backports-modules-5.2.0-8-generic N/A
 linux-firmware 1.181
Tags: eoan
Uname: Linux 5.2.0-8-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/07/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 0FN010
dmi.board.vendor: Dell Inc.
dmi.board.version: D02
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/07/2019:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn0FN010:rvrD02:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 3300
dmi.product.sku: 08BB
dmi.sys.vendor: Dell Inc.

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote :
Revision history for this message
Shih-Yuan Lee (fourdollars) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1839124

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Shih-Yuan Lee (fourdollars) wrote : AlsaInfo.txt

apport information

tags: added: originate-from-1798023 somerville
tags: added: apport-collected eoan
description: updated
Revision history for this message
Shih-Yuan Lee (fourdollars) wrote : CRDA.txt

apport information

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote : IwConfig.txt

apport information

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote : Lspci.txt

apport information

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote : ProcModules.txt

apport information

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote : PulseList.txt

apport information

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote : RfKill.txt

apport information

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote : UdevDb.txt

apport information

Revision history for this message
Shih-Yuan Lee (fourdollars) wrote : WifiSyslog.txt

apport information

Changed in oem-priority:
status: New → Triaged
importance: Undecided → Critical
assignee: nobody → Shih-Yuan Lee (fourdollars)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Brad Figg (brad-figg)
tags: added: ubuntu-certified
Rex Tsai (chihchun)
Changed in oem-priority:
importance: Critical → High
assignee: Shih-Yuan Lee (fourdollars) → nobody
You-Sheng Yang (vicamo)
summary: - BT advertising packet wakes up the system from S3 and suspend-to-idle
+ Qualcomm Atheros QCA6174 [168c:003e] Subsystem [1028:0310] BT
+ advertising packet wakes up the system from S3 and suspend-to-idle
tags: added: hwe-bluetooth hwe-suspend-resume
Revision history for this message
Rex Tsai (chihchun) wrote :

The workaround is to unload the linux kernel module before suspend. But most likely this needs to be fixed in kernel driver or firmware.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

This should be fixed in Linux v5.6.

Rex Tsai (chihchun)
tags: added: oem-priority
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.