From owner-cvs-sys  Sun Oct 12 01:55:39 1997
Return-Path: <owner-cvs-sys>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id BAA09474
          for cvs-sys-outgoing; Sun, 12 Oct 1997 01:55:39 -0700 (PDT)
          (envelope-from owner-cvs-sys)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA09443;
          Sun, 12 Oct 1997 01:55:25 -0700 (PDT)
          (envelope-from joerg@FreeBSD.org)
From: Joerg Wunsch <joerg@FreeBSD.ORG>
Received: (from joerg@localhost)
	by freefall.freebsd.org (8.8.6/8.8.5) id BAA02393;
	Sun, 12 Oct 1997 01:54:49 -0700 (PDT)
Date: Sun, 12 Oct 1997 01:54:49 -0700 (PDT)
Message-Id: <199710120854.BAA02393@freefall.freebsd.org>
To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-sys@FreeBSD.ORG
Subject: cvs commit: src/sys/scsi scsi_base.c sd.c
Sender: owner-cvs-sys@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

joerg       1997/10/12 01:54:48 PDT

  Modified files:
    sys/scsi             scsi_base.c sd.c 
  Log:
  Remove the call to scsi_start_unit() from sd_open().  It was causing
  much grieve to owners of IBM drives when used in conjunction with
  tagged command queuing, and didn't serve any purpose at all (since
  experiments have proven that it simply didn't work).
  
  Instead, call scsi_start_unit() once in sd_attach(), so in case the
  drive has been configured to `remote start', it will spin up there.
  (If it has spun down later, it must have been because of administrator
  action (scsi(8)) anyway.)
  
  While i was at it, bump the timeout for scsi_start_unit() to 30
  seconds.  10 seconds were way too few for most drives.
  
  Revision  Changes    Path
  1.52      +2 -2      src/sys/scsi/scsi_base.c
  1.112     +7 -6      src/sys/scsi/sd.c