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: Tue, 12 Jul 2022 06:52:14 +0000 [thread overview]
Message-ID: <bug-216230-215701-9WBqZs9M6j@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 #15 from madcatx@atlas.cz ---
I made a small discovery today. After adding pinctrl_amd module to my initramfs
I haven't been able to reproduce the problem so far. That may not be indicative
of anything because the problem does not appear every time. A bit more
interesting is my current output of /proc/interrupts. For IRQ9 it currently
shows
9: 0 11461 0 0 0 0
0 0 0 0 0 0 0 0
0 0 IR-IO-APIC 9-fasteoi acpi, pinctrl_amd
Notice that the number of recorded interrupts is around 11000. Before I added
pinctrl_amd to initramfs, there were two distinct cases. Either over 100000
interrupts with the kernel complaining about IRQ9 not being serviced or about
90 interrupts and no apparent issues. All of these numbers are from
/proc/interrupts dump done right after logging into DE after a reboot.
I was able to reproduce these figures multiple times. This suggests that some
HW starts to blast IRQs and doesn't stop until it gets serviced. Knowing this,
is there anything else you'd like me to try besides your suggestions above?
My CONFIG_PINCTRL_AMD is set to CONFIG_PINCTRL_AMD=m in my kernel config and
the respective module is loaded.
--
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-12 6:52 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
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 [this message]
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-9WBqZs9M6j@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.