From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219519] New: Hibernation Failure on 6.11+ due to btusb
Date: Fri, 22 Nov 2024 10:02:44 +0000 [thread overview]
Message-ID: <bug-219519-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219519
Bug ID: 219519
Summary: Hibernation Failure on 6.11+ due to btusb
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: lkml@antheas.dev
Regression: No
Created attachment 307262
--> https://bugzilla.kernel.org/attachment.cgi?id=307262&action=edit
Stack trace after resume
On an ASUS ROG Ally X (and possibly Legion Go) and a kernel of 6.11+, if
Bluetooth is enabled, hibernation will fail on resume with RIP
__list_del_entry_valid_or_report.cold.
This is under the function hci_unregister_dev
6.10 appears to work however. See the stack trace below. It is from a tainted
6.11 kernel, but the same issue occurs on 6.12.0 and 6.11.y
Bisection between 6.10 and 6.11 made some kernels that could not boot, so I
could not finish it. I also tried reverting "Fix not handling hibernation
actions" and "Bluetooth: btusb: Don't fail external suspend requests"
completely which did not help
The following lines were used to produce the trace:
```
sudo chvt 2
echo N | sudo tee /sys/module/printk/parameters/console_suspend
echo devices | sudo tee /sys/power/pm_test
echo disk | sudo tee /sys/power/state
```
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2024-11-22 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 10:02 bugzilla-daemon [this message]
2024-11-22 10:03 ` [Bug 219519] Hibernation Failure on 6.11+ due to btusb bugzilla-daemon
2024-11-22 16:47 ` bugzilla-daemon
2024-11-22 23:17 ` bugzilla-daemon
2024-11-22 23:18 ` 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-219519-62941@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