public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sid Boyce <g3vbv@blueyonder.co.uk>
To: linux-kernel@vger.kernel.org
Subject: RE: 2.6.23-rc1-git3 init failure
Date: Sun, 29 Jul 2007 02:44:26 +0100	[thread overview]
Message-ID: <46ABF0FA.8060301@blueyonder.co.uk> (raw)

 > Boot failure on x86_64 (64X2), says it can't find init, specifically
 > /init. 2.6.23-rc1-git1 boots and runs successfully. I haven't tried
 > -git2. I shall reboot on 2.6.23-rc1-git3 tomorrow and record the full
 > message.
 > Strings from vmlinux in both the above:-
 >
 > Kernel alive
 > /dev/console
 > <4>Warning: unable to open an initial console.
 > <4>Failed to execute %s
 > <4>Failed to execute %s.  Attempting defaults...
 > /sbin/init
 > /etc/init
 > /bin/init
 > /bin/sh
 > No init found.  Try passing init= option to kernel.
 >
 > Tried option "init=/sbin/init" and got the same failure.
 > Regards
 > Sid.

I see the sam problem with 2.6.23-rc1-git5.

Freeing unused kernel memory: 236k freed
failed to execute /init
kernel panic - not syncing: No init found. Try passing init= option to 
kernel

Copying /sbin/init to / results in the same error.
openSUSE 10.3Alpha6plus
# rpm -qf /sbin/init
sysvinit-2.86-90

Regards
Sid.

-- 
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support 
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks


             reply	other threads:[~2007-07-29  1:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-29  1:44 Sid Boyce [this message]
2007-07-30 14:25 ` 2.6.23-rc1-git3 init failure Michal Piotrowski
2007-07-30 23:46   ` Sid Boyce
2007-08-02 23:14   ` Sid Boyce
  -- strict thread matches above, loose matches on Subject: below --
2007-07-27  0:17 Sid Boyce

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=46ABF0FA.8060301@blueyonder.co.uk \
    --to=g3vbv@blueyonder.co.uk \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox