From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 213923] Bluetooth: AC9560 doesn't respond any more after suspend multiple times
Date: Wed, 18 Aug 2021 15:28:15 +0000 [thread overview]
Message-ID: <bug-213923-62941-qgM5vv5eH6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-213923-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=213923
Chethan T N (chethan.tumkur.narayan@intel.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |chethan.tumkur.narayan@inte
| |l.com
--- Comment #5 from Chethan T N (chethan.tumkur.narayan@intel.com) ---
Would you please help to provide more details on the test setup and test case.
Setup details:
Linux distribution : Ubuntu/Fedora ??
kernel version: 5.xx??
Model name: ??
From the logs shared looks like one every suspend/resume Bluetooth device is
getting enumerated and FW download sequence is initiated.
May i know why the above behavior ?
And also noticed that in most of the suspend/resume flow during the FW download
sequence itself the system is entering the suspend state.
//System entering SUSPEND State
37213 2021-08-06 12:39:52.879966 host controller 252
Sent Intel Secure Send
//System RESUME state
37222 2021-08-06 12:40:16.529947 host controller 3
Sent Intel Read Version
May i know why the above behavior?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-08-18 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 5:37 [Bug 213923] New: Bluetooth: AC9560 doesn't respond any more after suspend multiple times bugzilla-daemon
2021-08-02 8:28 ` [Bug 213923] " bugzilla-daemon
2021-08-06 7:18 ` bugzilla-daemon
2021-08-18 15:28 ` bugzilla-daemon [this message]
2021-08-18 17:08 ` 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-213923-62941-qgM5vv5eH6@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.