On Tue, Aug 01, 2000 at 10:34:39PM -0400, Thor Lancelot Simon wrote:
> Actually, I think there's a more serious bug here.
> 
> Since *we told* the hard disk to spin down, the fact that it's not ready the
> next time we issue it a command shouldn't be an error.  Certainly, it should
> not cause the DMA/PIO modes to be adjusted.  It seems to me we either need
> to explicitly tell the drive to spin up, or if we can't do that, ignore the

We can't because we don't know when the drive spins down (that's why an
in-kernel PM for disks would be good :)

> fact that it's not ready so long as the first command we hand it after we
> spin it down completes successfully within a reasonable timeout, where
> "reasonable" takes into account that the drive had to spin up first.

This timeout should already be enouth (it's something like 10s).
Also, it looks strange that the disk spins up just after spinning down.
Looks like it went off in the middle of a command.

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
--