From: Michael Doube <michael@doube.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Debora Velarde <debora@linux.vnet.ibm.com>,
Rajiv Andrade <srajiv@linux.vnet.ibm.com>,
Marcel Selhorst <m.selhorst@sirrix.com>,
"Rafael J. Wysocki" <rjw@suse.com>,
tpmdd-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [tpmdd-devel] [REGRESSION] Suspend fails because of TPM modules
Date: Mon, 29 Nov 2010 16:14:58 +0000 [thread overview]
Message-ID: <4CF3D182.8090907@doube.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1011291614060.981@pobox.suse.cz>
> I just found out, that if I modprobe tpm_tis module with
>
> itpm=1
>
> parameter, the problem doesn't happen any more and suspend works fine.
Not here unfortunately. Suspend still fails with itpm=1, and I get this
in my logs
Nov 29 15:52:32 doris kernel: [ 649.110527] resource map sanity check
conflict: 0xfed40000 0xfed44fff 0xfed43000 0xfed43fff Intel Flush Page
Nov 29 15:52:32 doris kernel: [ 649.110923] tpm_tis 00:09: 1.2 TPM
(device-id 0xB, rev-id 16)
Nov 29 15:52:32 doris kernel: [ 649.110929] tpm_tis 00:09: Intel iTPM
workaround enabled
Nov 29 15:54:34 doris kernel: [ 771.360067] tpm_tis 00:09:
tpm_transmit: tpm_send: error -62
Also, this patch:
http://marc.info/?l=linux-kernel&m=128769741101534&w=2
Looks for a string that is absent from my Vaio SZ650, so the workaround
is not applied (and if it was, it probably wouldn't work, right?).
I posted my DSDT to bugzilla:
https://bugzilla.kernel.org/attachment.cgi?id=38072
Michael
next prev parent reply other threads:[~2010-11-29 16:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 15:00 [REGRESSION] Suspend fails because of TPM modules Jiri Kosina
2010-11-29 15:15 ` Jiri Kosina
2010-11-29 15:19 ` Matthew Garrett
2010-11-29 15:22 ` Rajiv Andrade
2010-11-29 15:26 ` Jiri Kosina
2010-11-29 15:32 ` Matthew Garrett
2010-11-29 15:46 ` Rajiv Andrade
2010-11-29 15:41 ` Rajiv Andrade
2010-11-29 16:14 ` Michael Doube [this message]
2010-11-29 16:22 ` [tpmdd-devel] " Jiri Kosina
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=4CF3D182.8090907@doube.net \
--to=michael@doube.net \
--cc=debora@linux.vnet.ibm.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=m.selhorst@sirrix.com \
--cc=rjw@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.