This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux image oops release 4AJ.2.4

Hi all,
I have a self made OMAP4430 based board  which runs Android based on the release 4AJ2.2.. The device has no eMMC and is based on the Blaze configuration.

Unfortunately I can't get release 4AJ.2.4. running. The u-boot and the x-loader of this release are working. I can boot the android system form 4AJ.2.2.

Using the kernel of 4AJ.2.4 results in an 'segmentation oops'.
The u-boot loads the kernel and starts it. Shortly after this the x-loader is restarted. There is no output with the standard kernel config. Setting the kernel debug level to 7 I get the output shown below.

Any ideas?

Best regards,

Roman

-->

Hit any key to stop autoboot:  3  2  1  0  
kernel   @ 80308000 (4900296)
ramdisk  @ 81300000 (185346)
I2C read: I/O error
 
Starting kernel ...
 
Uncompressing Linux... done, booting the kernel.
<6>Booting Linux on physical CPU 0
<6>Initializing cgroup subsys cpu
<5>Linux version 3.4.34-01470-g43e7cb2 (jor@pc1280l) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #3 SMP PREEMPT Fri Mar 22 17:41:37 CET 2013
CPU: ARMv7 Processor [411fc093] revision 3 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: OMAP4 Blaze board
<6>Initialized persistent memory from a0000000-a01fffff
<6>cma: CMA: reserved 112 MiB at 99000000
<3>Cannot detect omap type!
<6>Reserving 20971520 bytes SDRAM for VRAM
<6>cma: CMA: reserved 16 MiB at 96800000
Memory policy: ECC disabled, Data cache writealloc
<6>OMAP4: Map 0x97a00000 to 0xfe600000 for dram barrier
<7>On node 0 totalpages: 200704
<7>free_area_init_node: node 0, pgdat c09edb80, node_mem_map c132e000
<7>  Normal zone: 1024 pages used for memmap
<7>  Normal zone: 0 pages reserved
<7>  Normal zone: 124416 pages, LIFO batch:31
<7>  HighMem zone: 1024 pages used for memmap
<7>  HighMem zone: 74240 pages, LIFO batch:15
<6>OMAP4430 ES2.3
<6>PERCPU: Embedded 9 pages/cpu @c1b35000 s13056 r8192 d15616 u36864
<7>pcpu-alloc: s13056 r8192 d15616 u36864 alloc=9*4096<c>
<7>pcpu-alloc: <c>[0] <c>0 <c>[0] <c>1 <c>
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 198656
<5>Kernel command line: console=ttyO2,115200n8 androidboot.console=ttyO2 omap_wdt.timer_margin=30 vmalloc=496M omapfb.fb_opt=-1,-1,-1,1,1280,720 androidboot.serialno=09112E7C0300C00C androidboot.bootloader=U-Boot_1.1.4-gc0da83d0
<6>PID hash table entries: 2048 (order: 1, 8192 bytes)
<6>Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
<6>Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>Memory: 378MB 114MB 289MB 3MB = 784MB total
<5>Memory: 648868k/648868k available, 399708k reserved, 299008K highmem
<5>Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xe0800000 - 0xff000000   ( 488 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc08f3000   (9132 kB)
      .init : 0xc08f3000 - 0xc094b300   ( 353 kB)
      .data : 0xc094c000 - 0xc09f08d0   ( 659 kB)
       .bss : 0xc09f08f4 - 0xc0b6a0f0   (1510 kB)
 <6>Preemptible hierarchical RCU implementation.
<6>NR_IRQS:626
<1>Unable to handle kernel paging request at virtual address 0000250c
<1>pgd = c0004000
<1>[0000250c] *pgd=00000000
<0>Internal error: Oops: 805 [#1] PREEMPT SMP ARM
<d>Modules linked in:
CPU: 0    Not tainted  (3.4.34-01470-g43e7cb2 #3)
PC is at omap_wakeupgen_init+0x220/0x2dc
LR is at omap_wakeupgen_init+0x1e4/0x2dc
pc : [<c0900a30>]    lr : [<c09009f4>]    psr: 600001d3
sp : c094df70  ip : c094df70  fp : c094df84
r10: 00000000  r9 : 411fc093  r8 : c1b32280
r7 : c0932e54  r6 : c09f0900  r5 : c09f126c  r4 : 00000004
r3 : 0000250c  r2 : 00002510  r1 : ffffffff  r0 : 00000000
Flags: nZCv  IRQs off  FIQs off  Mode SVC_32  ISA ARM  Segment kernel
Control: 10c5387d  Table: 8000404a  DAC: 00000015

....

[<c08f6340>] (init_IRQ+0x0/0x24) from [<c08f3728>] (start_kernel+0x1a4/0x304)
[<c08f3584>] (start_kernel+0x0/0x304) from [<80008044>] (0x80008044)
<0>Code: 1afffffb e302350c e3022510 e3e01000 (e7801003)
<4>---[ end trace 1b75b31a2719ed1c ]---
<0>Kernel panic - not syncing: Attempted to kill the idle task!
<0>Rebooting in 5 seconds..
<0>Restarting Linux version 3.4.34-01470-g43e7cb2 (jor@pc1280l) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #3 SMP PREEMPT Fri Mar 22 17:41:37 CET 2013
 
 
Texas Instruments Inc X-Loader 1.41.0-gc6116ffc (Mar 22 2013 - 11:14:18)
Starting OS Bootloader from MMC/SD1 ...
 
U-Boot 1.1.4-gc0da83d0 (Mar 22 2013 - 11:14:38)
<--

  • Roman,

    I assume you are using an OMAP GP device?  It seems this is a known issue with the 4AJ.2.3+ releases, as only HS is supported.

    Regards,
    Gina 

  • Hi Roman.

    I'm only on AJ2.3, but I believe the attached patch will fix your panic.

    Regards,

        Steve

  • Hi Steve,

    many thanks I will try your patch.

    Because of the answer from Gina I have a question about HS, GP and release AJ2.4.

    I as far as I know the only difference in the release builds for HS and GP devices are the separate signing step, correct? So I can still use my GP based device for release 4.2 using my self made images?

    Best regards and many thanks,

    Roman

  • Hi Roman.

    I've not used AJ2.4; just up to AJ2.3.  However, the changes between the two appear to be more incremental than earlier changes.  Both use a 3.4.x kernel, for example.

    Besides the signing, there are also runtime differences between HS and GP devices.  During startup, the kernel reads the ID of the chip and performs differently on HS and GP devices.  I've only used GP myself.

    I have 4AJ2.3 running on 4430- and 4460-based GP custom boards -- Phytec phyCORE-OMAP44xx.  I had to make other changes, but they were to add board files, sound drivers, etc for those specific boards.  Basically rewriting what existed for the SDP4430 (Blaze).

    Regards,

        Steve

  • Hi Steve,

    your patch is working. The linux kernel boot process goes a few steps further so this point can be closed.

    Now it stops on ducati firmware upload and in booting android from sdcard. I will come back if I need some .  ;-)

    BTW: On my board is a phyCore-OMAP4430 module installed.

    Many thanks,

    Roman

  • Hi Roman.

    We should probably talk offline about running on the phyCORE-OMAP44xx.  I can be reached at steve@scheftech.com.

    Regards,

        Steve