From owner-freebsd-bugs Tue Aug 1 22:10: 7 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 3739437BAFD for ; Tue, 1 Aug 2000 22:10:05 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id WAA24730; Tue, 1 Aug 2000 22:10:05 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 1 Aug 2000 22:10:05 -0700 (PDT) Message-Id: <200008020510.WAA24730@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Chris Hardie Subject: Re: kern/16740: kernel panics Reply-To: Chris Hardie Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/16740; it has been noted by GNATS. From: Chris Hardie To: freebsd-gnats-submit@FreeBSD.ORG Cc: Sheldon Hearn , Joakim Henriksson Subject: Re: kern/16740: kernel panics Date: Wed, 2 Aug 2000 00:04:33 -0500 (EST) Given the recent prognosis of "this could take a while", we need to take action to make our system more stable, so it is my intention to move from our SCSI drive to an IDE drive sometime in the next few days. I realize this limits opportunities to debug the problem on our system, so I wanted to make sure you didn't need anything else from us before we made the switch. I also wanted to note that we've been able to isolate the panics/crashes to happening 99% of the time during the run of a particular software package which does produce significant disk activity. If examining anything about this software would be useful, please let me know (again, sooner rather than later). Thanks for all your help thus far. Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message