Hi,

Here is the log before crash.

Starting kernel ...

Uncompressing 
Linux...........................................................................................................................
done, booting the kernel.
Linux version 2.6.31.1 (new...@ubuntu910vm) (gcc version 4.4.0 (GCC) )
#29 Tue Dec 15 14:54:04 PST 2009
CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE), cr=0000397f
CPU: VIVT data cache, VIVT instruction cache
Machine: RTS G5
Got g5 info
102292 C 1 3
00:1A:EA:10:22:92
Memory policy: ECC disabled, Data cache writeback
Memory clock: 99.53MHz (*27)
Run Mode clock: 199.07MHz (*2)
Turbo Mode clock: 199.07MHz (*1.0, inactive)
Msc0: 97787ff8 (f6000008)
Msc1: 23c7f8c (f600000c)
Msc2: 7ff07ff0 (f6000010)
mdcnfg: 1cb, mdrefr: 1802f
cccr: 141
CPLD Version: a02
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
Kernel command line: root=/dev/ram0 rootfstype=ext2  console=ttyS1,115200
PID hash table entries: 512 (order: 9, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 64MB 64MB = 128MB total
Memory: 103580KB available (3424K code, 397K data, 108K init, 0K highmem)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:208
Console: colour dummy device 80x30
Calibrating delay loop... 397.31 BogoMIPS (lpj=1986560)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
RTS Init: Dec 14 2009 21:48:29 CPLD Version: 0a02
set_uart_alt_func:irq = 21 alt_func = 1
set_uart_alt_func:irq = 20 alt_func = 1
pwr_switch_hold_count = 30
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
cfg80211: Calling CRDA to update world regulatory domain
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
NET: Registered protocol family 1
Trying to unpack rootfs image as initramfs...
rootfs image is not initramfs (no cpio magic); looks like an initrd
Freeing initrd memory: 22128K
rts-kbd: Traker 5 keyboard
input: rts-kbd as /class/input/input0
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 245
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
rts_backlight_power(): power: 1
Console: switching to colour frame buffer device 80x15
ipmi message handler version 39.2
ipmi device interface
IPMI Watchdog: driver initialized
pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 22) is a FFUART
pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 21) is a BTUART
console [ttyS1] enabled
pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 20) is a STUART
pxa2xx-uart.3: ttyS3 at MMIO 0x41600000 (irq = 7) is a HWUART
brd: module loaded
loop: module loaded
nbd: registered device at major 43
SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256) (6 bit
encapsulation enabled).
CSLIP: code copyright 1989 Regents of the University of California.
SLIP linefill/keepalive option.
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre <n...@cam.org>
eth0: SMC91C11xFD (rev 1) at c88ba300 IRQ 90 [nowait]
eth0: Ethernet addr: 00:1a:ea:10:22:92
physmap platform flash device: 00100000 at 00000000
Found: AMD AM29LV800BB
physmap-flash.0: 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.
RedBoot partition parsing not available
RTS xD/NAND driver: 21:53:13 Dec 14 2009
        Addr: 0x06000000
        Adding NAND chip
NAND device: Manufacturer ID: 0x98, Chip ID: 0x75 (Toshiba NAND 32MiB
3,3V 8-bit)
Scanning device for bad blocks
Bad eraseblock 0 at 0x000000000000
Using static partition definition
Creating 3 MTD partitions on "NAND 32MiB 3,3V 8-bit":
0x000000000000-0x000000200000 : "kernel image"
0x000000200000-0x000002000000 : "root file system"
0x000000000000-0x000002000000 : "entire nand device"
        Adding xD card
No NAND device found!!!
reset disable
driver isp1362-hcd, 2005-04-04
isp1362-hcd isp1362-hcd.0: ISP1362 Host Controller
isp1362-hcd isp1362-hcd.0: new USB bus registered, assigned bus number 1
isp1362_hc_reset:
isp1362-hcd isp1362-hcd.0: irq 87, io mem 0x08000000
isp1362_hc_start:
isp1362-hcd isp1362-hcd.0: ISP1362 Memory usage:
isp1362-hcd isp1362-hcd.0:   ISTL:    2 *  256:      512 @ $0000:$0100
isp1362-hcd isp1362-hcd.0:   INTL:   16 * ( 64+8):  1152 @ $0200
isp1362-hcd isp1362-hcd.0:   ATL :   32 * ( 64+8):  2304 @ $0680
isp1362-hcd isp1362-hcd.0:   USED/FREE:   3968       128
usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: ISP1362 Host Controller
usb usb1: Manufacturer: Linux 2.6.31.1 isp1362-hcd
usb usb1: SerialNumber: isp1362-hcd.0
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ISP1362 Host Controller, irq 87
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
I2C: i2c-0: PXA I2C adapter
Advanced Linux Sound Architecture Driver Version 1.0.20.
ALSA device list:
  #0: pxa2xx-ac97 (Philips UCB1400)
