Date: Sat, 26 May 2001 07:55:34 +0700 (ICT) From: Olivier Nicole <Olivier.Nicole@ait.ac.th> To: steve@napanet.net Cc: veldy@veldy.net, glassfish@frogbox.dyndns.org, freebsd-security@FreeBSD.ORG Subject: RE: Qmail + FreeBSD 4.3 Message-ID: <200105260055.HAA24510@bazooka.cs.ait.ac.th> In-Reply-To: <027f01c0e545$b4407080$3da2169d@napanet.net> (steve@napanet.net)
next in thread | previous in thread | raw e-mail | index | archive | help
Well, shame on me, I did have a machine going sig 11 this Thursday, and it was not hardware problem. It was a real sementation fault in a piece of code I did not tested enough. Correcting the NULL pointer did the trick. But then it was not a random error either. Adding some cooling may help a lot too. Remember that most PC case do not provide adequate cooling to any component (read disk) except CPU. http://www.cs.ait.ac.th/laboratory/fan/ Some trick that work well, remove memory and clean the contacts with a ruber (eraser). Be sure you don't put back ruber dirt in the memory slot. Be sure you don't touch the memory contacts with your fingers. It applies also for PCI/ISA cards, as well as for CPU that used this vertical slot. Best regards, Olivier >Same here, I have found that random sig 11's are often caused by memory or >CPU problems. One thing to try is underclocking - if you are running 133 >underclock to 100 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105260055.HAA24510>