mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Peter Jung <ptr1337@cachyos.org>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
	stable@vger.kernel.org, Gregory Price <gourry@gourry.net>,
	"Borislav Petkov (AMD)" <bp@alien8.de>,
	x86@kernel.org
Subject: Re: [tip: x86/urgent] x86/CPU/AMD: Add RDSEED fix for Zen5
Date: Mon, 24 Nov 2025 23:18:50 +0100	[thread overview]
Message-ID: <aSTZylJfiN5uXDi1@duo.ucw.cz> (raw)
In-Reply-To: <9a27f2e6-4f62-45a6-a527-c09983b8dce4@cachyos.org>

[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]

Hi!

> > Add a fix glue which checks microcode revisions.
> > 
> >    [ bp: Add microcode revisions checking, rewrite. ]
> > 
> > Cc:stable@vger.kernel.org
> > Signed-off-by: Gregory Price<gourry@gourry.net>
> > Signed-off-by: Borislav Petkov (AMD)<bp@alien8.de>
> > Link:https://lore.kernel.org/r/20251018024010.4112396-1-gourry@gourry.net
> > ---
> >   arch/x86/kernel/cpu/amd.c | 10 ++++++++++
> >   1 file changed, 10 insertions(+)
> > 
> > diff --git a/arch/x86/kernel/cpu/amd.c b/arch/x86/kernel/cpu/amd.c
> > index ccaa51c..bc29be6 100644
> > --- a/arch/x86/kernel/cpu/amd.c
> > +++ b/arch/x86/kernel/cpu/amd.c
> > @@ -1035,8 +1035,18 @@ static void init_amd_zen4(struct cpuinfo_x86 *c)
> >   	}
> >   }
> > +static const struct x86_cpu_id zen5_rdseed_microcode[] = {
> > +	ZEN_MODEL_STEP_UCODE(0x1a, 0x02, 0x1, 0x0b00215a),
> > +	ZEN_MODEL_STEP_UCODE(0x1a, 0x11, 0x0, 0x0b101054),
> > +};
> > +

> This fix seems to break quite a bunch of users in CachyOS. There has been
> now several users reporting that there system can not get properly into the
> graphical interface.
> 
> CachyOS is compiling the packages with -march=znver5 and the GCC compiler
> currently does pass RDSEED.

Besides other things, GCC should probably be fixed not to do that.

And this will be fun for both mainline and -stable: security bug or
broken boot, pick one :-(.

Best regards,
								Pavel
-- 
I don't work for Nazis and criminals, and neither should you.
Boycott Putin, Trump, Netanyahu and Musk!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      parent reply	other threads:[~2025-11-24 22:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 12:01 tip-bot2 for Gregory Price
2025-10-30 18:05 ` Jason A. Donenfeld
2025-10-30 21:48   ` Jason A. Donenfeld
2025-11-03 13:59 ` Peter Jung
2025-11-03 14:28   ` Borislav Petkov
2025-11-03 16:12   ` Thomas Gleixner
2025-11-24 22:18   ` Pavel Machek [this message]

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=aSTZylJfiN5uXDi1@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=bp@alien8.de \
    --cc=gourry@gourry.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=ptr1337@cachyos.org \
    --cc=stable@vger.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®