From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Mario Limonciello <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@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 16:10:54 +0100 [thread overview]
Message-ID: <6344e116-763f-98d5-5174-7395d761de45@molgen.mpg.de> (raw)
In-Reply-To: <39ff773039e04506affc4a8522bde99f@ausx13mpc120.AMER.DELL.COM>
[-- Attachment #1: Type: text/plain, Size: 3784 bytes --]
Dear Mario,
On 12/15/17 15:39, Mario.Limonciello@dell.com wrote:
>> -----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`
[…]
>> 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.
I think it started in Alexander’s reply (Message-ID:
<10b81a727ba940889095fa4bb29d0863@infineon.com>) that line breaks were
added to quotes. Your only adds a long “Original Message” header.
> <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.
Well as far as I understood it, it’s not a regression, and there is now
just better error reporting. Did you ever get the TPM to work?
>> 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
Unfortuntately it’s not listed with fwupd 0.7.0-0ubuntu4.3 in Ubuntu
16.04.3 LTS installed by Dell.
```
$ fwupdmgr get-devices
ro__sys_devices_pci0000_00_0000_00_02_0
Guid: 3ec3df3a-2290-56e5-9d2f-eda62e9ab50b
Provider: Udev
Flags: internal|locked
DeviceVendor: Intel Corporation
Created: 2017-12-15
Trusted: none
UEFI-5ffdbc0d-f340-441c-a803-8439c8c0ae10-dev0
Guid: 5ffdbc0d-f340-441c-a803-8439c8c0ae10
DisplayName: XPS 13 9360
Provider: UEFI
Flags: internal|allow-offline|require-ac
Version: 0.2.4.2
VersionLowest: 0.2.4.2
Created: 2017-12-15
Trusted: none
usb:00:05
Guid: 87c78d19-a3ed-5778-9b69-8eb701529940
DisplayName: Integrated_Webcam_HD
Provider: USB
Flags: none
Version: 99.24
Created: 2017-12-15
Trusted: none
usb:00:04
Guid: 0f15c153-cc04-589b-8886-aba87f98918d
DisplayName: Touchscreen
Provider: USB
Flags: none
Version: 17.17
Created: 2017-12-15
Trusted: none
```
>> 3. Updating to the firmware 2.4.2 from December 17th, 2017 didn’t fix
[The date is December 12th, 2017.]
> 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.
It looks like I am out of luck with Ubuntu 16.04.3 [1].
Kind regards,
Paul
[1] https://github.com/hughsie/fwupd/issues/301#issuecomment-342164366
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2017-12-15 15:10 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
2017-12-15 15:10 ` Paul Menzel [this message]
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=6344e116-763f-98d5-5174-7395d761de45@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--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=mario.limonciello@dell.com \
--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).