From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755158AbdDDRo2 (ORCPT ); Tue, 4 Apr 2017 13:44:28 -0400 Received: from mx3.molgen.mpg.de ([141.14.17.11]:53761 "EHLO mx1.molgen.mpg.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754025AbdDDRo1 (ORCPT ); Tue, 4 Apr 2017 13:44:27 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Tue, 04 Apr 2017 19:44:24 +0200 From: Paul Menzel To: Jason Gunthorpe Cc: tpmdd-devel@lists.sourceforge.net, Linux Kernel Mailing List , "Denis 'GNUtoo' Carikli" Subject: Re: [tpmdd-devel] Regression between Linux 3.16 and 4.8/4.9 on Lenovo X60 with coreboot Organization: =?UTF-8?Q?Max-Planck-Institut_f=C3=BCr_molekulare_Genetik?= In-Reply-To: <20170404171533.GA3255@obsidianresearch.com> References: <31e0ed69-174b-93ce-abf2-66cf08b1594e@molgen.mpg.de> <20170404171533.GA3255@obsidianresearch.com> Message-ID: <6cd95003c558c2d5aac6eaaa5cd3e86e@molgen.mpg.de> User-Agent: Roundcube Webmail/1.1.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Jason, Thank you for your reply. On 2017-04-04 19:15, Jason Gunthorpe wrote: > 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. GNUtoo got the messages below. Unfortunately, I don’t know, what Linux Kernel that is. ``` tpm_tis 00:07: 1.2 TPM (device-id 0x3202, rev-id 5) tpm tpm0: A TPM error (38) occurred attempting to determine the timeouts tpm tpm0: Issuing TPM_STARTUP tpm tpm0: [Hardware Error]: Adjusting reported timeouts: A 10000->10000us B 10000->10000us C 0->750000us D 0->750000us ``` > It would be helpful if you could prove/disprove this statement by > adding some debugging to 3.16. Could you please help me with that? Can I enable certain options to get more debugging information? > 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. How can I increase the retry count? >> Remove module and run `sudo modprobe tpm_tis itpm=1 force=1`. > > Is this really an 'itpm'? It doesn't look like it.. Sorry, I don’t know. Leaving that out, gives the same messages though. ``` tpm tpm0: Unable to read burstcount tpm tpm0: tpm_transmit: tpm_send: error -16 tpm_tis tpm_tis: Could not get TPM timeouts and durations ``` Kind regards, Paul Menzel