Re: BAD CPU --> SIG11

Jeff Coy Jr. (jcoy@jcoy-ppp.cscwc.pima.edu)
Sun, 12 May 1996 23:30:26 -0700 (MST)


On Sun, 12 May 1996, lilo wrote:

=> There are also known irregularities with L2 writeback cache and
=> cleanroom-microcode AMD DX2/80's. I've never seen anything more than weird
=> bogomips values though....
=>
i have a 486dx2-80, and the sig 11's only showed up for me when i really
pushed the machine, like when i recompiled gcc. the first build would be
fine, but the second build would crash about 45 minutes in. the crashes
weren't really frequent, but setting the CPU speed back to 66mHz solved
the problem and offered the fastest compile time.

the only other solution was turning off the external cache, but without
the extern cache, first stage gcc compile was 36 minutes at 80 mHz, but at
66 mHz i get 26 minute first stage builds.

with external cache & 80 mHz, first stage builds were about 19 minutes,
but i like to compile things like gcc from a script so as to not have to
watch it, so stability won out.

jeff

---
Why Linux? source code. POSIX. tcpip. job control. support from the authors.
drivers for most hardware.  because one terminal or process is never enough.
    forget the other O/Ss, i use Linux- the choice of a GNU generation.