From: "Michael Niewöhner" <linux@mniewoehner.de>
To: Jerry Snitselaar <jsnitsel@redhat.com>,
Lino Sanfilippo <l.sanfilippo@kunbus.com>
Cc: Lukas Wunner <lukas@wunner.de>,
Jarkko Sakkinen <jarkko@kernel.org>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
Philipp Rosenberger <p.rosenberger@kunbus.com>,
peterz@infradead.org
Subject: Re: [linus:master] [tpm, tpm_tis] e644b2f498: RIP:acpi_safe_halt
Date: Mon, 29 May 2023 17:07:54 +0200 [thread overview]
Message-ID: <fcdc5a27817b17d91df84bb06ad5d382829d5467.camel@mniewoehner.de> (raw)
In-Reply-To: <6nf5n6fdnkhx6taa2mecnsmyw7sdgaz6fbvkqy7jqkyd7jq2u7@ogsi6ije32in>
Hi Jerry,
On Thu, 2023-05-11 at 07:59 -0700, Jerry Snitselaar wrote:
>
> IIRC trying to catch the irq storm didn't work in the L490 case for
> some reason, so we might still need the dmi entry for that one.
>
> The info that the T490s had a pin wired up wrong came from Lenovo, but
> this one even looks to be a different vendor so I wonder how often
> this happens or if there is something else going on. Is it possible to
> get info about the tpm used in the Inspur system? The datasheet online
> doesn't mention it.
Are you sure about T490s? To me the wiring looks right on both s and non-s: Pin
18 / PIRQ# goes to PIRQA# of the PCH/SoC.
However on L490 Pin 18 / PIRQ# is wired wrongly to SERIRQ, which probably is the
reason that catching the interrupt storm didn't work: I guess this completely
messes up LPC communication and causes way more problems. In this case only a
DMI quirk can help.
BR
Michael
>
> Regards,
> Jerry
>
> > > Thanks,
> > >
> > > Lukas
>
next prev parent reply other threads:[~2023-05-29 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 6:12 kernel test robot
2023-05-10 22:00 ` Jarkko Sakkinen
2023-05-11 11:22 ` Lino Sanfilippo
2023-05-11 14:16 ` Lukas Wunner
2023-05-11 14:22 ` Lino Sanfilippo
2023-05-11 14:59 ` Jerry Snitselaar
2023-05-29 15:07 ` Michael Niewöhner [this message]
2023-05-29 20:58 ` Jerry Snitselaar
2023-05-30 14:40 ` Michael Niewöhner
2023-05-30 16:27 ` 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=fcdc5a27817b17d91df84bb06ad5d382829d5467.camel@mniewoehner.de \
--to=linux@mniewoehner.de \
--cc=jarkko@kernel.org \
--cc=jsnitsel@redhat.com \
--cc=l.sanfilippo@kunbus.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lukas@wunner.de \
--cc=oe-lkp@lists.linux.dev \
--cc=p.rosenberger@kunbus.com \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®