From: Michael Ellerman <michael@ellerman.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, sivaji <rameshmrm@gmail.com>
Subject: Re: 2.6.23-rc3 boot hang on MPC8641D
Date: Thu, 13 Sep 2007 15:59:32 +1000 [thread overview]
Message-ID: <1189663172.20396.1.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <57BB0290-6787-4504-BC29-0E92AB226E6C@kernel.crashing.org>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
On Thu, 2007-09-13 at 00:13 -0500, Kumar Gala wrote:
> On Sep 12, 2007, at 11:47 PM, sivaji wrote:
>
> >
> >
> > Hi,
> > I have JTAG Debugger connected to the board. I was given the
> > following commands in the root path of the kernel source
>
> If you can dump memory w/o connecting GDB, I suggest the following.
>
> Look in your kernel build for System.map and grep for log_buf you
> should get something like:
>
> c040b04c d log_buf
> c043b1a4 b __log_buf
>
> then dump the memory @ these addresses. I can't remember which one
> is the correct one. You'll want to subtract c000_0000 from the
> address to get a physical address that you can dump. This should
> help provide some possible insight into what's going on.
__log_buf is the actual buffer, log_buf points to the current insertion
point IIRC. It should be pretty obvious that you're looking at a dmesg
buffer though, unless there's nothing in there for some reason.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-09-13 5:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 4:18 2.6.23-rc3 boot hang on MPC8641D sivaji
2007-09-13 4:25 ` Kumar Gala
2007-09-13 4:47 ` sivaji
2007-09-13 5:13 ` Kumar Gala
2007-09-13 5:59 ` Michael Ellerman [this message]
2007-09-13 4:38 ` Zhang Wei-r63237
2007-09-13 4:52 ` sivaji
2007-09-13 5:11 ` Kumar Gala
2007-09-13 5:19 ` Zhang Wei-r63237
2007-09-13 5:32 ` sivaji
2007-09-13 6:46 ` Zhang Wei-r63237
2007-09-14 14:25 ` sivaji
2007-09-13 5:24 ` sivaji
2007-09-13 5:29 ` David Gibson
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=1189663172.20396.1.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=rameshmrm@gmail.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).