From: Paul Menzel <pmenzel-KUpvgZVWgV9o1qOY/usvUg@public.gmane.org>
To: Peter Huewe <PeterHuewe-Mmb7MZpHnFY@public.gmane.org>,
tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: Patrick Rudolph <siro-afHDD34IFkZrovVCs/uTlw@public.gmane.org>,
Arthur Heymans <arthur-ohM3iTZxzbjrDilwLfPoKQ@public.gmane.org>
Subject: Re: What does error code 38 mean?
Date: Mon, 24 Apr 2017 16:50:22 +0200 [thread overview]
Message-ID: <0603ee8e-ce81-9a46-4bb3-5fe4d7bda463@molgen.mpg.de> (raw)
In-Reply-To: <trinity-decde0f7-fedc-4dc2-b8e0-87a910625951-1492997557494@msvc-mesg-gmx108>
Dear Peter, dear TPM folks,
On 04/24/17 03:32, Peter Huewe wrote:
>> x60t kernel: tpm tpm0: A TPM error (38) occurred continue selftest
>
> 38=0x26= invalid post init, which means tpm did not receive tpm_startup command
> after reset.
Thank you for the quick reply. As this is during resume, could you
please point me to documentation, what is expected for resume from the
firmware?
Kind regards,
Paul
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
next prev parent reply other threads:[~2017-04-24 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 1:32 What does error code 38 mean? Peter Huewe
2017-04-24 14:50 ` Paul Menzel [this message]
[not found] ` <0603ee8e-ce81-9a46-4bb3-5fe4d7bda463-KUpvgZVWgV9o1qOY/usvUg@public.gmane.org>
2017-04-26 17:52 ` Ken Goldman
2017-04-26 17:57 ` What does error code 38 mean? -> hex vs. decimal Ken Goldman
2017-04-26 19:18 ` Jerry Snitselaar
2017-04-26 20:57 ` Ken Goldman
-- strict thread matches above, loose matches on Subject: below --
2017-04-23 19:57 What does error code 38 mean? Paul Menzel
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=0603ee8e-ce81-9a46-4bb3-5fe4d7bda463@molgen.mpg.de \
--to=pmenzel-kupvgzvwgv9o1qoy/usvug@public.gmane.org \
--cc=PeterHuewe-Mmb7MZpHnFY@public.gmane.org \
--cc=arthur-ohM3iTZxzbjrDilwLfPoKQ@public.gmane.org \
--cc=siro-afHDD34IFkZrovVCs/uTlw@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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).