From: Tom Rini <trini@kernel.crashing.org>
To: Joakim Tjernlund <joakim.tjernlund@lumentis.se>
Cc: "Linuxppc-Embedded@Ozlabs. Org" <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] Handle I-TLB Error and Miss separately on 8xx
Date: Thu, 13 Jan 2005 08:16:46 -0700 [thread overview]
Message-ID: <20050113151646.GZ3391@smtp.west.cox.net> (raw)
In-Reply-To: <20050112151508.GS3391@smtp.west.cox.net>
On Wed, Jan 12, 2005 at 08:15:08AM -0700, Tom Rini wrote:
> On Wed, Jan 12, 2005 at 03:17:11PM +0100, Joakim Tjernlund wrote:
> > > On Wed, Jan 12, 2005 at 08:53:17AM +0100, Joakim Tjernlund wrote:
[snip]
> > > > Patch looks good to me, but I want to ask when this error
> > > > can be triggered in practice?
> > >
> > > It is possible to see this in the real world, as we (<hat=mvista>) found
> > > this with a customers app.
> >
> > hmm, this app must have been doing something pretty special. Any idea what
> > caused it?
>
> Only vaugely. I'll poke the folks who did the investigation to see if
> they recall (the app is quite large) and follow up with details, I hope.
First, we couldn't get this issue to happen w/ anything but the custom
app. It would generate a lot of I-TLB Error exceptions, with bit 1 of
SRR1 set, and these went fine, the I-TLB got updated, and execution
continued. But then at some point, and we aren't sure why exactly, an
0x1100 is generated, and we crash. We don't know what went and caused
an 0x1100 to be generated instead of an 0x1300 (my wild-ass-guess is the
code jumped very very far ahead).
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-01-13 15:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 7:53 [PATCH] Handle I-TLB Error and Miss separately on 8xx Joakim Tjernlund
2005-01-12 14:06 ` Tom Rini
2005-01-12 14:17 ` Joakim Tjernlund
2005-01-12 15:15 ` Tom Rini
2005-01-13 15:16 ` Tom Rini [this message]
2005-01-14 14:03 ` Joakim Tjernlund
2005-01-14 17:38 ` Joakim Tjernlund
2005-01-14 17:47 ` Tom Rini
2005-01-14 17:56 ` Joakim Tjernlund
2005-01-14 18:05 ` Tom Rini
2005-01-14 19:51 ` Joakim Tjernlund
2005-01-18 20:09 ` Tom Rini
2005-01-18 22:02 ` Joakim Tjernlund
2005-01-19 17:25 ` Dan Malek
2005-01-19 18:06 ` Joakim Tjernlund
2005-01-19 18:37 ` Dan Malek
2005-01-19 19:58 ` Joakim Tjernlund
2005-01-19 0:30 ` Joakim Tjernlund
2005-01-19 17:28 ` Dan Malek
2005-01-19 18:12 ` Joakim Tjernlund
-- strict thread matches above, loose matches on Subject: below --
2005-01-07 16:22 Tom Rini
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=20050113151646.GZ3391@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=joakim.tjernlund@lumentis.se \
--cc=linuxppc-embedded@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).