linux-kernel - 3.17-rc2: root=/dev/mmcblk0p2 command line parsing fails

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 26 Aug 2014 13:47:09 +0200
From:	Pavel Machek <pavel@...x.de>
To:	Dinh Nguyen <dinh.linux@...il.com>
Cc:	Jaehoon Chung <jh80.chung@...sung.com>, dinguyen@...era.com,
	khilman@...aro.org, olof@...om.net, arnd@...db.de, arm@...nel.org,
	linux-arm-kernel@...ts.infradead.org,
	kernel list <linux-kernel@...r.kernel.org>,
	akpm@...ux-foundation.org
Subject: 3.17-rc2: root=/dev/mmcblk0p2 command line parsing fails

Hi!

> > > mmc0: new 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.16.0-11208-gef74117-dirty
> > > #2        
> > 
> > Hmm...today's tip-top(899552d6) and ba36899 booted just fine for me. I
> > noticed something, you must have commits on top of your ba36899? Mine
> > shows 3.16.0-11149-gba36899.
> 
> Ok, thanks for info. I went back to 3.16, and it worked in same
> config, and went to 3.17, and it broke.

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.

									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/