From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Tyler Stachecki" <stachecki.tyler@gmail.com>,
"Todd Brandt" <todd.e.brandt@linux.intel.com>
Cc: "Mario Limonciello" <mario.limonciello@amd.com>,
<linux-integrity@vger.kernel.org>, <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: Tue, 05 Sep 2023 01:30:20 +0300 [thread overview]
Message-ID: <CVAHLR1F623E.UTKKMHXN3GC2@suppilovahvero> (raw)
In-Reply-To: <ZPKiKrfVswqhrryZ@luigi.stachecki.net>
On Sat Sep 2, 2023 at 5:47 AM EEST, Tyler Stachecki wrote:
> On Fri, Aug 18, 2023 at 02:39:58PM -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 just ran 6.5.0-rc6 plus this patch on all 5 machines where the
> > problem was detected and they work now. It looks good.
> >
> > Tested-by: Todd Brandt <todd.e.brandt@linux.intel.com>
>
> I just wanted to report that at least on an SBC running a J4105, this
> prevented the kernel from booting *at all* ever since 6.1.46 was released.
>
> The fix which drops the ret assignment above allows the SBC to successfully
> boot a kernel again -- just mentioning for severity given that:
> 1) It also impacts the 6.1 LTS kernel that distros are tracking
> 2) In some cases, the kernel no longer boots anymore at all
>
> SBC this is seen on is a Seeed Studio ODYSSEY - X86J4105 for the curious.
>
> Tested-by: Tyler J Stachecki <stachecki.tyler@gmail.com>
Hi I submitted PR today:
https://lore.kernel.org/linux-integrity/20230904202512.29825-1-jarkko@kernel.org/T/#u
I hope this ends the story but please if does not.
Unfortunately I missed this tested-by b4 sending the PR (sorry
about that).
BR, Jarkko
next prev parent reply other threads:[~2023-09-04 22:30 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
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 [this message]
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=CVAHLR1F623E.UTKKMHXN3GC2@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=stachecki.tyler@gmail.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®