From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14916] New: build buildroot with glibc and linux kernel 5.4 will cause error: "FATAL: kernel too old"
Date: Mon, 18 Jul 2022 02:43:14 +0000 [thread overview]
Message-ID: <bug-14916-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=14916
Bug ID: 14916
Summary: build buildroot with glibc and linux kernel 5.4 will
cause error: "FATAL: kernel too old"
Product: buildroot
Version: 2022.02.3
Hardware: All
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: tgeh23@qq.com
CC: buildroot@uclibc.org
Target Milestone: ---
Refer to this article for details: https://www.jianshu.com/p/55952ae88965
1. qemu start error
[ 3.405278] Run /sbin/init as init process
FATAL: kernel too old
[ 3.484534] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x00007f00
[ 3.484974] CPU: 0 PID: 1 Comm: init Not tainted 5.4.195 #1
2. environment
host arch linux kernel buildroot glibc
ubuntu 20.04 x86_64 5.4.0-195/5.4.195 2022.02.3 2.34
3. error analysis
- buildroot set `BR2_TOOLCHAIN_HEADERS_AT_LEAST` to `5.4`
- but glibc's `--enable-kernel=X.Y.Z`
- buildroot missing `Z`
4. temporary solution
modify buildroot's .config `BR2_TOOLCHAIN_HEADERS_AT_LEAST` to `5.4.0`
5. recompile and start ok
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2022-07-18 2:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 2:43 bugzilla [this message]
2022-07-18 2:46 ` [Buildroot] [Bug 14916] build buildroot with glibc and linux kernel 5.4, start with qemu will cause error: "FATAL: kernel too old" bugzilla
2022-07-18 6:25 ` bugzilla
2022-07-18 21:43 ` bugzilla
2022-07-18 22:00 ` bugzilla
2022-07-19 3:27 ` bugzilla
2022-07-23 14:05 ` bugzilla
2022-10-25 20:22 ` bugzilla
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=bug-14916-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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