have you tried replacing init with another binary? maybe compile bash or something and replace init with bash. Then you can use that to check the kernel is all working fine.
I suspect the problem might be todo with this error "Warning: unable to open an initial console" - won't init want a console to write its output to? On Apr 24, 2:26 pm, renegade <[EMAIL PROTECTED]> wrote: > I'm trying to run android on PXA270 evalboard. > Root partition is placed on jffs2 partition in nand flash. > I copied file system from android emulator. > It seems that init process crashed... > Could anyone tel me what could be possible reason... > Details about hardware you can read from log... > Kernel log looks like that: > > U-Boot 1.1.6 (Apr 2 2008 - 14:35:33) > > DRAM: 64 MB > Flash: 2 MB > NAND: 64 MiB > In: serial > Out: serial > Err: serial > Hit any key to stop autoboot: 0 > Detected: 2027008 blocks of 512 bytes (989MB) SD card. > Vendor: Man 11 OEM JC "064MB" Date 11/2003 > Product: 320 > Revision: 0.10 > reading linux.igz > > 1213060 bytes read > ## Booting image at a1000000 ... > Image Name: Linux Kernel Image > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 1212996 Bytes = 1.2 MB > Load Address: a0800000 > Entry Point: a0800000 > Verifying Checksum ... OK > OK > > Starting kernel ... > > Uncompressing > Linux.................................................................................. > done, booting the ke. > Linux version 2.6.19_RC15 ([EMAIL PROTECTED]) (gcc version 4.2.1 > (CodeSourcery Sourcery G++ Lite 2007q3-53)) #219 Tue Apr 22 15:08 > CPU: XScale-PXA270 [69054117] revision 7 (ARMv5TE), cr=0000397f > Machine: HITEC > Memory policy: ECC disabled, Data cache writeback > Run Mode clock: 208.00MHz (*16) > Turbo Mode clock: 416.00MHz (*2.0, active) > Memory clock: 104.00MHz (/2) > System bus clock: 208.00MHz > Standard (MSC0= 0x13387aa8) NAND mode > The additional board GPIO's are configured > CPU0: D VIVT undefined 5 cache > CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets > CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets > Built 1 zonelists. Total pages: 16256 > Kernel command line: console=ttyS0,115200 root=/dev/mtdblock2 > rootfstype=jffs2 rw > PID hash table entries: 256 (order: 8, 1024 bytes) > start_kernel(): bug: interrupts were enabled early > 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: 64MB = 64MB total > Memory: 62220KB available (2200K code, 243K data, 204K init) > Mount-cache hash table entries: 512 > CPU: Testing write buffer coherency: ok > NET: Registered protocol family 16 > 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: 1024 (order: 0, 4096 bytes) > TCP: Hash tables configured (established 2048 bind 1024) > TCP reno registered > squashfs: version 3.2-r2 (2007/01/15) Phillip Lougher > squashfs: LZMA suppport for slax.org by jro > JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc. > yaffs Apr 22 2008 13:56:09 Installing. > io scheduler noop registered > io scheduler anticipatory registered (default) > Hitec Backlight Driver Initialized. > External logo in flash not found @ 0x1c0000 > pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 22) is a FFUART > pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 21) is a BTUART > pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 20) is a STUART > PPP generic driver version 2.4.2 > PPP Deflate Compression module registered > PPP BSD Compression module registered > PPP MPPE Compression module registered > Found: AMD AM29LV160DB > THB PXA module: Found 1 x16 devices at 0x0 in 16-bit bank > number of JEDEC chips: 1 > cfi_cmdset_0002: Disabling erase-suspend-program due to code > brokenness. > Using static partition definition > Creating 2 MTD partitions on "THB PXA module": > 0x00000000-0x00040000 : "boot" > 0x00040000-0x001f0000 : "kernel" > NAND device: Manufacturer ID: 0xec, Chip ID: 0x76 (Samsung NAND 64MiB > 3,3V 8-bit) > Using static partition definition > Creating 4 MTD partitions on "NAND 64MiB 3,3V 8-bit": > 0x00000000-0x03a00000 : "rootfs (ro)" > Add SSFTL support > 0x03a00000-0x04000000 : "config (rw)" > 0x04000000-0x04000000 : "additional" > mtd: partition "additional" is out of reach -- disabled > mmcblk0: mmc0:0001 064MB 1013504KiB > mmcblk0: p1 p2 > 0x00000000-0x04000000 : "whole NAND" > pxa27x_udc: version 01-01-2006 > ether gadget: using random self ethernet address > ether gadget: using random host ethernet address > usb0: Ethernet Gadget, version: May Day 2005 > usb0: using pxa27x_udc, OUT ep2out-bulk IN ep1in-bulk STATUS ep3in- > intr > usb0: MAC 16:93:a2:06:c0:32 > usb0: HOST MAC 8a:1c:c8:5c:b3:c7 > usb0: RNDIS ready > wm97xx: Version 0.64 [EMAIL PROTECTED] > Advanced Linux Sound Architecture Driver Version 1.0.13 (Tue Nov 28 > 14:07:24 2006 UTC). > AC97 for PXA255 registered > pxa2xx-ac97: reset > wm97xx: Detected a WM9712 codec > input: wm97xx touchscreen as /class/input/input0 > wm97xx: setting pen detect pull-up to 16000 Ohms > wm97xx: setting adc sample delay to 42 u Secs. > WM97XX: Vbat = 4.1V > WM97XX: Vref = 1.9V > ALSA device list: > #0: pxa2xx-ac97 (Wolfson WM9711,WM9712) > TCP cubic registered > NET: Registered protocol family 1 > HSPM init started > HSPM driver is loaded and configured > VFS: Mounted root (jffs2 filesystem). > Freeing init memory: 204K > Warning: unable to open an initial console. > Unable to handle kernel NULL pointer dereference at virtual address > 00000000 > pgd = c3e64000 > [00000000] *pgd=a0033031, *pte=00000000, *ppte=00000000 > Internal error: Oops: 17 [#1] > Modules linked in: > CPU: 0 > pc : [<c01d5a28>] lr : [<00000000>] Not tainted > sp : c034bec0 ip : c034eb0c fp : c034bedc > r10: 00000000 r9 : c034a000 r8 : c003bf28 > r7 : c3e4ae00 r6 : c034eb0c r5 : c3e4ae00 r4 : 00000001 > r3 : 00000000 r2 : c034f8e0 r1 : 00000000 r0 : c034f8e0 > Flags: Nzcv IRQs off FIQs on Mode SVC_32 Segment user > Control: 397F > Table: A3E64000 DAC: 00000015 > Process init (pid: 1, stack limit = 0xc034a260) > Stack: (0xc034bec0 to 0xc034c000) > bec0: c0371060 beb96b00 c034bf00 c3e4ae00 c034befc c034bee0 c01d721c > c01d59dc > bee0: c0371060 beb96b00 0000000c c034bf00 c034bfa4 c034bf00 c01ba1dc > c01d71a4 > bf00: 00000010 00000001 ffffffff c00526c0 00000000 00010000 c034bf6c > c034bf28 > bf20: c01be054 c01bc4b8 c034bf4c c034bf38 c008bfd0 00000231 c034bf7c > c034bf78 > bf40: c034bf6c 00000001 00000004 00000021 beb96b0c c0371060 c034a000 > 00000000 > bf60: c034bfa4 c034bf70 c01ba048 c01bdf30 00000004 ffffffff 00000000 > 00000000 > bf80: 00000000 00000000 00000000 ffffffff beb96b00 0000011a 00000000 > c034bfa8 > bfa0: c003bd80 c01ba17c 00000000 ffffffff 00000000 beb96b00 0000000c > beb96b0c > bfc0: 00000000 ffffffff beb96b00 0000011a 0001ae94 00000001 0001e190 > 00000344 > bfe0: beb96af8 beb96af0 00009711 0000ad3c 00000010 00000000 ffffffff > ffffffff > Backtrace: > Function entered at [<c01d59d0>] from [<c01d721c>] > r7 = C3E4AE00 r6 = C034BF00 r5 = BEB96B00 r4 = C0371060 > Function entered at [<c01d7198>] from [<c01ba1dc>] > r7 = C034BF00 r6 = 0000000C r5 = BEB96B00 r4 = C0371060 > Function entered at [<c01ba170>] from [<c003bd80>] > r7 = 0000011A r6 = BEB96B00 r5 = FFFFFFFF r4 = 00000000 > Code: f5d1f000 e593312c e1530004 0a000005 (e5913000) > <0>Kernel panic - not syncing: Attempted to kill init! > > Kernel version is 2.6.19 adjusted to my hardware... > The kernel is patched with android4-linux-2.6.18at3.tar.bz2 patch > (found > onhttp://ruckuus.wordpress.com/2008/03/19/porting-android-to-older-kern...). > I'm not sure if the patch is correct...(or if I can use it with my > kernel, but patch was applied succesfully). > > Thanks for reply! > Regards. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Internals" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-internals?hl=en -~----------~----~----~----~------~----~------~--~---
