From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 200039] BT advertising packet wakes up the system from S3 and suspend-to-idle
Date: Tue, 16 Oct 2018 06:28:53 +0000 [thread overview]
Message-ID: <bug-200039-62941-2z0tY0YAVk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-200039-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=200039
--- Comment #23 from Raghuram Hegde (raghuram.hegde@intel.com) ---
(In reply to AceLan Kao from comment #22)
> I think the behavior should be normal.
> When BT dialog is opened, it start accepting all advertisement, and stop
> receiving packet after it's closed. This behavior is easy to be observed.
> From the full log, packets before #219 are received when the BT dialog is
> opened, and #220 is received during S3.
>
> But the issue is, the advertising packets are only be received after there
> is a paired BT4 device(no matter it's connected or not).
> It very simple to verify.
>
> 1. remove all BT devices from BT dialog and close the BT dialog
> 2. run "btmon" and got nothing
>
> 1. pair non-BT4 devices(you can leave it connected) and close BT dialog
> 2. nothing from "btmon" if you don't touch the paired device.
>
> 1. pair BT4 devices and disconnected them(even power off them)
> 2. we got advertising packet from other BT4 devices.
>
> I'm not sure if "Accept all advertisement" is the culprit, but I'm willing
> to know if there is any command we can try to disable it to see if it helps.
In the full log, you can see that after #123, MGMT command 'Add Device' is sent
with Action parameter set to 'Auto-connect remote device (0x02)'. So, when
pairing with a LE device, 'HCI_AUTO_CONN_ALWAYS' flag is set.
In the HCI Disconnection Complete Event handler (hci_disconn_complete_evt in
net/bluetooth/hci_event.c), you can see that if the 'HCI_AUTO_CONN_ALWAYS' flag
is set, LE passive scan will be started.
Since for a paired LE device, 'HCI_AUTO_CONN_ALWAYS' flag is set, when we
disconnect it, LE passive scan will be started.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-10-16 6:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-200039-62941@https.bugzilla.kernel.org/>
2018-10-08 7:19 ` [Bug 200039] BT advertising packet wakes up the system from S3 and suspend-to-idle bugzilla-daemon
2018-10-08 7:21 ` bugzilla-daemon
2018-10-08 7:31 ` bugzilla-daemon
2018-10-09 10:53 ` bugzilla-daemon
2018-10-15 7:07 ` bugzilla-daemon
2018-10-15 8:43 ` bugzilla-daemon
2018-10-15 10:53 ` bugzilla-daemon
2018-10-15 11:25 ` bugzilla-daemon
2018-10-16 1:26 ` bugzilla-daemon
2018-10-16 6:28 ` bugzilla-daemon [this message]
2018-10-17 5:27 ` bugzilla-daemon
2018-10-27 19:22 ` bugzilla-daemon
2018-10-29 3:14 ` bugzilla-daemon
2018-11-16 15:17 ` bugzilla-daemon
2018-11-16 15:27 ` bugzilla-daemon
2019-02-27 15:22 ` bugzilla-daemon
2019-03-19 9:35 ` bugzilla-daemon
2019-03-19 9:43 ` bugzilla-daemon
2019-03-19 9:45 ` bugzilla-daemon
2019-09-11 8:29 ` bugzilla-daemon
2019-09-11 11:24 ` bugzilla-daemon
2019-09-11 16:05 ` bugzilla-daemon
2019-09-11 16:18 ` bugzilla-daemon
2019-09-19 14:45 ` bugzilla-daemon
2022-05-14 22:33 ` bugzilla-daemon
2022-05-14 23:42 ` 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-200039-62941-2z0tY0YAVk@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;
as well as URLs for NNTP newsgroup(s).