VFS: Cannot open root device "mmcblk0p1" or unknown-block(179,1)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

VFS: Cannot open root device "mmcblk0p1" or unknown-block(179,1)

9,069 Views
vishvapathi
Contributor V
VFS: Cannot open root device "mmcblk0p1" or unknown-block(179,1)          

Please append a correct "root=" boot option; here are the available partitions:

b300     7757824 mmcblk0  driver: mmcblk                              
b310        2048 mmcblk0boot1  (driver?)                              
b308        2048 mmcblk0boot0  (driver?)                              

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,1)

[<80047834>] (unwind_backtrace+0x0/0xf8) from [<80508af4>] (panic+0x74/0x18c)  

[<80508af4>] (panic+0x74/0x18c) from [<80008ce8>] (mount_block_root+0x170/0x224)

[<80008ce8>] (mount_block_root+0x170/0x224) from [<80008e84>] (mount_root+0xe8/)

[<80008e84>] (mount_root+0xe8/0x108) from [<80008fc4>] (prepare_namespace+0x120)

[<80008fc4>] (prepare_namespace+0x120/0x178) from [<800089b0>] (kernel_init+0x1)

[<800089b0>] (kernel_init+0x108/0x13c) from [<80041aa4>] (kernel_thread_exit+0x)

CPU2: stopping                                                            

[<80047834>] (unwind_backtrace+0x0/0xf8) from [<8003b324>] (do_IPI+0x150/0x17c)

[<8003b324>] (do_IPI+0x150/0x17c) from [<80040a0c>] (__irq_svc+0x4c/0xe8) 
Exception stack(0xbffb5f90 to 0xbffb5fd8)                                 
5f80:                                 80af9140 80000093 00000001 00000000  

5fa0: bffb4000 80af1ce4 80510fa0 80aa6e7c 1000406a 412fc09a 00000000 00000000  

5fc0: 00000000 bffb5fd8 8004f648 80041b04 40000013 ffffffff               

[<80040a0c>] (__irq_svc+0x4c/0xe8) from [<80041b04>] (default_idle+0x24/0x28)  

[<80041b04>] (default_idle+0x24/0x28) from [<80041d08>] (cpu_idle+0xc8/0x108)  

[<80041d08>] (cpu_idle+0xc8/0x108) from [<10505934>] (0x10505934)         
CPU3: stopping                                                            

[<80047834>] (unwind_backtrace+0x0/0xf8) from [<8003b324>] (do_IPI+0x150/0x17c)

[<8003b324>] (do_IPI+0x150/0x17c) from [<80040a0c>] (__irq_svc+0x4c/0xe8) 
Exception stack(0xbff01f90 to 0xbff01fd8)                                 
1f80:                                 80af9140 60000093 00000001 00000000  

1fa0: bff00000 80af1ce4 80510fa0 80aa6e7c 1000406a 412fc09a 00000000 00000000  

1fc0: 00000000 bff01fd8 8004f648 80041b04 40000013 ffffffff               

[<80040a0c>] (__irq_svc+0x4c/0xe8) from [<80041b04>] (default_idle+0x24/0x28)  

[<80041b04>] (default_idle+0x24/0x28) from [<80041d08>] (cpu_idle+0xc8/0x108)  

[<80041d08>] (cpu_idle+0xc8/0x108) from [<10505934>] (0x10505934)         
CPU1: stopping                                                            

[<80047834>] (unwind_backtrace+0x0/0xf8) from [<8003b324>] (do_IPI+0x150/0x17c)

[<8003b324>] (do_IPI+0x150/0x17c) from [<80040a0c>] (__irq_svc+0x4c/0xe8) 
Exception stack(0xbffadf90 to 0xbffadfd8)                                 
df80:                                 80af9140 60000093 00000001 00000000  

dfa0: bffac000 80af1ce4 80510fa0 80aa6e7c 1000406a 412fc09a 00000000 00000000  

dfc0: 00000000 bffadfd8 8004f648 80041b04 40000013 ffffffff               

[<80040a0c>] (__irq_svc+0x4c/0xe8) from [<80041b04>] (default_idle+0x24/0x28)  

[<80041b04>] (default_idle+0x24/0x28) from [<80041d08>] (cpu_idle+0xc8/0x108)  

[<80041d08>] (cpu_idle+0xc8/0x108) from [<10505934>] (0x10505934)         

 

Any help would be appreciated...

Thanks in advance


Original Attachment has been moved to: kerrnel-error.zip

Labels (2)
0 Kudos
6 Replies

