kernel panic

[PatelBlog]

Hi i am navee patel

I am trying to boot android in imx233 with the lms350 screen i have changed the screen driver also but i am not able to boot the android 

the kernel boot arguments are like this 

console=ttyAM0,115200 root=/dev/mmcblk0p2  rw rootwait lcd_panel=lms430 ssp1=mmc init=/init  rootfstype=ext2

the error i am getting is like as follows 

\0x00

\0x00

Feb 9 201114:40:50

EMI_CTRL 0x1C084040

FRAC 0x92926192

init_ddr_mt46v32m16_133Mhz

pow

er 0x00820710

Frac 0x92926192

start change cpu freq

hbus 0x00000003

cpu 0x00010001

Uncompressing Linux.........................................

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

.......................................... done, booting the kern

el.

Linux version 2.6.31-203-gee1fdae (naveen@naveen-laptop) (gcc version 4.1.2) #12 PREEMPT Wed Feb 9 14:39:20 IST 2011

CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177

CPU: VIVT data cache, VIVT instruction cache

Machine: STMP378X

Memory policy: ECC disabled, Data cache writeback

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

Kernel command line: -e console=ttyAM0,115200 root=/dev/mmcblk0p2 rw rootwait lcd_panel=lms430 ssp1=mmc init=/init rootfstype=ext2

PID hash table entries: 256 (order: 8, 1024 bytes)

Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)

Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)

Memory: 64MB = 64MB total

Memory: 59908KB available (4052K code, 663K data, 120K init, 0K highmem)

SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

NR_IRQS:224

Console: colour dummy device 80x30

console [ttyAM0] enabled

ram_console: buffer (null), invalid size 0, datasize 4294967284

Calibrating delay loop...

200.29 BogoMIPS (lpj=1001472)

Security Framework initialized

M

ount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

regulator: core version 0.5

NET: Registered protocol family 16

regulator: vddd: 800 <--> 1575 mV fast normal

regulator: vddd_bo: 800 <--> 1575 mV fast normal

regulator: vdda: 1500 <--> 2275 mV fast normal

regulator: vddio: 2800 <--> 3575 mV fast normal

regulator: overall_current: 0 <--> 2147483 mA fast normal

regulator: stmp3xxx-keyboard-1: 0 <--> 2147483 mA fast normal

regulator: stmp3xxx_ts-1: 0 <--> 2147483 mA fast normal

regulator: stmp3xxx-appuart-1: 0 <--> 2147483 mA fast normal

regulator: stmp3xxx-dbguart-1: 0 <--> 2147483 mA fast normal

regulator: stmp3xxx_wdt-1: 0 <--> 2147483 mA fast normal

regulator: stmp3xxx-rtc-1: 0 <--> 2147483 mA fast normal

regulator: stmp3xxx-fb-1: 0 <--> 2147483 mA fast normal

regulator: stmp3xxx-bl-1: 0 <--> 2147483 mA fast normal

regulator: stmp3xxx-rotdec-1: 0 <--> 2147483 mA fast normal

regulator: i2c_stmp3xxx-1: 0 <--> 2147483 mA fast normal

regulator: stmp3xxx-persistent-1: 0 <--> 2147483 mA fast normal

regulator: stmp3xxx-dcpboot-1: 0 <--> 2147483 mA fast normal

regulator: stmp3xxx-dcp-1: 0 <--> 2147483 mA fast normal

regulator: stmp3xxx-battery-1: 0 <--> 2147483 mA fast normal

regulator: stmp3xxx-pxp-1: 0 <--> 2147483 mA fast normal

regulator: mmc_ssp-1: 0 <--> 2147483 mA fast normal

regulator: mmc_ssp-2: 0 <--> 2147483 mA fast normal

regulator: charger-1: 0 <--> 2147483 mA fast normal

regulator: power-test-1: 0 <--> 2147483 mA fast normal

regulator: cpufreq-1: 0 <--> 2147483 mA fast normal

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

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 2048 (order: 2, 16384 bytes)

TCP bind hash table entries: 2048 (order: 1, 8192 bytes)

TCP: Hash tables conf

igured (established 2048 bind 2048)

TCP reno registered

NET: Registered protocol family 1

usb: DR gadget (utmi) registered

JFFS2 version 2.2. (NAND) \0xc2\0xa9 2001-2006 Red Hat, Inc.

msgmni has been set to 117

alg: No test for stdrng (krng)

cryptodev: driver loaded.

io scheduler noop registered

io scheduler anticipatory registered

io scheduler deadline registered

io scheduler cfq registered (default)

Console: switching to colour frame buffer device 60x34

