public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
* SDP support seems broken in LO
@ 2009-08-18 12:19 vimal singh
  2009-08-18 12:23 ` Shilimkar, Santosh
  0 siblings, 1 reply; 8+ messages in thread
From: vimal singh @ 2009-08-18 12:19 UTC (permalink / raw)
  To: linux-omap

LO seems broken on OMAP3430 SDP platform. I compile latest kernel with
'omap_3430sdp_defconfig' config options.

Booting hangs after kernel uncompressed and last message which appears
is 'booting the kernel'


Thanks and regards,
vimal

See below log:

## Booting image at 80000000 ...
   Image Name:   Linux-2.6.31-rc5-omap1-05896-ge0
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2520992 Bytes =  2.4 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.................................................................................................................................................................
done, booting the kernel.

^ permalink raw reply	[flat|nested] 8+ messages in thread

* RE: SDP support seems broken in LO
  2009-08-18 12:19 SDP support seems broken in LO vimal singh
@ 2009-08-18 12:23 ` Shilimkar, Santosh
  2009-08-18 12:58   ` vimal singh
  0 siblings, 1 reply; 8+ messages in thread
From: Shilimkar, Santosh @ 2009-08-18 12:23 UTC (permalink / raw)
  To: vimal singh, linux-omap@vger.kernel.org

> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> owner@vger.kernel.org] On Behalf Of vimal singh
> Sent: Tuesday, August 18, 2009 5:49 PM
> To: linux-omap@vger.kernel.org
> Subject: SDP support seems broken in LO
> 
> LO seems broken on OMAP3430 SDP platform. I compile latest kernel with
> 'omap_3430sdp_defconfig' config options.
> 
> Booting hangs after kernel uncompressed and last message which appears
> is 'booting the kernel'
> 
> 
> Thanks and regards,
> vimal
> 
> See below log:
> 
> ## Booting image at 80000000 ...
>    Image Name:   Linux-2.6.31-rc5-omap1-05896-ge0
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    2520992 Bytes =  2.4 MB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
> OK
> 
> Starting kernel ...
> 
> Uncompressing
> Linux.....................................................................
> ..........................................................................
> ..................
> done, booting the kernel.
Mainly because of frame-buffer and musb. You can try disabling these two and see if it boots.


Regards,
Santosh

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: SDP support seems broken in LO
  2009-08-18 12:23 ` Shilimkar, Santosh
@ 2009-08-18 12:58   ` vimal singh
  2009-08-18 13:00     ` Gadiyar, Anand
  0 siblings, 1 reply; 8+ messages in thread
From: vimal singh @ 2009-08-18 12:58 UTC (permalink / raw)
  To: Shilimkar, Santosh; +Cc: linux-omap@vger.kernel.org

On Tue, Aug 18, 2009 at 5:53 PM, Shilimkar,
Santosh<santosh.shilimkar@ti.com> wrote:
>> -----Original Message-----
>> From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
>> owner@vger.kernel.org] On Behalf Of vimal singh
>> Sent: Tuesday, August 18, 2009 5:49 PM
>> To: linux-omap@vger.kernel.org
>> Subject: SDP support seems broken in LO
>>
>> LO seems broken on OMAP3430 SDP platform. I compile latest kernel with
>> 'omap_3430sdp_defconfig' config options.
>>
>> Booting hangs after kernel uncompressed and last message which appears
>> is 'booting the kernel'
>>
>>
>> Thanks and regards,
>> vimal
>>
>> See below log:
>>
>> ## Booting image at 80000000 ...
>>    Image Name:   Linux-2.6.31-rc5-omap1-05896-ge0
>>    Image Type:   ARM Linux Kernel Image (uncompressed)
>>    Data Size:    2520992 Bytes =  2.4 MB
>>    Load Address: 80008000
>>    Entry Point:  80008000
>>    Verifying Checksum ... OK
>> OK
>>
>> Starting kernel ...
>>
>> Uncompressing
>> Linux.....................................................................
>> ..........................................................................
>> ..................
>> done, booting the kernel.
> Mainly because of frame-buffer and musb. You can try disabling these two and see if it boots.

I disabled frame-buffer and usb support fully:
# CONFIG_FB is not set
# CONFIG_USB_SUPPORT is not set

I still get same message.

-vimal

>
>
> Regards,
> Santosh
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 8+ messages in thread

