From: "David S. Miller" <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: RED State Exception on Ultra 1, 2.6.9-rc2
Date: Tue, 21 Sep 2004 19:48:13 +0000 [thread overview]
Message-ID: <20040921124813.3d2fa37c.davem@davemloft.net> (raw)
In-Reply-To: <1095742791.3421.3.camel@ori.thedillows.org>
On 21 Sep 2004 09:47:02 -0400
David Dillow <dave@thedillows.org> wrote:
> > > TL\000.0000.0000.0005 TT\000.0000.0000.0080
> > > TPC\000.0000.0040.ec98 TnPC\000.0000.0040.ec9c TSTATE\000.0000.8000.9504
> TPC: etrap_irq
> TnPC: etrap_irq
> > > TL\000.0000.0000.0004 TT\000.0000.0000.0010
> > > TPC\000.0000.0040.d000 TnPC\000.0000.0040.d004 TSTATE\000.0000.8000.9504
> TPC: tl1_s0n
> TnPC: tl1_s0n
> > > TL\000.0000.0000.0003 TT\000.0000.0000.0080
> > > TPC\000.0000.0040.ec98 TnPC\000.0000.0040.ec9c TSTATE\000.0000.8000.9502
> TPC: etrap_irq
> TnPC: etrap_irq
> > > TL\000.0000.0000.0002 TT\000.0000.0000.0010
> > > TPC\000.0000.0040.8c00 TnPC\000.0000.0040.8c04 TSTATE\000.0000.8008.9402
> TPC: tl0_ivec
> TnPC: tl0_ivec
> > > TL\000.0000.0000.0001 TT\000.0000.0000.0060
> > > TPC\000.0000.0042.1b68 TnPC\000.0000.0042.1b6c TSTATE\000.0000.8000.9602
> TPC: free_streaming_cluster
> TnPC: free_streaming_cluster
>
> Doh! Did I mess something up in my prior patch allowing larger than 1MB
> sbus_map_sg()'s?
I don't think so, based upon this trace. TT means "Trap Type", that's the
numbered trap the cpu took at each trap level and what the trap type numbers
mean is described in the UltraSPARC programmer's manual.
TSTATE's layout is defined by macros in include/asm-sparc64/pstate.h
Anyways, in free_streaming_cluster() we took a vectored interrupt (trap
type 0x60). In tl0_ivec we took an illegal instruction trap, which is
very odd because the instruction at 0x408c00:tl0_ivec is a branch.
It looks like something clobbered the instruction there, that is my best
guess. If you get one of these again you can, at the OBP prompt, say:
ok 0x408c00 dis
and see if the instruction has been corrupted there.
It may be your DMA mapping changes, so doing the following wouldn't hurt:
1) try running with those DMA mapping patches reverted
2) audit those patches for possible errors
Thanks.
next prev parent reply other threads:[~2004-09-21 19:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 4:59 RED State Exception on Ultra 1, 2.6.9-rc2 David Dillow
2004-09-21 6:31 ` David S. Miller
2004-09-21 13:47 ` David Dillow
2004-09-21 14:50 ` Tim Walberg
2004-09-21 19:48 ` David S. Miller [this message]
2004-09-22 3:25 ` David Dillow
2004-09-22 3:35 ` David S. Miller
2004-10-08 16:51 ` David Dillow
2004-10-11 4:09 ` David S. Miller
2004-10-29 6:14 ` David Dillow
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=20040921124813.3d2fa37c.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.