mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Windl, Ulrich" <u.windl@ukr.de>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Running new kernel on old (non-supported) CPU: Should it boot?
Date: Fri, 14 Nov 2025 11:50:53 +0000	[thread overview]
Message-ID: <f91888aed1914a6ca316369c5068aa94@ukr.de> (raw)

Hi!

I was confused by dmesg staring with the message

[    0.000000] unchecked MSR access error: RDMSR from 0x8b at rIP: 0xc156f2b0 (microcode_loader_disabled+0x3b/0x5a)
[    0.000000] Call Trace:
[    0.000000]  <IRQ>
[    0.000000]  </IRQ>
[    0.000000] Linux version 6.6.113 (oe-user@oe-host) (i586-poky-linux-gcc (GCC) 14.3.0, GNU ld (GNU Binutils) 2.44.0.20250715) #1 Sun Oct 19 14:31:02 UTC 2025

(issue can be found at https://unix.stackexchange.com/q/801323/320598, too)

So (as I read it) the kernel failed to update the CPU microcode due to RDMSR failing.
I'm unsure why it failed, but possibly because the old32-bit AMD Geode CPU does not support it.

The question remaining is:
Can the ability to update the microcode be tested with less noise (and then reported in plain words like "This CPU does not support microcode updates"),
Or is the kernel expected to run on such CPU at all? If not, should it panic with a corresponding message?

Sorry for the noise, but I have an embedded system that behaves odd since updating the firmware (and the Linux kernel). I'm just wondering whether it's a software issue, or a hardware issue (not incompatibility, but a defect).

Keep me in CC: when answering, or comment at stackexchange, as you prefer.

Kind regards,
Ulrich Windl


                 reply	other threads:[~2025-11-14 11:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=f91888aed1914a6ca316369c5068aa94@ukr.de \
    --to=u.windl@ukr.de \
    --cc=linux-kernel@vger.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®