Hi All,

I'm facing below error msg at loglevel 6 ----

VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 168K
Warning: unable to open an initial console.
init: cannot open '/initlogo.rle'
init: command 'loglevel' r=0
init: command 'export' r=0
init: command 'export' r=0
init: command 'export' r=0
init: command 'export' r=0
init: command 'export' r=0
init: command 'export' r=0
init: command 'export' r=0
init: command 'export' r=0
init: command 'export' r=0
init: command 'export' r=0
init: command 'symlink' r=0
init: command 'symlink' r=0
init: command 'symlink' r=0
init: command 'mkdir' r=0
init: command 'mkdir' r=0
init: command 'mkdir' r=0
init: command 'mount' r=-1
init: command 'mkdir' r=0
init: command 'symlink' r=0
init: command 'mkdir' r=-17
init: command 'mkdir' r=-17
init: command 'mkdir' r=0
init: command 'mkdir' r=0
init: command 'mkdir' r=0
init: command 'mkdir' r=0
init: command 'mkdir' r=0
init: command 'mkdir' r=0
init: command 'mount' r=0
init: command 'mkdir' r=0
init: command 'mount' r=0
init: command 'write' r=0
init: command 'write' r=0
init: command 'write' r=0
init: command 'write' r=-2
init: command 'write' r=-2
init: command 'write' r=0
init: command 'write' r=0
init: command 'mkdir' r=0
init: command 'mount' r=-1
init: command 'chown' r=0
init: command 'chown' r=-2
init: command 'chmod' r=-2
init: command 'write' r=0
init: command 'mkdir' r=0
init: command 'chown' r=-2
init: command 'chmod' r=-2
init: command 'write' r=0
init: command 'mkdir' r=0
init: command 'chown' r=-2
init: command 'chmod' r=-2
init: command 'write' r=0
init: processing action 0x27d90 (fs)
Kernel panic - not syncing: Attempted to kill init!

Thanks & Regards
Deepak

On Fri, Dec 24, 2010 at 6:54 PM, Srinidhi K V <[email protected]>wrote:

