Hi,
I am unable to boot kernel for omap 2430 board with 2.6.14.7.
I get following message :
Starting
kernel ...
Uncompressing
Linux..............................................................
Linux version 2.6.14.7-arm1-omap2 (r...@infba01539) (gcc version 4.4.1
(Sourcery0
CPU: TI OMAP2430 (ARM1136JF-S) [4107b366] revision 6
(ARMv6TEJ)
Machine: OMAP24xx
2430SDP
Memory policy: ECC disabled, Data cache
writeback
OMAP24302
Power Management for TI
OMAP.
Clocking rate (xtal/DPLL/MPU): 13.0/660/330
MHz
clock.c: Enable for dpll_ck without enable
code
Disabling unused clock "i2chs2_fck"... <6>
done
Disabling unused clock "i2c2_ick"... <6>
done
Disabling unused clock "i2chs1_fck"... <6>
done
Disabling unused clock "i2c1_ick"... <6>
done
Disabling unused clock "wdt1_ick"... <6>
done
Disabling unused clock "mpu_wdt_fck"... <6>
done
Disabling unused clock "mpu_wdt_ick"... <6>
done
Disabling unused clock "gpios_fck"... <6>
done
Disabling unused clock "gpios_ick"... <6>
done
Disabling unused clock "gpt2_fck"... <6>
done
Disabling unused clock "gpt2_ick"... <6>
done
Disabling unused clock "mdm_osc_ck"... <6>
done
CPU0: D VIPT write-back
cache
CPU0: I cache: 32768 bytes, associativity 4, 32 byte lines, 256
sets
CPU0: D cache: 32768 bytes, associativity 4, 32 byte lines, 256
sets
Built 1
zonelists
Kernel command line: console=ttyS0,115200n8 root=172.28.6.33:/dev/nfs
rw noinitrM
IRQ: Found an INTC at 0x480fe000 (revision 3.0) with 96
interrupts
Total of 96 interrupts on 1 active
controller
OMAP GPIO hardware version
2.4
PID hash table entries: 256 (order: 8, 4096
bytes)
OMAP GPTimer1 hardware version
1.6
OMAP GPTimer2 hardware version
1.6
Console: colour dummy device
80x30
Dentry cache hash table entries: 8192 (order: 3, 32768
bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384
bytes)
Memory: 32MB = 32MB
total
Memory: 29104KB available (2563K code, 563K data, 120K
init)
Mount-cache hash table entries:
512
CPU: Testing write buffer coherency:
ok
softlockup thread 0 started
up.
NET: Registered protocol family
16
OMAP DMA4 hardware Initialized (max
lch=32)
omap2_disp: timeout waiting for display controller
reset
OMAP Display hardware version
1.0
OMAP virtual buses
initialized
Registering OMAP device 'OMAP24xx I2C 03'. Parent at
L4CORE
Registering OMAP device 'OMAP24xx I2C 13'. Parent at
L4CORE
TWL4030 Power Companion
Active
TWL4030: Driver registration
complete.
usbcore: registered new driver
usbfs
usbcore: registered new driver
hub
musb_hdrc: version 2.2a/db-0.5.2, musb-dma, otg (peripheral+host),
debug=0
musb_hdrc: MHDRC RTL version
1.400
musb_hdrc: USB OTG mode controller at c2800000 using DMA, IRQ
92
Registering OMAP device 'omap-ostimer21'. Parent at
L4CORE
NetWinder Floating Point Emulator V0.97 (double
precision)
VFS: Disk quotas
dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096
bytes)
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat,
Inc.
Initializing Cryptographic
API
Registering OMAP device 'sdp2430_lcd9'. Parent at
L3
Registering OMAP device 'sdp2430_tv10'. Parent at
L3
Registering OMAP device 'omap24xxfb6'. Parent at
L3
omap24xxfb: Options
"<NULL>"
Console: switching to colour frame buffer device
30x40
omap24xxfb: fb0 frame buffer
device
omap24xxfb: display mode 240x320x16 hsync 19kHz vsync
58Hz
OMAP Watchdog Timer: initial timeout 60
sec
Serial: 8250/16550 driver $Revision: 1.90 $ 3 ports, IRQ sharing
disabled
ttyS0 at MMIO 0x4806a000 (irq = 72) is a
ST16654
ttyS1 at MMIO 0x4806c000 (irq = 73) is a
ST16654
ttyS2 at MMIO 0x4806e000 (irq = 74) is a
ST16654
TWL4030 GPIO Demux: IRQ Range 265 to 274, Initialization
Success
phy_clk_ctrl_sts =
0x0
Initializing TWL4030 USB module (v0451,
pc002)
io scheduler noop
registered
io scheduler anticipatory
registered
io scheduler deadline
registered
io scheduler cfq
registered
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024
blocksize
loop: loaded (max 8
devices)
OMAP Timer32K is
initialized
Registering OMAP device 'omap-twl4030rtc16'. Parent at
L4CORE
omap-twl4030rtc:TWL4030-RTC Power up reset
detected.
omap-twl4030rtc:Enabling TWL4030-
RTC.
TWL4030 LEDS: Driver registration
complete.
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre
<n...@cam.org>
eth0: SMC91C94 (rev 9) at c2856300 IRQ 245
[nowait]
eth0: Ethernet addr:
08:00:28:01:04:52
netconsole: not configured,
aborting
Linux video capture interface:
v1.00
Registering OMAP device 'omap24xxcam0'. Parent at
L3
EX3691:Failed to detect EX3691
SOC.
omap24xxcam: cannot initialize
sensor
Registering OMAP device 'omap24xxvout111'. Parent at
L3
omap24xxvout: registered device video1
[v4l2]
Registering OMAP device 'omap24xxvout212'. Parent at
L3
omap24xxvout: registered device video2
[v4l2]
OMAP HDQ Hardware Revision 0.3. Driver in interrupt
mode.
omapflash.1: Found 1 x16 devices at 0x0 in 16-bit
bank
omapflash.1: Found 1 x16 devices at 0x2000000 in 16-bit
bank
Intel/Sharp Extended Query Table at
0x010A
Intel/Sharp Extended Query Table at
0x010A
Intel/Sharp Extended Query Table at
0x010A
Intel/Sharp Extended Query Table at
0x010A
Intel/Sharp Extended Query Table at
0x010A
Using buffer write
method
cfi_cmdset_0001: Erase suspend on write
enabled
Creating 4 MTD partitions on "omapflash.
1":
0x00000000-0x00040000 :
"bootloader"
0x00040000-0x00060000 :
"params"
0x00060000-0x00260000 :
"kernel"
0x00260000-0x04000000 :
"filesystem"
omapflash.0: Found 1 x16 devices at 0x0 in 16-bit
bank
omapflash.0: Found 1 x16 devices at 0x4000000 in 16-bit
bank
Intel/Sharp Extended Query Table at
0x010A
Intel/Sharp Extended Query Table at
0x010A
Intel/Sharp Extended Query Table at
0x010A
Intel/Sharp Extended Query Table at
0x010A
Using buffer write
method
cfi_cmdset_0001: Erase suspend on write
enabled
Creating 4 MTD partitions on "omapflash.
0":
0x00000000-0x00040000 :
"(sibley)bootloader"
0x00040000-0x00080000 :
"(sibley)params"
0x00080000-0x00280000 :
"(sibley)kernel"
0x00280000-0x08000000 :
"(sibley)filesystem"
NAND: Unable to find NAND settings in GPMC Configuration -
quitting
oneNAND: Unable to find oneNAND configuration in GPMC -
quitting
usbmon: debugfs is not
available
usbcore: registered new driver
hset
Registering OMAP device 'omap_twl4030keypad1'. Parent at
L4CORE
Registering OMAP device 'omap_tsc20468'. Parent at
L4CORE
Registering OMAP device 'omap2430-mmc12'. Parent at
L3
Registering OMAP device 'omap2430-mmc217'. Parent at
L3
Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22
13:55:50 .
Registering OMAP device 'omap-dasf7'. Parent at
L3
OMAP243X TWL4030 Audio Support: Chip Rev[0x2f]
Initialized
audio support
initialized
Register_alsa_drv: Created ti_dasf
class
Register_alsa_drv: Created alsaDasf
class
[omap2_dasf_mailbox.c:[dasf_init_mailbox]
start
ALSA device
list:
#0:
TWL4030
NET: Registered protocol family
2
IP route cache hash table entries: 512 (order: -1, 2048
bytes)
TCP established hash table entries: 2048 (order: 1, 8192
bytes)
TCP bind hash table entries: 2048 (order: 1, 8192
bytes)
TCP: Hash tables configured (established 2048 bind
2048)
TCP reno
registered
TCP bic
registered
NET: Registered protocol family
1
NET: Registered protocol family
17
NET: Registered protocol family
15
Registering OMAP device 'omap-dxdev19'. Parent at
L4CORE
Registering OMAP device 'omap-sdram20'. Parent at
L3
VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev
2
OMAP GPIO switch handler
initializing
eth0: link
up
IP-Config:
Complete:
device=eth0, addr=172.28.6.34, mask=255.255.255.0,
gw=255.255.255.255,
host=172.28.6.34, domain=, nis-
domain=(none),
bootserver=172.28.6.33, rootserver=172.28.6.33,
rootpath=
Looking up port of RPC 100003/2 on
172.28.6.33
portmap: server 172.28.6.33 not responding, timed
out
Root-NFS: Unable to get nfsd port number from server, using
default
Looking up port of RPC 100005/1 on
172.28.6.33
portmap: server 172.28.6.33 not responding, timed
out
Root-NFS: Unable to get mountd port number from server, using
default
Root-NFS: Server returned error -5 while mounting /nfsroot/
rootfs
VFS: Unable to mount root fs via NFS, trying
floppy.
VFS: No root yet, retrying to mount root on 172.28.6.33:/dev/nfs
(unknown-block()
VFS: No root yet, retrying to mount root on 172.28.6.33:/dev/nfs
(unknown-block()
VFS: No root yet, retrying to mount root on 172.28.6.33:/dev/nfs
(unknown-block()
VFS: No root yet, retrying to mount root on 172.28.6.33:/dev/nfs
(unknown-block()
VFS: No root yet, retrying to mount root on 172.28.6.33:/dev/nfs
(unknown-block()
VFS: No root yet, retrying to mount root on 172.28.6.33:/dev/nfs
(unknown-block()
VFS: Cannot open root device "172.28.6.33:/dev/nfs" or unknown-
block(2,0)
Please append a correct "root=" boot
option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-
block(2,0)
Can anyone tell me what is going on wrong?
Thanks,
Sri.
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
