A Kernel panic in Booting Linux Kernel with OpenSBI on RocketChip.

344 views
Skip to first unread message

Benshan Mei

unread,
Mar 17, 2021, 8:34:01 AM3/17/21
to RISC-V SW Dev
OpenSBI v0.9
   ____                    _____ ____ _____
  / __ \                  / ____|  _ \_   _|
 | |  | |_ __   ___ _ __ | (___ | |_) || |
 | |  | | '_ \ / _ \ '_ \ \___ \|  _ < | |
 | |__| | |_) |  __/ | | |____) | |_) || |_
  \____/| .__/ \___|_| |_|_____/|____/_____|
        | |
        |_|

Platform Name             : freechips,rocketchip-unknown
Platform Features         : timer,mfdeleg
Platform HART Count       : 4
Firmware Base             : 0x80000000
Firmware Size             : 128 KB
Runtime SBI Version       : 0.2

Domain0 Name              : root
Domain0 Boot HART         : 1
Domain0 HARTs             : 0*,1*,2*,3*
Domain0 Region00          : 0x0000000080000000-0x000000008001ffff ()
Domain0 Region01          : 0x0000000000000000-0xffffffffffffffff (R,W,X)
Domain0 Next Address      : 0x0000000080200000
Domain0 Next Arg1         : 0x0000000082200000
Domain0 Next Mode         : S-mode
Domain0 SysReset          : yes

Boot HART ID              : 1
Boot HART Domain          : root
Boot HART ISA             : rv64imafdcsux
Boot HART Features        : scounteren,mcounteren
Boot HART PMP Count       : 16
Boot HART PMP Granularity : 4
Boot HART PMP Address Bits: 36
Boot HART MHPM Count      : 0
Boot HART MHPM Count      : 0
Boot HART MIDELEG         : 0x0000000000000222
Boot HART MEDELEG         : 0x000000000000b109
[    0.000000] Linux version 5.11.0-rc3 (ubuntu@optiplex-5060) (riscv64-unknown-linux-gnu-gcc (GCC) 9.2.0, GNU ld (GNU Binutils) 2.32) #57 SMP Wed Mar 17 17:15:16 CST 2021
[    0.000000] OF: fdt: Ignoring memory range 0x80000000 - 0x80200000
[    0.000000] earlycon: sbi0 at I/O port 0x0 (options '')
[    0.000000] printk: bootconsole [sbi0] enabled
[    0.000000] Oops - store (or AMO) access fault [#1]
[    0.000000] Modules linked in:
[    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 5.11.0-rc3 #57
[    0.000000] epc: ffffffe000256540 ra : ffffffe000402e4c sp : ffffffe000c03e70
[    0.000000]  gp : ffffffe000cb7bd0 tp : ffffffe000c0bd40 t0 : ffffffcefeffe000
[    0.000000]  t1 : ffffffe000609700 t2 : 0000000000000000 s0 : ffffffe000c03eb0
[    0.000000]  s1 : 0000000080200000 a0 : ffffffcefeffe000 a1 : 0000000000000000
[    0.000000]  a2 : 0000000000001000 a3 : ffffffcefefff000 a4 : 0000000000000000
[    0.000000]  a5 : ffffffcefeffe000 a6 : 0000000000000018 a7 : 0000000000000048
[    0.000000]  s2 : ffffffe000000000 s3 : ffffffcefeffe000 s4 : 00000000000000cf
[    0.000000]  s5 : 0000000000200000 s6 : ffffffe000cc0800 s7 : ffffffe000000000
[    0.000000]  s8 : 0000000080200000 s9 : ffffffe000cb8108 s10: 0000000000200000
[    0.000000]  s11: 0000000000000000 t3 : 0000000000000018 t4 : ffffffffffffffff
[    0.000000]  t5 : 0000000000000022 t6 : 000000000000003d
[    0.000000] status: 0000000200000100 badaddr: ffffffcefeffe000 cause: 0000000000000007
[    0.000000] random: get_random_bytes called from print_oops_end_marker+0x22/0x44 with crng_init=0
[    0.000000] ---[ end trace 0000000000000000 ]---
[    0.000000] Kernel panic - not syncing: Attempted to kill the idle task!
[    0.000000] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]---

Tommy Murphy

unread,
Mar 17, 2021, 10:49:58 AM3/17/21
to Benshan Mei, RISC-V SW Dev
I presume that the implied question is "why?"?
That being the case isn't it a question for the relevant project rather than the mailing list?

Benshan Mei

unread,
Mar 26, 2021, 9:57:41 PM3/26/21
to RISC-V SW Dev, tommy_...@hotmail.com, Benshan Mei
Thanks for your help. This panic has been solved by putting a chosen node into the device tree as in sifive/freedom!
Reply all
Reply to author
Forward
0 new messages