问题求助 -- VFS: Cannot open root device "mmcblk0p2"
最近做了块嵌入式实验板,用的是TI公司的芯片AM3517。
linux嵌入式系统采用SD卡来引导。XLoder,Uboot,Kernel都顺利启动,问题是最后一步的文件系统进不去,会报错。启动的信息参见附件。
困扰好几天了。请大家帮我看看这个问题如何来解决。
Texas Instruments X-Loader 1.45 (Jun 9 2011 - 18:34:20)
Starting X-loader on MMC...
Reading boot sector
214944 Bytes Read from MMC
Starting OS Bootloader from MMC...
Starting OS Bootloader....
U-Boot 2009.11 ( 6鏈?15 2011 - 16:50:07)
OMAP34xx/35xx-GP ES1.0, CPU-OPP2 L3-165MHz
AM3517EVM Board + LPDDR/NAND
I2C: ready
DRAM: 256 MB
NAND: 1024 MiB
*** Warning - bad CRC or NAND, using default environment
In: serial
Out: serial
Err: serial
Die ID #5074000100000000015da3961502000f
Net: davinci_emac_initialize
Ethernet PHY: GENERIC @ 0x01
DaVinci EMAC
Hit any key to stop autoboot: 0
mmc1 is available
reading boot.scr
** Unable to read "boot.scr" from mmc 0:1 **
reading uImage
2296500 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-2.6.32
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2296436 Bytes = 2.2 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux..............................................................................................................................
.................. done, booting the kernel.
Linux version 2.6.32 (realtimedsp@realtimedsp-desktop) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Wed Jun 15 16:58:55 CST 2011
CPU: ARMv7 Processor [411fc087] revision 7 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3517/AM3517 EVM
Memory policy: ECC disabled, Data cache writeback
AM3517 ES3.1 (l2cache iva sgx neon isp )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x100000
Reserving 4194304 bytes SDRAM for VRAM
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Kernel command line: console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 256MB = 256MB total
Memory: 251008KB available (3988K code, 344K data, 164K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:368
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
GPMC revision 5.0
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP GPIO hardware version 2.5
OMAP clockevent source: GPTIMER1 at 32768 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 503.12 BogoMIPS (lpj=1966080)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
failed to get lcd_backlight_pwr
OMAP DMA hardware revision 4.0
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c_omap i2c_omap.1: bus 1 rev3.12 at 400 kHz
regulator: VDCDC1: 1200 mV normal
regulator: VDCDC2: 3300 mV normal
regulator: VDCDC3: 1800 mV normal
regulator: LDO1: 1800 mV normal
regulator: LDO2: 3300 mV normal
Switching to clocksource 32k_counter
musb_hdrc: version 6.0, cppi4.1-dma, otg (peripheral+host), debug=0
AM3517 OTG revision 4ea41001, PHY f0836a2, control 00
musb_hdrc: USB OTG mode controller at d0810000 using DMA, IRQ 71
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
AM3517 Linux PSP version 03.00.00.04 (AM3517EVM)
NetWinder Floating Point Emulator V0.97 (double precision)
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
JFFS2 version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.
msgmni has been set to 490
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
OMAP DSS rev 2.0
OMAP DISPC rev 3.0
OMAP VENC rev 2
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
console [ttyS2] enabled
brd: module loaded
loop: module loaded
omap2-nand driver initializing
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit)
Creating 5 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000080000 : "xloader-nand"
0x000000080000-0x000000240000 : "uboot-nand"
0x000000240000-0x000000280000 : "params-nand"
0x000000280000-0x000000780000 : "linux-nand"
0x000000780000-0x000040000000 : "jffs2-nand"
vcan: Virtual CAN interface driver
CAN device driver interface
TI High End CAN Controller Driver 0.7
failed to get can_stb
ti_hecc ti_hecc.1: device registered (reg_base=d0870000, irq=24)
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 1
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: OMAP-EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.32 ehci_hcd
usb usb1: SerialNumber: ehci-omap.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbtest
g_ether gadget: using random self ethernet address
g_ether gadget: using random host ethernet address
usb0: MAC 6e:48:93:3d:05:8c
usb0: HOST MAC 3e:89:e8:b0:99:a3
g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
g_ether gadget: g_ether ready
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.32 musb-hcd
usb usb2: SerialNumber: musb_hdrc
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
rtc-s35390a 1-0030: error resetting chip
rtc-s35390a: probe of 1-0030 failed with error -5
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v0.1.0)
vpfe_init
vpfe-capture vpfe-capture: v4l2 device registered
vpfe-capture vpfe-capture: video device registered
tvp5150a 1-005d: tvp5150a 1-005d decoder driver registered !!
vpfe-capture vpfe-capture: v4l2 sub device tvp5150a registered
vpfe_register_ccdc_device: DM6446 CCDC
DM6446 CCDC is registered with vpfe.
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
Advanced Linux Sound Architecture Driver Version 1.0.21.
usbcore: registered new interface driver snd-usb-audio
No device for DAI tlv320aic23
No device for DAI omap-mcbsp-dai-0
No device for DAI omap-mcbsp-dai-1
No device for DAI omap-mcbsp-dai-2
No device for DAI omap-mcbsp-dai-3
No device for DAI omap-mcbsp-dai-4
OMAP3517 / AM3517 EVM SoC init
AIC23 Audio Codec 0.1
tlv320aic23_write cannot write 000 to register R15
asoc: tlv320aic23 <-> omap-mcbsp-dai-1 mapping ok
tlv320aic23_write cannot write 001 to register R9
tlv320aic23_write cannot write 004 to register R5
tlv320aic23_write cannot write 117 to register R0
tlv320aic23_write cannot write 117 to register R1
mmc0: new high speed SD card at address 0002
mmcblk0: mmc0:0002 SD256 244 MiB (ro)
mmcblk0:
tlv320aic23_write cannot write 010 to register R4
p1 p2
tlv320aic23_write cannot write 070 to register R2
tlv320aic23_write cannot write 070 to register R3
tlv320aic23_write cannot write 001 to register R9
ALSA device list:
#0: am3517evm (tlv320aic23)
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
can: controller area network core (rev 20090105 abi
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Power Management for TI OMAP3.
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
regulator_init_complete: incomplete constraints, leaving LDO2 on
regulator_init_complete: incomplete constraints, leaving LDO1 on
davinci_emac_probe: using random MAC addr: 16:02:3f:bb:ba:51
emac-mii: probed
drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
omapdss DPI error: display already enabled
omap_vout omap_vout: 'lcd' Display already enabled
omapdss DPI error: display already enabled
omap_vout omap_vout: 'lcd' Display already enabled
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 1
omap_vout omap_vout: Buffer Size = 3686400
omap_vout omap_vout: : registered and initialized video device 2
VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2)
Please append a correct "root=" boot option; here are the available partitions:
1f00 512 mtdblock0 (driver?)
1f01 1792 mtdblock1 (driver?)
1f02 256 mtdblock2 (driver?)
1f03 5120 mtdblock3 (driver?)
1f04 1040896 mtdblock4 (driver?)
b300 250752 mmcblk0 driver: mmcblk
b301 56196 mmcblk0p1
b302 192780 mmcblk0p2
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(9)
本帖最后由 tianqingwang 于 2011-06-17 11:33 编辑
回复 1# libaineu2004
这个分区已经做了,分区可读写吗?
回复 2# tianqingwang
谢谢。问题已经解决了。是硬件原因造成的。SD卡始终处于写保护状态,故而出错。
启动信息里有这句话
mmcblk0: mmc0:0002 SD256 244 MiB (ro)
ro代表read only的意思。即SD卡处于写保护状态。。。。要么是用户把SD卡写保护开关拨到lock的位置,要么就是硬件电路出问题了。
我前两天出了同样的问题,也花了好几天工夫,问题就是lock锁住了!
。。这个没碰到过。。留个标记。
本帖最后由 protheschildren 于 2012-01-15 19:12 编辑
关注留言,楼主很是心细啊。。。
学习了
希望大家发表自己的看法!我先赞成一下
可以用fdisk -l 查看一下,我以前遇到过你这种问题,也自己解决了
如何查看写保护?