stmp3xxx-dbguart: ttyAM0 at MMIO 0x80070000 (

irq = 0) is a Debug UART

stmp3xxx-appuart.0: ttySP0 at MMIO 0x8006c000 (irq = 24) is a stmp3xxx-appuart.0

Found APPUART 3.0.0

loop: module loaded

GPMI NAND Flash driver

bch_init: initialized

ecc8_init: initialized

Scanning for NAND Flash chips...

No NAND device found!!!

gpmi gpmi: No NAND Flash chips found

usbmon: debugfs is not available

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

mice: PS/2 mouse device common for all mice

input: stmp3xxx-keyboard as /class/input/input0

input: STMP3XXX touchscreen as /class/input/input1

input: stmp3xxx-rotdec as /class/input/input2

STMP3xxx RTC driver v1.0 hardware v2.0.0

stmp3xxx-rtc stmp3xxx-rtc: rtc core: registered stmp3xxx-rtc as rtc0

Linux video capture interface: v2.00

stmp3xxx-pxp stmp3xxx-pxp: initialized

IRQ 3/stmp3xxx-battery: IRQF_DISABLED is not guaranteed on shared IRQs

stmp3xxx-battery stmp3xxx-battery.0: 5v disconnection handled

stmp3xxx watchdog: initialized, heartbeat 19 sec

stmp3xxx-dcp stmp3xxx-dcp: DCP crypto enabled.!

logger: created 64K log 'log_main'

logger: created 256K log 'log_events'

logger: created 64K log 'log_radio'

Advanced Linux Sound Architecture Driver Version 1.0.20.

stmp378x-audio stmp378x-audio: STMP378X ADC/DAC Audio Codec 0.1

No device for DAI stmp378x adc/dac

stmp3xxx-spdif stmp3xxx-spdif: STMP3XXX SPDIF Audio Transmitter 0

.1

No device for codec stmp3xxx spdif

No device for DAI stmp3xxx spdif

No device for DAI stmp3xxx adc/dac

No device for DAI stmp3xxx spdif

asoc: stmp378x adc/dac <-> stmp3xxx adc/dac mapping ok

asoc: stmp3xxx spdif <-> stmp3xxx spdif mapping ok

stmp3xxx_request_pin: CONFLICT DETECTED pin 2:7 caller spdif owner stmp3xxx-rotdec

ALSA device list:

#0: STMP3780 Devb (stmp378x adc/dac)

#1: STMP3780 Devb (stmp3xxx spdif)

TCP cubic registered

NET: Registered protocol family 17

RPC: Registered udp transport module.

RPC: Registered tcp transport module.

stmp3xxx-rtc stmp3xxx-rtc: setting system clock to 1970-01-01 00:00:04 UTC (4)

Waiting for root device /dev/mmcblk0p2...

mmc0: new SDHC card at address e624

mmcblk0: mmc0:e624 SU04G 3.69 GiB (ro)

mmcblk0: p1 p2 p3

VFS: Cannot open root device "mmcblk0p2" or unknown-block(179,2)

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

b300 3872256 mmcblk0 driver: mmcblk

b301 16822 mmcblk0p1

b302 1049256 mmcblk0p2

b303 864864 mmcblk0p3

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

please help me with this

advanced thanks to you all

S N Naveen patel

[Bogumil]

I've similar issue fixed with iMX28EVK, hope this helps.

The reason of it is mmcblk0 is discovered as read-only (see end of line mmcblk0: mmc0:e624 SU04G 3.69 GiB (ro)). If it is read-write than no info at the end of this line should be printed.

Check hardware and software pins config.

I found write protect state of SD card in device.c mxs_mmc_platform_data.get_wp function (mxs_mmc_get_wp_ssp0 on iMX28).

Second thing, don't know how it is on imx233, but in iMX28 rootfs is on 3-rd partition (mmcblk0p3).

[Ameeca]

I have the exact same problem but I know for sure that my RFS is on mmcblk0p2.

I think this is an issue with the actual SD card.

[BharathiSubrama]

1. As Balaji says, it is related to RFS. There are 3 partitions are available in your SD Card. Make sure, whether RFS in P2 or P3 and set it. 2. Set the correct rootfstype.

[Balaji_ng]

where are you putting your root filesystem? I think it is not in mmcblk0p2. Either you have your rootfs on mmcblk0p2 or change the kernel command line option to whereever your rootfile system is.

[PatelBlog]

I have ported the android but the touch screen is not working. what might be the problem. 

thanks in advance

S N Naveen patel

[BennyKukoy]

I suspect that the reason might be your card. What's the brand of your SD?