* RE: SDP support seems broken in LO
  2009-08-18 12:58   ` vimal singh
@ 2009-08-18 13:00     ` Gadiyar, Anand
  2009-08-18 13:10       ` vimal singh
  0 siblings, 1 reply; 8+ messages in thread
From: Gadiyar, Anand @ 2009-08-18 13:00 UTC (permalink / raw)
  To: vimal singh, Shilimkar, Santosh; +Cc: linux-omap@vger.kernel.org

> >> LO seems broken on OMAP3430 SDP platform. I compile latest kernel with
> >> 'omap_3430sdp_defconfig' config options.
> >>
> >> Booting hangs after kernel uncompressed and last message which appears
> >> is 'booting the kernel'
> >>
> >>
> >> Thanks and regards,
> >> vimal
> >>
> >> See below log:
> >>
> >> ## Booting image at 80000000 ...
> >>    Image Name:   Linux-2.6.31-rc5-omap1-05896-ge0
> >>    Image Type:   ARM Linux Kernel Image (uncompressed)
> >>    Data Size:    2520992 Bytes =  2.4 MB
> >>    Load Address: 80008000
> >>    Entry Point:  80008000
> >>    Verifying Checksum ... OK
> >> OK
> >>
> >> Starting kernel ...
> >>
> >> Uncompressing Linux.....................................................................
> >> 
> ..............................................................
> ............
> >> ..................
> >> done, booting the kernel.
> > Mainly because of frame-buffer and musb. You can try disabling these two and see if it boots.
> 
> I disabled frame-buffer and usb support fully:
> # CONFIG_FB is not set
> # CONFIG_USB_SUPPORT is not set
> 
> I still get same message.
> 
> -vimal
> 


Do you have CONFIG_DEBUG_LL enabled? If so, could you enable that please to
see if we have a crash somewhere?

- Anand
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: SDP support seems broken in LO
  2009-08-18 13:00     ` Gadiyar, Anand
@ 2009-08-18 13:10       ` vimal singh
  2009-08-18 13:14         ` Gadiyar, Anand
  0 siblings, 1 reply; 8+ messages in thread
From: vimal singh @ 2009-08-18 13:10 UTC (permalink / raw)
  To: Gadiyar, Anand; +Cc: Shilimkar, Santosh, linux-omap@vger.kernel.org

On Tue, Aug 18, 2009 at 6:30 PM, Gadiyar, Anand<gadiyar@ti.com> wrote:
>> >> LO seems broken on OMAP3430 SDP platform. I compile latest kernel with
>> >> 'omap_3430sdp_defconfig' config options.
>> >>
>> >> Booting hangs after kernel uncompressed and last message which appears
>> >> is 'booting the kernel'
>> >>
>> >>
>> >> Thanks and regards,
>> >> vimal
>> >>
>> >> See below log:
>> >>
>> >> ## Booting image at 80000000 ...
>> >>    Image Name:   Linux-2.6.31-rc5-omap1-05896-ge0
>> >>    Image Type:   ARM Linux Kernel Image (uncompressed)
>> >>    Data Size:    2520992 Bytes =  2.4 MB
>> >>    Load Address: 80008000
>> >>    Entry Point:  80008000
>> >>    Verifying Checksum ... OK
>> >> OK
>> >>
>> >> Starting kernel ...
>> >>
>> >> Uncompressing Linux.....................................................................
>> >>
>> ..............................................................
>> ............
>> >> ..................
>> >> done, booting the kernel.
>> > Mainly because of frame-buffer and musb. You can try disabling these two and see if it boots.
>>
>> I disabled frame-buffer and usb support fully:
>> # CONFIG_FB is not set
>> # CONFIG_USB_SUPPORT is not set
>>
>> I still get same message.
>>
>> -vimal
>>
>
>
> Do you have CONFIG_DEBUG_LL enabled? If so, could you enable that please to
> see if we have a crash somewhere?
>

Here is the log after enabling 'CONFIG_DEBUG_LL':

## Booting image at 80000000 ...
   Image Name:   Linux-2.6.31-rc5-omap1-05896-ge0
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2303384 Bytes =  2.2 MB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux....................................................................................................................................................
done, booting the kernel.
<5>Linux version 2.6.31-rc5-omap1-05896-ge087f6f-dirty
(x0094262@omaplinux2) (gcc version 4.2.1 (CodeSourcery Sourcery G++
Lite 2007q3-51)) #7 Tue Aug 18 18:38:47 IST 2009
CPU: ARMv7 Processor [411fc081] revision 1 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP3430 3430SDP board
Memory policy: ECC disabled, Data cache writeback
<7>On node 0 totalpages: 32768
<7>free_area_init_node: node 0, pgdat c048c700, node_mem_map c04da000
<7>  Normal zone: 256 pages used for memmap
<7>  Normal zone: 0 pages reserved
<7>  Normal zone: 32512 pages, LIFO batch:7
<6>OMAP3430 ES2.0
<6>SRAM: Mapped pa 0x40200000 to va 0xe3000000 size: 0x100000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
<5>Kernel command line: mem=128M console=ttyS0,115200n8 noinitrd
root=/dev/nfs rw
nfsroot=10.24.246.118:/home1/vimal_fs/newfs,nolock,tcp,rsize=1024,wsize=1024
ip=dhcp nohz=off
PID hash table entries: 512 (order: 9, 2048 bytes)
<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: 124828KB available (4132K code, 529K data, 128K init, 0K highmem)
<6>SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
<6>NR_IRQS:402
<6>Clocking rate (Crystal/DPLL/ARM core): 26.0/332/500 MHz
<6>Reprogramming SDRC clock to 332000000 Hz
<6>GPMC revision 5.0
<6>IRQ: Found an INTC at 0xd8200000 (revision 4.0) with 96 interrupts
<6>Total of 96 interrupts on 1 active controller
<6>OMAP34xx GPIO hardware version 2.5
<6>OMAP clockevent source: GPTIMER1 at 32768 Hz
Console: colour dummy device 80x30
<6>Calibrating delay loop...


