From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ayman El-Khashab <ayman@elkhashab.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: help with kernel panics in task swapper on 460ex
Date: Sat, 14 Aug 2010 09:44:31 +1000 [thread overview]
Message-ID: <1281743071.2987.411.camel@pasglop> (raw)
In-Reply-To: <20100813203636.GA11899@crust.elkhashab.com>
On Fri, 2010-08-13 at 15:36 -0500, Ayman El-Khashab wrote:
>
> The exact details (though I don't think they are too useful are as follows.
> The one interesting item if I read it correctly, is that the CPU was
> trying to get instructions from c002xxxx address. However, this board only
> has 512MB of memory so it seems that the address (if it is physical) isn't
> valid.
Actually this is a perfectly valid virtual address. The kernel maps
memory at 0xc0000000 (at least the first 768M of it, the rest is
dynamically mapped in/out).
> Are there any tricks we can use to analyze this problem? Or is there any
> information we can collect to help pinpoint where this issue might lie?
Well, xmon is your friend ...
Ben.
prev parent reply other threads:[~2010-08-13 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 20:36 help with kernel panics in task swapper on 460ex Ayman El-Khashab
2010-08-13 23:44 ` Benjamin Herrenschmidt [this message]
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=1281743071.2987.411.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=ayman@elkhashab.com \
--cc=linuxppc-dev@ozlabs.org \
/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).