From: Jarkko Sakkinen <jarkko@kernel.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Peter Huewe <peterhuewe@gmx.de>,
linux-integrity@vger.kernel.org, jgg@ziepe.ca,
James.Bottomley@hansenpartnership.com
Subject: Re: Dell XPS 13 9310 2-in-1: tpm tpm0: invalid TPM_STS.x 0xff, dumping stack for forensics
Date: Wed, 4 May 2022 09:31:30 +0300 [thread overview]
Message-ID: <YnIdwmLR4qtJUbS3@kernel.org> (raw)
In-Reply-To: <a1d39c04-d0a4-4b0b-5e39-5330e79d5fc0@molgen.mpg.de>
On Thu, Apr 28, 2022 at 05:35:37PM +0200, Paul Menzel wrote:
> Dear Linux folks,
>
>
> On a Dell XPS 13 9310 2-in-1, Linux 5.17.3 on Debian sid/unstable logs the
> trace below:
>
> ```
> [ 0.000000] Linux version 5.17.0-1-amd64 (debian-kernel@lists.debian.org)
> (gcc-11 (Debian 11.2.0-20) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1
> SMP PREEMPT Debian 5.17.3-1 (2022-04-18)
> […]
> [ 0.000000] DMI: Dell Inc. XPS 13 9310 2-in-1/02P55J, BIOS 2.7.0
> 12/11/2021
> […]
> [171059.677004] tpm tpm0: invalid TPM_STS.x 0xff, dumping stack for
> forensics
> [171059.677012] CPU: 5 PID: 38885 Comm: kworker/5:0 Not tainted
> 5.17.0-1-amd64 #1 Debian 5.17.3-1
> [171059.677014] Hardware name: Dell Inc. XPS 13 9310 2-in-1/02P55J, BIOS
> 2.7.0 12/11/2021
> [171059.677016] Workqueue: tpm_dev_wq tpm_dev_async_work
> [171059.677022] Call Trace:
> [171059.677025] <TASK>
> [171059.677028] dump_stack_lvl+0x48/0x5e
> [171059.677032] tpm_tis_status.cold+0x19/0x20
> [171059.677035] tpm_tis_send_data+0x3f/0x250
> [171059.677037] tpm_tis_send_main+0x2e/0xf0
> [171059.677039] tpm_transmit+0xd3/0x3e0
> [171059.677041] tpm_dev_transmit.constprop.0+0x67/0xc0
> [171059.677043] ? tpm_try_get_ops+0x44/0x90
Weird, TPM gives 0xFF when locality is not set, and it is set according
to the log. Initially looks like faulty behaving TPM.
BR, Jarkko
prev parent reply other threads:[~2022-05-04 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a1d39c04-d0a4-4b0b-5e39-5330e79d5fc0@molgen.mpg.de>
2022-04-29 8:04 ` Dell XPS 13 9310 2-in-1: tpm tpm0: invalid TPM_STS.x 0xff, dumping stack for forensics Paul Menzel
2022-04-29 12:22 ` Paul Menzel
2022-05-04 6:31 ` Jarkko Sakkinen [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=YnIdwmLR4qtJUbS3@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=pmenzel@molgen.mpg.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;
as well as URLs for NNTP newsgroup(s).