linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jerry Snitselaar <jsnitsel@redhat.com>
To: "Michael Niewöhner" <linux@mniewoehner.de>
Cc: Lino Sanfilippo <l.sanfilippo@kunbus.com>,
	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: Tue, 30 May 2023 09:27:14 -0700	[thread overview]
Message-ID: <kjcmnmspnpzp7j64msdeygfv76fah5whslldczlfzlk57cxp7b@myllnwmy43vo> (raw)
In-Reply-To: <0e837a2e859b4c633b068368f3c28ba30fc1af70.camel@mniewoehner.de>

On Tue, May 30, 2023 at 04:40:26PM +0200, Michael Niewöhner wrote:
> On Mon, 2023-05-29 at 13:58 -0700, Jerry Snitselaar wrote:
> > On Mon, May 29, 2023 at 05:07:54PM +0200, Michael Niewöhner wrote:
> > > 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
> > > 
> > 
> > I'm searching to see if I can find the old bug/email where that info
> > from Lenovo originated.  It could be that the info was wrong, and
> > it was some firmware issue instead. IIRC the the T490s issue could be
> > solved with the code looking for the irq storm, but the L490 needed
> > the dmi check even with the irq storm checking code.
> 
> Tbh I wonder why the T490s suffers from that interrupt storm at all, but that
> might be a FW bug (it's not handling the interrupt). L490 definitely needs that
> DMI check, right.
> 
> > 
> > 
> > I haven't found the info yet, but I did find some other reports from back
> > then.
> > 
> > Spurious irq reported with 5.5.7, so after the irq reverts in v5.5:
> > 
> > tpm_tis IFX0785:00: 2.0 TPM
> > Hardware name: Entroware Proteus/Proteus, BIOS 1.07.07TE0 11/15/2019
> 
> That's actually a Clevo N151CU. According to schematics it's wired correctly to
> PIRQA#, so probably a FW bug as well.
> 
> > 
> > Thinkpad P53
> > tpm_tis STM7308:00: 2.0 TPM
> > Hardware name: LENOVO 20QNCTO1WW/20QNCTO1WW, BIOS N2NET34W (1.19 ) 11/28/2019
> > 
> > 
> > 
> > Reports from before the 5.5 reverts:
> > 
> > tpm_tis MSFT0101:00: 2.0 TPM
> > Hyperbook NH5/Clevo NH55RCQ
> 
> PIRQ# wired to GPP_B0 - needs correct setup in firmware -> probably a firmware
> bug.
> 
> > 
> > tpm_tis IFX0785:00: 2.0 TPM 
> > Clevo N151CU-derived notebook
> 
> Same device as Entroware Proteus.
> 

Hi Michael,

Out of curiousity, where are you grabbing the schematics from?

Regards,
Jerry


> > 
> > 
> > Regards,
> > Jerry
> > 
> > > > 
> > > > Regards,
> > > > Jerry
> > > > 
> > > > > > Thanks,
> > > > > > 
> > > > > > Lukas
> > > > 
> > > 
> > 
> 


      reply	other threads:[~2023-05-30 16:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <202305041325.ae8b0c43-yujie.liu@intel.com>
2023-05-10 22:00 ` [linus:master] [tpm, tpm_tis] e644b2f498: RIP:acpi_safe_halt 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
2023-05-29 20:58             ` Jerry Snitselaar
2023-05-30 14:40               ` Michael Niewöhner
2023-05-30 16:27                 ` Jerry Snitselaar [this message]

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=kjcmnmspnpzp7j64msdeygfv76fah5whslldczlfzlk57cxp7b@myllnwmy43vo \
    --to=jsnitsel@redhat.com \
    --cc=jarkko@kernel.org \
    --cc=l.sanfilippo@kunbus.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@mniewoehner.de \
    --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;
as well as URLs for NNTP newsgroup(s).