Date: Thu, 02 Jul 1998 21:20:10 -0400 From: "Michael R. Gile" <gilem@wsg.net> To: freebsd-stable@FreeBSD.ORG Subject: 2.2 and SMI conflicts (was: signal 10 errors) Message-ID: <199807030127.SAA14079@hub.freebsd.org> In-Reply-To: <199806301611.MAA05306@brain.zeus.leitch.com> References: <Tom's messageof "Mon, June 29, 1998 22:33:08 -0700"regarding "Re: determining ecc errors on freebsd-stable"id <Pine.BSF.3.96.980629223112.1069B-100000@shell.uniserve.ca> <19980629184220.15472@supersex.com> <Pine.BSF.3.96.980629223112.1069B-100000@shell.uniserve.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
>This is a new install of freebsd-stable, and it causes these errors >during long builds, namely kernels and big apps. I have tested the >system with all the diags i could find, including Norton and AMI, >which turned up nothing. The strange thing is that this system almost >always exhibits this problem when building a freebsd kernel, but the >stock installation of RedHat 5.1 works fine, built at least 10 kernels >in a row with no errors like this. well, after searching high and low for hardware failures, i found a section in the BIOS for this machine for SMI. This was set to enabled, and had the following individual settings - automatic system reboot - over temperature alarm - ecc scrubbing turning off any of these individually did not get rid of the signal 10 problem. However, disabling the SMI totally makes 2.2-stable run rocksolid. it is now performed almost 400 kernel compiles with not so much as a hiccup. Any comments on this apparent incompatibility? Thanks. ====================================================== Michael Gile gilem@wsg.net President (518)435-0682 Web Services Group http://www.wsg.net/ 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?199807030127.SAA14079>