[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230523151956.GB31298@wunner.de>
Date: Tue, 23 May 2023 17:19:56 +0200
From: Lukas Wunner <lukas@...ner.de>
To: Péter Ujfalusi <peter.ujfalusi@...ux.intel.com>
Cc: Lino Sanfilippo <LinoSanfilippo@....de>, peterhuewe@....de,
jarkko@...nel.org, jgg@...pe.ca, jsnitsel@...hat.com,
hdegoede@...hat.com, oe-lkp@...ts.linux.dev, lkp@...el.com,
peterz@...radead.org, linux@...ewoehner.de,
linux-integrity@...r.kernel.org, linux-kernel@...r.kernel.org,
l.sanfilippo@...bus.com, p.rosenberger@...bus.com
Subject: Re: [PATCH 1/2] tpm, tpm_tis: Handle interrupt storm
On Tue, May 23, 2023 at 12:35:09PM +0300, Péter Ujfalusi wrote:
> In some boot I don't get a print at all and reboot takes
> 2 minutes (tpm timeout), or as it happened now:
>
> # dmesg | grep tpm
> [ 4.306999] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0x1B, rev-id 22)
> [ 4.325868] [PETER] tpm_tis_process_unhandled_interrupt: unhandled_irqs: 1
> [ 4.325908] [PETER] tpm_tis_process_unhandled_interrupt: unhandled_irqs: 2
> ...
> [ 4.329579] [PETER] tpm_tis_process_unhandled_interrupt: unhandled_irqs: 91
> [ 5.129056] [PETER] tpm_tis_process_unhandled_interrupt: unhandled_irqs: 1
> ...
> [ 5.129561] [PETER] tpm_tis_process_unhandled_interrupt: unhandled_irqs: 10
This looks like the interrupt line may be floating and any interrupts
you get are probably caused by induced static or something.
Thanks,
Lukas
Powered by blists - more mailing lists