Date: Wed, 22 Jan 1997 17:10:01 -0800 (PST) From: mmcg@cs.monash.edu.au To: freebsd-bugs Subject: Re: kern/2094: wd1: interrupt timeout: Message-ID: <199701230110.RAA15781@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/2094; it has been noted by GNATS.
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<seekdone,drq> error 0
> wd1: interrupt timeout:
> wd1: status 50<seekdone> error 1<no_dam>
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199701230110.RAA15781>