From: Luke -Jr <luke@dashjr.org>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mips@linux-mips.org
Subject: Re: bcm33xx port
Date: Sun, 8 Jun 2008 15:20:38 -0500 [thread overview]
Message-ID: <200806081520.43090.luke@dashjr.org> (raw)
In-Reply-To: <484C38A6.7080503@mips.com>
On Sunday 08 June 2008, Kevin D. Kissell wrote:
> Luke -Jr wrote:
> > On Sunday 08 June 2008, Kevin D. Kissell wrote:
> >> and (b) control being transferred to a block of memory that isn't
> >> actually code, as can happen if exception vectors or global
> >> pointers-to-functions aren't set up correctly, or if the kernel stack is
> >> being corrupted. When you say "the instruction in question is a store
> >> word", how do you know that?
> >
> > The RI error spits out a bunch of info, including epc which presumably
> > points to the instruction causing the problem: ac85ffc0; this is 'sw
> > a1,-64(a0)'
>
> But unless the processor itself is actually defective, there is no way that
> a SW instruction can cause an RI exception. Sometimes a kernel crash
> is so violent that the kernel stack frame cannot be reliably decoded by
> the crash dump code, and this would appear to be one of those cases.
In that case, wouldn't the "kernel stack" appear to be complete nonsense?
Yet the stack in this case is quite logical and consistent. Furthermore, if I
skip the bzero stuff (by commenting out the call), it will crash shortly
thereafter when the ELF loader attempts to write to it in another way.
Is it very unlikely that the bcm3345 is simply raising the wrong exception (or
perhaps Linux is misinterpreting the exception)?
> I find the address of 0xac85ffc0 to be a bit suspicious, myself. That's
> a kseg1 (non-cacheable identity map) address for physical address
> 0x0c85ffc0, which would be legitimate (though suspicious) if you had
> 256MB of RAM, but the boot log quote you posted earlier suggests
> that you've only got 16M. Is there really memory of some kind at
> that address? Are you calling routines in a boot ROM from Linux?
ac85ffc0 is the instruction for 'sw a1,-64(a0)', not an address.
The board has only 8 MB RAM, to the best I can tell from looking up the RAM
chip (hynix KOREA HY57V641620HG 0229A T-7).
> Debugging Linux kernel crashes is probably not the best way to learn
> the MIPS privileged resource architecture. I'd strongly recommend
> http://www.amazon.com/See-MIPS-Second-Dominic-Sweetman/dp/0120884216/
Can you recommend any gratis materials to read? I don't have room in my budget
to spend money on this hobby right now..
Luke
next prev parent reply other threads:[~2008-06-08 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806072113.26433.luke@dashjr.org>
[not found] ` <Pine.LNX.4.55.0806080342310.15673@cliff.in.clinika.pl>
2008-06-08 4:32 ` bcm33xx port Luke -Jr
2008-06-08 12:53 ` Maciej W. Rozycki
2008-06-08 18:56 ` Luke -Jr
2008-06-08 19:53 ` Kevin D. Kissell
2008-06-08 20:14 ` Maciej W. Rozycki
2008-06-08 20:20 ` Luke -Jr [this message]
2008-06-08 19:59 ` Maciej W. Rozycki
2008-06-08 20:27 ` Luke -Jr
2008-06-08 22:13 ` Maciej W. Rozycki
2008-06-08 23:36 ` Luke -Jr
2008-06-09 6:40 ` Geert Uytterhoeven
2008-06-09 6:05 ` Luke -Jr
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=200806081520.43090.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=kevink@mips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.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