From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: Rajiv Andrade <srajiv@linux.vnet.ibm.com>
Cc: Jeff Layton <jlayton@poochiereds.net>,
linux-kernel@vger.kernel.org, tpmdd-devel@lists.sourceforge.net,
"debora@linux.vnet.ibm.com" <debora@linux.vnet.ibm.com>
Subject: Re: TPM chip prevents machine from suspending
Date: Tue, 29 Mar 2011 11:03:23 -0400 [thread overview]
Message-ID: <4D91F4BB.5090708@linux.vnet.ibm.com> (raw)
In-Reply-To: <4D91ED0C.8070503@linux.vnet.ibm.com>
On 03/29/2011 10:30 AM, Rajiv Andrade wrote:
> On 03/29/2011 09:25 AM, Stefan Berger wrote:
>> On 03/29/2011 08:08 AM, Jeff Layton wrote:
>>>>> Is there some way short of recompiling with CONFIG_TCG_* turned off
>>> to disable the TPM driver at boot time?
>>>
>> As far as I know, 'no'. I'd defer it to the maintainers as to how they would want to solve your particular problem... either by using above work-around, which would be more transparent, or actively having to turn the driver off with a command line parameter.
>>
>> Stefan
>>
> I'm handling a patch from Stefan that solves so, for now,
> I'd recommend to use Stefan's tool.
Well, at least none of the patches I submitted in the series solves this
particular problem.
I am not sure whether this problem should be fixed since it's hopefully
rare. If it was to be fixed, how it should be fixed. Here are a couple
of options:
- declare it a lost case due to broken out-of-spec BIOS -- don't fix it;
machine won't suspend a 2nd time
- 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
- send a command to the TPM upon resume and if it returns with error
code 38 send TPM_Startup(ST_STATE) -> this masks the BIOS problem; log
this case; TPM stays usable; machine will suspend a 2nd time; a
colleague tells me it may not be 'safe'
Options 2 and 3 would now also run for all the rest of the machines with
a good BIOS...
Stefan
next prev parent reply other threads:[~2011-03-29 15:42 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 [this message]
2011-03-30 19:43 ` [tpmdd-devel] " Eric Paris
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=4D91F4BB.5090708@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=debora@linux.vnet.ibm.com \
--cc=jlayton@poochiereds.net \
--cc=linux-kernel@vger.kernel.org \
--cc=srajiv@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).