linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Erhard Furtner <erhard_f@mailbox.org>,
	x86@kernel.org, Linux Regressions <regressions@lists.linux.dev>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	jpoimboe@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Breno Leitao <leitao@debian.org>
Subject: Re: [bisected] Kernel v6.9-rc3 fails to boot on a Thinkpad T60 with MITIGATION_RETHUNK=y (regression from v6.8.5)
Date: Sat, 13 Apr 2024 11:46:09 +0200	[thread overview]
Message-ID: <68e3503c-5573-4d82-8fb0-5b955c212d67@leemhuis.info> (raw)
In-Reply-To: <ZhpOIeVq1KQXzjBp@archie.me>

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


  reply	other threads:[~2024-04-13  9:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-13  0:49 [bisected] Kernel v6.9-rc3 fails to boot on a Thinkpad T60 with MITIGATION_RETHUNK=y (regression from v6.8.5) Erhard Furtner
2024-04-13  9:19 ` Bagas Sanjaya
2024-04-13  9:46   ` Linux regression tracking (Thorsten Leemhuis) [this message]
2024-04-13 10:49     ` Erhard Furtner
2024-04-14  8:36     ` Borislav Petkov
2024-04-14  9:08       ` Borislav Petkov
2024-04-17  8:38         ` Linux regression tracking (Thorsten Leemhuis)
2024-04-17  8:40           ` Thorsten Leemhuis

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=68e3503c-5573-4d82-8fb0-5b955c212d67@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=bagasdotme@gmail.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=erhard_f@mailbox.org \
    --cc=jpoimboe@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=regressions@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).