From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 203391] New: Hit kernel panic when build linux-next with ubuntu 18.04
Date: Tue, 23 Apr 2019 03:22:31 +0000 [thread overview]
Message-ID: <bug-203391-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=203391
Bug ID: 203391
Summary: Hit kernel panic when build linux-next with ubuntu
18.04
Product: File System
Version: 2.5
Kernel Version: 5.1.0-rc5-3f018f4a019a
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: lilideng@outlook.com
Regression: No
Created attachment 282463
--> https://bugzilla.kernel.org/attachment.cgi?id=282463&action=edit
Serial console log
1 Create a Ubuntu 18.04
2 Clone latest linux-next, build kernel successfully
3 Reboot
4 Hit kernel panic
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
done.
Begin: Running /scripts/local-premount ... [ 9.150164] Btrfs loaded,
crc32c=crc32c-intel
Scanning for Btrfs filesystems
done.
Warning: fsck not present, so skipping root file system
[ 9.286671] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts:
(null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
/sbin/init: error while loading shared libraries:
/usr/lib/x86_64-linux-gnu/libip4tc.so.0: invalid ELF header
[ 9.424886] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x00007f00
[ 9.425715] CPU: 39 PID: 1 Comm: init Not tainted 5.1.0-rc5-3f018f4a019a #1
[ 9.425715] Hardware name: Microsoft Corporation Virtual Machine/Virtual
Machine, BIOS 090007 06/02/2017
[ 9.425715] Call Trace:
[ 9.425715] dump_stack+0x46/0x5b
[ 9.425715] panic+0xf8/0x2c2
[ 9.425715] do_exit+0xb8d/0xb90
[ 9.425715] do_group_exit+0x3a/0xa0
[ 9.425715] __x64_sys_exit_group+0x14/0x20
[ 9.425715] do_syscall_64+0x4f/0x110
[ 9.425715] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 9.425715] RIP: 0033:0x7f5083940056
[ 9.425715] Code: Bad RIP value.
[ 9.425715] RSP: 002b:00007ffdb07cb888 EFLAGS: 00000206 ORIG_RAX:
00000000000000e7
[ 9.425715] RAX: ffffffffffffffda RBX: 00007f5083946ce0 RCX:
00007f5083940056
[ 9.425715] RDX: 000000000000007f RSI: 000000000000003c RDI:
000000000000007f
[ 9.425715] RBP: 00007ffdb07cc380 R08: 00000000000000e7 R09:
00007ffdb07cb344
[ 9.425715] R10: 0000000000000020 R11: 0000000000000206 R12:
0000000000000011
[ 9.425715] R13: 00007f5083b3e010 R14: 00007f5083b3df80 R15:
00007f5083b4c170
[ 9.425715] Kernel Offset: 0x1fc00000 from 0xffffffff81000000 (relocation
range: 0xffffffff80000000-0xffffffffbfffffff)
[ 9.425715] ---[ end Kernel panic - not syncing: Attempted to kill init!
exitcode=0x00007f00 ]---
--
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2019-04-23 3:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-203391-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.