From owner-freebsd-hackers@FreeBSD.ORG  Wed Jul 16 08:53:00 2003
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id AFA4737B401
	for <hackers@freebsd.org>; Wed, 16 Jul 2003 08:53:00 -0700 (PDT)
Received: from l07.oase.research.kpn.com (l07.oase.research.kpn.com
	[139.63.192.207])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DCC6C43F93
	for <hackers@freebsd.org>; Wed, 16 Jul 2003 08:52:58 -0700 (PDT)
	(envelope-from k.j.koster@telecom.tno.nl)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 16 Jul 2003 17:52:57 +0200
Message-ID: <0DD8055E0FECF744B5FF8053F80C4A2D011F40E3@l07.oase.research.kpn.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: 4.8 panic "ffs_clusteralloc: map mismatch"
Thread-Index: AcNLpNDBTF3qofDsQECnB5U7ZgyErwADP2Ug
From: <k.j.koster@telecom.tno.nl>
To: <andr@dgap.mipt.ru>
cc: hackers@freebsd.org
Subject: RE: 4.8 panic "ffs_clusteralloc: map mismatch"
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jul 2003 15:53:01 -0000

Dear Andrew,

>=20
> My system has brand new MB (supermicro dual proc mainbord=20
> with U160 SCSI &=20
> fxp NIC integrated), P3 processor & memory (btw, ECC memory).=20
> Other components are not-so-new, but they worked flawlessly=20
> for about a year with another MB.=20
>
There is a little memory tester at memtest86.com that I always use on =
new systems. It works a bit like a pregnancy test: if it saysyou have =
memory errors, you have memory errors. If it says no errors, you still =
don't know if you have any.

Memory errors are hard to spot and may require subtle combinations of =
all systems components to crop up. Having said that, I found that most =
systems remain stable if they pass both a night of memtest86 and a make =
-j 8 world.

    Kees Jan

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
 You can't have everything.  Where would you put it?
                                     [Steven Wright]