From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219514] PC does not resume from suspend, bisect points to btusb/mediatek
Date: Mon, 30 Dec 2024 19:22:34 +0000 [thread overview]
Message-ID: <bug-219514-62941-L66FxJQGfX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219514-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219514
--- Comment #3 from Perroboc (bright.wing2924@fastmail.com) ---
Seems that #219290 is related.
Also discussed in Fedora boards:
https://discussion.fedoraproject.org/t/system-cannot-wake-up/134199
https://discussion.fedoraproject.org/t/kernel-6-11-3-200-fc40-unable-to-resume-from-suspend-when-bluetooth-enabled/134008
--
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:[~2024-12-30 19:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 19:43 [Bug 219514] New: PC does not resume from suspend, bisect points to btusb/mediatek bugzilla-daemon
2024-11-19 19:45 ` [Bug 219514] " bugzilla-daemon
2024-12-15 21:06 ` bugzilla-daemon
2024-12-15 21:14 ` [Bug,219514] " bluez.test.bot
2024-12-30 19:22 ` bugzilla-daemon [this message]
2025-01-02 23:55 ` [Bug 219514] " bugzilla-daemon
2025-01-04 5:36 ` bugzilla-daemon
2025-01-04 6:48 ` bugzilla-daemon
2025-01-04 15:27 ` bugzilla-daemon
2025-01-06 8:53 ` bugzilla-daemon
2025-01-06 10:18 ` bugzilla-daemon
2025-01-06 13:09 ` bugzilla-daemon
2025-01-06 14:41 ` bugzilla-daemon
2025-01-07 9:05 ` bugzilla-daemon
2025-01-07 21:02 ` bugzilla-daemon
2025-01-09 18:15 ` bugzilla-daemon
2025-02-07 21:22 ` bugzilla-daemon
2025-02-07 21:24 ` bugzilla-daemon
2025-02-17 15:22 ` bugzilla-daemon
2025-02-17 15:27 ` 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-219514-62941-L66FxJQGfX@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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).