From: Christian Kujau <lists@nerdbynature.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: 3.4.0-rc1: No init found
Date: Tue, 3 Apr 2012 00:20:24 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.01.1204030008080.4930@trent.utfs.org> (raw)
Going from 3.3-rc7 to 3.4-rc1 (with "make oldconfig" inbetween) did not
go well on this PowerBook G4 machine:
Apr 2 15:18:23 [ 8.318816] EXT4-fs (hda6): mounted filesystem with ordered data mode. Opts: (null)
Apr 2 15:18:23 [ 8.320286] VFS: Mounted root (ext4 filesystem) readonly on device 3:6.
Apr 2 15:18:23 [ 8.341555] devtmpfs: mounted
Apr 2 15:18:23 [ 8.343384] Freeing unused kernel memory: 204k freed
Apr 2 15:18:23 [ 8.457056] Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
Apr 2 15:18:23 [ 8.459936] Rebooting in 180 seconds..
No bootoptions were changed, no disks swapped, no partitions altered
whatsoever. Full .config & dmesg:
http://nerdbynature.de/bits/3.4.0-rc1/init/
Thanks,
Christian.
PS: Unfortunately I cannot boot into the old (3.3-rc7) kernel
right now (which is still installed via "yaboot" and present in
/boot), because of this:
http://nerdbynature.de/bits/3.4.0-rc1/init/mac-invalid-memory.JPG
Booting into Debian's "squeeze" kernel (2.6.32) which resides in
the same /boot directory succeeds.
--
BOFH excuse #334:
50% of the manual is in .pdf readme files
next reply other threads:[~2012-04-03 7:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 7:20 Christian Kujau [this message]
2012-04-03 8:08 ` Benjamin Herrenschmidt
2012-04-03 17:18 ` Christian Kujau
2012-04-03 18:53 ` Christian Kujau
2012-04-04 12:36 ` Suzuki K. Poulose
2012-04-04 16:45 ` Christian Kujau
2012-04-10 7:23 ` Benjamin Herrenschmidt
2012-04-10 16:56 ` Christian Kujau
2012-07-05 22:36 ` Tabi Timur-B04825
2012-07-06 5:20 ` Suzuki K. Poulose
2012-04-10 5:47 ` Christian Kujau
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=alpine.DEB.2.01.1204030008080.4930@trent.utfs.org \
--to=lists@nerdbynature.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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
all inboxes | Powered by JetHome®