[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <68e3503c-5573-4d82-8fb0-5b955c212d67@leemhuis.info>
Date: Sat, 13 Apr 2024 11:46:09 +0200
From: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@...mhuis.info>
To: Bagas Sanjaya <bagasdotme@...il.com>,
Erhard Furtner <erhard_f@...lbox.org>, x86@...nel.org,
Linux Regressions <regressions@...ts.linux.dev>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
jpoimboe@...nel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>, Breno Leitao <leitao@...ian.org>
Subject: Re: [bisected] Kernel v6.9-rc3 fails to boot on a Thinkpad T60 with
MITIGATION_RETHUNK=y (regression from v6.8.5)
On 13.04.24 11:19, Bagas Sanjaya wrote:
> On Sat, Apr 13, 2024 at 02:49:56AM +0200, Erhard Furtner wrote:
>> Greetings!
>>
>> With MITIGATION_RETHUNK=y selected in kernel .config v6.9-rc3 fails to boot on my Thinkpad T60. The resulting kernel stalls booting at "x86/fpu: x87 FPU will use FXSAVE":
>> [...]
>> 4461438a8405e800f90e0e40409e5f3d07eed381 is the first bad commit
There was an earlier report about this here:
https://lore.kernel.org/all/78e0d19c-b77a-4169-a80f-2eef91f4a1d6@gmail.com/
Boris there suggested: "perhaps we should make
CONFIG_MITIGATION_RETHUNK depend on !X86_32":
https://lore.kernel.org/all/20240403173059.GJZg2SUwS8MXw7CdwF@fat_crate.local/
But that did not happen afaics. Would it be wise to go down that path?
Ciao, Thorsten
Powered by blists - more mailing lists