From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Jason Gunthorpe <jgg@ziepe.ca>, Alexander.Steffen@infineon.com
Cc: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Regression 4.15-rc2] New messages `tpm tpm0: A TPM error (2314) occurred continue selftest`
Date: Fri, 8 Dec 2017 17:07:39 +0100 [thread overview]
Message-ID: <c544a476-5ea9-df81-ea8b-01fa578738f0@molgen.mpg.de> (raw)
In-Reply-To: <20171208155641.GA2883@ziepe.ca>
Dear Jason, dear Alexander,
Thank you for your replies.
Am 08.12.2017 um 16:56 schrieb Jason Gunthorpe:
> On Fri, Dec 08, 2017 at 12:14:04PM +0000, Alexander.Steffen@infineon.com wrote:
[…]
>> Anyway, from the log messages it is clear that tpm_msleep got called
>> seven times with delays of 20/40/80/160/320/640/1280ms. But still
>> all timestamps lie within the same second. How can this be with a
>> cumulated delay of ~2.5s?
>
> Yes, that does seem to be the bug, our sleep function doesn't work
> aynmore for some reason :|
I have no access to the system right now, but want to point out, that
the log was created by `journactl -k`, so I do not know if that messes
with the time stamps. I checked the output of `dmesg` but didn’t see the
TPM error messages in the output – only `tpm_tis MSFT0101:00: 2.0 TPM
(device-id 0xFE, rev-id 4)`. Do I need to pass a different error message
to `dmesg`?
>> Also, I've just noticed that despite the name tpm_msleep calls
>> usleep_range, not msleep. Can this have an influence? Should
>> tpm_msleep call msleep for longer delays, as suggested by
>> Documentation/timers/timers-howto.txt?
>
> This change was introduced recently and is probably the source of this
> regression.
I’ll try to test this on Monday.
Kind regards,
Paul
next prev parent reply other threads:[~2017-12-08 16:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 12:34 [Regression 4.15-rc2] New messages `tpm tpm0: A TPM error (2314) occurred continue selftest` Paul Menzel
2017-12-06 16:40 ` Jason Gunthorpe
2017-12-07 15:56 ` Alexander.Steffen
2017-12-07 18:37 ` Jason Gunthorpe
2017-12-08 12:14 ` Alexander.Steffen
2017-12-08 15:56 ` Jason Gunthorpe
2017-12-08 16:07 ` Paul Menzel [this message]
2017-12-08 16:18 ` Jason Gunthorpe
2017-12-11 12:54 ` Paul Menzel
2017-12-11 16:08 ` Alexander.Steffen
2017-12-14 10:33 ` Paul Menzel
2017-12-14 12:20 ` Alexander.Steffen
2017-12-14 14:15 ` Mario.Limonciello
2017-12-14 16:12 ` Alexander.Steffen
2017-12-14 19:43 ` Mario.Limonciello
2017-12-15 11:54 ` Paul Menzel
2017-12-15 14:39 ` Mario.Limonciello
2017-12-15 15:10 ` Paul Menzel
2017-12-15 15:24 ` Mario.Limonciello
2017-12-15 15:38 ` Paul Menzel
2017-12-15 14:54 ` Alexander.Steffen
2017-12-15 15:26 ` Paul Menzel
2017-12-21 13:36 ` Mimi Zohar
2017-12-22 14:00 ` Alexander.Steffen
2017-12-22 14:08 ` Paul Menzel
2017-12-08 16:17 ` Mimi Zohar
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=c544a476-5ea9-df81-ea8b-01fa578738f0@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=Alexander.Steffen@infineon.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).