From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 220473] Linux 6.16 doesn't let me to shutdown the system and sometimes to boot it (lib/list_debug.c:35)
Date: Tue, 09 Sep 2025 13:39:35 +0000 [thread overview]
Message-ID: <bug-220473-215701-ZBiGfVty3z@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220473-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220473
--- Comment #10 from binarygator@gmail.com ---
(In reply to Mario Limonciello (AMD) from comment #9)
> This commit should probably help.
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/
> drivers/platform/x86?id=5549202b9c02c2ecbc8634768a3da8d9e82d548d
Hello Mario,
I don't know if that commit is part of version 6.16.5, but I got that update
today on Fedora and it somewhat looks worse (but it may just be my
imagination!).
The lib/list_debug.c:35 bug is still visible, and after a bit the tty starts
printing orange stacktraces without ever stopping or reaching GDM.
I tried to build a kernel from scratch but I did not have much luck.
Thanks for taking the time to answer me!
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-09-09 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-220473-215701@https.bugzilla.kernel.org/>
2025-08-22 11:09 ` [Bug 220473] Linux 6.16 doesn't let me to shutdown the system and sometimes to boot it (lib/list_debug.c:35) bugzilla-daemon
2025-08-22 14:34 ` bugzilla-daemon
2025-09-05 22:24 ` bugzilla-daemon
2025-09-06 2:14 ` bugzilla-daemon
2025-09-09 13:39 ` bugzilla-daemon [this message]
2025-09-09 14:27 ` bugzilla-daemon
2025-10-07 9:28 ` bugzilla-daemon
2026-03-19 15:24 ` bugzilla-daemon
2026-03-19 17:23 ` bugzilla-daemon
2026-03-20 3:16 ` 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-220473-215701-ZBiGfVty3z@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@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