linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Thu, 02 Jan 2025 23:55:07 +0000	[thread overview]
Message-ID: <bug-219514-62941-wXfMuccD2a@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219514-62941@https.bugzilla.kernel.org/>

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

Olivier Croquette (olivier@croquette.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |olivier@croquette.de

--- Comment #4 from Olivier Croquette (olivier@croquette.de) ---
I also bisected this and came to commit
d019930b0049fc2648a6b279893d8ad330596e81, which is in the same area. I also
found similar reports:

https://bugzilla.kernel.org/show_bug.cgi?id=219290
https://bugzilla.redhat.com/show_bug.cgi?id=2314036
https://bbs.archlinux.org/viewtopic.php?id=295916
https://bbs.archlinux.org/viewtopic.php?id=299987
https://discussion.fedoraproject.org/t/kernel-6-11-3-200-fc40-unable-to-resume-from-suspend-when-bluetooth-enabled/134008/10
https://discussion.fedoraproject.org/t/system-cannot-wake-up/134199/39

A workaround that works for me and does not require to patch the kernel is the
following service:

# /etc/systemd/system/bt-fix.service
# 
# Author: Bojan Kseneman
#
https://discussion.fedoraproject.org/t/kernel-6-11-3-200-fc40-unable-to-resume-from-suspend-when-bluetooth-enabled/134008/17

[Unit]
Description=Disable Bluetooth before going to sleep
Before=sleep.target
StopWhenUnneeded=yes

[Service]
Type=oneshot
RemainAfterExit=yes

ExecStart=/usr/sbin/rfkill block bluetooth
ExecStop=/usr/sbin/rfkill unblock bluetooth

[Install]
WantedBy=sleep.target



I also wrote on the linux-bluetooth mailing list, with stack trace from a
kernel oops:

https://lore.kernel.org/linux-bluetooth/073c3b772abe84d480913495eea0c4da73607d6e.camel@croquette.de/T/#u

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2025-01-02 23:55 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 ` [Bug 219514] " bugzilla-daemon
2025-01-02 23:55 ` bugzilla-daemon [this message]
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-wXfMuccD2a@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).