From: Ralf Baechle <ralf@linux-mips.org>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Jun Sun <jsun@mvista.com>, linux-mips@oss.sgi.com
Subject: Re: a really really weird crash on swarm
Date: Mon, 19 Aug 2002 15:28:17 +0200 [thread overview]
Message-ID: <20020819152817.A14266@linux-mips.org> (raw)
In-Reply-To: <Pine.GSO.3.96.1020819144136.14441E-100000@delta.ds2.pg.gda.pl>; from macro@ds2.pg.gda.pl on Mon, Aug 19, 2002 at 02:57:14PM +0200
On Mon, Aug 19, 2002 at 02:57:14PM +0200, Maciej W. Rozycki wrote:
> > Really odd because the register only lost the upper 16 bits; the lower 16
> > bits still have their expected value.
>
> It is a typical symptom of a register being corrupted between a "lui" and
> an "addiu" -- an exception must have done it in the immediately preceding
> code. You might be able to track a reason down by carefully studying
> possible exception paths at the place of the problem. Unfortunately you
> don't have much of the state preserved at this stage -- you only know
> which register was corrupted.
Little exception potencial in this case as the interrupts got disabled and
the addresses used were rsp. should all be in KSEG0.
> Another possible approach is to add some code that compares the values of
> the register upon an exception entry and exit and wait for it to trigger
> -- for a single register it shouldn't be too tough and you have still much
> of the state available before an "rfe" or "eret".
Don't try to think too deterministic - Jun was working on first silicon, so
not necessarily on a deterministic platform as we'd like. Fortunately
as you may have seen in the kernel code there's already newer silicon so
I'd simply file this one to /dev/null for now.
Ralf
prev parent reply other threads:[~2002-08-20 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 23:22 a really really weird crash on swarm Jun Sun
2002-08-10 0:07 ` Justin Carlson
2002-08-11 16:51 ` Ralf Baechle
2002-08-19 12:57 ` Maciej W. Rozycki
2002-08-19 13:28 ` Ralf Baechle [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=20020819152817.A14266@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
/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