From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jarkko Sakkinen <jarkko@kernel.org>,
"Tj (Elloe Linux)" <ml.linux@elloe.vision>
Cc: linux-integrity@vger.kernel.org, jsnitsel@redhat.com
Subject: Re: Bug: TPM returned invalid status
Date: Wed, 27 Jan 2021 10:11:56 -0800 [thread overview]
Message-ID: <b1e71d07546ccce7957ead9cc80303734251f6c9.camel@HansenPartnership.com> (raw)
In-Reply-To: <YBGqWp5FqKQJK1is@kernel.org>
On Wed, 2021-01-27 at 20:00 +0200, Jarkko Sakkinen wrote:
> On Wed, Jan 27, 2021 at 07:58:08PM +0200, Jarkko Sakkinen wrote:
> > On Mon, Jan 25, 2021 at 09:00:54AM +0000, Tj (Elloe Linux) wrote:
> > > Seeing this on Lenovo E495's that have:
> > >
> > > AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
> > >
> > > Linux version 5.11.0-rc4+ (tj@elloe000) (gcc (Ubuntu
> > > 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu)
> > > 2.34) #12 SMP PREEMPT Sun Jan 24 11:28:01 GMT 2021
> > > Command line: BOOT_IMAGE=/vmlinuz-5.11.0-rc4+
> > > root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows
> > > 2016" systemd.unified_cgroup_hierarchy=1 nosplash
> > > ...
> > > efi: EFI v2.70 by Lenovo
> > >
> > > efi: ACPI=0xbddfd000 ACPI 2.0=0xbddfd014 TPMFinalLog=0xbdc2d000
> > > SMBIOS=0xba4d7000 SMBIOS 3.0=0xba4ca000 MEMATTR=0xb5611018
> > > ESRT=0xb9075000 RNG=0xba5c2598 TPMEventLog=0xb13ae
> > > 018
> > > ...
> > > DMI: LENOVO 20NECTO1WW/20NECTO1WW, BIOS R11ET32W (1.12 )
> > > 12/23/2019
> > > ...
> > > tpm_tis NTC0702:00: 2.0 TPM (device-id 0xFC, rev-id 1)
> > > ------------[ cut here ]------------
> > > TPM returned invalid status
> > > WARNING: CPU: 3 PID: 1 at drivers/char/tpm/tpm_tis_core.c:249
> >
> > There's a patch set in cycle that should fix this:
> >
> > https://lore.kernel.org/linux-integrity/20201001180925.13808-1-James.Bottomley@HansenPartnership.com/
> >
> > James, where are we at with this?
>
> I'm interested because I'm yet to send my pr and this is generating
> constantly bug reports.
It's part of the enable interrupts series, which there's a lot of
discussion over. However, that single patch can be broken out of the
series if you like. The specific blocker was the screaming interrupt
on the Lenovo that Jerry was looking at. He propose a quirk to fix its
so perhaps we're now ready to move the entire series forward?
James
next prev parent reply other threads:[~2021-01-27 18:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 9:00 Bug: TPM returned invalid status Tj (Elloe Linux)
2021-01-27 17:58 ` Jarkko Sakkinen
2021-01-27 18:00 ` Jarkko Sakkinen
2021-01-27 18:11 ` James Bottomley [this message]
2021-01-28 5:59 ` Jarkko Sakkinen
2021-03-30 2:04 ` Kees Cook
2021-04-08 9:03 ` Tj (Elloe Linux)
2021-04-09 9:55 ` Aw: " Lino Sanfilippo
2021-04-14 11:05 ` Jarkko Sakkinen
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=b1e71d07546ccce7957ead9cc80303734251f6c9.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=jarkko@kernel.org \
--cc=jsnitsel@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=ml.linux@elloe.vision \
/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).