[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YBSTOrlgTPpzoblY@kernel.org>
Date: Sat, 30 Jan 2021 00:59:06 +0200
From: Jarkko Sakkinen <jarkko@...nel.org>
To: Łukasz Majczak <lma@...ihalf.com>
Cc: Guenter Roeck <linux@...ck-us.net>,
Peter Huewe <peterhuewe@....de>,
Jason Gunthorpe <jgg@...pe.ca>,
linux-integrity@...r.kernel.org, linux-kernel@...r.kernel.org,
Radoslaw Biernacki <rad@...ihalf.com>,
Marcin Wojtas <mw@...ihalf.com>,
Alex Levin <levinale@...gle.com>,
James.Bottomley@...senpartnership.com
Subject: Re: [PATCH] tpm_tis: Add missing start/stop_tpm_chip calls
On Tue, Jan 26, 2021 at 04:46:07PM +0100, Łukasz Majczak wrote:
> Hi Jarkko, Guenter
>
> Yes, here are the logs when failure occurs -
> https://gist.github.com/semihalf-majczak-lukasz/1575461f585f1e7fb1e9366b8eceaab9
> Look for a phrase "TPM returned invalid status"
>
> Guenter - good suggestion - I will try to keep it as tight as possible.
>
> Best regards,
> Lukasz
Is it possible for you try out with linux-next? Thanks. It's a known
issue, which ought to be fixed by now.
The log message is harmless, it'a warning not panic, and does not
endanger system stability. WARN()'s always dump stack trace. No oops
is happening.
/Jarkko
Powered by blists - more mailing lists