A friend of mine had the same problem with a K6-2 450. He finally fixed it by setting the cpu core voltage to the right value.
Don't believe your mobo manual, have a look at the processor itself - it should be stamped on there. Christian > -----Original Message----- > From: Colin Boyd [mailto:[EMAIL PROTECTED] > Sent: Friday, April 21, 2000 5:26 PM > To: [email protected] > Subject: Signal 11? > > > Hello... > > I wrote in the other day detailing the overwhelming amount of erradic > behaviour my new system (K62-550,128MB,16M Vid) > > I have a tyan trinity AGP motherboard. > > I've finally got the network card working....and the systems general > stability seems ok...(admittedly I haven't done much...browsed the web and > such...) But it still won't let me compile the kernel without crashing. In > my message the other day I said that everytime I tried it would bomb with a > signal 6....at a diffrent place each time. Counting the rest of the general > system instability I decided to follow some advice and run a comprehensive > memory test....and it passed. > > So now I'm wondering if anyone else could share a few ideas as to problems. > All my peripherals work (which is very few) and there are no IRQ conflicts. > The memory test (as I said before) passed, and the HD is brand new, fresh > out of the box. Here's the detailed list of parts...in case anyone can pick > out a known-to-be-a-bitch part. > > Tyan Trinity AGP Motherboard w/ AMD K6-2 550Mz > Diamond Stealth SG540 16M video. > 128M SDRAM (1 new 64M, and 1 old - both 100mhz - both passed memtest86) > 10GB Maxtor HD > Kingston EtherX KNE100TX 10/100 > > I am running Debian 2.2 - I know it's frozen and not stable, but I couldn't > make the kernel compile when I installed a fresh slink either...and potato > is just so much more trick! > > And here is what I get when the kernel compile dies. > > ---begin----- > > gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 > -fomit-f > rame-pointer -fno-strict-aliasing -pipe -fno-strength-reduce -m486 > -malign-loops > =2 -malign-jumps=2 -malign-functions=2 -DCPU=586 -c -o devinet.o devinet.c > cpp: output pipe has been closed > {standard input}: Assembler messages: > {standard input}:0: Warning: end of file not at end of a line; newline > inserted > {standard input}:277: Error: suffix or operands invalid for `xor' > gcc: Internal compiler error: program cc1 got fatal signal 11 > make[4]: *** [devinet.o] Error 1 > make[4]: Leaving directory `/usr/src/linux/net/ipv4' > make[3]: *** [first_rule] Error 2 > make[3]: Leaving directory `/usr/src/linux/net/ipv4' > make[2]: *** [_subdir_ipv4] Error 2 > make[2]: Leaving directory `/usr/src/linux/net' > make[1]: *** [_dir_net] Error 2 > make[1]: Leaving directory `/usr/src/linux' > make: *** [stamp-build] Error 2 > egypt3:/usr/src/linux# > > ----end------ > > Yes...it does look like the assembler loses track of an op code in memory > and can't find it again....this would lead me to think it was a memory > problem if memtest86 wasn't so adament that it was OK. > > Note that while it died working on compiling ipv4 *this* time....it also > shows signs of being a memory error by dying at a diffrent point almost > every time... > > So my question is....is there anything that can be wrong...that > would appear > to be a memory error....when there really isn't a memory error? Or > basically > can anyone give me any new thoughts on the issue at all? > > Thanks.... > > -Colin > > ________________________________________________________________________ > Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com > > > -- > Unsubscribe? mail -s unsubscribe > [EMAIL PROTECTED] < /dev/null >
