From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 216230] "irq9: nobody cared" on Thinkpad T14 Gen1 (AMD) when s2idle is enabled
Date: Mon, 11 Jul 2022 07:02:00 +0000 [thread overview]
Message-ID: <bug-216230-215701-Ic34WSNzSX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216230-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216230
--- Comment #5 from madcatx@atlas.cz ---
Thanks for looking into this.
It turns out that the issue is more difficult to reproduce than I'd originally
thought. I saw a few cold boots that went fine and one warm boot when the irq9
fault happened. It looks like the cold/warm boot was just a red herring.
My machine is affected by the NVMe slow wakeup bug so I only started to use
s2idle since kernel 5.18. As such I don't know if this is a regression. I'll
see if I can downgrade the firmware if you think that'd help you track this
down. FTR I'm on version 1.40 which seems to be the latest one as of now.
I attached the requested logs.
--
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:[~2022-07-11 7:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 18:24 [Bug 216230] New: "irq9: nobody cared" on Thinkpad T14 Gen1 (AMD) when s2idle is enabled bugzilla-daemon
2022-07-09 18:26 ` [Bug 216230] " bugzilla-daemon
2022-07-10 15:52 ` bugzilla-daemon
2022-07-11 6:56 ` bugzilla-daemon
2022-07-11 6:56 ` bugzilla-daemon
2022-07-11 6:57 ` bugzilla-daemon
2022-07-11 7:02 ` bugzilla-daemon [this message]
2022-07-11 16:09 ` bugzilla-daemon
2022-07-11 16:30 ` bugzilla-daemon
2022-07-11 16:36 ` bugzilla-daemon
2022-07-11 17:34 ` bugzilla-daemon
2022-07-11 17:34 ` bugzilla-daemon
2022-07-11 17:40 ` bugzilla-daemon
2022-07-11 19:10 ` bugzilla-daemon
2022-07-11 19:14 ` bugzilla-daemon
2022-07-11 19:37 ` bugzilla-daemon
2022-07-12 6:52 ` bugzilla-daemon
2022-07-12 15:34 ` bugzilla-daemon
2022-07-13 6:33 ` bugzilla-daemon
2022-07-13 17:18 ` bugzilla-daemon
2022-07-13 17:29 ` bugzilla-daemon
2022-07-13 18:04 ` bugzilla-daemon
2022-07-14 11:31 ` bugzilla-daemon
2022-07-14 11:34 ` bugzilla-daemon
2022-07-14 13:15 ` bugzilla-daemon
2022-07-14 13:48 ` 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-216230-215701-Ic34WSNzSX@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.