Quantcast

Kernel panic in booting from NAND

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Kernel panic in booting from NAND

fantajista
I flashed my images refer to this site.
http://www.gumstix.org/how-to/70-writing-images-to-flash.html 

After flashing my images made by bitbake, I powered off my Gumstix and remove microSD. Then powered on.

In booting from NAND, I got Kernel panic error.
>Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

When I used these images, I succeeded to boot.
http://cumulus.gumstix.org/images/angstrom/developer/2011-07-08-0945/

My kernel version is 2.6.39.

thanks.

â– part of boot log
-----------------
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xbc (Micron NAND 512MiB 1,8V 16-bit)
UBI error: ubi_init: UBI error: cannot initialize UBI, error -19
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
cdc_ncm: 23-Apr-2011
usbcore: registered new interface driver cdc_ncm
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 2
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
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: OMAP-EHCI Host Controller
usb usb2: Manufacturer: Linux 2.6.39 ehci_hcd
usb usb2: SerialNumber: ehci-omap.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
twl_rtc twl_rtc: Power up reset detected.
i2c /dev entries driver
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
overo SoC init
asoc: twl4030-hifi <-> omap-mcbsp-dai.1 mapping ok
ALSA device list:
  #0: overo
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
ThumbEE CPU extension supported.
Power Management for TI OMAP3.
sr_init: No PMIC hook to init smartreflex
smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
clock: disabling unused clocks to save power
registered taskstats version 1
fbcvt: 1024x768@60: CVT Name - .786M3-R
Console: switching to colour frame buffer device 128x48
regulator_init_complete: VDAC: incomplete constraints, leaving on
regulator_init_complete: vads7846: incomplete constraints, leaving on
twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:11 UTC (946684811)
UBIFS error (pid 1): ubifs_mount: cannot open "ubi0:rootfs", error -19
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00          524288 mtdblock0  (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
---------------
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Kernel panic in booting from NAND

fantajista
I found that no mtd partitions were created.

root@overo:~# ls /dev/mtd*
/dev/mtd0  /dev/mtd0ro  /dev/mtdblock0

In succeeded to boot from NAND, I saw these boot log, but in failed, I didn't.
-----
Creating 5 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000080000 : "xloader"
0x000000080000-0x000000240000 : "uboot"
0x000000240000-0x000000280000 : "uboot environment"
0x000000280000-0x000000680000 : "linux"
0x000000680000-0x000020000000 : "rootfs"
-----

I confirmed the menuconfig whether UBI file system is enable in this site.
http://processors.wiki.ti.com/index.php/UBIFS_Support#Configuration

Why mtd partitions are NOT created?

I'd appreciate a pointer if I missed something.

Thanks,
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Kernel panic in booting from NAND

fantajista
I could boot successfully.

I enabled "CONFIG_MTD_PARTITIONS" in menuconfig by selecting to

Device Drivers -> Memory Technology Device (MTD) Suppor -> Enable UBI - Unsorted block images -> MTD partitioning support.

Then, I did bitbake kernel and copy uImage to microSD. After that, I flashed uImage with u-boot.

Thanks,
Loading...