[sw-dev] Booting Linux from U-Boot in qemu-system-riscv64?

[Michael Opdenacker]

Hi Anup,

On 12/2/20 3:28 PM, Anup Patel wrote:
> root=/dev/vda2 rootwait console=ttyS0 earlycon=sbi


Many thanks for the "earlycon=sbi" tip. It doesn't solve the problem yet
but definitely helps to get further details:

[    0.000000] Linux version 5.10.0-rc5-00357-gaae5ab854e38
(mike at mike-laptop) (riscv64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04)
9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #11 SMP Tue Dec 1 07:13:44
CET 2020
[    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] efi: UEFI not found.
[    0.000000] Zone ranges:
[    0.000000]   DMA32    [mem 0x0000000080200000-0x0000000081ffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000080200000-0x0000000081ffffff]
[    0.000000] Initmem setup node 0 [mem
0x0000000080200000-0x0000000081ffffff]
[    0.000000] Unable to handle kernel paging request at virtual address
ffffffe007e00001
[    0.000000] Oops [#1]
[    0.000000] Modules linked in:
[    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted
5.10.0-rc5-00357-gaae5ab854e38 #11
[    0.000000] epc: ffffffe0004a8b38 ra : ffffffe000021cb8 sp :
ffffffe001003f60
[    0.000000]  gp : ffffffe0010e1fb0 tp : ffffffe00100bd40 t0 :
ffffffe001d8efc0
[    0.000000]  t1 : 0000000081f8efc0 t2 : 2d656b696d40656b s0 :
ffffffe001003f80
[    0.000000]  s1 : ffffffe007e00000 a0 : ffffffe007e00000 a1 :
ffffffe001d8ef80
[    0.000000]  a2 : 0000000000000000 a3 : 0000000000000000 a4 :
0000000000000000
[    0.000000]  a5 : ffffffdf7fe00000 a6 : ffffffe0010104b8 a7 :
0000000000000030
[    0.000000]  s2 : ffffffe0010e30a8 s3 : 0000000000000003 s4 :
fffffffffffffff3
[    0.000000]  s5 : 00000000bffe1c70 s6 : 0000000000000000 s7 :
0000000000000000
[    0.000000]  s8 : 00000000bff6a042 s9 : 0000000080200000 s10:
0000000000000000
[    0.000000]  s11: 0000000000000000 t3 : 0000000000000018 t4 :
0000000000000001
[    0.000000]  t5 : 0000000000000018 t6 : 0000000001e00000
[    0.000000] status: 0000000000000100 badaddr: ffffffe007e00001 cause:
000000000000000d
[    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! ]---


Now I guess I can compare with the run in which the kernel is directly
started without U-Boot...

Suggestions welcome of course...

Thanks again,

Michael.

-- 
Michael Opdenacker, CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com