lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAB4CAwdreurhxYz82PN_1guRK67=PvZxGa3zVhQ_opN8+guH0A@mail.gmail.com>
Date:   Thu, 21 Dec 2017 17:43:35 +0800
From:   Chris Chiu <chiu@...lessm.com>
To:     Paul Menzel <pmenzel@...gen.mpg.de>
Cc:     Linux Kernel <linux-kernel@...r.kernel.org>,
        Linux Upstreaming Team <linux@...lessm.com>,
        Alexander Steffen <Alexander.Steffen@...ineon.com>,
        Peter Huewe <PeterHuewe@....de>,
        Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
        Jason Gunthorpe <jgg@...pe.ca>, linux-integrity@...r.kernel.org
Subject: Re: TPM driver breaks S3 suspend

On Thu, Dec 21, 2017 at 5:22 PM, Paul Menzel <pmenzel@...gen.mpg.de> wrote:
> Dear Chris,
>
>
> Thank you for bringin gup the issue.
>
>>      We have a desktop which has S3 suspend (to RAM) problem due to
>> error messages as follows.
>> [  198.908282] tpm tpm0: Error (38) sending savestate before suspend
>> [  198.908289] __pnp_bus_suspend(): tpm_pm_suspend+0x0/0x160 returns 38
>> [  198.908293] dpm_run_callback(): pnp_bus_suspend+0x0/0x20 returns 38
>> [  198.908298] PM: Device 00:0b failed to suspend: error 38
>>
>>      However, the first suspend after boot is working although it still
>> shows an interesting message during resume.
>> [  155.789945] tpm tpm0: A TPM error (38) occurred continue selftest
>>
>>      The error code 38 in definition is TPM_ERR_INVALID_POSTINIT. I
>> found some explanations which said this error code means that this
>> command was received in the wrong sequence relative to a TPM_Startup
>> command. Don't really know what happens here and how should I deal
>> with this? Any suggestions? Please let me know what else information
>> should I provide.
>
>
> Please provide more information. Tell us your Linux version, attach your
> config and tell us the system name and if you know it the TPM version.

Sorry for the missing information. This is reproducible in kernel 4.14
and latest
4.15-rc2 with all TPM drivers selected. What system name do you need? It's
Acer Desktop Veriton 4410G. The TPM version shows in dmesg is
[    0.640244] tpm_tis 00:0b: 1.2 TPM (device-id 0xFE, rev-id 71)

Chris

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