From: Conor Dooley <conor.dooley@microchip.com>
To: <linux-riscv@lists.infradead.org>
Cc: <palmer@dabbelt.com>, <conor@kernel.org>
Subject: weird backtrace during kernel panic, possibly due to mapping symbols
Date: Mon, 29 May 2023 14:23:54 +0100 [thread overview]
Message-ID: <20230529-glare-modify-653f50de5602@wendy> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1544 bytes --]
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.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
reply other threads:[~2023-05-29 13:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230529-glare-modify-653f50de5602@wendy \
--to=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
/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