linux-mips
[Top] [All Lists]

Re: [Oops] Indy R4600 Oops(es) w/ 2.4.19-rc1

To: jbglaw@lug-owl.de
Subject: Re: [Oops] Indy R4600 Oops(es) w/ 2.4.19-rc1
From: Karel van Houten <vhouten@kpn.com>
Date: Mon, 1 Jul 2002 19:24:59 +0200 (MET DST)
Cc: linux-mips@oss.sgi.com
In-reply-to: <20020701151359.GR17216@lug-owl.de> from "jbglaw@lug-owl.de" at Jul 01, 2002 05:13:59 PM
Sender: owner-linux-mips@oss.sgi.com
> On Mon, 2002-07-01 16:28:13 +0200, Maciej W. Rozycki <macro@ds2.pg.gda.pl>
> wrote in message
> <Pine.GSO.3.96.1020701161009.7601E-100000@delta.ds2.pg.gda.pl>:
> > On Mon, 1 Jul 2002, Jan-Benedict Glaw wrote:
> > 
> > > Okay, stupid idea. All these flush functions seem to be never called in
> > > parallel or recursive, so if might be possible to have a global flags
> > > variable and instead of always calling __save..() and __restore..(),
> > > we bulid a pair of inline functions doing this. This wouldn't give
> > > any penalty for !CONFIG_CPU_R4X00 and doesn't obscure the code so much
> > > as all those #ifdef and #endif's would do... I'll test my suggestion
> > > as fast as I reach my Indy again (is powered down at home...).
> > 
> >  Feel free to use the change privately.  Otherwise please code a real fix,
> > i.e. a set of buggy-R4600-specific functions, as CONFIG_CPU_R4X00 means
> > other processors as well, e.g. R4000 or R4400 which are fine here. 
> > 
> >  Actually blocking interrupts for over 0.01s as it used to be done is
> 
> Ah. That would explain the huge time drifts when the box is under
> load...
> 

Indeed, I'm now running 2.4.18, and for the first time my DS5000/260 and
DS5000/200 can keep exact time, even under heavy load.
Btw, I use a R4400SC CPU.

-- 
Karel van Houten

----------------------------------------------------------
The box said "Requires Windows 95 or better."
I can't understand why it won't work on my Linux computer. 
----------------------------------------------------------


<Prev in Thread] Current Thread [Next in Thread>