Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 6 Dec 1997 11:40:18 +0100
From:      Philippe Regnauld <regnauld@deepo.prosa.dk>
To:        Kris Kennaway <kkennawa@physics.adelaide.edu.au>
Cc:        freebsd-current@FreeBSD.ORG
Subject:   Re: wd0 interrupt timeout
Message-ID:  <19971206114018.41854@deepo.prosa.dk>
In-Reply-To: <Pine.OSF.3.90.971206201515.28502A-100000@bragg>; from Kris Kennaway on Sat, Dec 06, 1997 at 08:25:32PM %2B1030
References:  <Pine.OSF.3.90.971206201515.28502A-100000@bragg>

next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway writes:
> 
> For the past several days (the first time being on Dec 2 as shown) I've been 
> seeing the following messages popping up:

	[...]

> The system will completely hang for several seconds - no process 
> activity, no disk activity, nothing - then the drive in question makes 
> the "powering up" sound it does when I first power up the machine, the 
> error appears on the console and activity resumes.

	You have auto-spindown / APM enable in the BIOS, and your
	disk spins down when it's been idle for some time (definable).

	The timeout is a warning when the disk doesn't respond to commands
	right away -- you usually don't see this on laptops since 2.5" disks
	usually spin up faster.

	Shouldn't be too harmful.

-- 
 -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]-
  "Pluto placed his bad dog at the entrance of Hades to keep the dead IN and
             the living OUT! The archetypical corporate firewall?"
   - S. Kelly Bootle, about Cerberus ["MYTHOLOGY", in Marutukku distrib] -



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971206114018.41854>