Date: Mon, 18 Sep 2000 20:36:16 -0400 From: "Paul A. Howes" <pahowes@fair-ware.com> To: <freebsd-stable@freebsd.org> Subject: RE: Make world is dying... Message-ID: <PCEHKHHDDCJMAMJLBLNCMECEDCAA.pahowes@fair-ware.com>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format. ------=_NextPart_000_0040_01C021B0.17B1E8B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit All- I think I found the problem. I have used the memory before, it was known good. I swapped it out, and had the same problem. I tried a second, identical, CPU with a new heat sink, and still had the same problem. I received a thought-provoking email from one kind FreeBSD user that pointed me to the CPU I was using: The Cyrix P-166 itself, was the problem. The email is reproduced below: If it's occurring in the same place consistently, it's not a RAM failure; I used to have a Cx-6x86L-PR166 (ie. Pre-MMX Cx) and it died at roughly the same place in a makeworld consistently; at the time I figured that I'd cooked the CPU in it's lifetime (was prone to overheating), ditched it in favour of a Pentium-100 and it all worked well.... no changes made other than the CPU. That RAM is still doing sterling service in a dual PPro system now. If that's still the case regardless, then it's either a Cyrix CPU bug or a code generation bug in GCC that affects them specifically. This turned out to be exactly my case. I installed a spare Pentium-100 I have, and buildworld is working flawlessly, so far. Evidently, there's a CPU-specific bug in "cc1" that causes it to crash on this particular Cyrix processor. I do not know enough about the differences between the older-generation Cyrix processors and the Pentium processors of the same vintage to draw any conclusions, but I would be learn more about this phenomenon. -- Paul A. Howes pahowes@fair-ware.com ------=_NextPart_000_0040_01C021B0.17B1E8B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 5.50.4207.2601" name=3DGENERATOR></HEAD> <BODY> <P><SPAN class=3D078202800-19092000><FONT=20 face=3DNewCenturySchlbk>All-</FONT></SPAN></P> <P><SPAN class=3D078202800-19092000><FONT face=3DNewCenturySchlbk>I = think I found=20 the problem. I have used the memory before, it was known = good. I=20 swapped it out, and had the same problem. I tried a second, = identical, CPU=20 with a new heat sink, and still had the same problem. I received a = thought-provoking email from one kind FreeBSD user that pointed me to = the CPU I=20 was using: The Cyrix P-166 itself, was the problem. The = email is=20 reproduced below:</FONT></SPAN></P> <BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px"> <P><SPAN class=3D078202800-19092000><FONT face=3DNewCenturySchlbk>If = it's=20 occurring in the same place consistently, it's not a RAM failure; = I<SPAN=20 class=3D078202800-19092000> </SPAN>used to have a Cx-6x86L-PR166 (ie. = Pre-MMX=20 Cx) and it died at roughly the<SPAN class=3D078202800-19092000> = </SPAN>same=20 place in a makeworld consistently; at the time I figured that I'd<SPAN = class=3D078202800-19092000> </SPAN>cooked the CPU in it's lifetime = (was prone to=20 overheating), ditched it in<SPAN class=3D078202800-19092000> = </SPAN>favour of a=20 Pentium-100 and it all worked well.... no changes made other<SPAN=20 class=3D078202800-19092000> </SPAN>than the CPU. That RAM is still = doing=20 sterling service in a dual PPro system<SPAN = class=3D078202800-19092000>=20 </SPAN>now.</FONT></P> <P><FONT face=3DNewCenturySchlbk>If that's still the case regardless, = then it's=20 either a Cyrix CPU bug or a<SPAN class=3D078202800-19092000> = </SPAN>code=20 generation bug in GCC that affects them=20 specifically.</FONT></P></SPAN></BLOCKQUOTE> <P><SPAN class=3D078202800-19092000><FONT face=3DNewCenturySchlbk>This = turned out to=20 be exactly my case. I installed a spare Pentium-100 I have, and = buildworld=20 is working flawlessly, so far. Evidently, there's a CPU-specific = bug in=20 "cc1" that causes it to crash on this particular Cyrix processor. = I do not=20 know enough about the differences between the older-generation Cyrix = processors=20 and the Pentium processors of the same vintage to draw any conclusions, = but I=20 would be learn more about this phenomenon.</FONT></SPAN></P> <P><FONT face=3DNewCenturySchlbk>--<SPAN class=3D078202800-19092000>=20 <BR></SPAN></FONT><EM><FONT face=3DNewCenturySchlbk>Paul A.=20 Howes<BR></FONT></EM><A href=3D"mailto:pahowes@fair-ware.com"><EM><FONT=20 face=3DNewCenturySchlbk>pahowes@fair-ware.com</FONT></EM></A></P> <P><FONT face=3DNewCenturySchlbk></FONT> </P> <P><FONT face=3DNewCenturySchlbk></FONT> </P></BODY></HTML> ------=_NextPart_000_0040_01C021B0.17B1E8B0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PCEHKHHDDCJMAMJLBLNCMECEDCAA.pahowes>