All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>, Jason Gunthorpe <jgg@ziepe.ca>
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: Thu, 21 Dec 2017 08:36:00 -0500	[thread overview]
Message-ID: <1513863360.5221.53.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <d70c683a-9ac2-e731-d6fd-173ac35c5b1b@molgen.mpg.de>

Hi Paul,

On Mon, 2017-12-11 at 13:54 +0100, Paul Menzel wrote:
> Dear Jason,
> 
> 
> On 12/08/17 17:18, Jason Gunthorpe wrote:
> > 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
> 
> It looks like I was running an older Linux kernel version, when running 
> `dmesg`. Sorry for the noise. Here are the messages with the Linux 
> kernel time stamps, showing that the delays work correctly.
> 
> ```
> $ uname -a
> Linux Ixpees 4.15.0-041500rc2-generic #201712031230 SMP Sun Dec 3 
> 17:32:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> $ sudo dmesg | grep TPM
> [    0.000000] ACPI: TPM2 0x000000006F332168 000034 (v03        Tpm2Tabl 
> 00000001 AMI  00000000)
> [    1.114355] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
> [    1.125250] tpm tpm0: A TPM error (2314) occurred continue selftest
> [    1.156645] tpm tpm0: A TPM error (2314) occurred continue selftest
> [    1.208053] tpm tpm0: A TPM error (2314) occurred continue selftest
> [    1.299640] tpm tpm0: A TPM error (2314) occurred continue selftest
> [    1.471223] tpm tpm0: A TPM error (2314) occurred continue selftest
> [    1.802819] tpm tpm0: A TPM error (2314) occurred continue selftest
> [    2.454320] tpm tpm0: A TPM error (2314) occurred continue selftest
> [    3.734808] tpm tpm0: TPM self test failed
> [    3.759675] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
> ```

I've sort of been following this thread, but just want to make sure
that once the self test is/was fixed, that you aren't seeing the IMA
message.

Assuming this is fixed, could someone provide the commit that fixes
it?

thanks,

Mimi

WARNING: multiple messages have this Message-ID (diff)
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>, Jason Gunthorpe <jgg@ziepe.ca>
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: Thu, 21 Dec 2017 08:36:00 -0500	[thread overview]
Message-ID: <1513863360.5221.53.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <d70c683a-9ac2-e731-d6fd-173ac35c5b1b@molgen.mpg.de>

Hi Paul,

On Mon, 2017-12-11 at 13:54 +0100, Paul Menzel wrote:
> Dear Jason,
> 
> 
> On 12/08/17 17:18, Jason Gunthorpe wrote:
> > 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
> 
> It looks like I was running an older Linux kernel version, when running 
> `dmesg`. Sorry for the noise. Here are the messages with the Linux 
> kernel time stamps, showing that the delays work correctly.
> 
> ```
> $ uname -a
> Linux Ixpees 4.15.0-041500rc2-generic #201712031230 SMP Sun Dec 3 
> 17:32:03 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> $ sudo dmesg | grep TPM
> [    0.000000] ACPI: TPM2 0x000000006F332168 000034 (v03        Tpm2Tabl 
> 00000001 AMI  00000000)
> [    1.114355] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
> [    1.125250] tpm tpm0: A TPM error (2314) occurred continue selftest
> [    1.156645] tpm tpm0: A TPM error (2314) occurred continue selftest
> [    1.208053] tpm tpm0: A TPM error (2314) occurred continue selftest
> [    1.299640] tpm tpm0: A TPM error (2314) occurred continue selftest
> [    1.471223] tpm tpm0: A TPM error (2314) occurred continue selftest
> [    1.802819] tpm tpm0: A TPM error (2314) occurred continue selftest
> [    2.454320] tpm tpm0: A TPM error (2314) occurred continue selftest
> [    3.734808] tpm tpm0: TPM self test failed
> [    3.759675] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
> ```

I've sort of been following this thread, but just want to make sure
that once the self test is/was fixed, that you aren't seeing the IMA
message.

Assuming this is fixed, could someone provide the commit that fixes
it?

thanks,

Mimi

  parent reply	other threads:[~2017-12-21 13:36 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
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 [this message]
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=1513863360.5221.53.camel@linux.vnet.ibm.com \
    --to=zohar@linux.vnet.ibm.com \
    --cc=Alexander.Steffen@infineon.com \
    --cc=jgg@ziepe.ca \
    --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.