All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7580] Invalid filesystem in Pandaboard defconfig
Date: Thu, 24 Dec 2015 16:51:08 +0000	[thread overview]
Message-ID: <bug-7580-163-o4G4tVqPbw@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-7580-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=7580

--- Comment #9 from Sergio Prado <sergio.prado@e-labworks.com> ---
I could successfully reproduce this error.

The problem is that an ext2 rootfs image is generated, and by default u-boot
passes rootfstype=ext3 to the kernel command line, so the kernel panics trying
to mount ext2 as ext3:

[    2.573730] No filesystem could mount root, tried:  ext3
[    2.578399] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(179,2)

Changing rootfs to ext3 or removing rootfstype from the kernel command line
should fix this problem.

I've also tested with the last U-Boot mainline (2015.10) and it worked (this
version does not pass rootfstype to the kernel command line).

So I'm preparing a patch to bump U-Boot and kernel version and fix this
problem.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2015-12-24 16:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30  0:40 [Buildroot] [Bug 7580] New: Invalid filesystem in Pandaboard defconfig bugzilla at busybox.net
2014-10-30  1:14 ` [Buildroot] [Bug 7580] " bugzilla at busybox.net
2014-11-07  7:27 ` bugzilla at busybox.net
2014-11-08 11:31 ` bugzilla at busybox.net
2014-11-09 13:23 ` bugzilla at busybox.net
2014-11-09 16:38 ` bugzilla at busybox.net
2014-11-10  9:17 ` bugzilla at busybox.net
2014-11-12 21:33 ` bugzilla at busybox.net
2014-11-12 21:34 ` bugzilla at busybox.net
2015-12-24 16:51 ` bugzilla at busybox.net [this message]
2015-12-25 17:32 ` bugzilla at busybox.net
2016-03-07 20:24 ` bugzilla at busybox.net

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=bug-7580-163-o4G4tVqPbw@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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 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.