[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5a344d1ffa66fac828feb3d1c6abce010da94609.camel@linux.intel.com>
Date: Thu, 17 Aug 2023 15:25:15 -0700
From: Todd Brandt <todd.e.brandt@...ux.intel.com>
To: Jarkko Sakkinen <jarkko@...nel.org>, mario.limonciello@....com,
linux-integrity@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, len.brown@...el.com,
charles.d.prestopine@...el.com, rafael.j.wysocki@...el.com
Subject: Re: REGRESSION WITH BISECT: v6.5-rc6 TPM patch breaks S3 on some
Intel systems
On Fri, 2023-08-18 at 00:47 +0300, Jarkko Sakkinen wrote:
> On Fri Aug 18, 2023 at 12:09 AM EEST, Todd Brandt wrote:
> > While testing S3 on 6.5.0-rc6 we've found that 5 systems are seeing
> > a
> > crash and reboot situation when S3 suspend is initiated. To
> > reproduce
> > it, this call is all that's required "sudo sleepgraph -m mem
> > -rtcwake
> > 15".
>
> 1. Are there logs available?
> 2. Is this the test case: https://pypi.org/project/sleepgraph/ (never
> used it before).
There are no dmesg logs because the S3 crash wipes them out. Sleepgraph
isn't actually necessary to activate it, just an S3 suspend "echo mem >
/sys/power/state".
So far it appears to only have affected test systems, not production
hardware, and none of them have TPM chips, so I'm beginning to wonder
if this patch just inadvertently activated a bug somewhere else in the
kernel that happens to affect test hardware.
I'll continue to debug it, this isn't an emergency as so far I haven't
seen it in production hardware.
>
> I'll see if I can repeat it with QEMU + swtpm.
>
> > I’ve created a Bugzilla to track this issue here:
> > https://bugzilla.kernel.org/show_bug.cgi?id=217804
>
> Thank you for reporting this.
>
> BR, Jarkko
Powered by blists - more mailing lists