linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dinh.linux@gmail.com (Dinh Nguyen)
To: linux-arm-kernel@lists.infradead.org
Subject: socfpga mmc (was Re: [GIT PULL] SOCFPGA DTS updates for 3.17)
Date: Thu, 14 Aug 2014 15:56:02 -0500	[thread overview]
Message-ID: <53ED2262.50604@gmail.com> (raw)
In-Reply-To: <20140814184710.GA11558@amd.pavel.ucw.cz>



On 8/14/14, 1:47 PM, Pavel Machek wrote:
> Hi!
> 
> I tried booting kernel based on ba36899, and got:
> 
> 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.

But just a thought, should one really be developing and debugging with
commits in a merge window?

Dinh
> 
> IIRC it worked ok in 3.16 in similar config. It may be stupid mistake,
> but if you know what I did wrong, I'd like to know... (-6 is ENXIO, so
> -- how can the device be there and not be there at the same time?)
> 
> 									Pavel
> 

  reply	other threads:[~2014-08-14 20:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15  4:06 [GIT PULL] SOCFPGA DTS updates for 3.17 dinguyen at altera.com
2014-07-15  4:41 ` Olof Johansson
2014-07-15  7:29 ` Jaehoon Chung
2014-07-15 15:01   ` Dinh Nguyen
2014-07-16  1:34     ` Jaehoon Chung
2014-07-16 21:05       ` Dinh Nguyen
2014-08-14 18:47   ` socfpga mmc (was Re: [GIT PULL] SOCFPGA DTS updates for 3.17) Pavel Machek
2014-08-14 20:56     ` Dinh Nguyen [this message]
2014-08-14 21:02       ` Pavel Machek
2014-08-14 21:25         ` Dinh Nguyen
     [not found]         ` <20140826114707.GA16372@amd>
2014-08-26 21:00           ` 3.17-rc2: root=/dev/mmcblk0p2 command line parsing fails Dinh Nguyen
2014-09-09 11:49             ` Pavel Machek
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=53ED2262.50604@gmail.com \
    --to=dinh.linux@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).