From: Abhishek Kumar <Abhishek.kumar@exaleapsemi.com>
To: "libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: glibc with kernel-4.14 headers on riscv
Date: Wed, 27 Apr 2022 07:11:07 +0000 [thread overview]
Message-ID: <MA1PR0101MB142920F0659B78607AE930519AFA9@MA1PR0101MB1429.INDPRD01.PROD.OUTLOOK.COM> (raw)
Hi ,
I am woking on kernel-4.14 to give support for riscv (fu540 plateform) ,I am using glibc2.27 for my kernel after build the kernel when booting it at boot time it is giving me error "FATAL: kernel too old",
so please suggest me which glibc version I should use for my kernel-4.14 so that it will be compatible for riscv.
bellow is the error I am getting at boot time.
[ 1.106608] This architecture does not have kernel memory protection.
FATAL: kernel too old
[ 1.182177] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 1.182177]
[ 1.191211] CPU: 2 PID: 1 Comm: init Tainted: G W 4.14.155-riscv #1
[ 1.198584] Call Trace:
[ 1.201032] [<ffffffe000027c6e>] walk_stackframe+0x0/0xa2
[ 1.206403] [<ffffffe000027dac>] show_stack+0x26/0x34
[ 1.211445] [<ffffffe00033cc9a>] dump_stack+0x66/0x84
[ 1.216475] [<ffffffe00002b186>] panic+0xca/0x1de
[ 1.221163] [<ffffffe00002d976>] do_exit+0x734/0x738
[ 1.226111] [<ffffffe00002d9d0>] do_group_exit+0x26/0x82
[ 1.231407] [<ffffffe00002da40>] SyS_exit_group+0x14/0x18
[ 1.236792] [<ffffffe000026cb4>] check_syscall_nr+0x1e/0x22
please try to give some suggestions.
Thanks
Abhishek
next reply other threads:[~2022-04-27 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 7:11 Abhishek Kumar [this message]
2022-04-27 7:50 ` Florian Weimer
2022-04-27 18:55 ` Adhemerval Zanella
2022-05-27 8:54 ` Abhishek Kumar
2022-06-01 19:40 ` Adhemerval Zanella
2022-06-01 20:56 ` Dorian ROSSE
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=MA1PR0101MB142920F0659B78607AE930519AFA9@MA1PR0101MB1429.INDPRD01.PROD.OUTLOOK.COM \
--to=abhishek.kumar@exaleapsemi.com \
--cc=libc-help@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).