Re: [9fans] Uh oh, disk problems.

[Dan Cross <cross@math.psu.edu>]

In article <20010412130455.A012D19A01@mail.cse.psu.edu> you write:
>Although it's not good that your drive is going bad, it's good that
>it's not the driver.

Ha!  Maybe for you.  ;-)

Nah, I too, am glad that the driver isn't at fault---software problems
always seem far more insideous than a simple case of bad hardware.  My
only real complaint about the driver is that it didn't emit a more
informative diagnostic, but that's largely an asthetic issue.

>Next time I delve into the driver I'm going to make it more interrupt
>driven so you won't see the Inil interrupt.

Cool.  btw- the Inil seems to be printed in response to a call to
atanop() which is called after ataready() times out in
atastartgenio().  Why the Inil message is printed out is sort of
unclear to me.  My suspicion is atatstartgenio() is attempting to abort
an operation, which has ceased to exist.  I suppose a simple way to get
rid of the message would be to add a state flag to the data structure
which describes the controller state that says, ``I'm aborting an
operation....'' and the test for that in atainterrupt(), but I'm very
unfamiliar with the issue, so I doubt that would be correct.  ;-)

	- Dan C.