> Hi Deepak,
> I has the same issue while porting Froyo on Hawkboard. I had flashed the
> kernel to NAND, I erased it and reflashed it to NAND and this did the trick.
> I am not sure it will work, but you can give a try.
>
> Thanks
> Srinidhi
>
> On Fri, Dec 24, 2010 at 2:17 PM, deepak singal <[email protected]>wrote:
>
>> Hi All,
>>
>> I am trying to port gingerbread on omapevm3530 based target board using
>> latest gingerbread source code and rowboat fyoro kernel 2.6.32.
>> I have checked out the latest source code and built android root file
>> system and kernel.
>>  <http://git.android-x86.org/>
>> I am facing below kernel panic --
>>
>> ## Booting image at 80000000 ...
>>    Image Name:   Linux-2.6.32
>>    Image Type:   ARM Linux Kernel Image (uncompressed)
>>    Data Size:    2407496 Bytes =  2.3 MB
>>    Load Address: 80008000
>>    Entry Point:  80008000
>>    Verifying Checksum ... OK
>> OK
>>
>> Starting kernel ...
>>
>> Uncompressing
>> Linux.....................................................................................................................................................
>> Linux version 2.6.32 (r...@celestial-laptop) (gcc version 4.4.1 (Sourcery
>> G++ Lite 2010q1-202) ) #6 Fri Dec 24 16:37:18 CST 2010
>> CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=10c53c7f
>> CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
>> Machine: OMAP3 EVM
>> Memory policy: ECC disabled, Data cache writeback
>> OMAP3430/3530 ES2.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: 32512
>> Kernel command line: console=ttyS0,115200n8 root=/dev/mmcblk0p2
>> androidboot.console=ttyS0 rw ip=off devfs=mount init=/init rootdelay=3
>> PID hash table entries: 512 (order: -1, 2048 bytes)
>> Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
>> Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
>> Memory: 128MB = 128MB total
>> Memory: 120348KB available (4212K code, 824K data, 168K init, 0K highmem)
>> Hierarchical RCU implementation.
>> NR_IRQS:402
>> Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
>> Reprogramming SDRC clock to 332000000 Hz
>> 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... 499.92 BogoMIPS (lpj=1949696)
>> Mount-cache hash table entries: 512
>> CPU: Testing write buffer coherency: ok
>> regulator: core version 0.5
>> NET: Registered protocol family 16
>> omap3evmdc: Driver registration complete
>> 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 2600 kHz
>> twl4030: PIH (irq 7) chaining IRQs 368..375
>> twl4030: power (irq 373) chaining IRQs 376..383
>> twl4030: gpio (irq 368) chaining IRQs 384..401
>> regulator: VMMC1: 1850 <--> 3150 mV normal standby
>> regulator: VDAC: 1800 mV normal standby
>> regulator: VAUX2_4030: 1800 mV normal standby
>> regulator: VPLL2: 1800 mV normal standby
>> regulator: VSIM: 1800 <--> 3000 mV normal standby
>> regulator: VUSB1V5: 1500 mV normal standby
>> regulator: VUSB1V8: 1800 mV normal standby
>> twl_reg twl_reg.18: can't register VUSB1V8, -16
>> twl_reg: probe of twl_reg.18 failed with error -16
>> i2c_omap i2c_omap.2: bus 2 rev3.12 at 400 kHz
>> i2c_omap i2c_omap.3: bus 3 rev3.12 at 400 kHz
>> Switching to clocksource 32k_counter
>> musb_hdrc: version 6.0, musb-dma, otg (peripheral+host), debug=0
>> musb_hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92
>> NET: Registered protocol family 2
>> IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
>> TCP established hash table entries: 4096 (order: 3, 32768 bytes)
>> TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
>> TCP: Hash tables configured (established 4096 bind 4096)
>> 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.
>> omap-iommu omap-iommu.0: isp registered
>> OMAP35x  Linux PSP version 03.00.01.06 (OMAP3EVM)
>> NetWinder Floating Point Emulator V0.97 (double precision)
>> ashmem: initialized
>> 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 235
>> 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
>> OMAP DSI rev 1.0
>> Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>> serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a ST16654
>> console [ttyS0] enabled
>> serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a ST16654
>> serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a ST16654
>> brd: module loaded
>> loop: module loaded
>> omap2-nand driver initializing
>> OneNAND driver initializing
>> omap2-onenand omap2-onenand: initializing on CS0, phys base 0x20000000,
>> virtual base c8880000
>> Muxed OneNAND 128MB 1.8V 16-bit (0x30)
>> OneNAND version = 0x0221
>> Scanning device for bad blocks
>> onenand_bbt_wait: ecc error = 0x2222, controller error 0x2400
>> Bad eraseblock 676 at 0x05480000
>> Creating 5 MTD partitions on "omap2-onenand":
>> 0x000000000000-0x000000080000 : "xloader-onenand"
>> 0x000000080000-0x000000260000 : "uboot-onenand"
>> 0x000000260000-0x000000280000 : "params-onenand"
>> 0x000000280000-0x000000780000 : "linux-onenand"
>> 0x000000780000-0x000008000000 : "jffs2-onenand"
>> smsc911x: Driver version 2008-10-21.
>> smsc911x-mdio: probed
>> eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:01,
>> irq=-1)
>> net eth0: MAC Address: 00:50:c2:7e:88:a4
>> 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
>> android init
>> android_probe pdata: c047bac8
>> android_bind
>> android_usb gadget: android_usb 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
>> f_adb init
>> android_register_function adb
>> adb_bind_config
>> f_mass_storage init
>> android_register_function usb_mass_storage
>> input: TWL4030 Keypad as
>> /devices/platform/i2c_omap.1/i2c-1/1-004a/twl4030_keypad/input/input0
>> ads7846 spi1.0: touchscreen, irq 335
>> input: ADS7846 Touchscreen as
>> /devices/platform/omap2_mcspi.1/spi1.0/input/input1
>> using rtc device, twl_rtc, for alarms
>> twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
>> twl_rtc twl_rtc: Power up reset detected.
>> twl_rtc twl_rtc: Enabling TWL-RTC.
>> i2c /dev entries driver
>> Linux video capture interface: v2.00
>> tvp514x 3-005d: Registered to v4l2 master omap34xxcam!!
>> omap-iommu omap-iommu.0: isp: version 1.1
>> usbcore: registered new interface driver uvcvideo
>> USB Video Class driver (v0.1.0)
>> OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
>> usbcore: registered new interface driver usbhid
>> usbhid: USB HID core driver
>> logger: created 64K log 'log_main'
>> logger: created 256K log 'log_events'
>> logger: created 64K log 'log_radio'
>> logger: created 64K log 'log_system'
>> Advanced Linux Sound Architecture Driver Version 1.0.21.
>> usbcore: registered new interface driver snd-usb-audio
>> 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
>> OMAP3 EVM SoC init
>> asoc: twl4030 <-> omap-mcbsp-dai-0 mapping ok
>> ALSA device list:
>>   #0: omap3evm (twl4030)
>> TCP cubic registered
>> NET: Registered protocol family 17
>> NET: Registered protocol family 15
>> Power Management for TI OMAP3.
>> Division by zero in kernel.
>> [<c0038890>] (unwind_backtrace+0x0/0xd0) from [<c017cb5c>]
>> (Ldiv0+0x8/0x10)
>> Division by zero in kernel.
>> [<c0038890>] (unwind_backtrace+0x0/0xd0) from [<c017cb5c>]
>> (Ldiv0+0x8/0x10)
>> SmartReflex driver initialized
>> VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1
>> twl_rtc twl_rtc: setting system clock to 2000-01-01 00:00:00 UTC
>> (946684800)
>> mmc0: new high speed SD card at address b368
>> mmcblk0: mmc0:b368 SD02G 1.85 GiB
>>  mmcblk0: p1 p2
>> tvp514x 3-005d: chip id mismatch msb:0xfb lsb:0xfb
>> tvp514x 3-005d: Unable to detect decoder
>> tvp514x 3-005d: chip id mismatch msb:0xfb lsb:0xfb
>> tvp514x 3-005d: Unable to detect decoder
>> tvp514x 3-005d: chip id mismatch msb:0xfb lsb:0xfb
>> tvp514x 3-005d: Unable to detect decoder
>> tvp514x 3-005d: chip id mismatch msb:0xfb lsb:0xfb
>> tvp514x 3-005d: Unable to detect decoder
>> 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 0
>> omap_vout omap_vout: Buffer Size = 3686400
>> omap_vout omap_vout: : registered and initialized video device 1
>> Waiting 3sec before mounting root device...
>> kjournald starting.  Commit interval 5 seconds
>> EXT3-fs (mmcblk0p2): using internal journal
>> EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
>> VFS: Mounted root (ext3 filesystem) on device 179:2.
>> Freeing init memory: 168K
>> Warning: unable to open an initial console.
>> init: cannot open '/initlogo.rle'
>> Kernel panic - not syncing: Attempted to kill init!
>>
>>
>> Any help will be highly appreciated.
>>
>> Thanks & Regards,
>> Deepak
>>
>> --
>> unsubscribe: 
>> [email protected]<android-porting%[email protected]>
>> website: http://groups.google.com/group/android-porting
>>
>
>

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

Reply via email to