platform-driver-x86.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 16:36:08 +0000	[thread overview]
Message-ID: <bug-216230-215701-rkiIwCWA3a@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 #8 from Mario Limonciello (AMD) (mario.limonciello@amd.com) ---
> Although I'm afraid it won't be very interesting.

It might not be, but once we know the timing relative to pinctrl-amd loading we
can know if it's that.  If it's not, then our next step will be to crank up
ACPI debugging output to see if it correlates with an ACPI event.

> Okay. Would adding pinctrl_amd to initramfs be enough to rule out this
> possibility?

Yeah that or compiling it as built-in.

> I'm aware but I've been using this machine with forced ASPM for about 2 years
> with no apparent issues related to that. I'll give it a go.

I guess  the reason you do it is for improved power consumption.  I think you
should contrast how much you save with a watt meter and what devices forcing
ASPM actually changes.  If If you find that you have improved power consumption
from something it's better to ask Lenovo to change the defaults in their BIOS. 
They're more well equipped to do stress testing and analysis that PCIe is still
performing properly using the proper equipment.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-07-11 16:36 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 [this message]
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-rkiIwCWA3a@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).