From: Eric Paris <eparis@redhat.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: Rajiv Andrade <srajiv@linux.vnet.ibm.com>,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [tpmdd-devel] TPM chip prevents machine from suspending
Date: Wed, 30 Mar 2011 15:43:58 -0400 [thread overview]
Message-ID: <1301514238.561.9.camel@unknown001a4b0c2895> (raw)
In-Reply-To: <4D91F4BB.5090708@linux.vnet.ibm.com>
On Tue, 2011-03-29 at 11:03 -0400, Stefan Berger wrote:
> - send a command to the TPM upon resume and if TPM response returns
> with error code 38 set a flag and don't send TPM_SaveState() upon the
> next suspend; log this case; the TPM becomes unusable; machine will
> suspend a 2nd time
I assume there is no reasonable way to detect this particular piece of
broken BIOS/hardware? If not I think this sounds like the best option
to me. If the TPM doesn't work after resume not much we can do other
than accept it doesn't work and move along.....
next prev parent reply other threads:[~2011-03-30 19:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 14:08 TPM chip prevents machine from suspending Jeff Layton
2011-03-28 17:25 ` Stefan Berger
2011-03-28 18:12 ` Jeff Layton
2011-03-28 19:45 ` Jeff Layton
2011-03-28 19:57 ` Sisir Koppaka
2011-03-28 20:16 ` Jeff Layton
2011-03-28 20:32 ` Sisir Koppaka
2011-03-28 23:10 ` Stefan Berger
2011-03-29 0:19 ` Stefan Berger
2011-03-29 12:08 ` Jeff Layton
2011-03-29 12:25 ` Stefan Berger
2011-03-29 12:30 ` Jeff Layton
2011-03-29 14:30 ` Rajiv Andrade
2011-03-29 15:03 ` Stefan Berger
2011-03-30 19:43 ` Eric Paris [this message]
2012-01-21 17:01 ` [Sony Vaio TX3] TPM chip prevents machine from suspending a second time Jonathan Nieder
2012-01-23 20:52 ` Stefan Berger
2012-01-29 10:49 ` John Hughes
2012-01-29 18:22 ` Stefan Berger
2012-01-30 9:10 ` John Hughes
2012-02-26 15:44 ` Jonathan Nieder
2012-05-03 15:34 ` John Hughes
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=1301514238.561.9.camel@unknown001a4b0c2895 \
--to=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srajiv@linux.vnet.ibm.com \
--cc=stefanb@linux.vnet.ibm.com \
--cc=tpmdd-devel@lists.sourceforge.net \
/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).