From: Jarkko Sakkinen <jarkko@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>,
Matthew Garrett <mjg59@google.com>,
linux-integrity <linux-integrity@vger.kernel.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: Recent tpm_tis IRQ handling changes are causing kernel backtraces
Date: Tue, 1 Jun 2021 21:03:13 +0300 [thread overview]
Message-ID: <20210601180313.vd32yqaqjjt5gzrv@kernel.org> (raw)
In-Reply-To: <89d5b891-97d8-caed-4eb1-6d4d485a2fd1@redhat.com>
On Tue, Jun 01, 2021 at 06:04:40PM +0200, Hans de Goede wrote:
> Hi,
>
> On 5/31/21 6:36 AM, Jarkko Sakkinen wrote:
> >> Interestingly enough the first backtrace is also happening on a:
> >> "Dell Inc. XPS 13 9310/0MRT12, BIOS 2.2.0 04/06/2021"
> >>
> >> So it seems that at least with 5.12.6 (which has the last 2 fixes)
> >> all reports are about the XPS 13 9310. I wonder if there is an
> >> issue with the TPM interrupt line on the XPS 13 9310; I've asked the
> >> reporters to try adding tpm_tis.interrupts=0 to their kernel commandline.
> >
> > This is helpful for sure that these all are happening on matching hardware.
>
> So our kernel-backtrace tracking info (ABRT) just recorded a third backtrace
> with a kernel >= 5.12.6, again on the XPS 13 9310, so now we have 3 variants:
>
> 1. Backtrace starting with a call to ima_add_boot_aggregate
> https://bugzilla.redhat.com/show_bug.cgi?id=1963712
>
> 2. Backtrace starting with a call to tpm_dev_async_work:
> https://bugzilla.redhat.com/show_bug.cgi?id=1964974
> (note this one is not easily reproducible)
>
> 3. Backtrace starting with a call to rng_dev_read:
> https://bugzilla.redhat.com/show_bug.cgi?id=1920510
>
> 3. is the new one. All bugs linked above are public, all 3 backtraces
> so far have only been reported on the XPS 13 9310 (with kernel >= 5.12.6)
> and I've asked all the reporters to check if tpm_tis.interrupts=0 helps.
>
> Regards,
>
> Hans
I'll put myself watcher for each of these once I have the account, thank
you (will take tomorrow, it's 9PM atm).
/Jarkko
next prev parent reply other threads:[~2021-06-01 18:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 13:09 Recent tpm_tis IRQ handling changes are causing kernel backtraces Hans de Goede
2021-03-16 15:34 ` Hans de Goede
2021-03-16 19:18 ` Jarkko Sakkinen
2021-05-08 9:07 ` Hans de Goede
2021-05-10 17:25 ` Jarkko Sakkinen
2021-05-11 8:37 ` Hans de Goede
2021-05-11 23:48 ` Jarkko Sakkinen
2021-05-26 19:03 ` Hans de Goede
2021-05-27 14:00 ` Jarkko Sakkinen
2021-05-27 15:27 ` Hans de Goede
[not found] ` <20210531043616.u3v25qzkkrik5apq@kernel.org>
2021-05-31 8:24 ` Hans de Goede
2021-06-01 18:02 ` Jarkko Sakkinen
2021-06-01 16:04 ` Hans de Goede
2021-06-01 18:03 ` Jarkko Sakkinen [this message]
2021-06-14 13:33 ` Hans de Goede
2021-06-15 13:01 ` Jarkko Sakkinen
2021-06-15 13:59 ` Hans de Goede
2021-06-23 13:37 ` Jarkko Sakkinen
2021-06-21 12:04 ` Hans de Goede
2021-06-23 13:40 ` Jarkko Sakkinen
2021-06-23 13:54 ` Hans de Goede
2021-06-29 18:04 ` Recent tpm_tis IRQ handling changes are causing kernel backtraces] Jarkko Sakkinen
2021-06-29 19:14 ` Hans de Goede
2021-06-29 22:05 ` Jarkko Sakkinen
2021-06-30 12:47 ` Hans de Goede
2021-06-30 13:36 ` Hans de Goede
2021-07-09 18:44 ` Jarkko Sakkinen
2021-07-17 16:10 ` Hans de Goede
2021-07-27 2:50 ` 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=20210601180313.vd32yqaqjjt5gzrv@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=hdegoede@redhat.com \
--cc=jsnitsel@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=mjg59@google.com \
/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).