[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211018114429.GA13693@duo.ucw.cz>
Date: Mon, 18 Oct 2021 13:44:29 +0200
From: Pavel Machek <pavel@....cz>
To: Peter Zijlstra <peterz@...radead.org>
Cc: tglx@...utronix.de, mingo@...hat.com, bp@...en8.de, x86@...nel.org,
hpa@...or.com, linux-kernel@...r.kernel.org, rafael@...nel.org,
len.brown@...el.com, linux-pm@...r.kernel.org,
sfr@...b.auug.org.au, gor@...ux.ibm.com
Subject: Re: next-20211015: suspend to ram on x86-32 broken
Hi!
> > > commit 8850cb663b5cda04d33f9cfbc38889d73d3c8e24 (HEAD)
> > > Author: Peter Zijlstra <peterz@...radead.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.
Reverting smp.c hunk is enough to get suspend/resume to work.
Best regards,
Pavel
--
http://www.livejournal.com/~pavelmachek
Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)
Powered by blists - more mailing lists