From owner-freebsd-current Mon Dec 15 12:24:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA09612 for current-outgoing; Mon, 15 Dec 1997 12:24:54 -0800 (PST) (envelope-from owner-freebsd-current) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA09263 for ; Mon, 15 Dec 1997 12:23:03 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.com [204.244.210.252] by pop.uniserve.com with smtp (Exim 1.73 #1) id 0xhh0y-0002nT-00; Mon, 15 Dec 1997 12:21:20 -0800 Date: Mon, 15 Dec 1997 12:21:18 -0800 (PST) From: Tom To: Greg Lehey cc: FreeBSD current users Subject: Re: UFS problems on -current (panic: ffs_alloccg: map corrupted) In-Reply-To: <19971215194623.30917@lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Dec 1997, Greg Lehey wrote: > I've been having a large number of these panics in the last few days > after replacing significant parts of my system. In each case, the ... > First, the changes: > > Old New > > P54C, 133 MHz K6/233 > Old motherboard, IWill P55XB2, Intel TX chipset > forgot the name > 96 MB SIMM memory 128 MB mixed EDO SIMM and SDRAM > Adaptec 1542A and Adaptec 2940UW and 2940 host adapters > 2940 host adapters > IDE system disk IDE system disk > > I've checked all sorts of things, including: Except the RAM. Mixed SIMMs and SDRAM can be hairy. Tom