From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Chris Chiu <chiu@endlessm.com>
Cc: peterhuewe@gmx.de, jgg@ziepe.ca, linux-integrity@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Upstreaming Team <linux@endlessm.com>
Subject: Re: TPM driver breaks S3 suspend
Date: Sun, 24 Dec 2017 22:33:35 +0200 [thread overview]
Message-ID: <20171224203335.su56j5qs6rt6wd4v@linux.intel.com> (raw)
In-Reply-To: <CAB4CAwfSCvj1cudi+MWaB5g2Z67d9DwY1o475YOZD64ma23UiQ@mail.gmail.com>
On Thu, Dec 21, 2017 at 04:04:56PM +0800, Chris Chiu wrote:
> Hi,
> We have a desktop which has S3 suspend (to RAM) problem due to
> error messages as follows.
> [ 198.908282] tpm tpm0: Error (38) sending savestate before suspend
> [ 198.908289] __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x160 returns 38
> [ 198.908293] dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 38
> [ 198.908298] PM: Device 00:0b failed to suspend: error 38
>
> However, the first suspend after boot is working although it still
> shows an interesting message during resume.
> [ 155.789945] tpm tpm0: A TPM error (38) occurred continue selftest
>
> The error code 38 in definition is TPM_ERR_INVALID_POSTINIT. I
> found some explanations which said this error code means that this
> command was received in the wrong sequence relative to a TPM_Startup
> command. Don't really know what happens here and how should I deal
> with this? Any suggestions? Please let me know what else information
> should I provide. Thanks
>
> Chris
The sequences for initializing TPM 1.x devices has been fairly static
for a long time. Has this occured after a kernel update? Is there a
kernel version where it used to work and a version where it doesn't?
Thanks.
/Jarkko
next prev parent reply other threads:[~2017-12-24 20:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 8:04 TPM driver breaks S3 suspend Chris Chiu
2017-12-21 9:22 ` Paul Menzel
2017-12-21 9:43 ` Chris Chiu
2017-12-24 20:35 ` Jarkko Sakkinen
2017-12-21 10:19 ` Alexander.Steffen
2017-12-21 16:17 ` Jason Gunthorpe
2017-12-22 2:05 ` Chris Chiu
2017-12-22 13:34 ` Alexander.Steffen
2017-12-24 20:37 ` Jarkko Sakkinen
2017-12-24 20:33 ` Jarkko Sakkinen [this message]
2017-12-25 2:43 ` Chris Chiu
2018-01-02 14:43 ` Jarkko Sakkinen
2018-03-15 10:11 ` Daniel Drake
2018-03-16 13:44 ` Jarkko Sakkinen
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=20171224203335.su56j5qs6rt6wd4v@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=chiu@endlessm.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=peterhuewe@gmx.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 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).