Date: Tue, 14 Nov 2000 15:52:41 -0800 From: Kent Stewart <kstewart@urx.com> To: Kerry Davis <kedavis@uswest.net> Cc: "Smith, Malcolm" <Malcolm.Smith@nrc.ca>, freebsd-questions@FreeBSD.ORG Subject: Re: make world crashing repeatedly Message-ID: <3A11D049.DA8F7E42@urx.com> References: <003601c04e93$08a9aaf0$0200000a@system>
next in thread | previous in thread | raw e-mail | index | archive | help
Kerry Davis wrote: > > the odd thing, though, is that any other OS I try - including NT - works > fine. > Making the OS and then running it is different. If you are getting 1-bit errors running NT, you may never notice it unless you see a BSOD or the usual memory related exception error. When you are building the system, 1-bit errors will sooner or later kill the job. Kent > -----Original Message----- > From: Smith, Malcolm <Malcolm.Smith@nrc.ca> > To: 'Kerry Davis' <kedavis@uswest.net> > Date: Tuesday, November 14, 2000 3:59 PM > Subject: RE: make world crashing repeatedly > > >Kerry, > > > >Reading your symptoms again, it might be a heat problem. Check > >that all of your fans are working properly. > > > >The L2 cache could be a problem because it may contain a bad bit. > >Bad cache bits don't always cause an immediate failure, > >and they don't tend to put parity bits on them so you > >don't get a "Bad Cache Memory" error or anything like that. > > > >On one motherboard that I had, the company installed one of the > >cache chips backwards, and it still took quite a few seconds of > >BIOS tests before it even complained about that (that was after > >the chip was fried; I think it even tested all of memory without > >complaining the first few times!) > > > >Bad memory can cause many bogus error messages, and if your > >box is old (which a 486 is likely to be), then maybe it is > >just bad cache. If it makes no difference after you turn the > >cache off, then it is probably something else. > > > >Memory errors are often heat related, so it could be cache trouble > >caused by too much heat. > > > >My nasty 486 motherboard (the one that had the backwards cache chip) > >would not install OpenBSD. It turned out to be a bad PCI slot. > >Go figure. But, if I didn't use one of the PCI slots it was fine; > >if I did, it would crash. Needless to say, I needed all the slots > >(video + 2 NIC). > > > >If it is a hardware problem, the best fix might just be to buy > >another 486 motherboard. I know the used computer stores here sell them > >REAL CHEAP, so I would guess you could pick one up for about $10. > > > >Good luck, > > Malcolm > > > >> -----Original Message----- > >> From: Kerry Davis [mailto:kedavis@uswest.net] > >> Sent: Tuesday, November 14, 2000 2:21 PM > >> To: Smith, Malcolm > >> Cc: freebsd-questions@FreeBSD.ORG > >> Subject: Re: make world crashing repeatedly > >> > >> > >> but can you offer any explanation about why it would matter at all? > >> > >> > >> -----Original Message----- > >> From: Smith, Malcolm <Malcolm.Smith@nrc.ca> > >> To: 'Kerry Davis' <kedavis@uswest.net> > >> Date: Tuesday, November 14, 2000 3:16 PM > >> Subject: RE: make world crashing repeatedly > >> > >> > >> >Kerry, > >> > > >> >Actually, you will probably find that the external cache > >> >only makes about 10-20% difference in speed. The internal > >> >cache makes about a 10X difference. Also, if the 486-75 > >> >overdrive is like the 486-100, then the L1 cache is larger > >> >than on a regular 486 and so the effect of L2 is lessened > >> >(I am assuming your L2 cache is in the 64 KB - 256 KB range). > >> > > >> >I get the 10-20% difference from tests I did on a 486-100 > >> >with 128 KB L2 cache (many years ago). > >> > > >> >You might want to give it a try (rebuilding the kernel in 30 hrs > >> >might still be better than getting Fatal Signals. > >> > > >> >Hope this helps... > >> > > >> >Malcolm Smith > >> > > >> >> -----Original Message----- > >> >> From: Kerry Davis [mailto:kedavis@uswest.net] > >> >> Sent: Tuesday, November 14, 2000 2:03 PM > >> >> To: Zaitsau, Andrei > >> >> Cc: freebsd-questions@FreeBSD.ORG > >> >> Subject: Re: make world crashing repeatedly > >> >> > >> >> > >> >> actually it's currently using an Intel 486-75 overdrive. > >> >> > >> >> and if I disabled external cache, it might take 24 days to > >> >> run, not just 24 > >> >> hours. > >> >> > >> >> -----Original Message----- > >> >> From: Zaitsau, Andrei <AZaitsau@panasonicfa.com> > >> >> To: 'Kerry Davis' <kedavis@uswest.net> > >> >> Date: Tuesday, November 14, 2000 2:45 PM > >> >> Subject: RE: make world crashing repeatedly > >> >> > >> >> > >> >> >Let me guess...is it AMD processor? > >> >> >I had the same problem. But as soon as I disabled external > >> >> cache in BIOS, > >> >> it > >> >> >worked just fine. You might want to try that... > >> >> >Tell me if it helps. > >> >> >Andrei. > >> >> > > >> >> >-----Original Message----- > >> >> >From: Kerry Davis [mailto:kedavis@uswest.net] > >> >> >Sent: Tuesday, November 14, 2000 3:34 PM > >> >> >To: freebsd-questions@FreeBSD.ORG > >> >> >Subject: make world crashing repeatedly > >> >> > > >> >> > > >> >> >What causes Fatal Signal 27 and Fatal Signal 26 during "make > >> >> world?" I > >> >> >haven't been able to find ANY information on the problem. > >> >> > > >> >> >My first attempt to cvsup from 4.1 to Stable seemed to be > >> >> okay, everything > >> >> >apparently was ftp'd successfully over my DSL connection. > >> >> but "make world" > >> >> >died after about 7 hours, with the "fatal signal 27" > >> >> message. no other > >> >> >explanation given. > >> >> > > >> >> >following that, I did "make clean" as someone suggested, and > >> >> tried "make > >> >> >world" again. that time, it ran for about 12 hours, and > >> >> died with "fatal > >> >> >signal 26" showing "cc: Internal compiler error: program cc1 > >> >> got fatal > >> >> >signal 26" then "error code 1" and "stop in > >> >> >/usr/src/gnu/libexec/uucp/libunix" followed by "stop in" and > >> >> "error code 1" > >> >> >again for each level up: /usr/src/gnu/libexec/uucp, then > >> >> >/usr/src/gnu/libexec, then /usr/src/gnu, then /usr/src > >> >> > > >> >> >any suggestions? > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > >> >> >To Unsubscribe: send mail to majordomo@FreeBSD.org > >> >> >with "unsubscribe freebsd-questions" in the body of the message > >> >> > > >> >> > >> >> > >> >> > >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org > >> >> with "unsubscribe freebsd-questions" in the body of the message > >> >> > >> > > >> > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A11D049.DA8F7E42>