weird backtrace during kernel panic, possibly due to mapping symbols
Conor Dooley
conor.dooley at microchip.com
Mon May 29 06:23:54 PDT 2023
Hey!
I posted this weird backtrace on IRC over the weekend & Palmer thinks
the blame lies with binutils 2.40 emitting mapping symbols that the
stack dumper cannot handle:
[<ffffffff800048c4>] $xrv64i2p0_m2p0_a2p0_c2p0_zihintpause2p0_zmmul1p0+0x0/0x7e
[<ffffffff800048c4>] $xrv64i2p0_m2p0_a2p0_c2p0_zihintpause2p0_zmmul1p0+0x0/0x7e
[<ffffffff806062b6>] $xrv64i2p0_m2p0_a2p0_c2p0_zihintpause2p0_zmmul1p0+0x34/0x4e
[<ffffffff806062b6>] $xrv64i2p0_m2p0_a2p0_c2p0_zihintpause2p0_zmmul1p0+0x34/0x4e
[<ffffffff805f92f2>] $xrv64i2p0_m2p0_a2p0_c2p0_zihintpause2p0_zmmul1p0+0xe2/0x280
[<ffffffff805f92f2>] $xrv64i2p0_m2p0_a2p0_c2p0_zihintpause2p0_zmmul1p0+0xe2/0x280
[<ffffffff808012ac>] mount_block_root+0x174/0x206
[<ffffffff808012ac>] mount_block_root+0x174/0x206
[<ffffffff8080139c>] mount_root+0x5e/0x15c
[<ffffffff8080139c>] mount_root+0x5e/0x15c
[<ffffffff808015c6>] prepare_namespace+0x12c/0x162
[<ffffffff808015c6>] prepare_namespace+0x12c/0x162
[<ffffffff8060767e>] $xrv64i2p0_m2p0_a2p0_c2p0_zihintpause2p0_zmmul1p0+0xb6/0xba
[<ffffffff8060767e>] $xrv64i2p0_m2p0_a2p0_c2p0_zihintpause2p0_zmmul1p0+0xb6/0xba
[<ffffffff80607698>] kernel_init+0x16/0x10c
[<ffffffff80607698>] kernel_init+0x16/0x10c
[<ffffffff8060767e>] $xrv64i2p0_m2p0_a2p0_c2p0_zihintpause2p0_zmmul1p0+0xb6/0xba
[<ffffffff8060767e>] $xrv64i2p0_m2p0_a2p0_c2p0_zihintpause2p0_zmmul1p0+0xb6/0xba
[<ffffffff80003406>] ret_from_fork+0x6/0x1c
[<ffffffff80003406>] ret_from_fork+0x6/0x1c
The panic itself is just a missing rootfs, so nothing to be concerned
about :)
Cheers,
Conor.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-riscv/attachments/20230529/a08d2bf9/attachment.sig>
More information about the linux-riscv
mailing list