From: Bob Breuer <breuerr@mc.net>
To: sparclinux@vger.kernel.org
Subject: Re: 2.6.11.10 failure on Hypersparc sparc32 [was: Re: sparc32 2.6
Date: Thu, 19 May 2005 15:24:05 +0000 [thread overview]
Message-ID: <428CAF95.4000802@mc.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0505190111530.13987@bobcat>
Jurij Smakov wrote:
> Hi again,
>
> I have now tried the pristine 2.6.11.10 kernel and it fails on mounting
> initrd too on my Hypersparc-powered SS10. The last messages (same as
> with Debian kernels) I see are:
>
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> RAMDISK: cramfs filesystem found at block 0
^^^^
I don't think my initrds have been of the cramfs type.
> RAMDISK: Loading 2556KiB [1 disk] into ram disk... done.
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(0,0)
> <0>Press L1-A to return to the boot prom
>
> It would be nice if you (or someone else) could confirm (or not :-)
> that, since it would eliminate possible initrd/toolchain problems.
>
> http://www.wooyd.org/misc/sparc32.config
With that config, I can't boot the resulting image because it's too
large for the silo that I'm using.
[root@sparky linux-2.6.11.10]# ls -l arch/sparc/boot/image
-rwxr-xr-x 1 root root 2921764 May 19 04:34 arch/sparc/boot/image
Built with: gcc version 3.3.4 20040623 (Red Hat 3.3.4-2)
Here's the similar output from the latest Aurora kernel:
Linux version 2.6.11-1.1166sp1 (root@arthur.devel.redhat.com) (gcc
version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #1 Fri Mar 4 21:55:08 EST 2005
...
NET: Registered protocol family 1
NET: Registered protocol family 17
Freeing unused kernel memory: 156k freed
Red Hat nash version 4.1.18 starting
Mounted /proc filesystem
...
No explicit mention of a ramdisk, but nash is the shell used with the
initrd.
Some more details about that kernel and it's initrd:
[root@sparky boot]# ls -l *1166*
-rw-r--r-- 1 root root 25816 Mar 4 21:07 config-2.6.11-1.1166sp1
-rw-r--r-- 1 root root 753917 Mar 7 10:09 initrd-2.6.11-1.1166sp1.img
-rw-r--r-- 1 root root 453452 Mar 4 21:07 System.map-2.6.11-1.1166sp1
-rwxr-xr-x 1 root root 2471360 Mar 4 21:31 vmlinuz-2.6.11-1.1166sp1
[root@sparky boot]# file vmlinuz-2.6.11-1.1166sp1
vmlinuz-2.6.11-1.1166sp1: ELF 32-bit MSB executable, SPARC, version 1
(SYSV), statically linked, stripped
[root@sparky boot]# file initrd-2.6.11-1.1166sp1.img
initrd-2.6.11-1.1166sp1.img: gzip compressed data, from Unix, max
compression
[root@sparky boot]# zcat initrd-2.6.11-1.1166sp1.img >/tmp/initrd
[root@sparky boot]# file /tmp/initrd
/tmp/initrd: ASCII cpio archive (SVR4 with no CRC)
Looks like my initrd is a cpio archive instead of cramfs.
And here's the versions of my mkinitrd and silo:
mkinitrd-4.1.18-2
silo-1.4.8-1
Bob
next prev parent reply other threads:[~2005-05-19 15:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 5:20 2.6.11.10 failure on Hypersparc sparc32 [was: Re: sparc32 2.6 work] Jurij Smakov
2005-05-19 14:35 ` 2.6.11.10 failure on Hypersparc sparc32 [was: Re: sparc32 2.6 Tom 'spot' Callaway
2005-05-19 15:24 ` Bob Breuer [this message]
2005-05-19 16:24 ` Jurij Smakov
2005-05-19 16:41 ` Jurij Smakov
2005-05-19 17:12 ` Tom 'spot' Callaway
2005-05-20 3:45 ` Bob Breuer
2005-06-04 4:21 ` Jurij Smakov
2005-06-04 5:18 ` 2.6.11.10 failure on Hypersparc sparc32 [was: Re: sparc32 2.6 work] William Lee Irwin III
2005-06-04 16:34 ` 2.6.11.10 failure on Hypersparc sparc32 [was: Re: sparc32 2.6 Bob Breuer
2005-06-05 3:13 ` Jurij Smakov
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=428CAF95.4000802@mc.net \
--to=breuerr@mc.net \
--cc=sparclinux@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.