[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <nycvar.YFH.7.76.1905292327080.1962@cbobk.fhfr.pm>
Date: Wed, 29 May 2019 23:27:34 +0200 (CEST)
From: Jiri Kosina <jikos@...nel.org>
To: Pavel Machek <pavel@....cz>
cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Peter Zijlstra <peterz@...radead.org>, x86@...nel.org,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3] x86/power: Fix 'nosmt' vs. hibernation triple fault
during resume
On Wed, 29 May 2019, Pavel Machek wrote:
> > As explained in
> >
> > 0cc3cd21657b ("cpu/hotplug: Boot HT siblings at least once")
> >
> > we always, no matter what, have to bring up x86 HT siblings during boot at
> > least once in order to avoid first MCE bringing the system to its
> > knees.
>
>
> > Cc: stable@...r.kernel.org # v4.19+
> > Debugged-by: Thomas Gleixner <tglx@...utronix.de>
> > Fixes: 0cc3cd21657b ("cpu/hotplug: Boot HT siblings at least once")
> > Signed-off-by: Jiri Kosina <jkosina@...e.cz>
>
> Acked-by: Pavel Machek <pavel@....cz>
>
> But I'm less sure if this is -stable material. Is reverting
> 0cc3cd21657be04cb0559fe8063f2130493f92cf in -stable an option?
Well, without that commit, first MCE to come kills nosmt system.
--
Jiri Kosina
SUSE Labs
Powered by blists - more mailing lists