From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Todd Brandt <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,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: REGRESSION WITH BISECT: v6.5-rc6 TPM patch breaks S3 on some Intel systems
Date: Fri, 18 Aug 2023 07:10:48 +0700 [thread overview]
Message-ID: <ZN63CG6d3d7ifq7U@debian.me> (raw)
In-Reply-To: <485e8740385239b56753ce01d8995f01f84a68e5.camel@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On Thu, Aug 17, 2023 at 02:09:00PM -0700, 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".
>
> I’ve created a Bugzilla to track this issue here:
> https://bugzilla.kernel.org/show_bug.cgi?id=217804
>
> I've bisected the issue to this patch:
>
> commit 554b841d470338a3b1d6335b14ee1cd0c8f5d754
> Author: Mario Limonciello <mario.limonciello@amd.com>
> Date: Wed Aug 2 07:25:33 2023 -0500
>
> tpm: Disable RNG for all AMD fTPMs
>
Thanks for the regression report. I'm adding it to regzbot:
#regzbot ^introduced: 554b841d470338
#regzbot title: Disabling RNG for AMD fTPMs breaks S3 on some Intel systems
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-08-18 3:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 21:09 REGRESSION WITH BISECT: v6.5-rc6 TPM patch breaks S3 on some Intel systems Todd Brandt
2023-08-17 21:47 ` Jarkko Sakkinen
2023-08-17 22:25 ` Todd Brandt
2023-08-17 22:33 ` Jarkko Sakkinen
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 [this message]
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=ZN63CG6d3d7ifq7U@debian.me \
--to=bagasdotme@gmail.com \
--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=regressions@lists.linux.dev \
--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