From owner-freebsd-scsi Sat May 16 23:56:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13659 for freebsd-scsi-outgoing; Sat, 16 May 1998 23:56:39 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13653 for ; Sat, 16 May 1998 23:56:38 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id AAA01616; Sun, 17 May 1998 00:52:14 -0600 (MDT) Date: Sun, 17 May 1998 00:52:14 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199805170652.AAA01616@narnia.plutotech.com> To: The Hermit Hacker cc: scsi@FreeBSD.ORG Subject: Re: Atrocious transfer rates... Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Basically, it describes the problem (under Linux, at least) as: > > "The LED-light indicating SCSI activity on the computer front shines > constantly for about 30 secs, goes out for about 10 secs after which the > SCSI bus appears to be reset (my CD ROM-drive is activated momentarily) > and I can use the system again. " > - http://confused.ume.maine.edu/~aic7xxx/aic7xxx/4988.html > > Now, I'm curious, but assuming that this is a bus hang (even with > the CAM drivers in place), why isn't the system able to recover? > > The report is based on the same drive as mine, including Rev... The bug in the L912 firmware causes the drive to spaz and never release the bus. If the drive wedges and fails to respond to a bus reset, there isn't anything that the OS can do other than possibly ask the operator to power cycle the device. Upgrade your firmware already... -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message