Dear Peter, dear TPM folks,
On 04/24/17 03:32, Peter Huewe wrote:
>> x60t kernel: tpm tpm0: A TPM error (38) occurred continue selftest
>
> 38=0x26= invalid post init, which means tpm did not receive tpm_startup
> command
> after reset.
Thank you for the quick reply. As this is during resume,
Dear Linux folks,
On resume, Linux 4.11-rc7 logs the messages below.
```
[…]
Apr 23 21:42:05 lenovox60t kernel: pciehp :00:1c.0:pcie004: Timeout
on hotplug command 0x1038 (issued 109528 msec ago)
Apr 23 21:42:05 lenovox60t kernel: tpm tpm0: A TPM error (38) occurred
continue selftest
Apr
Dear Greg,
On 2017-04-15 22:50, Greg KH wrote:
> On Sat, Apr 15, 2017 at 06:26:22PM +0300, Jarkko Sakkinen wrote:
>> From: "Maciej S. Szmigiero"
>>
>> Since commit 1107d065fdf1 ("tpm_tis: Introduce intermediate layer for
>> TPM access") Atmel 3203 TPM on ThinkPad
Dear Robert,
Thank you for your reply.
On 2017-04-12 23:49, Moore, Robert wrote:
>> On 2017-04-12 17:54, Moore, Robert wrote:
>> > And probably the dmesg if error messages appear in there.
>>
>> Linux doesn’t log any messages, as the `tpm` module doesn’t load.
>> Please
>> find the output
Dear Robert,
Thank you for looking into this.
On 2017-04-12 17:54, Moore, Robert wrote:
And probably the dmesg if error messages appear in there.
Linux doesn’t log any messages, as the `tpm` module doesn’t load. Please
find the output of `sudo acpidump` attached.
[…]
Kind regards,
Dear Jarkko,
On 2017-04-07 22:13, Jarkko Sakkinen wrote:
> On Thu, Apr 06, 2017 at 01:10:13PM -0600, Jason Gunthorpe wrote:
>> On Thu, Apr 06, 2017 at 08:26:22PM +0200, Paul Menzel wrote:
>> > >We added direct ACPI binding to the driver in addition to PNP, so if
>>
On 2017-04-06 18:55, Jason Gunthorpe wrote:
> On Thu, Apr 06, 2017 at 08:18:33AM +0200, Paul Menzel wrote:
>
>> Indeed, that improves the situation. I still need to pass `force=1` to
>> the
>> module to get `/dev/tpm0`. No idea, why it’s not in included in Linux
>&g
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 kerne