Re: Another oops (1.3.93)

Tim Middelkoop (mtim@lab.housing.fsu.edu)
Sun, 28 Apr 1996 23:25:47 -0400 (EDT)


Unable to handle kernel paging request at virtual address 00000004
current->tss.cr3 = 00646000, %cr3 = 00646000
*pde = 00000000
Oops: 0002
CPU: 0
EIP: 0010:[<0011c9ae>]
EFLAGS: 00010206
eax: 01031414 ebx: 00000378 ecx: 000000de edx: 0094a000
esi: 0094a000 edi: 40007000 ebp: 00ded000 esp: 00acdf54
ds: 0018 es: 002b fs: 002b gs: 002b ss: 0018
Process bash (pid: 488, process nr: 43, stackpage=00acd000)
Stack: 001e0018 003ece80 011e6e10 00001000 40007000 00001000 001e8308
00ded000
00000000 00000378 0094a000 00000000 00000000 00000000 00000000
00000000
00122c92 011e6e10 003ece80 40007000 00001000 01031414 00001000
40007000
Call Trace: [<00122c92>] [<0010a5d9>]
Code: f3 a5 83 e3 03 89 d9 f3 a4 07 6a 00 8b 74 24 28 56 e8 bc 36
PPP: ppp line discipline successfully unregistered

Cyrix dx2-66 with sig-11 problems that can be corrected by turning off
the external cache, it was on when this happened because I am trying to
see if the new cpu fan i have installed is a solution, so far no sig-11's

i don't know if this will help, ksymoops kept giving me seg-faults.
tim...

--
Tim Middelkoop                                   O
http://intrism.hcsys.com/~mtim                  /\,
mtim@freenet.tlh.fl.us                        \/\
----Try linux today----                         /

GE d- s+:- a22 C++ UL++ P++++ L+++ E+> W++ N+ o? K? w--(++) O M V-- PS+ PE Y+ PGP t 5 X R- tv b++ DI? D+ G e+ h-- r-- y+

On Sun, 28 Apr 1996, Derek Fawcus wrote:

> Linus Torvalds wrote: > > On Fri, 26 Apr 1996, Matthew White wrote: > > > > > > I do have a Cyrix chip. 486-DX2/66. And you know, I got another oops on > > > Apr. 23. As well, the 00000004 came up. I can send that to you too, if > > > you'd like. If it makes a difference, I also a victim of the sig11 bug > > > (I even got one while making clean!) but I 99.44% sure it's my cache memory. > > > > Ok, this thing is more or less confirmed - there are some serious > > problems with Cyrix chips. Not nice. > > Just as another datapoint, I've been soaking a bunch of machines which > contain SGS Thompson devices (a rebadged Cyrix), they all get a similar > problem. Either a sig11 or a kernel panic as above. > > The intended use of these systems is for a turnkey control/EPOS system > running a different OS (FlexOS). We were experiencing a number of system > panics and unexplained behaviour. This occured around the time that we > switched to the SGS devices. However these failures wouldn't happen with > any sort of pattern except that memory appeared to be getting corrupted, > so I set up the kit to run Linux as a test. > > The soak test simply consisted of a continuous loop of recompiling the > kernel: > > while make clean && make zImage && make modules && make modules_install; do > echo .version >/dev/tty8; done > > These would usually die after 3 to 5 complete loops. The hardware itself > was known to be good, and the memory system was running at the lowest > possible settings. Replacing the ST device (DX2-66) with an alternative > suppliers (sometime a 40 MHz bus device) would allow the test to run without > problems. The longest I left if for was 27 complete loops. > > These tests were tried out on 3 different makes of motherboards. Eventually > the SGS devices would always fail. > > As a result of this, we've now stopped using these SGS Thompson devices > (or any Cyrix varient), and are now specifying AMD devices (120 and/or 133). > > DF > -- > Derek Fawcus (G7FVS) df@eyrie.demon.co.uk >