Date: Fri, 10 Mar 2000 00:00:03 -0800 (PST) From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/7678: Problems with a 386-16 Message-ID: <200003100800.AAA44997@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/7678; it has been noted by GNATS. From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: <freebsd-gnats-submit@FreeBSD.org>, <hsu@clinet.fi> Cc: Subject: Re: kern/7678: Problems with a 386-16 Date: Thu, 9 Mar 2000 22:03:06 -0800 I have seen this kind of problem before as well on older 386/16 systems. It began sometime in the 2.2 series of kernels. In fact I think I submitted it as a pr that has subsequently been closed. I can confirm that this is not ram related - I've run all 2.2 series on 4MB. (the systems were very slow, of course) I do however believe this is a CPU bug. There is a well-known 80386 bug only present in early 16's that broke FPU support. (note that any surface-mount 386-16 is well after the bug was fixed) There are probably other ones as well. I believe that the triggering incident on this bug is a newer version of GCC, NOT the FreeBSD kernel. In my case, swapping out the 80386-16 CPU with another 80386-16 CPU fixed the problem. (obviously it was a socketed CPU) The only difference between the CPU's was that they were manufactured in different geographical locations. Otherwise both were marked as Intel CPU's. Ted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003100800.AAA44997>