Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph G. Boike <joe.boike@acsatlanta.com>
To: buildroot@busybox.net
Subject: [Buildroot] can't find root fs kernel panic
Date: Fri, 20 Jun 2008 10:03:08 -0500	[thread overview]
Message-ID: <485BC6AC.1090301@acsatlanta.com> (raw)
In-Reply-To: <mailman.1147.1213963958.1345.buildroot@uclibc.org>

I'm hoping someone can help me with this.
I'm using this morning buildroot (How do I determine the rev #?)
Built for an Atmel at91sam9260 processor and eval board.
I've tried using the ext2, ext2.gz and jffs root filesystems with the 
same results.
Below is an abridged capture from the kernel during boot.
I've tried google, but everything I saw was related to the bootloader 
pointing to the wrong disk.
My u-boot invocation is:
bootp 21500000 linux.gz; bootp 20410000 rootfs.ext2.gz; bootm 21500000
Is the Kernel command line correct?
(I've tried 2 different boards, so I don't think it's h/w.)

Regards,
Joe

Starting kernel ...

Uncompressing 
Linux....................................................................................................
Linux version 2.6.24.4 (JoeB at elab14_linux.localdomain) (gcc version 
4.2.1) #2 Fri Jun 20 10:07:40 EDT 2008
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Atmel AT91SAM9260-EK
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 199 MHz, master 99 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: mem=64M console=ttyS0,115200 
initrd=0x20410000,3145728 root=/dev/ram0 rw

Memory: 64MB = 64MB total
Memory: 58056KB available (3352K code, 238K data, 140K init)

checking if image is initramfs...it isn't (bad gzip magic numbers); 
looks like an initrd
Freeing initrd memory: 3072K
NetWinder Floating Point Emulator V0.97 (double precision)
DLM (built Jun 20 2008 09:40:47) installed
JFS: nTxBlock = 478, nTxLock = 3824

RAMDISK driver initialized: 16 RAM disks of 15360K size 1024 blocksize

RAMDISK: Couldn't find valid RAM disk image starting at 0.
List of all partitions:
No filesystem could mount root, tried:  ext2 cramfs msdos vfat jfs
Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(1,0)

       reply	other threads:[~2008-06-20 15:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1147.1213963958.1345.buildroot@uclibc.org>
2008-06-20 15:03 ` Joseph G. Boike [this message]
2008-06-20 19:32   ` [Buildroot] can't find root fs kernel panic Peter Korsgaard
2008-06-20 20:48   ` Thiago A. Corrêa
2008-06-21  2:28   ` [Buildroot] can t " Mike Sander
     [not found]   ` <485C66DD.2070304@ripnet.com>
2008-06-23 16:48     ` Joseph G. Boike

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=485BC6AC.1090301@acsatlanta.com \
    --to=joe.boike@acsatlanta.com \
    --cc=buildroot@busybox.net \
    /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