From: Pavel Machek <pavel@denx.de>
To: Dinh Nguyen <dinh.linux@gmail.com>
Cc: Jaehoon Chung <jh80.chung@samsung.com>,
Dinh Nguyen <dinguyen@altera.com>,
Kevin Hilman <khilman@linaro.org>,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
arm@kernel.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
kernel list <linux-kernel@vger.kernel.org>,
akpm@linux-foundation.org
Subject: Re: 3.17-rc2: root=/dev/mmcblk0p2 command line parsing fails
Date: Tue, 9 Sep 2014 13:49:41 +0200 [thread overview]
Message-ID: <20140909114941.GE15404@amd> (raw)
In-Reply-To: <CADhT+wdx2SsHnk=zML7a6mUVJxvLQ9ARO16QoYYsopAqhw7cow@mail.gmail.com>
Hi!
> > The problem is still there in 3.17-rc2. 3.16 does not have the
> > problem. Messages are still similar:
> >
> > mmc0: new high speed SDHC card at address b368
> > mmcblk0: mmc0:b368 USD 7.45 GiB
> > mmcblk0: p1 p2 p3 p4
> > VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error
> > -6
> > Please append a correct "root=" boot option; here are the available
> > partitions:
> > b300 7822336 mmcblk0 driver: mmcblk
> > b301 102400 mmcblk0p1 00082434-01
> > b302 1048576 mmcblk0p2 00082434-02
> > b303 1024 mmcblk0p3 00082434-03
> > b304 6086656 mmcblk0p4 00082434-04
> > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> > CPU: 0 PID: 1 Comm: swapper/0 Not tainted
> > 3.17.0-rc2-00368-gec0400b-dirty #83
> >
> >
> > What is going on there? Clearly partition table was parsed and
> > partitions are available; does the mention of unknown-block(0,0) mean
> > that kernel failed to parse the command line?
> >
> > I replaced "root=/dev/mmcblk0p2" with "root=b302" and have a booting
> > system.
>
>
> Can you do a bisect? 3.17-rc2 booted fine for me today:
>
> EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
> VFS: Mounted root (ext3 filesystem) on device 179:2.
> Freeing unused kernel memory: 252K (c052d000 - c056c000)
> random: nonblocking pool is initialized
Bisect would be hard... and I believe the problem is somewhere in
block layer now -- not socfpga-specific.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2014-09-09 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1405397216-909-1-git-send-email-dinguyen@altera.com>
[not found] ` <53C4D874.2040206@samsung.com>
[not found] ` <20140814184710.GA11558@amd.pavel.ucw.cz>
[not found] ` <53ED2262.50604@gmail.com>
[not found] ` <20140814210252.GB26857@amd.pavel.ucw.cz>
2014-08-26 11:47 ` 3.17-rc2: root=/dev/mmcblk0p2 command line parsing fails Pavel Machek
2014-08-26 21:00 ` Dinh Nguyen
2014-09-09 11:49 ` Pavel Machek [this message]
2014-09-17 13:20 ` Russell King - ARM Linux
2014-09-17 13:47 ` Russell King - ARM Linux
2014-09-17 14:25 ` Paul Gortmaker
2014-09-17 14:57 ` [PATCH] Revert "init: make rootdelay=N consistent with rootwait behaviour" Paul Gortmaker
2014-09-18 13:17 ` Pavel Machek
2015-04-09 9:42 ` rootdelay regression is back in 4.0? was " Pavel Machek
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=20140909114941.GE15404@amd \
--to=pavel@denx.de \
--cc=akpm@linux-foundation.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=dinguyen@altera.com \
--cc=dinh.linux@gmail.com \
--cc=jh80.chung@samsung.com \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.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;
as well as URLs for NNTP newsgroup(s).