Messages in this thread | | | Date | Tue, 06 Jul 1999 22:17:12 -0500 | From | "Thomas E. Dodd /CSDC" <> | Subject | Re: 2.2.10 oops (finally, something I can report!) |
| |
Justin Ossevoort wrote: > > Before someone else comes saying that they had problems with a Cyrix > processor ( I don't use one myself ;-) ), > wouldn't it be logical to search the problem somewhere else, instead of > blaming it on the cpu, pherhaps we should be blaming it on the support of > the cpu. Linus has already pointed in the direction of the "comma bug", > that would pherhaps be a good clue. He thought there could be some > problems in that fix. So if some people with a (alike) Cyric cpu (having > sometimes some Oopses) could just _try_ and disable the MTRR support > and/or the "comma bug" workaround. > I don't know where this oops occurs, is it pherhaps some signal register > of the cpu that indicated this fault (on which the kernel responded) for > if this is the case, it could just be that the bug lies in the processor's > signal registers. (I don't know the actual name of those things, I just > know that they exist in some form). >
Just to take a different side.
I had Cx6x86 PR150 (non MMX), 120MHz overclocked to 166MHz (83 x 2) and ran kernels from 2.0.32 to 2.2.5 on it. Only problem ever was the gcc bug.
So Cyrix can make a stable platform.
I now run a K6-3, the Cyrix was to slow now.
-Thomas
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |