Find the answer to your Linux question:
Results 1 to 4 of 4
I'm using marvell littleton board with pxa310 processor, and linux kernel 2.6.29 with android patch downloaded from marvell website. In make menuconfig, I enabled the "Kernel hacking -- Kernel low ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Nov 2010
    Posts
    4

    Unhappy Failed to start kernel 2.6.29 with android patch


    I'm using marvell littleton board with pxa310 processor, and linux kernel 2.6.29 with android patch downloaded from marvell website. In make menuconfig, I enabled the "Kernel hacking -- Kernel low level debuging fuctions" to see the error message during booting. After burning zImage file into the board, the kernel booted and stuck after printing the following things:

    ------------------------------------------------------------------------
    Code:
    Uncompressing Linux.............................................................................................
    ............................................................................... done, booting the kernel.
    <5>Linux version 2.6.29 (rootHBM) (gcc version 4.4.3 (ctng-1.6.1) ) #1 Thu Nov 18 10:04:14 CST 2010
    CPU: XScale-V3 based processor [69056892] revision 2 (ARMv5TE), cr=0000397f
    CPU: VIVT data cache, VIVT instruction cache
    Machine: Marvell Form Factor Development Platform (aka Littleton)
    Memory policy: ECC disabled, Data cache writeback
    <7>On node 0 totalpages: 32768
    <7>free_area_init_node: node 0, pgdat c051c16c, node_mem_map c0626000
    <7> Normal zone: 256 pages used for memmap
    <7> Normal zone: 0 pages reserved
    <7> Normal zone: 32512 pages, LIFO batch:7
    <7>On node 1 totalpages: 0
    <7>free_area_init_node: node 1, pgdat c051c7ec, node_mem_map 00000000
    <7>On node 2 totalpages: 0
    <7>free_area_init_node: node 2, pgdat c051ce6c, node_mem_map 00000000
    <7>On node 3 totalpages: 0
    <7>free_area_init_node: node 3, pgdat c051d4ec, node_mem_map 00000000
    <6>RO Mode clock: 60.00MHz (inactive)
    <6>Run Mode clock: 208.00MHz (*16)
    <6>Turbo Mode clock: 208.00MHz (*1, inactive)
    <6>HSIO bus clock: 104.00MHz
    Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
    <5>Kernel command line: console=ttyS2,115200 mem=128M ip=192.168.1.101:192.168.1.100::255.255.255.0::eth0n com
    m_v75 uart_dma android
    PID hash table entries: 512 (order: 9, 2048 bytes)
    Console: colour dummy device 80x30
    <3>ram_console: buffer (null), invalid size 0, datasize 4294967284
    <6>Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    <6>Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    <6>Memory: 128MB = 128MB total
    <5>Memory: 123504KB available (5036K code, 1075K data, 144K init)
    <6>Calibrating delay loop... 206.37 BogoMIPS (lpj=804864)
    Mount-cache hash table entries: 512
    <6>CPU: Testing write buffer coherency: ok
    <6>net_namespace: 500 bytes
    <6>NET: Registered protocol family 16
    bio: create slab <bio-0> at 0
    <5>SCSI subsystem initialized
    <6>usbcore: registered new interface driver usbfs
    <6>usbcore: registered new interface driver hub
    <6>usbcore: registered new device driver usb
    <6>I2C: i2c-0: PXA I2C adapter
    <6>I2C: i2c-1: PXA I2C adapter
    <4>micco unavailable!
    <6>NET: Registered protocol family 23
    <6>Bluetooth: Core ver 2.15
    <6>NET: Registered protocol family 31
    <6>Bluetooth: HCI device and connection manager initialized
    <6>Bluetooth: HCI socket layer initialized
    <6>NET: Registered protocol family 2
    <6>Switched to NOHz mode on CPU #0
    <6>IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    <6>TCP established hash table entries: 4096 (order: 3, 32768 bytes)
    <6>TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
    <6>TCP: Hash tables configured (established 4096 bind 4096)
    <6>TCP reno registered
    <6>NET: Registered protocol family 1
    initializing op table for PXA310
    <4>No pmic_ops registered!
    <4>No pmic_ops registered!
    <6>Register device ipmc successful.
    <6>Initialize IPM.
    <6>Intel(c) Memory Management - SRAM Allocation
    <6>Intel(c) Memory Management is now Enabled
    <4>NetWinder Floating Point Emulator V0.97 (double precision)
    <6>ashmem: initialized
    <6>Installing knfsd (copyright (C) 1996 okirmonad.swb.de).
    <6>JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
    yaffs Nov 18 2010 09:55:59 Installing. 
    <6>msgmni has been set to 241
    <6>alg: No test for stdrng (krng)
    <6>io scheduler noop registered
    <6>io scheduler anticipatory registered
    <6>io scheduler deadline registered
    <6>io scheduler cfq registered (default)
    i2c: error: exhausted retries
    i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0
    i2c: ICR: 000007e0 ISR: 00000002
    i2c: log: [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [0
    0000006:00000000] [00000006:00000000] [00000006:00000000] [00000007:00000000] [00000447:000007e0] 
    <3>max7320_read: failed to read
    <6>failed to detect max7320!
    i2c: error: exhausted retries
    i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0
    i2c: ICR: 000007e0 ISR: 00000002
    i2c: log: [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [0
    0000006:00000000] [00000006:00000000] [00000006:00000000] [00000007:00000000] [00000447:000007e0] 
    <3>max7321_read: failed to read
    <6>failed to detect max7321 (addr:0x60)!
    <4>max7321: probe of 0-0060 failed with error -952112124
    i2c: error: exhausted retries
    i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0
    i2c: ICR: 000007e0 ISR: 00000002
    i2c: log: [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [0
    0000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000007:000007e0] [00000442:0000
    07e0] 
    <3>max7321_read: failed to read
    <6>failed to detect max7321 (addr:0x61)!
    <4>max7321: probe of 0-0061 failed with error -952112636
    i2c: error: exhausted retries
    i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0
    i2c: ICR: 000007e0 ISR: 00000002
    i2c: log: [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [0
    0000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000447:000007e0] 
    <3>max7321_read: failed to read
    <6>failed to detect max7321 (addr:0x62)!
    <4>max7321: probe of 0-0062 failed with error -952113148
    i2c: error: exhausted retries
    i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0
    i2c: ICR: 000007e0 ISR: 00000002
    i2c: log: [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [0
    0000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000447:000007e0] 
    <3>max7321_read: failed to read
    <6>failed to detect max7321 (addr:0x63)!
    <4>max7321: probe of 0-0063 failed with error -952113660
    i2c: error: exhausted retries
    i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0
    i2c: ICR: 000007e0 ISR: 00000002
    i2c: log: [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [0
    0000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000447:000007e0] 
    <3>max7321_read: failed to read
    <6>failed to detect max7321 (addr:0x64)!
    <4>max7321: probe of 0-0064 failed with error -952114172
    i2c: error: exhausted retries
    i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0
    i2c: ICR: 000007e0 ISR: 00000002
    i2c: log: [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [0
    0000006:00000000] [00000006:00000000] [00000006:00000000] [00000007:00000000] [00000447:000007e0] 
    <3>max7321_read: failed to read
    <6>failed to detect max7321 (addr:0x66)!
    <4>max7321: probe of 0-0066 failed with error -952114684
    i2c: error: exhausted retries
    i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0
    i2c: ICR: 000007e0 ISR: 00000002
    i2c: log: [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [0
    0000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000447:000007e0] 
    <3>max7321_read: failed to read
    <6>failed to detect max7321 (addr:0x6c)!
    <4>max7321: probe of 0-006c failed with error -952115196
    i2c: error: exhausted retries
    i2c: msg_num: 0 msg_idx: -2000 msg_ptr: 0
    i2c: ICR: 000007e0 ISR: 00000002
    i2c: log: [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [0
    0000006:00000000] [00000006:00000000] [00000006:00000000] [00000006:00000000] [00000007:000007e0] [00000442:0000
    07e0] 
    <3>max7321_read: failed to read
    <6>failed to detect max7321 (addr:0x6d)!
    <4>max7321: probe of 0-006d failed with error -952136188
    <4>pxa2xx-fb pxa2xx-fb: machine LCCR3 setting contains illegal bits: 00300000

    -----------------------------------------------------------------------

    Anyone can help? Thanks.
    Last edited by MikeTbob; 11-27-2010 at 12:27 PM. Reason: Added code tags

  2. #2
    Administrator MikeTbob's Avatar
    Join Date
    Apr 2006
    Location
    Texas
    Posts
    7,864
    I can't really help, but I can however point my finger at links like you would not believe, look there's one!
    Linux-Kernel Archive: Re: [PATCH 2.6.29.2] PXA I2C: Define log level for i2c PXA error report
    Seems related to me, what do you think?
    I do not respond to private messages asking for Linux help, Please keep it on the forums only.
    All new users please read this.** Forum FAQS. ** Adopt an unanswered post.

    I'd rather be lost at the lake than found at home.

  3. #3
    Just Joined!
    Join Date
    Nov 2010
    Posts
    4
    It seems not because of I2c issuers, but thanks any way.

  4. #4
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,380
    Have you contacted the board manufacturer (Marvell)? They are the ones who are most likely to help you. If those of us here have not had experience with this particular board, then you are probably SOL. I have had experience with some ARM boards from Technologic Systems (PC-104 boards) and have not had such problems.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •