From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 16 10:47:22 2003 Return-Path: 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 6D18937B401 for ; Wed, 16 Jul 2003 10:47:22 -0700 (PDT) Received: from dgap-gw.mipt.ru (dgap-gw.mipt.ru [194.85.81.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id E62C843F3F for ; Wed, 16 Jul 2003 10:47:20 -0700 (PDT) (envelope-from andrew@nas.dgap.mipt.ru) Received: (qmail 11113 invoked from network); 16 Jul 2003 17:47:20 -0000 Received: from unknown (HELO nas.dgap.mipt.ru) ([194.85.81.203]) (envelope-sender ) by dgap-gw.mipt.ru (qmail-ldap-1.03) with SMTP for ; 16 Jul 2003 17:47:20 -0000 Received: from nas.dgap.mipt.ru (localhost [127.0.0.1]) by nas.dgap.mipt.ru (8.12.8p1/8.12.8) with ESMTP id h6GHlJvt082361; Wed, 16 Jul 2003 21:47:19 +0400 (MSD) (envelope-from andrew@nas.dgap.mipt.ru) Received: (from andrew@localhost) by nas.dgap.mipt.ru (8.12.8p1/8.12.8/Submit) id h6GHlJvD082360; Wed, 16 Jul 2003 21:47:19 +0400 (MSD) Date: Wed, 16 Jul 2003 21:47:19 +0400 From: "Andrew L. Neporada" To: k.j.koster@telecom.tno.nl Message-ID: <20030716174719.GA82339@nas.dgap.mipt.ru> References: <0DD8055E0FECF744B5FF8053F80C4A2D011F40E3@l07.oase.research.kpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0DD8055E0FECF744B5FF8053F80C4A2D011F40E3@l07.oase.research.kpn.com> User-Agent: Mutt/1.4i 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 17:47:22 -0000 On Wed, Jul 16, 2003 at 05:52:57PM +0200, k.j.koster@telecom.tno.nl wrote: > Dear Andrew, > > > > > My system has brand new MB (supermicro dual proc mainbord > > with U160 SCSI & > > fxp NIC integrated), P3 processor & memory (btw, ECC memory). > > Other components are not-so-new, but they worked flawlessly > > for about a year with another MB. > > > 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. ;-) I always use exactly the same software for memory testing. This system passed it successfully. > > 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. Test run of 10 'make -j8 buildworld' started... > > Kees Jan > > ===================================================== > You can't have everything. Where would you put it? > [Steven Wright] Andrew.