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: Fri, 18 Oct 2024 17:01:18 -0600 [thread overview]
Message-ID: <1bb5dd7f-15b5-4d9d-97ef-75ebdc24e7d9@kernel.dk> (raw)
In-Reply-To: <016ecb00-2331-472c-88e4-66b1dbecfc99@kernel.dk>
On 10/18/24 12:03 PM, Jens Axboe wrote:
> On 10/18/24 11:56 AM, Borislav Petkov wrote:
>> On Fri, Oct 18, 2024 at 10:48:19AM -0600, Jens Axboe wrote:
>>> Funky... Not sure I'll have time to get a serial console on this
>>> thing before next week.
>>
>> That would be much appreciated.
>
> I will probably have some time to get that going on Monday. Just to set
> expectations in terms of timing, the above should've read "before the end
> of next week".
I took time out of "would otherwise have had a beer" time on a Friday
afternoon and got a serial console on it. Here's the crash at boot:
BUG: unable to handle page fault for address: 00000001000141ab
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 0 P4D 0
Oops: Oops: 0000 [#1] SMP
CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.12.0-rc2+ #143
Hardware name: Dell Inc. PowerEdge R7625/06444F, BIOS 1.8.3 04/02/2024
RIP: 0010:load_microcode_amd.isra.0+0x334/0x450
Code: e7 06 48 81 c7 c0 97 7e 96 e8 f8 bb 4e 00 89 c7 89 c0 4c 8b 2c c5 40 20 e2 95 49 01 ed e8 44 f9 ff ff 48 85 c0 74 12 8b 40 1c <41> 39 85 28 01 00 00 0f 92 c0 0f b6 c0 09 c3 41 8d 4c 24 01 41 83
RSP: 0018:ffffa41ac00e7e08 EFLAGS: 00010282
RAX: 000000000aa00116 RBX: 0000000000000000 RCX: 0000000000a00000
RDX: 0000000000aa0f00 RSI: 0000000000000200 RDI: 000000000000000a
RBP: 0000000000014080 R08: 000000000000aa01 R09: ffff93ebc1106000
R10: ffffa41ac00e7df0 R11: 0000000000002000 R12: 0000000000000001
R13: 0000000100014083 R14: ffff93ebc103b400 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff93f127e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000001000141ab CR3: 000000ba2de28001 CR4: 0000000000370ef0
Call Trace:
<TASK>
? __die_body.cold+0x19/0x2b
? page_fault_oops+0x90/0x210
? load_microcode_amd.isra.0+0x185/0x450
? exc_page_fault+0x6c/0x130
? asm_exc_page_fault+0x22/0x30
? load_microcode_amd.isra.0+0x334/0x450
? load_microcode_amd.isra.0+0x32c/0x450
save_microcode_in_initrd+0x90/0xb0
? find_blobs_in_containers+0xb0/0xb0
do_one_initcall+0x2e/0x190
? try_to_wake_up+0x1c0/0x4b0
kernel_init_freeable+0xdd/0x210
? rest_init+0xc0/0xc0
kernel_init+0x16/0x120
ret_from_fork+0x2d/0x50
? rest_init+0xc0/0xc0
ret_from_fork_asm+0x11/0x20
</TASK>
Modules linked in:
CR2: 00000001000141ab
---[ end trace 0000000000000000 ]---
RIP: 0010:load_microcode_amd.isra.0+0x334/0x450
Code: e7 06 48 81 c7 c0 97 7e 96 e8 f8 bb 4e 00 89 c7 89 c0 4c 8b 2c c5 40 20 e2 95 49 01 ed e8 44 f9 ff ff 48 85 c0 74 12 8b 40 1c <41> 39 85 28 01 00 00 0f 92 c0 0f b6 c0 09 c3 41 8d 4c 24 01 41 83
RSP: 0018:ffffa41ac00e7e08 EFLAGS: 00010282
RAX: 000000000aa00116 RBX: 0000000000000000 RCX: 0000000000a00000
RDX: 0000000000aa0f00 RSI: 0000000000000200 RDI: 000000000000000a
RBP: 0000000000014080 R08: 000000000000aa01 R09: ffff93ebc1106000
R10: ffffa41ac00e7df0 R11: 0000000000002000 R12: 0000000000000001
R13: 0000000100014083 R14: ffff93ebc103b400 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff93f127e00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00000001000141ab CR3: 000000ba2de28001 CR4: 0000000000370ef0
note: swapper/0[1] exited with irqs disabled
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 ]---
which appears to be here:
(gdb) l *load_microcode_amd+0x334
0xffffffff810914a4 is in load_microcode_amd (arch/x86/kernel/cpu/microcode/amd.c:971).
966
967 p = find_patch(cpu);
968 if (!p)
969 continue;
970
971 if (c->microcode >= p->patch_id)
972 continue;
973
974 ret = UCODE_NEW;
975 }
heading home, so didn't poke. As you know, there are 32 nodes in this
sytem, looks like:
axboe@r7625 /s/d/s/node> grep . node*/cpulist
node0/cpulist:0-7,256-263
node1/cpulist:8-15,264-271
node2/cpulist:16-23,272-279
node3/cpulist:24-31,280-287
node4/cpulist:32-39,288-295
node5/cpulist:40-47,296-303
node6/cpulist:48-55,304-311
node7/cpulist:56-63,312-319
node8/cpulist:64-71,320-327
node9/cpulist:72-79,328-335
node10/cpulist:80-87,336-343
node11/cpulist:88-95,344-351
node12/cpulist:96-103,352-359
node13/cpulist:104-111,360-367
node14/cpulist:112-119,368-375
node15/cpulist:120-127,376-383
node16/cpulist:128-135,384-391
node17/cpulist:136-143,392-399
node18/cpulist:144-151,400-407
node19/cpulist:152-159,408-415
node20/cpulist:160-167,416-423
node21/cpulist:168-175,424-431
node22/cpulist:176-183,432-439
node23/cpulist:184-191,440-447
node24/cpulist:192-199,448-455
node25/cpulist:200-207,456-463
node26/cpulist:208-215,464-471
node27/cpulist:216-223,472-479
node28/cpulist:224-231,480-487
node29/cpulist:232-239,488-495
node30/cpulist:240-247,496-503
node31/cpulist:248-255,504-511
and .config has:
CONFIG_NODES_SHIFT=5
CONFIG_USE_PERCPU_NUMA_NODE_ID=y
--
Jens Axboe
next prev parent reply other threads:[~2024-10-18 23:01 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 [this message]
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] " tip-bot2 for Borislav Petkov (AMD)
2024-10-22 16:08 ` [tip: x86/urgent] x86/microcode/AMD: Pay attention to the stepping dynamically 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=1bb5dd7f-15b5-4d9d-97ef-75ebdc24e7d9@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