IPv4 over IPv4 tunneling driver
GRE over IPv4 tunneling driver
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
NET: Registered protocol family 15
lib80211: common routines for IEEE802.11 drivers
XScale DSP coprocessor detected.
RAMDISK: gzip image found at block 0
VFS: Mounted root (ext2 filesystem) on device 1:0.
Freeing init memory: 108K
Kernel panic - not syncing: Attempted to kill init!
[<c00294e0>] (unwind_backtrace+0x0/0xd8) from [<c02a0524>] (panic+0x40/0x108)
[<c02a0524>] (panic+0x40/0x108) from [<c0041318>] (do_exit+0x68/0x5dc)
[<c0041318>] (do_exit+0x68/0x5dc) from [<c0041918>] (do_group_exit+0x8c/0xc0)
[<c0041918>] (do_group_exit+0x8c/0xc0) from [<c004a48c>]
(get_signal_to_deliver+0x2d8/0x310)
[<c004a48c>] (get_signal_to_deliver+0x2d8/0x310) from [<c0026490>]
(do_signal+0x54/0x4ec)
[<c0026490>] (do_signal+0x54/0x4ec) from [<c0023e0c>] (work_pending+0x1c/0x20)


On Wed, Dec 16, 2009 at 9:32 AM, linux newbie <linux.newbi...@gmail.com> wrote:
> Hi,
>
> I download the 2.6.31 kernel from kernel.org and updated it with our
> board specific patch. Then I enabled Android specific stuff using make
> menuconfig ->  device drivers->staging drivers->Andriod.
>
> I havent updated the kernel with yaffs2 patch, as I am downloading the
> andriod rootfs into SDRAM (ext2) and commenting out mounting yaffs2 in
> init.rc file.
>
> Apart from above kernel modifications do I need to make any other
> changes in kernel?
>
> Thanks
>
> On Wed, Dec 16, 2009 at 7:05 AM, Novin S. <novin...@gmail.com> wrote:
>> The problem is that the kernel you are using on your device is not
>> suited for the version of the root fs or it is not properly patched
>> with android specific diffs....
>>
>> On Dec 15, 3:24 pm, "Dennis.Yxun" <dennis.y...@gmail.com> wrote:
>>> do u use ramdisk or others?
>>> make sure kernel can find 'init' program
>>>
>>> On Tue, Dec 15, 2009 at 4:34 PM, linux newbie 
>>> <linux.newbi...@gmail.com>wrote:
>>>
>>>
>>>
>>> > Hi,
>>>
>>> > Thanks for your reply.
>>>
>>> > As the messages are printing on the lcd, I couldn't able to get the
>>> > logs. Anyway I shall try tomorrow.
>>> > After Freeing Init memory, I am getting this Kernel Panic (seems
>>> > console is opened properly)
>>>
>>> > Please let me know, whether the procedure I am using to bring up
>>> > Android is correct or not?
>>>
>>> > Thanks
>>>
>>> > On Tue, Dec 15, 2009 at 6:29 PM, jack <yichang.zhu...@gmail.com> wrote:
>>> > > Hello,
>>>
>>> > > According to my porting experience, there will be many causes
>>> > > resulting in kernel panic.
>>> > > Pasting more logs before the line kernel panic will help for others to
>>> > > figure out your problem. Thanks.
>>>
>>> > > Regards
>>> > > Jack
>>>
>>> > > On 12月15日, 上午11時58分, linux newbie <linux.newbi...@gmail.com> wrote:
>>> > >> Hi,
>>>
>>> > >> Our embedded platform has pxa255. We downloaded linux_2_6_31_1,
>>> > >> compiled with EABI (downloaded the toolchain from Codesourcery),
>>> > >> modified the kernel to add our hardware based support. We also
>>> > >> compiled the user space applications with latest tool chain and able
>>> > >> to boot the system perfectly.
>>>
>>> > >> I downloaded the Android SDK, extracted the root file system.
>>>
>>> > >> As our system has 128MB of sdram, we extracted the contents of system
>>> > >> and userdata image and put it in root fs system folder. Also I
>>> > >> commented out mount yaffs2 section in init.rc file.
>>>
>>> > >> I copied the /dev contents to android root fs and etc -> /system/etc.
>>>
>>> > >> While booting it shows,
>>>
>>> > >> kernel panic - not syncing: attempted to kill init.
>>>
>>> > >> can anyone help me out in to fix this issue.
>>>
>>> > >> Thanks
>>>
>>> > > --
>>> > > unsubscribe: 
>>> > > android-porting+unsubscr...@googlegroups.com<android-porting%2Bunsubscribe@
>>> > >  googlegroups.com>
>>> > > website:http://groups.google.com/group/android-porting
>>>
>>> > --
>>> > unsubscribe: 
>>> > android-porting+unsubscr...@googlegroups.com<android-porting%2Bunsubscribe@
>>> >  googlegroups.com>
>>> > website:http://groups.google.com/group/android-porting
>>
>> --
>> unsubscribe: android-porting+unsubscr...@googlegroups.com
>> website: http://groups.google.com/group/android-porting
>

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

Reply via email to