From: Peter Zijlstra <peterz@infradead.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
x86@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
rafael@kernel.org, len.brown@intel.com, linux-pm@vger.kernel.org,
sfr@canb.auug.org.au, gor@linux.ibm.com
Subject: Re: next-20211015: suspend to ram on x86-32 broken
Date: Mon, 18 Oct 2021 11:15:39 +0200 [thread overview]
Message-ID: <YW07O8ZPLVnbGLR7@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20211018081300.GA18193@duo.ucw.cz>
On Mon, Oct 18, 2021 at 10:13:00AM +0200, Pavel Machek wrote:
> Hi!
> > It said
> >
> > commit 8850cb663b5cda04d33f9cfbc38889d73d3c8e24 (HEAD)
> > Author: Peter Zijlstra <peterz@infradead.org>
> > Date: Tue Sep 21 22:16:02 2021 +0200
> >
> > sched: Simplify wake_up_*idle*()
> >
> > is first bad commit.
>
> And reverting that one on the top of -next indeed fixes resume on
> thinkpad x60.
Can you try with just reverting the smp.c hunk and leaving the sched
hunk in place? I've got a hotplug lock related splat in my inbox from
late last week that I didn't get around to yet, I suspect they're
related.
next prev parent reply other threads:[~2021-10-18 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 9:39 5.15-rc on x86-32: chromium dies with floating point exception Pavel Machek
2021-10-17 10:25 ` next-20211015: suspend to ram on x86-32 broken Pavel Machek
2021-10-18 7:13 ` Pavel Machek
2021-10-18 8:13 ` Pavel Machek
2021-10-18 9:15 ` Peter Zijlstra [this message]
2021-10-18 11:44 ` Pavel Machek
2021-10-18 14:52 ` Peter Zijlstra
2021-10-17 10:41 ` 5.15-rc on x86-32: chromium dies with floating point exception Borislav Petkov
2021-10-17 12:58 ` Pavel Machek
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=YW07O8ZPLVnbGLR7@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=gor@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
--cc=rafael@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.