Message-ID: <17fc594b-b80b-4918-8945-4aef35dc9c94@suse.com>
Date: Mon, 2 Jun 2025 10:00:38 +0930
From: Qu Wenruo <wqu@...e.com>
To: linux-arm-kernel@...ts.infradead.org, LKML
 <linux-kernel@...r.kernel.org>, devicetree@...r.kernel.org
Subject: Kernel crash on boot, arm64 VM

Hi,

It looks like there is a regression related to the device tree/acpi 
parsing in the latest upstream kernel branch.

The arm64 VM crash at boot, with the following call trace:

[    0.586215] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[    0.590523] ACPI: bus type drm_connector registered
[    0.591658] Unable to handle kernel paging request at virtual address 
fefefefefefeffba
[    0.591662] Mem abort info:
[    0.591662]   ESR = 0x0000000096000004
[    0.591664]   EC = 0x25: DABT (current EL), IL = 32 bits
[    0.591665]   SET = 0, FnV = 0
[    0.591666]   EA = 0, S1PTW = 0
[    0.591667]   FSC = 0x04: level 0 translation fault
[    0.591668] Data abort info:
[    0.591669]   ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
[    0.591670]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0
[    0.591671]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[    0.591673] [fefefefefefeffba] address between user and kernel 
address ranges
[    0.591675] Internal error: Oops: 0000000096000004 [#1]  SMP
[    0.782557] Freeing initrd memory: 29504K
[    0.849513] Modules linked in:
[    0.849987] CPU: 2 UID: 0 PID: 1 Comm: swapper/0 Not tainted 
6.15.0-custom+ #121 PREEMPT(voluntary)
[    0.851281] Hardware name: QEMU KVM Virtual Machine, BIOS unknown 
2/2/2022
[    0.852223] pstate: 20400005 (nzCv daif +PAN -UAO -TCO -DIT -SSBS 
BTYPE=--)
[    0.853160] pc : kobject_put+0x18/0xc8
[    0.853674] lr : of_node_put+0x20/0x38
[    0.854202] sp : ffff80008010fcd0
[    0.854662] x29: ffff80008010fcd0 x28: 0000000000000000 x27: 
ffffd2503c550130
[    0.855633] x26: ffffd2503c651960 x25: 0000000000000006 x24: 
ffffd2503c761fc4
[    0.856631] x23: ffffd2503c083140 x22: 0000000000000000 x21: 
0000000000000000
[    0.857609] x20: 0000000000000000 x19: fefefefefefeff7e x18: 
0000000000000000
[    0.858603] x17: ffffd2503ca54b10 x16: 00000000c041c2e1 x15: 
0000000000000000
[    0.859501] x14: 0000000000000000 x13: 00000000ffffffff x12: 
6265722d6e6f6373
[    0.860434] x11: ffff80008010fbb0 x10: 0000000000000073 x9 : 
ffffd2503c5a671c
[    0.861418] x8 : ffff80008010fcf8 x7 : fefefefefefefefe x6 : 
0000000ef878d830
[    0.862417] x5 : ffffd2503ca54b52 x4 : 0000000000000000 x3 : 
ffffd2503bff0158
[    0.863414] x2 : 000000000000000f x1 : ffff6a2842a80000 x0 : 
fefefefefefeff7e
[    0.864410] Call trace:
[    0.864747]  kobject_put+0x18/0xc8 (P)
[    0.865277]  of_node_put+0x20/0x38
[    0.865757]  psci_idle_init+0x6c/0xe8
[    0.866308]  do_one_initcall+0x60/0x2b0
[    0.866871]  do_initcalls+0x100/0x148
[    0.867388]  kernel_init_freeable+0x188/0x1e0
[    0.868002]  kernel_init+0x28/0x158
[    0.868485]  ret_from_fork+0x10/0x20
[    0.868995] Code: a9be7bfd 910003fd f9000bf3 aa0003f3 (3940f000)
[    0.869845] ---[ end trace 0000000000000000 ]---
[    0.870568] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0000000b
[    0.871567] SMP: stopping secondary CPUs
[    0.872160] Kernel Offset: 0x524fbadc0000 from 0xffff800080000000
[    0.872990] PHYS_OFFSET: 0xffffc389c0000000
[    0.873572] CPU features: 0x0800,000000e0,01002650,8201720b
[    0.874359] Memory Limit: none
[    0.874789] Rebooting in 5 seconds..

The full dmesg (aarch64_dmesg.txt) is attached for the failed boot sequence.

The VM is using edk2-aarch64 as firmware, with the attached libvirt xml 
(aarch64.xml).

Thanks,
Qu
View attachment "aarch64_dmesg.txt" of type "text/plain" (50536 bytes)

View attachment "aarch64.xml" of type "text/xml" (8255 bytes)

Powered by blists - more mailing lists