From: Peter Zijlstra <peterz@infradead.org>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: peterhuewe@gmx.de, jarkko@kernel.org, hdegoede@redhat.com,
jgg@ziepe.ca, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: tpm_sis IRQ storm on ThinkStation P360 Tiny
Date: Fri, 5 May 2023 19:19:15 +0200 [thread overview]
Message-ID: <20230505171915.GA1821641@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <toe7jsgedknsqj3dgw2fasjlqcpgpiqgloifxow4vnt3tntabw@l6emb5zpbff5>
On Fri, May 05, 2023 at 08:05:53AM -0700, Jerry Snitselaar wrote:
> It will poll like it has for years with tpm_tis.interrupts=0 so that
> should be working as it was prior to 6.3 when interrupts were re-enabled
> for tpm_tis. Are you seeing this with 6.2 as well? IIRC with that Thinkpad
> case is when it was first realized that interrupts had accidentally been
> disabled for tpm_tis at one point by a change.
v6.2 gets me:
[ 8.888394] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0x1D, rev-id 54)
[ 8.891123] tpm tpm0: [Firmware Bug]: TPM interrupt not working, polling instead
> I guess myself or someone else needs to revisit catching this in
> general when the irq storm happens, and disabling interrupts for
> tpm_tis. I think last time I was incorporating some feedback from
> tglx, let my adhd get me distracted with some other issue and never
> returned to it.
>
> The diff below should (compile tested) work for the P360, but
> tpm_tis.interrupts=0 is a good work-around.
Yep, I suppose it would. I'll keep the kernel parameter for now, that's
easier than making sure I consistently apply that patch.
Thanks!
next prev parent reply other threads:[~2023-05-05 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 13:07 tpm_sis IRQ storm on ThinkStation P360 Tiny Peter Zijlstra
2023-05-05 15:05 ` Jerry Snitselaar
2023-05-05 17:19 ` Peter Zijlstra [this message]
2023-05-05 17:25 ` Jerry Snitselaar
2023-05-11 0:02 ` Jarkko Sakkinen
2023-05-11 14:26 ` Jerry Snitselaar
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=20230505171915.GA1821641@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=hdegoede@redhat.com \
--cc=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=jsnitsel@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=tglx@linutronix.de \
/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