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" <rafael.j.wysocki@intel.com>,
Len Brown <len.brown@intel.com>,
Thorsten Leemhuis <linux@leemhuis.info>
Subject: Re: [Regression 4.15-rc2] New messages `tpm tpm0: A TPM error (2314) occurred continue selftest`
Date: Fri, 15 Dec 2017 16:38:09 +0100 [thread overview]
Message-ID: <6076476b-ee73-d7f4-481b-3bc98e1127c5@molgen.mpg.de> (raw)
In-Reply-To: <5bb6d2bc874f4227b7341c88373cf01f@ausx13mpc120.AMER.DELL.COM>
[-- Attachment #1: Type: text/plain, Size: 3455 bytes --]
Dear Mario,
On 12/15/17 16:24, Mario.Limonciello@dell.com wrote:
>> -----Original Message-----
>> From: Paul Menzel [mailto:pmenzel@molgen.mpg.de]
>> Sent: Friday, December 15, 2017 9:11 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@intel.com; len.brown@intel.com
>> Subject: Re: [Regression 4.15-rc2] New messages `tpm tpm0: A TPM error (2314)
>> occurred continue selftest`
>>
>> 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`
[…]
>>>> 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?
>
> I don't personally use a TPM with Linux on the XPS 9360, but TPM was
> tested by our partners when the XPS 9360 was enabled for Ubuntu.
It’d be great to know how it was tested, as currently it doesn’t work
here. I included the output in my reply to Alexander just 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
>>
>> Unfortuntately it’s not listed with fwupd 0.7.0-0ubuntu4.3 in Ubuntu
>> 16.04.3 LTS installed by Dell.
>
> If you're unwilling to upgrade to a newer userspace, you can write
> a simple application that can use the new dell-smbios from 4.15 interface to look this up.
Is the newer userspace officially supported by Dell. Because I really
like to avoid the time-waste with the Dell support again, if I do not
use their installed OS. Sometimes the Dell support even claims the
installed Ubuntu flavor does not get any support by Dell.
> Most of the work is already done (see
> https://github.com/torvalds/linux/blob/master/tools/wmi/dell-smbios-example.c#L179)
>
> You'll just need to add some parsing around the output (see fwupd code) to
> tell the version. If you do this, please feel free to submit it platform-x86, it may be useful
> for someone else in this sample application too.
>
> Given you don't have a newer fwupd on your system you won't be able to "easily" flash
> the newer TPM firmware.
I assume you don’t make these decisions, but please relay to your
superiors that working functionality in the recommended/shipped OS is
really what customers expect buying a device with GNU/Linux support. In
my opinion, Dell and Canonical really need to step up there.
Kind regards,
Paul
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2017-12-15 15:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 12:34 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
2017-12-15 15:24 ` Mario.Limonciello
2017-12-15 15:38 ` Paul Menzel [this message]
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=6076476b-ee73-d7f4-481b-3bc98e1127c5@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=linux@leemhuis.info \
--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
all inboxes | Powered by JetHome®