From: Carsten Langgaard <carstenl@mips.com>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: "H. J. Lu" <hjl@lucon.org>, Jun Sun <jsun@mvista.com>,
linux-mips@oss.sgi.com
Subject: Re: Malta crashes on the latest 2.4 kernel
Date: Thu, 11 Jul 2002 09:50:22 +0200 [thread overview]
Message-ID: <3D2D38BE.F1C6AC73@mips.com> (raw)
In-Reply-To: 20020711043601.B3207@dea.linux-mips.net
Ralf Baechle wrote:
> On Wed, Jul 10, 2002 at 04:49:00PM -0700, H. J. Lu wrote:
>
> > > See the crash scene. Anybody knows the cause? It is strange to see the
> > > reserved exception.
> > >
> >
> > The 2.4 kernel checked out around Jul 4 09:28 PDT works fine on Malta.
>
> Jun's patch certainly is correct for some MIPS32 CPUs; others may get
> away without this one. Previous experience with pipeline hazards on MIPS
> processors has shown that at times hazards may change even between minor
> revisions of a CPU; documentation isn't always trustworthy about such
> minor details of the pipeline.
I actually discovered the hazard problem on a 4Kc, based on some older RTL, but
the hazard some how disappear on a newer revision.
So you are absolutely right.
>
> Ralf
--
_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
Denmark http://www.mips.com
next prev parent reply other threads:[~2002-07-11 7:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 23:12 Malta crashes on the latest 2.4 kernel Jun Sun
2002-07-10 23:49 ` H. J. Lu
2002-07-11 1:18 ` Jun Sun
2002-07-11 2:36 ` Ralf Baechle
2002-07-11 6:19 ` Kevin D. Kissell
2002-07-11 6:19 ` Kevin D. Kissell
2002-07-11 6:56 ` Geert Uytterhoeven
2002-07-11 8:35 ` Kevin D. Kissell
2002-07-11 11:45 ` Ralf Baechle
2002-07-11 11:59 ` Ralf Baechle
2002-07-11 7:50 ` Carsten Langgaard [this message]
2002-07-11 7:44 ` Carsten Langgaard
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=3D2D38BE.F1C6AC73@mips.com \
--to=carstenl@mips.com \
--cc=hjl@lucon.org \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=ralf@oss.sgi.com \
/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.