From owner-freebsd-stable@FreeBSD.ORG  Tue Jan 27 10:06:58 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id C23E516A4CE
	for <freebsd-stable@freebsd.org>;
	Tue, 27 Jan 2004 10:06:58 -0800 (PST)
Received: from corb.mc.mpls.visi.com (corb.mc.mpls.visi.com [208.42.156.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0F5F443D67
	for <freebsd-stable@freebsd.org>;
	Tue, 27 Jan 2004 10:06:36 -0800 (PST)	(envelope-from veldy@veldy.net)
Received: from veldy.net (fuggle.veldy.net [209.98.200.33])
	by corb.mc.mpls.visi.com (Postfix) with ESMTP
	id 4066584AE; Tue, 27 Jan 2004 12:05:46 -0600 (CST)
Received: from localhost (localhost.veldy.net [127.0.0.1])
	by veldy.net (Postfix) with ESMTP
	id D0AF41CC65; Tue, 27 Jan 2004 12:05:45 -0600 (CST)
Received: from veldy.net ([127.0.0.1])
 by localhost (fuggle.veldy.net [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 00141-08; Tue, 27 Jan 2004 12:05:43 -0600 (CST)
Received: from 148L241 (localhost.veldy.net [127.0.0.1])
	by veldy.net (Postfix) with SMTP
	id 078731CC61; Tue, 27 Jan 2004 12:05:43 -0600 (CST)
Message-ID: <001d01c3e500$2e393e50$2637630a@nic.target.com>
From: "Thomas T. Veldhouse" <veldy@veldy.net>
To: "Marina Brown" <marina@surferz.net>,
	"Stanislav Grozev" <tacho@orbitel.bg>, <freebsd-stable@freebsd.org>
References: <20040127053642.GA10191@octavo.daemonz.org>
	<04012702040502.00743@tamiru>
Date: Tue, 27 Jan 2004 12:05:36 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Virus-Scanned: by amavisd-new at veldy.net
Subject: Re: FreeBSD constantly crashing
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Jan 2004 18:06:58 -0000


> The answer seems to be in your dmesg.
>
> pid 28555 (qmailadmin), uid 89: exited on signal 11
>
> ...that means you have bad ram in your new computer. It's common
> for computer stores to sell ram that is less than perfect. Replace the
> ram and you should be fine.
>
> Marina Brown
>
>

That is not the only reason for a signal 11 (or signal 10), just the most
quoted.  These can also be caused by over-optimized binaries.  I often see
signal 11s on all my FreeBSD machines when I optimize binaries (just with
the system compiler and -O -march=pentium4).  However, I NEVER see them
under Linux and all tests show normal for the hardware.  Simply put, I think
this is an overused stock answer to blame the hardware ... no offense to the
last poster intended.

Tom Veldhouse