From: kernel test robot <oliver.sang@intel.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
<linux-serial@vger.kernel.org>, <oliver.sang@intel.com>
Subject: [rt-devel:linux-6.8.y-rt] [serial] 0a81ac5ba5: Kernel_panic-not_syncing:No_working_init_found
Date: Mon, 5 Feb 2024 22:23:16 +0800 [thread overview]
Message-ID: <202402052207.a61afe51-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "Kernel_panic-not_syncing:No_working_init_found" on:
commit: 0a81ac5ba5b985c0803c4f0d9272578fc7b1d361 ("serial: 8250: Switch to nbcon console")
https://git.kernel.org/cgit/linux/kernel/git/rt/linux-rt-devel.git linux-6.8.y-rt
in testcase: boot
compiler: clang-17
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
we cannot connect the issue with the code, but by more runs, the issue still
shows on this commit and keeps clean on parent.
we also noticed the issue doesn't always happen on this commit, as below,
happens 15 times out of 20 runs.
dd0b9d75b0ea983e 0a81ac5ba5b985c0803c4f0d927
---------------- ---------------------------
fail:runs %reproduction fail:runs
| | |
:20 75% 15:20 dmesg.Kernel_panic-not_syncing:No_working_init_found
:20 75% 15:20 dmesg.boot_failures
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202402052207.a61afe51-lkp@intel.com
[ 217.891235][ T1] LKP_SERVER=internal-lkp-server
[ 217.892392][ T1] selinux=0
[ 217.893299][ T1] prompt_ramdisk=0
[ 217.894242][ T1] vga=normal
[ 217.930082][ T1] Starting init: /bin/sh exists but couldn't execute it (error -8)
[ 217.931991][ T1] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
[ 217.933840][ T1] CPU: 0 PID: 1 Comm: swapper Tainted: G TN 6.8.0-rc1-00059-g0a81ac5ba5b9 #1
[ 217.935596][ T1] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 217.936883][ T1] Call Trace:
[ 217.937287][ T1] <TASK>
[ 217.937698][ T1] dump_stack_lvl (kbuild/src/consumer/lib/dump_stack.c:?)
[ 217.938293][ T1] panic (kbuild/src/consumer/kernel/panic.c:284)
[ 217.938820][ T1] ? rest_init (kbuild/src/consumer/init/main.c:1433)
[ 217.939385][ T1] kernel_init (main.c:?)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240205/202402052207.a61afe51-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-02-05 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 14:23 kernel test robot [this message]
2024-02-14 13:58 ` [rt-devel:linux-6.8.y-rt] [serial] 0a81ac5ba5: Kernel_panic-not_syncing:No_working_init_found Sebastian Andrzej Siewior
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=202402052207.a61afe51-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=bigeasy@linutronix.de \
--cc=john.ogness@linutronix.de \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
/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).