From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: kernel test robot <oliver.sang@intel.com>
Cc: John Ogness <john.ogness@linutronix.de>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-serial@vger.kernel.org
Subject: Re: [rt-devel:linux-6.8.y-rt] [serial] 0a81ac5ba5: Kernel_panic-not_syncing:No_working_init_found
Date: Wed, 14 Feb 2024 14:58:39 +0100 [thread overview]
Message-ID: <20240214135839.2Dr1E3JM@linutronix.de> (raw)
In-Reply-To: <202402052207.a61afe51-lkp@intel.com>
On 2024-02-05 22:23:16 [+0800], kernel test robot wrote:
> kernel test robot noticed "Kernel_panic-not_syncing:No_working_init_found" on:
…
> ---------------- ---------------------------
> 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
…
> [ 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.
Before that, there is:
| [ 201.601164][ T219] request_module: modprobe binfmt-464c cannot be processed, kmod busy with 50 threads for more than 5 seconds now
| [ 201.790029][ T1] Failed to execute /init (error -8)
| [ 217.930082][ T1] Starting init: /bin/sh exists but couldn't execute it (error -8)
I *think* there is some kind of memory corruption and the init-ELF file
isn't recognized. I don't think this related to printk.
Did you see similar reports to this one? This is -rc1 based. I'm going
to release rc4 based something today with printk mostly unchanged. Will
be interesting to see if this comes back or not.
Sebastian
prev parent reply other threads:[~2024-02-14 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 14:23 [rt-devel:linux-6.8.y-rt] [serial] 0a81ac5ba5: Kernel_panic-not_syncing:No_working_init_found kernel test robot
2024-02-14 13:58 ` Sebastian Andrzej Siewior [this message]
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=20240214135839.2Dr1E3JM@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=john.ogness@linutronix.de \
--cc=linux-serial@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
/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).