-vimal

> - Anand
>
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 8+ messages in thread

* RE: SDP support seems broken in LO
  2009-08-18 13:10       ` vimal singh
@ 2009-08-18 13:14         ` Gadiyar, Anand
  2009-08-18 13:29           ` vimal singh
  2009-08-25 11:21           ` Roger Quadros
  0 siblings, 2 replies; 8+ messages in thread
From: Gadiyar, Anand @ 2009-08-18 13:14 UTC (permalink / raw)
  To: vimal singh; +Cc: Shilimkar, Santosh, linux-omap@vger.kernel.org

<snip>

> Here is the log after enabling 'CONFIG_DEBUG_LL':
> 
> ## Booting image at 80000000 ...
>    Image Name:   Linux-2.6.31-rc5-omap1-05896-ge0
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    2303384 Bytes =  2.2 MB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
> OK
> 
> Starting kernel ...
> 
> Uncompressing Linux.........................................................
> ...........................................................................................
> done, booting the kernel.
> <5>Linux version 2.6.31-rc5-omap1-05896-ge087f6f-dirty
> (x0094262@omaplinux2) (gcc version 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-51)) #7 Tue Aug 18 18:38:47 IST 2009

And here's the problem - you're using CodeSourcery's 2007q3 toolchain.
This has been discussed in the past on this list. I don't know exactly
what causes the problem or what fixes this.

Move to 2008q3 or 2009q1 as a workaround.

- Anand



^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: SDP support seems broken in LO
  2009-08-18 13:14         ` Gadiyar, Anand
@ 2009-08-18 13:29           ` vimal singh
  2009-08-25 11:21           ` Roger Quadros
  1 sibling, 0 replies; 8+ messages in thread
From: vimal singh @ 2009-08-18 13:29 UTC (permalink / raw)
  To: Gadiyar, Anand; +Cc: Shilimkar, Santosh, linux-omap@vger.kernel.org

> Move to 2008q3 or 2009q1 as a workaround.

Thanks Anand... it came up. :)

-vimal
> - Anand
>
>
>

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: SDP support seems broken in LO
  2009-08-18 13:14         ` Gadiyar, Anand
  2009-08-18 13:29           ` vimal singh
@ 2009-08-25 11:21           ` Roger Quadros
  1 sibling, 0 replies; 8+ messages in thread
From: Roger Quadros @ 2009-08-25 11:21 UTC (permalink / raw)
  To: ext Gadiyar, Anand
  Cc: vimal singh, Shilimkar, Santosh, linux-omap@vger.kernel.org

ext Gadiyar, Anand wrote:
> <snip>
> 
>> Here is the log after enabling 'CONFIG_DEBUG_LL':
>>
>> ## Booting image at 80000000 ...
>>    Image Name:   Linux-2.6.31-rc5-omap1-05896-ge0
>>    Image Type:   ARM Linux Kernel Image (uncompressed)
>>    Data Size:    2303384 Bytes =  2.2 MB
>>    Load Address: 80008000
>>    Entry Point:  80008000
>>    Verifying Checksum ... OK
>> OK
>>
>> Starting kernel ...
>>
>> Uncompressing Linux.........................................................
>> ...........................................................................................
>> done, booting the kernel.
>> <5>Linux version 2.6.31-rc5-omap1-05896-ge087f6f-dirty
>> (x0094262@omaplinux2) (gcc version 4.2.1 (CodeSourcery Sourcery G++ Lite 2007q3-51)) #7 Tue Aug 18 18:38:47 IST 2009
> 
> And here's the problem - you're using CodeSourcery's 2007q3 toolchain.
> This has been discussed in the past on this list. I don't know exactly
> what causes the problem or what fixes this.

To know more about this see the discussion in this thread
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg12363.html

> 
> Move to 2008q3 or 2009q1 as a workaround.
> 
> - Anand
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2009-08-25 11:21 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-08-18 12:19 SDP support seems broken in LO vimal singh
2009-08-18 12:23 ` Shilimkar, Santosh
2009-08-18 12:58   ` vimal singh
2009-08-18 13:00     ` Gadiyar, Anand
2009-08-18 13:10       ` vimal singh
2009-08-18 13:14         ` Gadiyar, Anand
2009-08-18 13:29           ` vimal singh
2009-08-25 11:21           ` Roger Quadros

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox