From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 216230] New: "irq9: nobody cared" on Thinkpad T14 Gen1 (AMD) when s2idle is enabled
Date: Sat, 09 Jul 2022 18:24:25 +0000 [thread overview]
Message-ID: <bug-216230-215701@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=216230
Bug ID: 216230
Summary: "irq9: nobody cared" on Thinkpad T14 Gen1 (AMD) when
s2idle is enabled
Product: Drivers
Version: 2.5
Kernel Version: 5.18.10
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Platform_x86
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
Reporter: madcatx@atlas.cz
Regression: No
Whenever I power up my T14 Gen1 TP with AMD chip, I get the following error
about 4 seconds after boot
[ 4.304639] kernel: irq 9: nobody cared (try booting with the "irqpoll"
option)
[ 4.304652] kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.18.9-arch1-1
#1 137f0035b2ece06cb65382579db27e9de66af504
[ 4.304654] kernel: Hardware name: LENOVO 20UDS02D00/20UDS02D00, BIOS
R1BET71W(1.40 ) 04/05/2022
[ 4.304655] kernel: Call Trace:
[ 4.304656] kernel: <IRQ>
[ 4.304658] kernel: dump_stack_lvl+0x48/0x5d
[ 4.304662] kernel: __report_bad_irq+0x35/0xaa
[ 4.304664] kernel: note_interrupt.cold+0xa/0x65
[ 4.304666] kernel: handle_irq_event+0x72/0x80
[ 4.304669] kernel: handle_fasteoi_irq+0x8e/0x1f0
[ 4.304671] kernel: __common_interrupt+0x46/0xa0
[ 4.304674] kernel: common_interrupt+0x81/0xa0
[ 4.304677] kernel: </IRQ>
[ 4.304677] kernel: <TASK>
[ 4.304678] kernel: asm_common_interrupt+0x22/0x40
[ 4.304681] kernel: RIP: 0010:cpuidle_enter_state+0xdc/0x380
[ 4.304684] kernel: Code: 00 00 31 ff e8 95 70 80 ff 45 84 ff 74 16 9c 58 0f
1f 40 00 f6 c4 02 0f 85 8f 02 00 00 31 ff e8 fa 44 86 ff fb 0f 1f 44 00 00 <45>
85 f6 0f 88 22 01 00 00 49 63 ce 48 8d 04 49 48 8d 04 81 49 8d
[ 4.304685] kernel: RSP: 0018:ffffb77f401a7e90 EFLAGS: 00000246
[ 4.304687] kernel: RAX: ffff8f606f872cc0 RBX: 0000000000000003 RCX:
0000000000000000
[ 4.304688] kernel: RDX: 0000000100930767 RSI: fffffffc2980382f RDI:
0000000000000000
[ 4.304688] kernel: RBP: ffff8f5980bcfc00 R08: 0000000000000002 R09:
000000004b6f7f5c
[ 4.304689] kernel: R10: 0000000000000d4c R11: 0000000000000002 R12:
ffffffff94d51300
[ 4.304690] kernel: R13: 0000000100930767 R14: 0000000000000002 R15:
0000000000000000
[ 4.304692] kernel: cpuidle_enter+0x2d/0x40
[ 4.304693] kernel: do_idle+0x1ba/0x220
[ 4.304695] kernel: cpu_startup_entry+0x1d/0x20
[ 4.304696] kernel: start_secondary+0x11c/0x140
[ 4.304699] kernel: secondary_startup_64_no_verify+0xd5/0xdb
[ 4.304702] kernel: </TASK>
When the machine boots up, I can check /proc/interrupts and get this for IRQ 9
9: 0 100076 0 0 0 0
0 0 0 0 0 0 0 0
0 0 IR-IO-APIC 9-fasteoi acpi, pinctrl_amd
Rather interestingly, when I reboot the machine, I don't get any IRQ-related
errors during boot and everything works fine. /proc/interrupts now looks like
this
9: 0 87 0 0 0 0
0 0 0 0 0 0 0 0
0 0 IR-IO-APIC 9-fasteoi acpi, pinctrl_amd
The number of interrupts very slowly increases as the computer runs.
This odd IRQ9 error that happens only on the first cold boot happens only when
I enable "Windows sleep", aka s2idle, mode in BIOS. Switching to S3 ("Linux
sleep") takes care of the IRQ problem but I'd rather stick to s2idle because
the latest Lenovo firmware has some issues that go away when s2idle is enabled.
Thanks!
--
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 reply other threads:[~2022-07-09 18:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 18:24 bugzilla-daemon [this message]
2022-07-09 18:26 ` [Bug 216230] "irq9: nobody cared" on Thinkpad T14 Gen1 (AMD) when s2idle is enabled 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
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@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;
as well as URLs for NNTP newsgroup(s).