1. This forum section is a read-only archive which contains old newsgroup posts. If you wish to post a query, please do so in one of our main forum sections (here). This way you will get a faster, better response from the members on Motherboard Point.

linux dies on custom at91rm9200 board

Discussion in 'Embedded' started by amstewa2, Sep 24, 2006.

  1. amstewa2

    amstewa2 Guest

    Hello all Im trying to get linux up and running on my system.
    I have 16MB of SDRAM at 0x20000000 and 2MB of dataflash.
    I've started with the at91rm9200dk files in the kernel as my start
    point, and I can get it to boot if and only if I disable my dCache.
    Im imaging there is a setting somewhere Im over looking that is
    still trying to map the caches with 32MB of ram (which the dk has)
    but I have only 16MB.... anyways, below is the full log from power
    till death. Any suggestions on something to try?
    Any Help is MUCH apreciated... ive been at this for weeks
    and I've almost given up.


    xPress any key to enter bootloader

    JAM CAM LOADER VER 1.01 Aug 19 2006 12:34:50
    *----------------------------------------*
    DataFlash:AT45DB161
    Nb pages: 004096
    Page Size: 000528
    Size=02162688 bytes
    Logical address: 0xC0000000
    *----------------------------------------*
    1: Download Dataflash [addr]
    2: Read Dataflash [addr]
    3: Start U-BOOT
    4: Clear bootloader section in Dataflash
    5: Run Memory Test
    *----------------------------------------*
    Enter: 3
    Load U-BOOT from dataflash[c0008000] to SDRAM[20f00000]
    Set PLLA to 180Mhz and Master clock to 60Mhz and start U-BOOT

    U-Boot 1.1.4 (Aug 31 2006 - 21:11:40)

    U-Boot code: 20F00000 -> 20F17360 BSS: -> 20F34204
    RAM Configuration:
    Bank #0: 20000000 16 MB
    Atmel: Flash: 0 kB
    DataFlash:AT45DB161
    Nb pages: 4096
    Page Size: 528
    Size= 2162688 bytes
    Logical address: 0xC0000000
    Area 0: C0000000 to C0007FFF (RO)
    Area 1: C0008000 to C001FFFF (RO)
    Area 2: C0020000 to C0027FFF
    Area 3: C0028000 to C020FFFF
    In: serial
    Out: serial
    Err: serial
    Hit any key to stop autoboot: 0
    U-Boot> tftpboot 20800000 test
    TFTP from server 192.168.0.55; our IP address is 192.168.0.56
    Filename 'test'.
    Load address: 0x20800000
    Loading
    #################################################################

    #################################################################
    #########################################################
    done
    Bytes transferred = 956208 (e9730 hex)
    U-Boot> bootm 20800000 c0123000
    ## Booting image at 20800000 ...
    Image Name: Linux-2.6.17
    Image Type: ARM Linux Kernel Image (uncompressed)
    Data Size: 956144 Bytes = 933.7 kB
    Load Address: 20008000
    Entry Point: 20008000
    Verifying Checksum ... OK
    OK
    ## Loading Ramdisk Image at c0123000 ...
    Image Name: Jam Cam Root
    Image Type: ARM Linux RAMDisk Image (uncompressed)
    Data Size: 734282 Bytes = 717.1 kB
    Load Address: 00000000
    Entry Point: 00000000
    Verifying Checksum ... OK

    Starting kernel ...

    Uncompressin
    Linux.............................................................. done
    booting the kernel.

    41129200:00000106:C000507A
    2010AB28-202E0028>20008000
    202E0028
    20008000: E321F0D3 EE109F10 EB0000B1 E1B0A005 0A00005A EB0000C6 E1B0800
    0A000068
    20008020: EB000014 E59FD0EC E28FE000 E28AF00C E3800002 E3A0501F EE035F1
    EE024F10
    20008040: EA000006 00000000 00000000 00000000 00000000 00000000 0000000
    00000000
    20008060: E1A00000 EE010F10 EE103F10 E1A03003 E1A03003 E1A0F00D E59F409
    E1A00004
    20008080: E3A03000 E2806901 E4803004 E4803004 E4803004 E4803004 E130000
    1AFFFFF9
    200080A0: E59A7008 E1A06A2F E1873A06 E7843106 E2840A03 E5A03000 E283360
    E5A03004
    200080C0: E2833601 E5A03004 E2833601 E5803004 E2840A03 E3876202 E580600
    E3C7700C
    200080E0: E5983008 E0840003 E2633901 E3530B02 83A03B02 E0806003 E598300
    E1833007
    Linux version 2.6.17 ([email protected]) (gcc version 3.4.5) #4 Thu Sep 2
    13:03:29 EDT 2006
    CPU: ARM920Tid(wb) [41129200] revision 0 (ARMv4T)
    Machine: Jam Cam --> rm9200dk based
    Memory policy: ECC disabled, Data cache writeback
    Clocks: CPU 179 MHz, master 59 MHz, main 18.432 MHz
    CPU0: D VIVT write-back cache
    CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
    CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
    Built 1 zonelists
    Kernel command line: mem=16M console=ttyS0,115200 root=/dev/ram0 r
    keepinitrd
    AT91: 96 gpio irqs in 3 banks
    PID hash table entries: 128 (order: 7, 512 bytes)
    Console: colour dummy device 80x30
    Dentry cache hash table entries: 2048 (order: 1, 8192 bytes)
    Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
    Memory: 16MB = 16MB total
    Memory: 13500KB available (1540K code, 347K data, 88K init)
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    checking if image is initramfs...it <6>NET: Registered protocol family 16
    slab: Internal list corruption detected in cache 'size-32'(84), slabp
    c023a000(-2). Hexdump:

    000: 84 f9 21 c0 84 f9 21 c0 6c 01 00 00 6c a1 23 c0
    010: fe ff ff ff 36 00 00 00 00 00 94 e5 fd ff ff ff
    020: fd ff ff ff fd ff ff ff fd ff ff ff fd ff ff ff
    030: fd ff ff ff fd ff ff ff fd ff ff ff fe ff ff ff
    040: fd ff ff ff fd ff ff ff fd ff ff ff fd ff ff ff
    050: 0e 00 00 00 0f 00 00 00 37 00 00 00 fd ff ff ff
    060: fd ff ff ff fd ff ff ff fe ff ff ff fd ff ff ff
    070: fd ff ff ff fd ff ff ff fd ff ff ff fd ff ff ff
    080: fd ff ff ff fd ff ff ff fd ff ff ff fd ff ff ff
    090: fd ff ff ff fd ff ff ff fd ff ff ff fd ff ff ff
    0a0: fd ff ff ff fd ff ff ff fd ff ff ff fe ff ff ff
    0b0: fd ff ff ff fd ff ff ff fe ff ff ff 0d 00 00 00
    0c0: fd ff ff ff fd ff ff ff fd ff ff ff fd ff ff ff
    0d0: fd ff ff ff fd ff ff ff fd ff ff ff 40 00 00 00
    0e0: 30 00 00 00 31 00 00 00 32 00 00 00 33 00 00 00
    0f0: 34 00 00 00 35 00 00 00 36 00 00 00 fd ff ff ff
    100: fd ff ff ff fd ff ff ff fd ff ff ff fd ff ff ff
    110: fd ff ff ff fd ff ff ff fe ff ff ff 41 00 00 00
    120: 42 00 00 00 43 00 00 00 44 00 00 00 45 00 00 00
    130: 46 00 00 00 47 00 00 00 48 00 00 00 49 00 00 00
    140: 4a 00 00 00 4b 00 00 00 4c 00 00 00 4d 00 00 00
    150: 4e 00 00 00 4f 00 00 00 50 00 00 00 51 00 00 00
    160: 52 00 00 00 53 00 00 00 ff ff ff ff
    kernel BUG at mm/slab.c:2700!
    Unable to handle kernel NULL pointer dereference at virtual address
    00000000
    pgd = c0004000
    [00000000] *pgd=00000000
    Internal error: Oops: 805 [#1]
    Modules linked in:
    CPU: 0
    PC is at __bug+0x40/0x54
    LR is at 0x1
    pc : [<c0023a08>] lr : [<00000001>] Not tainted
    sp : c022be3c ip : 60000093 fp : c022be4c
    r10: c021f984 r9 : 0000000a r8 : c08b6930
    r7 : c01f7080 r6 : c023a000 r5 : c01f7080 r4 : 00000000
    r3 : 00000000 r2 : 00000000 r1 : 00000a33 r0 : 00000001
    Flags: nZCv IRQs off FIQs on Mode SVC_32 Segment kernel
    Control: C000717F Table: 20004000 DAC: 00000017
    Process swapper (pid: 1, stack limit = 0xc022a198)
    Stack: (0xc022be3c to 0xc022c000)
    be20:
    0000016c
    be40: c022be6c c022be50 c0066c94 c00239d8 fffffffe c023a0e8 c023a16c
    c023a000
    be60: c022beb0 c022be70 c006710c c0066bc4 0000002c c022be80 c023a01c
    00000036
    be80: c08b6944 000000d0 c01f7080 000000d0 60000013 c00a4400 c0220a94
    00000000
    bea0: c01ae760 c022bed0 c022beb4 c0068224 c0066f28 c023a8a8 c0184cb4
    c02d56f4
    bec0: fffffff4 c022befc c022bed4 c00a4400 c0068150 00000020 c01a4804
    c01a4804
    bee0: c01a479c c01ae74c 00000000 00000000 c022bf24 c022bf00 c00e23a0
    c00a4374
    bf00: c01a479c c01a4804 c01ae894 00000000 00000000 c001c8ec c022bf44
    c022bf28
    bf20: c00e12c8 c00e22c0 c01a479c c01a4794 c022a000 00000000 c022bf58
    c022bf48
    bf40: c00e135c c00e122c c01a4794 c022bf7c c022bf5c c00e4748 c00e1350
    c022bf68
    bf60: c01a4794 c001c784 c022a000 c001ce14 c022bf90 c022bf80 c00e47dc
    c00e4674
    bf80: 00000000 c022bfa0 c022bf94 c001152c c00e47cc c022bff4 c022bfa4
    c001e0f8
    bfa0: c0011520 00000001 c001ed84 c002f764 00000000 00000000 c001e058
    c0035948
    bfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000
    00000000
    bfe0: 00000000 00000000 00000000 c022bff8 c0035948 c001e068 e5850004
    e3a0100a
    Backtrace:
    [<c00239c8>] (__bug+0x0/0x54) from [<c0066c94>] (check_slabp+0xe0/0xf8)
    r4 = 0000016C
    [<c0066bb4>] (check_slabp+0x0/0xf8) from [<c006710c>]
    (cache_alloc_refill+0x1f4/0x6b8)
    r6 = C023A000 r5 = C023A16C r4 = C023A0E8
    [<c0066f18>] (cache_alloc_refill+0x0/0x6b8) from [<c0068224>]
    (__kmalloc+0xe4/0x110)
    [<c0068140>] (__kmalloc+0x0/0x110) from [<c00a4400>]
    (sysfs_create_link+0x9c/0x11c)
    r7 = FFFFFFF4 r6 = C02D56F4 r5 = C0184CB4 r4 = C023A8A8
    [<c00a4364>] (sysfs_create_link+0x0/0x11c) from [<c00e23a0>]
    (bus_add_device+0xf0/0xfc)
    [<c00e22b0>] (bus_add_device+0x0/0xfc) from [<c00e12c8>]
    (device_add+0xac/0x124)
    [<c00e121c>] (device_add+0x0/0x124) from [<c00e135c>]
    (device_register+0x1c/0x20)
    r7 = 00000000 r6 = C022A000 r5 = C01A4794 r4 = C01A479C
    [<c00e1340>] (device_register+0x0/0x20) from [<c00e4748>]
    (platform_device_add+0xe4/0x158)
    r4 = C01A4794
    [<c00e4664>] (platform_device_add+0x0/0x158) from [<c00e47dc>]
    (platform_device_register+0x20/0x24)
    r7 = C001CE14 r6 = C022A000 r5 = C001C784 r4 = C01A4794
    [<c00e47bc>] (platform_device_register+0x0/0x24) from [<c001152c>]
    (at91_add_standard_devices+0x1c/0x2c)
    r4 = 00000000
    [<c0011510>] (at91_add_standard_devices+0x0/0x2c) from [<c001e0f8>]
    (init+0xa0/0x268)
    [<c001e058>] (init+0x0/0x268) from [<c0035948>] (do_exit+0x0/0x7ac)
    Code: 1b0041f4 e59f0014 eb0041f2 e3a03000 (e5833000)
    <0>Kernel panic - not syncing: Attempted to kill init!
     
    amstewa2, Sep 24, 2006
    #1
    1. Advertisements

  2. Why dont you copy our ramdisk to SDRAM before booting?
    Try downloading both the kernel and the ramdisk to SDRAM and then try boot
    and see what happens.

    I would be good to see the bootcmd and bootargs variable.
    /ulf
     
    Ulf Samuelsson, Sep 24, 2006
    #2
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.