From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Lorenzo T. Flores" <lorenzo@alphagolf.com>
Cc: David Baird <dhbaird@gmail.com>, linuxppc-embedded@ozlabs.org
Subject: Re: booting an ML405
Date: Mon, 7 Jul 2008 20:29:58 -0600 [thread overview]
Message-ID: <fa686aa40807071929s3ba2a33cl5f6a411c89fc2132@mail.gmail.com> (raw)
In-Reply-To: <4872C4D0.4060006@alphagolf.com>
On Mon, Jul 7, 2008 at 7:37 PM, Lorenzo T. Flores <lorenzo@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.
next prev parent reply other threads:[~2008-07-08 2:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 1:05 booting an ML405 Lorenzo T. Flores
2008-07-04 2:02 ` David Baird
2008-07-08 1:37 ` Lorenzo T. Flores
2008-07-08 2:29 ` Grant Likely [this message]
2008-07-08 17:12 ` David Baird
2008-07-10 1:11 ` Lorenzo T. Flores
2008-07-08 14:58 ` John Linn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa686aa40807071929s3ba2a33cl5f6a411c89fc2132@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=dhbaird@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=lorenzo@alphagolf.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).