question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

buildroot Incorrect selection of kernel headers: expected 5.16.x, got 5.14.x (was: ULX3S -- kernel panic on boot)

See original GitHub issue
--============= Liftoff! ===============--

OpenSBI v0.8-1-gecf7701
   ____                    _____ ____ _____
  / __ \                  / ____|  _ \_   _|
 | |  | |_ __   ___ _ __ | (___ | |_) || |
 | |  | | '_ \ / _ \ '_ \ \___ \|  _ < | |
 | |__| | |_) |  __/ | | |____) | |_) || |_
  \____/| .__/ \___|_| |_|_____/|____/_____|
        | |
        |_|

Platform Name       : LiteX / VexRiscv-SMP
Platform Features   : timer,mfdeleg
Platform HART Count : 8
Boot HART ID        : 0
Boot HART ISA       : rv32imas
BOOT HART Features  : time
BOOT HART PMP Count : 0
Firmware Base       : 0x40f00000
Firmware Size       : 124 KB
Runtime SBI Version : 0.2

MIDELEG : 0x00000222
MEDELEG : 0x0000b101
[    0.000000] Linux version 5.14.0 (florent@panda) (riscv32-buildroot-linux-gnu-gcc.br_real (Buildroot 2021.08-381-g279167ee8d) 10.3.0, GNU ld (GNU Binutils) 2.36.1) #1 SMP Tue Sep 21 12:57:31 CEST 2021
[    0.000000] earlycon: liteuart0 at I/O port 0x0 (options '')
[    0.000000] Malformed early option 'console'
[    0.000000] earlycon: liteuart0 at MMIO 0xf0001000 (options '')
[    0.000000] printk: bootconsole [liteuart0] enabled
[    0.000000] kobject ((ptrval)): tried to init an initialized object, something is seriously wrong.
[    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 5.14.0 #1
[    0.000000] Call Trace:
[    0.000000] [<c0003b64>] dump_backtrace+0x2c/0x3c
[    0.000000] Unable to handle kernel paging request at virtual address ffffffff
[    0.000000] Oops [#1]
[    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 5.14.0 #1
[    0.000000] epc : unflatten_dt_nodes+0x374/0x568
[    0.000000]  ra : unflatten_dt_nodes+0x36c/0x568
[    0.000000] epc : c03fbde0 ra : c03fbdd8 sp : c06a3db0
[    0.000000]  gp : c072e8d8 tp : c06a8740 t0 : 00000000
[    0.000000]  t1 : 000000cf t2 : 00000000 s0 : c06a3f30
[    0.000000]  s1 : c3ffeb20 a0 : ffffffff a1 : c0ef003c
[    0.000000]  a2 : 00000000 a3 : 00000001 a4 : c3ffeb50
[    0.000000]  a5 : ffffffff a6 : 000000ec a7 : 00000011
[    0.000000]  s2 : 00000000 s3 : c0ef003c s4 : c3ffea50
[    0.000000]  s5 : c3ffeafc s6 : c0ef005c s7 : c0ef0000
[    0.000000]  s8 : c0673c58 s9 : 00000000 s10: c3ffea50
[    0.000000]  s11: c3ffeb51 t3 : 00000000 t4 : 00000000
[    0.000000]  t5 : 00000001 t6 : ffffffff
[    0.000000] status: 00000100 badaddr: ffffffff cause: 0000000f
[    0.000000] [<c03fbde0>] unflatten_dt_nodes+0x374/0x568
[    0.000000] [<c03fc09c>] __unflatten_device_tree+0xc8/0x184
[    0.000000] [<c05aaa20>] unflatten_device_tree+0x3c/0x5c
[    0.000000] [<c0591c48>] setup_arch+0x100/0x558
[    0.000000] [<c058eee8>] start_kernel+0x8c/0x63c
[    0.000000] random: get_random_bytes called from oops_exit+0x48/0x94 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! ]---

Any hints? I’m using freshly built gateware nothing fancy ./make.py --build --board ulx3s --device LFE5U-85F but with binary blob of images. I’ll try with a fresh build of buildroot

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:13 (12 by maintainers)

github_iconTop GitHub Comments

1reaction
geertucommented, Apr 26, 2022

https://github.com/litex-hub/linux/tree/litex-rebase is at v5.18-rc3, and working fine on my OrangeCrab.

0reactions
enjoy-digitalcommented, May 27, 2022

The initial issue has been fixed thanks to @sebeaumont’s PRs, we can probably close this.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Incorrect selection of kernel headers: expected 4.9.x, got 4.6.x ...
The root cause for this mis-match was that the bootlin toolchain won't be downloaded by buildroot automatically, but is expected in the PATH ......
Read more >
Incorrect selection of kernel headers: expected 4.13.x, got 5.0.x
I tried to change both of "buildroot -> Toolchain -> Custom kernel headers series " and kernel version to 4.18, which is the...
Read more >
Error compiling buildroot - kernel - Unix Stack Exchange
It seems like your Buildroot configuration is incorrect, but since you didn't provide your config, there's no real way to give a precise...
Read more >
[Buildroot] [PATCH] Fix "Incorrect selection of kernel headers
[Buildroot] [PATCH] Fix "Incorrect selection of kernel headers: expected 4.11.x, got 4.15.x" for qemu_x86_64_defconfig.
Read more >
Fix "Incorrect selection of kernel headers: expected 4.11.x, got ...
Fix "Incorrect selection of kernel headers: expected 4.11.x, got 4.15.x" for qemu_x86_64_defconfig. Message ID, 20180303072704.11166-1-ciro.santilli@gmail.com.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found