From owner-freebsd-scsi Mon May 12 03:26:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA10149 for freebsd-scsi-outgoing; Mon, 12 May 1997 03:26:19 -0700 (PDT) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10144 for ; Mon, 12 May 1997 03:26:17 -0700 (PDT) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.8.5/8.8.5) with ESMTP id DAA28695; Mon, 12 May 1997 03:26:15 -0700 (PDT) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.5/8.8.5) with SMTP id DAA19730; Mon, 12 May 1997 03:26:14 -0700 (PDT) Date: Mon, 12 May 1997 03:26:14 -0700 (PDT) From: Chris Timmons To: Nick Esborn cc: freebsd-scsi@FreeBSD.ORG Subject: Re: 2.2.1R + Adaptec 2940UW + Microp 3243WT spontaneous reboot In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Nick, Something else you might try (after upgrading to 2.2-STABLE) would be to set up a serial console and trap the output with a printer, another machine running kermit, Paul Vixie's rtty, etc. In the past I've trapped clues to mystery reboots which otherwise were being lost. I also had a narrow 3243 which I finally sent back after a year+ of suffering with it. Under any kind of high load (eg. amanda backups, bonnie, etc) the drive would spin down and require a power-off reset before working again. (Your machine actually reboots all the way and comes back up, right?) Hopefully the -WT version of the drive is much newer than mine and really only needs Justin's latest to work great. I'm tracking 2.2-STABLE with 3940UW controllers, Atlas I and Barracuda drives and see nothing but stability and high performance since the last driver changes made just ahead of 1997-May-01. -Chris