From owner-freebsd-security  Fri May 25 17:56:35 2001
Delivered-To: freebsd-security@freebsd.org
Received: from mail.cs.ait.ac.th (mail.cs.ait.ac.th [192.41.170.16])
	by hub.freebsd.org (Postfix) with ESMTP id F208637B422
	for <freebsd-security@FreeBSD.ORG>; Fri, 25 May 2001 17:56:30 -0700 (PDT)
	(envelope-from Olivier.Nicole@ait.ac.th)
Received: from bazooka.cs.ait.ac.th (on@bazooka.cs.ait.ac.th [192.41.170.2])
	by mail.cs.ait.ac.th (8.11.3/8.9.3) with ESMTP id f4QCLwY13565;
	Sat, 26 May 2001 19:21:59 +0700 (ICT)
From: Olivier Nicole <Olivier.Nicole@ait.ac.th>
Received: (from on@localhost)
	by bazooka.cs.ait.ac.th (8.8.5/8.8.5) id HAA24510;
	Sat, 26 May 2001 07:55:34 +0700 (ICT)
Date: Sat, 26 May 2001 07:55:34 +0700 (ICT)
Message-Id: <200105260055.HAA24510@bazooka.cs.ait.ac.th>
To: steve@napanet.net
Cc: veldy@veldy.net, glassfish@frogbox.dyndns.org,
	freebsd-security@FreeBSD.ORG
In-reply-to: <027f01c0e545$b4407080$3da2169d@napanet.net> (steve@napanet.net)
Subject: RE: Qmail + FreeBSD 4.3
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-security.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-security>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-security>
X-Loop: FreeBSD.org

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