linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <Mario.Limonciello@dell.com>
To: <pmenzel@molgen.mpg.de>, <Alexander.Steffen@infineon.com>,
	<jgg@ziepe.ca>
Cc: <linux-integrity@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<rafael.j.wysocki@intel.com>, <len.brown@intel.com>
Subject: RE: [Regression 4.15-rc2] New messages `tpm tpm0: A TPM error (2314) occurred continue selftest`
Date: Fri, 15 Dec 2017 14:39:53 +0000	[thread overview]
Message-ID: <39ff773039e04506affc4a8522bde99f@ausx13mpc120.AMER.DELL.COM> (raw)
In-Reply-To: <127aefc5-44e1-7382-2548-5cd4774275b0@molgen.mpg.de>

> -----Original Message-----
> From: Paul Menzel [mailto:pmenzel@molgen.mpg.de]
> Sent: Friday, December 15, 2017 5:54 AM
> To: Limonciello, Mario <Mario_Limonciello@Dell.com>; Alexander Steffen
> <Alexander.Steffen@infineon.com>; Jason Gunthorpe <jgg@ziepe.ca>
> Cc: linux-integrity@vger.kernel.org; linux-kernel@vger.kernel.org; Rafael J.
> Wysocki <rafael.j.wysocki@intel.com>; Len Brown <len.brown@intel.com>
> Subject: Re: [Regression 4.15-rc2] New messages `tpm tpm0: A TPM error (2314)
> occurred continue selftest`
> 
> [Adding Rafael and Len as they, to my knowledge, also use or have a
> access to a Dell XPS 13 9360. With latest Linux master do you get TPM
> self-test errors, when cold starting the system without the power supply
> plugged in?]
> 
> Dear Mario, dear Alexander,
> 
> 
> the added line breaks to the quoted parts really mess up the citation.
> Can we please try to use MUAs avoiding that, or fixing that manually?

I don't know what you mean.  I think this is directed at Alexander?
If this is directed to me I can't change mail clients, sorry.

<snip>

> >
> > Yes it's required for the TPM model/vendor that is used in the XPS model that
> > Paul has.  If you try to run the upgrade without clearing it the firmware will
> > reject the upgrade.
> 
> Mario, thank you for your quick reaction.
> 
> […]
> 
> 1.  Can you reproduce this issue too?

I haven't seen this, but if this is a regression I also have not run anything
later than 4.15-rc1 right now.

> 2.  How do I find out, what TPM firmware version is installed?

fwupd will tell you.  Documentation (and code) here:
https://github.com/hughsie/fwupd/tree/master/plugins/dell

> 3.  Updating to the firmware 2.4.2 from December 17th, 2017 didn’t fix

The TPM in the XPS is a discrete TPM that is treated separately from the system
firmware payload.  It supports both a "1.2" and a "2.0" firmware. 

It is independently flashed from a separate TPM payload that is distributed
on LVFS.

  reply	other threads:[~2017-12-15 14:39 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
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 [this message]
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=39ff773039e04506affc4a8522bde99f@ausx13mpc120.AMER.DELL.COM \
    --to=mario.limonciello@dell.com \
    --cc=Alexander.Steffen@infineon.com \
    --cc=jgg@ziepe.ca \
    --cc=len.brown@intel.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    --cc=rafael.j.wysocki@intel.com \
    /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).