From: Borislav Petkov <bp@alien8.de>
To: Dario Ackermann <dario@darioackermann.ch>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev,
x86@kernel.org, tglx@kernel.org
Subject: Re: AW: [REGRESSION] x86/microcode: boot hangs bringing up first secondary CPU on i7-6700HQ, avoided by dis_ucode_ldr
Date: Tue, 10 Nov 2026 10:52:57 -0800 [thread overview]
Message-ID: <20261110185257.GFavNoCWszSXhRkaOV@fat_crate.local> (raw)
In-Reply-To: <691747894523180440145931.1352.2026111016821@darioackermann.ch>
On Tue, Nov 10, 2026 at 04:08:17PM +0000, Dario Ackermann wrote:
> Sorry for the thread-mixup.
>
> I tested v7.4-rc2 (7475ea8b5861). It still hangs while bringing up CPU1,
> with both default AP bringup and cpuhp.parallel=0.
Ok, so I don't understand: which kernel did work fine, without any cmdline
switches?
Pls send full dmesg from that one. IOW, did any kernel at all load microcode
successfully on your machine?
Also, send one from 7.4 with dis_ucode_ldr on the cmdline.
Also, check whether you're running the latest microcode packages by updating
your distro blobs.
And put your reply under the text you're replying to, like I just did.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-11-10 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mw9nsyuj.70b4b79c-e987-49da-abe1-0164defd8d5a@darioackermann.ch>
2026-11-09 21:09 ` Dario Ackermann
[not found] ` <630330232567670562275469.6204.202611921938@darioackermann.ch>
2026-11-10 5:55 ` Thorsten Leemhuis
2026-11-10 16:08 ` Dario Ackermann
[not found] ` <691747894523180440145931.1352.2026111016821@darioackermann.ch>
2026-11-10 18:52 ` Borislav Petkov [this message]
2026-11-11 9:45 ` Dario Ackermann
[not found] ` <067545724320102351351556.0634.2026111194556@darioackermann.ch>
2026-11-12 0:42 ` Borislav Petkov
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=20261110185257.GFavNoCWszSXhRkaOV@fat_crate.local \
--to=bp@alien8.de \
--cc=dario@darioackermann.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=tglx@kernel.org \
--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
all inboxes | Powered by JetHome®