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>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: AMD zen microcode updates breaks boot
Date: Sun, 20 Oct 2024 18:47:25 -0600 [thread overview]
Message-ID: <df217737-6e2c-41fe-b558-3e2ab6dc0d9e@kernel.dk> (raw)
In-Reply-To: <20241020121819.GAZxT1CyR_5vLLZ5e6@fat_crate.local>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
On 10/20/24 6:18 AM, Borislav Petkov wrote:
> Ok, this diff at the end should fix it completely. I think. The same dance,
> replace, build and boot.
Works, outside of waiting 3 min for the serial console spewage from the
patch! But it boots and it's happy after that. Attached here gzip'ed as
it's 1.3M otherwise.
> I've moved the iteration over the nodes in the late loading path as this is
> where we need it only anyway. If you wanna test that too and you feel brave,
> do this after the machine boots:
>
> # echo 1 > /sys/devices/system/cpu/microcode/reload
>
> It should say
>
> bash: echo: write error: File descriptor in bad state
I get:
root@r7625 ~# echo 1 > /sys/devices/system/cpu/microcode/reload
warning: An error occurred while redirecting file '/sys/devices/system/cpu/microcode/reload'
open: Permission denied
and no output in dmesg.
--
Jens Axboe
[-- Attachment #2: r7625-dmesg.txt.gz --]
[-- Type: application/gzip, Size: 106285 bytes --]
next prev parent reply other threads:[~2024-10-21 0:47 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-27 15:17 AMD zen microcode updates breaks boot Jens Axboe
2024-09-28 6:10 ` 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 [this message]
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=df217737-6e2c-41fe-b558-3e2ab6dc0d9e@kernel.dk \
--to=axboe@kernel.dk \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.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