From owner-freebsd-hackers Tue Feb 18 02:21:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA24323 for hackers-outgoing; Tue, 18 Feb 1997 02:21:08 -0800 (PST) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA24316 for ; Tue, 18 Feb 1997 02:20:55 -0800 (PST) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id VAA23461 for hackers@freebsd.org; Tue, 18 Feb 1997 21:20:51 +1100 (EST) From: David Dawes Message-Id: <199702181020.VAA23461@rf900.physics.usyd.edu.au> Subject: Re: dup alloc panic In-Reply-To: from J Wunsch at "Feb 18, 97 09:38:30 am" To: hackers@freebsd.org Date: Tue, 18 Feb 1997 21:20:51 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL30 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >As Thomas David Rivers wrote: > >> With that in mind; I can say that I've only machines that >> have experienced this problem are 386s. I don't have the where-with-all >> to put together a 486/586 that I can trash in this manner. >> >> Also, this doesn't seem to jive with Joerg's similar problem when >> newfs's MFS file systems. [Joerg - was that even a 386 machine?] > >Yes, my scratch machine is a 386 one. I can't remember i have >observed it somewhere else. I'm coming in on this thread a bit late, I hope the subject line is still valid. I've had a dup alloc panic recently, with a RELENG_2_2 kernel dating from a couple of weeks ago (Pentium, SCSI disk on an NCR controller). It happened while re-populating a disk after doing a newfs. I ended up doing the newfs again (fsck had too much trouble), and repopulating (but in a different order). It's been OK since. David