From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219514] New: PC does not resume from suspend, bisect points to btusb/mediatek
Date: Tue, 19 Nov 2024 19:43:46 +0000 [thread overview]
Message-ID: <bug-219514-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=219514
Bug ID: 219514
Summary: PC does not resume from suspend, bisect points to
btusb/mediatek
Product: Drivers
Version: 2.5
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: h@realh.co.uk
Regression: No
Created attachment 307246
--> https://bugzilla.kernel.org/attachment.cgi?id=307246&action=edit
dmesg shortly after booting with the "bad" kernel
In recent kernels my system keeps hanging when trying to resume from suspend.
The fans power up, as do my keyboard LEDs, but the displays stay off and
pressing Caps Lock does not toggle its LED. This means I can't get a log when
the problem occurs.
My motherboard is an MSI MAG X670E TOMAHAWK WIFI with an onboard Mediatek
wireless device, and I'm using Arch Linux.
lspci: 0f:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express
Wireless Network Adapter
lsusb: 0e8d:0616 MediaTek Inc. Wireless_Device
git bisect points to ceac1cb0259de682d78f5c784ef8e0b13022e9d9 as the first bad
commit. It's been difficult to pinpoint it, because the bug isn't 100%
consistent, but this commit has exhibited the bug every time I've tried it, and
subsequent revisions nearly always do. I've tested the previous commit,
6dc22ab9f085ae165e4ce89d61fb426f94e8a969, several times, and it's successfully
resumed every time.
--
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-19 19:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 19:43 bugzilla-daemon [this message]
2024-11-19 19:45 ` [Bug 219514] PC does not resume from suspend, bisect points to btusb/mediatek 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
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@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).