2,146 Views
alexyang
NXP Employee
NXP Employee

Please check your kernel boot parameters on u-boot.

The below is a part of your kernel log, but Kernel command is not proper to boot with mmc0

---------------------------------------------------------------------------------------------

Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 227328   

Kernel command line: console=ttymxc0,115200 setenv bootargs ${bootargs} root=/d4

PID hash table entries: 4096 (order: 2, 16384 bytes)

---------------------------------------------------------------------------------------------

- Alex Yang

0 Kudos

2,146 Views
mike_m
Contributor I

Make sure the SD card you are using is NOT write protected.  The default mount command

for SD cards (in uboot) use the "rw" option.  If the card is write protected, the mount will

fail and give you this same error message.  While this may not be your problem, it is certainly

easy to test

2,146 Views
BrilliantovKiri
Senior Contributor I

Please recheck SD-card IOMUX configuration, I solve similar problem with follow configuration, thanks Weidong from technical support :

/* ESDHC1 WP */

_MX53_PAD_DI0_PIN4__ESDHC1_WP |

    MUX_PAD_CTRL(PAD_CTL_HYS | PAD_CTL_PKE | PAD_CTL_PUE | PAD_CTL_PUS_360K_DOWN |

                                   PAD_CTL_DSE_HIGH | PAD_CTL_SRE_FAST)

If I use PAD_CTL_PUS_100K_UP I can't mount rootfs with follow error:

Waiting for root device /dev/mmcblk0p1...

mmc0: new high speed SDHC card at address e624

mmcblk0: mmc0:e624 SU04G 3.69 GiB

mmcblk0: p1

mmc0: Timeout waiting for hardware interrupt.

mxsdhci: ============== REGISTER DUMP ==============

mxsdhci: Sys addr: 0x85690000 | Version:  0x00001201

mxsdhci: Blk size: 0x00000200 | Blk cnt:  0x00000008

mxsdhci: Argument: 0x00049c14 | Trn mode: 0x193a0023

mxsdhci: Present:  0xff800008 | Host ctl: 0x00000023

mxsdhci: Clock:    0x000e011f

mxsdhci: Int stat: 0x00000000

mxsdhci: Int enab: 0x117f010f | Sig enab: 0x117f000f

mxsdhci: Caps:     0x07f30000

mxsdhci: ===========================================

------------[ cut here ]------------

WARNING: at drivers/mmc/host/mx_sdhci.c:747 sdhci_send_command+0x24/0x658()

Modules linked in:

[<c003558c>] (unwind_backtrace+0x0/0xf0) from [<c0056ddc>] (warn_slowpath_common+0x4c/0x64)

............

unwind: Unknown symbol address c000899c

unwind: Index not found c000899c

---[ end trace 7e25820bda734871 ]---

mmcblk0: error -110 transferring data, sector 302100, nr 8, card status 0x0

mmcblk0: error -110 sending stop command, response 0x0, card status 0x0

end_request: I/O error, dev mmcblk0, sector 302100

Buffer I/O error on device mmcblk0p1, logical block 0

lost page write due to I/O error on mmcblk0p1



0 Kudos

2,146 Views
vishvapathi
Contributor V

Hi Kirill,

   Thanks for your response. I will check it out. I loaded the rootfs files from freescale website and the EVB is up and running. How to i export and set values to GPIO's in Linux. If there is any document kindly share.

Thanks in advance

0 Kudos

2,146 Views
BrilliantovKiri
Senior Contributor I

Hello!

If you Linux configured found rootfs on SD-card please check what your Linux builded with MMC support, MMC support should be enabled in not modules mode.

Also please check what you can work with SD-card from U-Boot and Linux configure SD-card pins.

0 Kudos

2,146 Views
vishvapathi
Contributor V

Hi Kirill,

Thanks for your response. But wat did u mean by "not module mode"???

during start up in console

mmc0: new high speed DDR MMC card at address 0001                         
mmcblk0: mmc0:0001 SEM08G 7.39 GiB                                        
wm8962 0-001a: customer id 0 revision D                                   
mmcblk0boot0: mmc0:0001 SEM08G partition 1 2.00 MiB                       
mmcblk0boot1: mmc0:0001 SEM08G partition 2 2.00 MiB                       
mmcblk0: unknown partition table                                         
mmcblk0boot1: unknown partition table                                    

mmcblk0boot0: unknown partition table

getting these. Does this mean anything wrong with my SD.  while i am able to view the rootfs files when i connect to linux host

0 Kudos