From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: <todd.e.brandt@linux.intel.com>, <mario.limonciello@amd.com>,
<linux-integrity@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <len.brown@intel.com>,
<charles.d.prestopine@intel.com>, <rafael.j.wysocki@intel.com>
Subject: Re: REGRESSION WITH BISECT: v6.5-rc6 TPM patch breaks S3 on some Intel systems
Date: Fri, 18 Aug 2023 01:33:23 +0300 [thread overview]
Message-ID: <CUV6EA5WZ2O5.5G3IV9BQITOG@suppilovahvero> (raw)
In-Reply-To: <5a344d1ffa66fac828feb3d1c6abce010da94609.camel@linux.intel.com>
On Fri Aug 18, 2023 at 1:25 AM EEST, Todd Brandt wrote:
> 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.
OK, I'll still see if I could reproduce it just in case.
BR, Jarkko
next prev parent reply other threads:[~2023-08-17 22:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 21:09 Todd Brandt
2023-08-17 21:47 ` Jarkko Sakkinen
2023-08-17 22:25 ` Todd Brandt
2023-08-17 22:33 ` Jarkko Sakkinen [this message]
2023-08-18 1:58 ` Limonciello, Mario
2023-08-18 17:00 ` Jarkko Sakkinen
2023-08-18 17:21 ` Mario Limonciello
[not found] ` <CUVV2MQRCGET.2U22LFQPX1J3G@suppilovahvero>
2023-08-18 17:57 ` Mario Limonciello
2023-08-18 18:07 ` Jarkko Sakkinen
2023-08-18 18:11 ` Mario Limonciello
2023-08-18 20:08 ` Todd Brandt
2023-08-18 21:39 ` Todd Brandt
2023-09-02 2:47 ` Tyler Stachecki
2023-09-04 22:30 ` Jarkko Sakkinen
2023-08-18 16:51 ` Jarkko Sakkinen
2023-08-18 0:10 ` Bagas Sanjaya
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=CUV6EA5WZ2O5.5G3IV9BQITOG@suppilovahvero \
--to=jarkko@kernel.org \
--cc=charles.d.prestopine@intel.com \
--cc=len.brown@intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=rafael.j.wysocki@intel.com \
--cc=todd.e.brandt@linux.intel.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®