Re: Solving suspend-level confusion

[Pavel Machek <pavel@ucw.cz>]

Hi!

> > Yes, I don't call suspend for it because I can be sure the drivers are
> > idle (before beginning to write the image, freeze all process, flush all
> > dirty buffers and suspend all other drivers, I then wait on my own I/O
> > until it is flushed too). I know it's broken to do so, but it was a good
> > work around for wearing out the thing by spinning it down and then
> > immediately spinning it back up, and I wasn't sure what the right state
> > to try to put it in is (sound familiar?!). If you want to tell me how I
> > could tell it to quiesce without spin down, I'll happily do that.
> 
> Very easy... with the current code, just use state 4 for the round
> of suspend callbacks, ide-disk will then avoid spinning down.

There are some network drivers that test for "4" and fails suspend
with something like "invalid suspend state" :-(.

								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!