From: Jens Axboe <axboe@kernel.dk>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
the arch/x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: AMD zen microcode updates breaks boot
Date: Fri, 27 Sep 2024 09:17:46 -0600 [thread overview]
Message-ID: <91194406-3fdf-4e38-9838-d334af538f74@kernel.dk> (raw)
Hi,
Got home from conference travels and updated two test boxes to current
-git (sha 075dbe9f6e3c), both AMD boxes. One of them boots fine, the
other one does not. One is a Dell R7525, cpu:
2 socket AMD EPYC 7763 64-Core Processor
and it boots fine on -git. The other is a Dell R7625, cpu:
2 socket AMD EPYC 9754 128-Core Processor
and that one does not boot. Just get a black screen when the kernel
should load. Because I didn't have much to go on here, I bisected the
issue, and it came up with:
94838d230a6c835ced1bad06b8759e0a5f19c1d3 is the first bad commit
commit 94838d230a6c835ced1bad06b8759e0a5f19c1d3 (HEAD)
Author: Borislav Petkov <bp@alien8.de>
Date: Thu Jul 25 13:20:37 2024 +0200
x86/microcode/AMD: Use the family,model,stepping encoded in the patch ID
which seems plausible. And indeed, reverting that commit (and its fixup)
on top of current -git does indeed solve it. Happy to test patches,
unfortunately I don't have much to offer up in terms of oops or whatever
to help diagnose this. In lieu of instant ideas to prevent this issue on
-rc1, perhaps a revert?
--
Jens Axboe
next reply other threads:[~2024-09-27 15:17 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 15:17 Jens Axboe [this message]
2024-09-28 6:10 ` AMD zen microcode updates breaks boot Borislav Petkov
2024-09-28 11:31 ` Jens Axboe
2024-09-30 4:43 ` Borislav Petkov
2024-09-30 12:27 ` Jens Axboe
2024-09-30 16:16 ` Borislav Petkov
2024-09-30 16:25 ` Jens Axboe
2024-10-09 9:12 ` Borislav Petkov
2024-10-09 11:04 ` Jens Axboe
2024-10-10 13:46 ` Borislav Petkov
2024-10-10 13:50 ` Jens Axboe
2024-10-17 2:34 ` Jens Axboe
2024-10-17 10:02 ` Borislav Petkov
2024-10-17 14:05 ` Jens Axboe
2024-10-17 14:13 ` Borislav Petkov
2024-10-17 14:23 ` Jens Axboe
2024-10-17 14:27 ` Borislav Petkov
2024-10-17 14:40 ` Jens Axboe
2024-10-18 11:58 ` Borislav Petkov
2024-10-18 12:49 ` Borislav Petkov
2024-10-18 13:30 ` Jens Axboe
2024-10-18 15:51 ` Borislav Petkov
2024-10-18 16:45 ` Dr. David Alan Gilbert
2024-10-18 16:47 ` Jens Axboe
2024-10-18 17:59 ` Dr. David Alan Gilbert
2024-10-18 16:48 ` Jens Axboe
2024-10-18 17:56 ` Borislav Petkov
2024-10-18 18:03 ` Jens Axboe
2024-10-18 23:01 ` Jens Axboe
2024-10-19 9:37 ` Borislav Petkov
2024-10-19 13:54 ` Jens Axboe
2024-10-19 23:21 ` Borislav Petkov
2024-10-20 3:24 ` Jens Axboe
2024-10-20 12:18 ` Borislav Petkov
2024-10-21 0:47 ` Jens Axboe
2024-10-21 7:31 ` Borislav Petkov
2024-10-21 17:00 ` Jens Axboe
2024-10-22 12:05 ` Borislav Petkov
2024-10-22 12:07 ` [PATCH 1/2] x86/microcode/AMD: Pay attention to the stepping dynamically Borislav Petkov
2024-10-22 12:08 ` [PATCH 2/2] x86/microcode/AMD: Split load_microcode_amd() Borislav Petkov
2024-10-22 13:15 ` Jens Axboe
2024-10-22 14:33 ` Borislav Petkov
2024-10-22 16:08 ` [tip: x86/urgent] x86/microcode/AMD: Pay attention to the stepping dynamically tip-bot2 for Borislav Petkov (AMD)
2024-10-22 16:08 ` [tip: x86/urgent] x86/microcode/AMD: Split load_microcode_amd() tip-bot2 for Borislav Petkov (AMD)
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=91194406-3fdf-4e38-9838-d334af538f74@kernel.dk \
--to=axboe@kernel.dk \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.