From mboxrd@z Thu Jan  1 00:00:00 1970
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Uh oh, disk problems.
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Message-Id: <20010412130455.A012D19A01@mail.cse.psu.edu>
Date: Thu, 12 Apr 2001 09:04:53 -0400
Topicbox-Message-UUID: 8179a3a8-eac9-11e9-9e20-41e7f4b1d025

On Thu Apr 12 02:07:24 EDT 2001, cross@math.psu.edu wrote:
> In article <001c01c0c235$6bf8da20$16096887@cs.research.belllabs.com> you write:
> >
> >If you are really seeing a NOP then that means the drive command didn't
> >complete in 30s and the driver tried to abort it. That's pretty unusual and
> >that
> >code hasn't been exercised much and it's perfectly plausible for the NOP
> >interrupt to come after the driver thinks the command is finished. You
> >could try putting in some debugging for that condition and see what the
> >state really is before the nop happens.
>
> Thanks for the information, Jim.  I found out through further instrumenting
> the code that it is indeed a bad block on the disk.  Sigh.  I think I'll
> replace the disk before it gets any worse.
>
> >Are you using DMA?
>
> Yes, I am....
>
> 	- Dan C.

Although it's not good that your drive is going bad, it's good that
it's not the driver.

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

--jim