From jjchin@jtnet.com  Sun Nov 24 10:11:06 1996
Received: from jtnet.com (jtnet.com [165.254.156.252])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA03141
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 24 Nov 1996 10:11:00 -0800 (PST)
Received: (from root@localhost) by jtnet.com (8.8.3/8.8.3)
	id NAA02345; Sun, 24 Nov 1996 13:10:56 -0500 (EST)
Message-Id: <199611241810.NAA02345@jtnet.com>
Date: Sun, 24 Nov 1996 13:10:56 -0500 (EST)
From: root@jtnet.com
Reply-To: root@jtnet.com
To: FreeBSD-gnats-submit@freebsd.org
Subject: wd1: interrupt timeout:
X-Send-Pr-Version: 3.2

>Number:         2094
>Category:       kern
>Synopsis:       wd1: interrupt timeout:
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          support
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov 24 10:20:07 PST 1996
>Closed-Date:    Sun Apr 26 10:19:48 PDT 1998
>Last-Modified:  Sun Apr 26 10:19:57 PDT 1998
>Originator:     SysAdmin
>Release:        FreeBSD 2.1.5
>Organization:
-- 
   System Administrator <root@jtnet.com>
   JTNET -- Just the Net (div. of Onesimus Enterprises International, Inc.)
>Environment:
Intel Pentium 166 System with 82MB RAM

	

>Description:
every so often I get the following kernel error message.
	wd1: interrupt timeout:
	wd1: status 58<seekdone,drq> error 0
	wd1: interrupt timeout:
	wd1: status 50<seekdone> error 1<no_dam>

	

>How-To-Repeat:
it repeats itself every so often, not user repeatable

	

>Fix:
I'm looking for a fix.  Can the interrupt timeout be extended?
	
	

>Release-Note:
>Audit-Trail:

From: mmcg@cs.monash.edu.au
To: freebsd-gnats-submit@freebsd.org, root@jtnet.com
Cc: mmcg@heraclitus.cs.monash.edu.au
Subject: Re: kern/2094: wd1: interrupt timeout:
Date: Thu, 23 Jan 1997 12:04:57 +1100 (EST)

 >every so often I get the following kernel error message.
 >        wd1: interrupt timeout:
 >        wd1: status 58&lt;seekdone,drq&gt; error 0
 >        wd1: interrupt timeout:
 >        wd1: status 50&lt;seekdone&gt; error 1&lt;no_dam&gt;
 
 I had this - it happens when the drive spins itself down
 after being idle for a while.  The interrupt timeout is
 reported by the kernel while the drive is spinning up again.
 It appears to have no effect on the disk - I've never lost
 data, etc.
 
 This behaviour appears to depend on both your motherboard and
 drive; I have a Quantum Sirocco 2550AT which does it in one
 of my machines but not the other, whereas other drives do not
 spin down in either machine.
 
 In any case, a workaround I used was to touch a file on each
 drive every 30 seconds (via a script started from rc.local).
 
 Cheers,
 
     Mike.
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Sun Apr 26 10:19:48 PDT 1998 
State-Changed-Why:  
timed out 
>Unformatted:
