From owner-freebsd-hackers Thu Oct 24 21:20:48 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id VAA19292 for hackers-outgoing; Thu, 24 Oct 1996 21:20:48 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id VAA19280 for ; Thu, 24 Oct 1996 21:20:41 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA02664; Fri, 25 Oct 1996 00:20:02 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Fri, 25 Oct 1996 00:20 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id WAA17149; Thu, 24 Oct 1996 22:47:43 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id WAA14873; Thu, 24 Oct 1996 22:48:19 -0400 (EDT) Date: Thu, 24 Oct 1996 22:48:19 -0400 (EDT) From: Thomas David Rivers Message-Id: <199610250248.WAA14873@lakes.water.net> To: ghelmer@cs.iastate.edu, ponds!freefall.cdrom.com!freebsd-hackers, ponds!ponds!rivers Subject: Re: Daily panic's with 2.1.5R. Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I finally swapped everything out of that box into a GW2K P-90 box (the > only hardware that changed was the motherboard, case, and power supply) & > upgraded it to 2.1.5, and when I checked it five or six weeks later, it > had been up solid since the upgrade (I left that job soon after the swap). > I figure it was something due to the early PCI implementation. Anyway, to > the point -- bad hardware seemed to be the cause of the troubles. The way > news pounds on the I/O subsystem seems to point out transient hardware > problems, so perhaps that could be related to your problem? > > Just a thought, > Guy Helmer Thanks for the insight - I had given that some thought myself... However, I've seen this panic on an AHA 1542B with a reliable SCSI disk and a new IDE controller and brand new IDE drive (both on the same ISA machine - non PCI.) As far as I've determined thus far, the frequency of the problem seems related to the the different parameters used to newfs the file system... particularly the number of inodes. - Dave R. -