From: Hans de Goede <hdegoede@redhat.com>
To: Jarkko Sakkinen <jarkko@kernel.org>,
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: Mon, 21 Jun 2021 14:04:52 +0200 [thread overview]
Message-ID: <49bfb4a7-eb3c-77f9-ff8e-b37617a26195@redhat.com> (raw)
In-Reply-To: <5680899e-9040-7641-e6ac-23edd2d988cf@redhat.com>
Hi,
On 6/14/21 3:33 PM, Hans de Goede wrote:
> Hi,
>
> On 6/1/21 6:04 PM, 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.
>
> Quick status update, I've got a response from a XPS 13 9310 user in:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1920510
>
> Indicating that a. he can reproduce this with the latest >= 5.12.6 kernels;
> and b. it goes away when specifying tpm_tis.interrupts=0 as I expected
> (I expected this because all the bug-reports started when the interrupt
> code got fixed/re-enabled a while ago).
One more status update.
- A new 4th variant of the backtrace has been spotted, where the problem hits
when called from probe() -> tpm2_auto_startup -> tpm2_do_selftest, see:
https://bugzilla.redhat.com/show_bug.cgi?id=1958381
- So far all reports with kernel >= 5.12.6 have been on a Dell XPS 13 9310
models. But the new variant is happening on a Dell XPS 15 9500 and the
backtrace starting at ima_add_boot_aggregate is also being reported on
a Dell XPS 15 9500 (as well as on the XPS 13 9310).
Regards,
Hans
next prev parent reply other threads:[~2021-06-21 12:05 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
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 [this message]
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=49bfb4a7-eb3c-77f9-ff8e-b37617a26195@redhat.com \
--to=hdegoede@redhat.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=jarkko@kernel.org \
--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).