From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: tpmdd-devel@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [tpmdd-devel] Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot
Date: Tue, 4 Apr 2017 11:15:33 -0600 [thread overview]
Message-ID: <20170404171533.GA3255@obsidianresearch.com> (raw)
In-Reply-To: <31e0ed69-174b-93ce-abf2-66cf08b1594e@molgen.mpg.de>
On Tue, Apr 04, 2017 at 06:29:06PM +0200, Paul Menzel wrote:
> Unfortunately, there seems to have been a regression between Linux 3.16
> and 4.8 and 4.9, so that the Linux kernel doesn’t create the TPM
> device.
That old kernel did not check error codes when reading burst count,
the new one does. It is quite possible the older kernel is failing to
read burst count and subtly malfunctioning.
It would be helpful if you could prove/disprove this statement by
adding some debugging to 3.16.
As to why the burst count cannot be read.. I don't know, check if
increasing the retries helps, it could be this particular TPM is out
of spec for the cold startup process.
> Remove module and run `sudo modprobe tpm_tis itpm=1 force=1`.
Is this really an 'itpm'? It doesn't look like it..
Jason
next prev parent reply other threads:[~2017-04-04 17:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 16:29 Paul Menzel
2017-04-04 17:15 ` Jason Gunthorpe [this message]
2017-04-04 17:44 ` [tpmdd-devel] " Paul Menzel
2017-04-05 11:03 Maciej S. Szmigiero
2017-04-05 13:36 ` Jarkko Sakkinen
2017-04-06 6:18 ` Paul Menzel
2017-04-06 11:52 ` Maciej S. Szmigiero
2017-04-06 16:55 ` Jason Gunthorpe
2017-04-06 18:26 ` Paul Menzel
2017-04-06 19:10 ` Jason Gunthorpe
2017-04-07 20:13 ` Jarkko Sakkinen
2017-04-07 20:58 ` Paul Menzel
2017-04-06 18:58 ` Jarkko Sakkinen
2017-04-08 10:40 ` Denis 'GNUtoo' Carikli
2017-04-08 20:25 ` Jason Gunthorpe
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=20170404171533.GA3255@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
--cc=tpmdd-devel@lists.sourceforge.net \
--subject='Re: [tpmdd-devel] Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot' \
/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
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).