booting an ML405

Grant Likely grant.likely at secretlab.ca
Tue Jul 8 12:29:58 EST 2008


On Mon, Jul 7, 2008 at 7:37 PM, Lorenzo T. Flores <lorenzo at alphagolf.com> wrote:
> David,
>
> Thanks for the response. I searched a little more and found that many people
> recommend looking through __log_buf to see if info is getting printed to
> memory. Below I've added the printouts I get both before and after the
> system hangs. Also, I'm not using Uartlite. I'm using 16550; however, I have
> created the same design with Uartlite and adjusted the console parameter to
> reflect that change. In both instances the kernel hangs. You're right too,
> this is common...I just need to figure out how to read out this __log_buf
> address:
>
> If I stop the processor after it hangs:

... This looks like ASCII text; let's try decoding it...

> XMD% mrd 0xc0259fa4 10
> C0259FA4:   3C353E5B    '<5>['
> C0259FA8:   20202020    '    '
> C0259FAC:   302E3030    '0.00'
> C0259FB0:   30303030    '0000'
> C0259FB4:   5D204C69    '] Li'
> C0259FB8:   6E757820    'nux '
> C0259FBC:   76657273    'vers'
> C0259FC0:   696F6E20    'ion '
> C0259FC4:   322E362E    '2.6.'
> C0259FC8:   32352D72    '25-r'

Looks like you've found how to read the logbuf; now you just need to
dump it to a file so tha tyou can read it.  :-)

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.


More information about the Linuxppc-embedded mailing list