From: Jason Gunthorpe <jgg@ziepe.ca>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Alexander.Steffen@infineon.com, 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 09:18:14 -0700 [thread overview]
Message-ID: <20171208161814.GB2883@ziepe.ca> (raw)
In-Reply-To: <c544a476-5ea9-df81-ea8b-01fa578738f0@molgen.mpg.de>
On Fri, Dec 08, 2017 at 05:07:39PM +0100, Paul Menzel wrote:
> 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`?
It is a good question, I don't know.. If your kernel isn't setup to
timestamp messages then the journalstamp will certainly be garbage.
No idea why you wouldn't see the messages in dmesg, if they are not in
dmesg they couldn't get into the journal
Jason
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Alexander.Steffen@infineon.com, 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 09:18:14 -0700 [thread overview]
Message-ID: <20171208161814.GB2883@ziepe.ca> (raw)
In-Reply-To: <c544a476-5ea9-df81-ea8b-01fa578738f0@molgen.mpg.de>
On Fri, Dec 08, 2017 at 05:07:39PM +0100, Paul Menzel wrote:
> 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`?
It is a good question, I don't know.. If your kernel isn't setup to
timestamp messages then the journalstamp will certainly be garbage.
No idea why you wouldn't see the messages in dmesg, if they are not in
dmesg they couldn't get into the journal
Jason
next prev parent reply other threads:[~2017-12-08 16:18 UTC|newest]
Thread overview: 51+ 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 12:34 ` Paul Menzel
2017-12-06 16:40 ` Jason Gunthorpe
2017-12-06 16:40 ` Jason Gunthorpe
2017-12-07 15:56 ` Alexander.Steffen
2017-12-07 15:56 ` Alexander.Steffen
2017-12-07 18:37 ` Jason Gunthorpe
2017-12-07 18:37 ` Jason Gunthorpe
2017-12-08 12:14 ` Alexander.Steffen
2017-12-08 12:14 ` Alexander.Steffen
2017-12-08 15:56 ` Jason Gunthorpe
2017-12-08 16:07 ` Paul Menzel
2017-12-08 16:07 ` Paul Menzel
2017-12-08 16:18 ` Jason Gunthorpe [this message]
2017-12-08 16:18 ` Jason Gunthorpe
2017-12-11 12:54 ` Paul Menzel
2017-12-11 12:54 ` Paul Menzel
2017-12-11 16:08 ` Alexander.Steffen
2017-12-11 16:08 ` Alexander.Steffen
2017-12-14 10:33 ` Paul Menzel
2017-12-14 10:33 ` Paul Menzel
2017-12-14 12:20 ` Alexander.Steffen
2017-12-14 12:20 ` Alexander.Steffen
2017-12-14 14:15 ` Mario.Limonciello
2017-12-14 14:15 ` Mario.Limonciello
2017-12-14 16:12 ` Alexander.Steffen
2017-12-14 16:12 ` Alexander.Steffen
2017-12-14 19:43 ` Mario.Limonciello
2017-12-14 19:43 ` Mario.Limonciello
2017-12-15 11:54 ` Paul Menzel
2017-12-15 11:54 ` Paul Menzel
2017-12-15 14:39 ` Mario.Limonciello
2017-12-15 14:39 ` Mario.Limonciello
2017-12-15 15:10 ` Paul Menzel
2017-12-15 15:10 ` Paul Menzel
2017-12-15 15:24 ` Mario.Limonciello
2017-12-15 15:24 ` Mario.Limonciello
2017-12-15 15:38 ` Paul Menzel
2017-12-15 15:38 ` Paul Menzel
2017-12-15 14:54 ` Alexander.Steffen
2017-12-15 14:54 ` Alexander.Steffen
2017-12-15 15:26 ` Paul Menzel
2017-12-15 15:26 ` Paul Menzel
2017-12-21 13:36 ` Mimi Zohar
2017-12-21 13:36 ` Mimi Zohar
2017-12-22 14:00 ` Alexander.Steffen
2017-12-22 14:00 ` Alexander.Steffen
2017-12-22 14:08 ` Paul Menzel
2017-12-22 14:08 ` Paul Menzel
2017-12-08 16:17 ` Mimi Zohar
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=20171208161814.GB2883@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Alexander.Steffen@infineon.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.