From owner-freebsd-hackers  Tue Jan 21 15:42:14 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id PAA22772
          for hackers-outgoing; Tue, 21 Jan 1997 15:42:14 -0800 (PST)
Received: from rover.village.org (rover.village.org [204.144.255.49])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id PAA22765
          for <hackers@freebsd.org>; Tue, 21 Jan 1997 15:42:08 -0800 (PST)
Received: from rover.village.org [127.0.0.1] 
	by rover.village.org with esmtp (Exim 0.56 #1)
	id E0vmppO-00009W-00; Tue, 21 Jan 1997 16:42:06 -0700
Subject: Re: Spin down problem back? 
To: hackers@freebsd.org
In-reply-to: Your message of "Tue, 21 Jan 1997 14:51:34 MST."
		<E0vmo6R-0000Fx-00@rover.village.org> 
References: <E0vmo6R-0000Fx-00@rover.village.org>  
Date: Tue, 21 Jan 1997 16:42:06 -0700
From: Warner Losh <imp@village.org>
Message-Id: <E0vmppO-00009W-00@rover.village.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <E0vmo6R-0000Fx-00@rover.village.org> Warner Losh writes:
: I'm running a -current kernel from Nov 24.  I have just been able to
: recreate a spindown problem with my Jaz drive.

This problem also happens on a -current kernel from Jan 19, so this
has been broken for a while.

To recap: Accessing the raw device of a SCSI disk that has spun down
is now broken and causes that device to go offline forever.  Think JAZ
drive in spin down mode :-).

I recreated this problem five times in a row, and I have verified that
my SCSI bus is indeed properly terminated and seated by phyiscal
inspection and reseating of connectors.  No other problems on the
system can be seen.

Warner