From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Uh oh, disk problems.
Date: Thu, 12 Apr 2001 09:04:53 -0400 [thread overview]
Message-ID: <20010412130455.A012D19A01@mail.cse.psu.edu> (raw)
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
next reply other threads:[~2001-04-12 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 13:04 jmk [this message]
2001-04-12 18:06 ` Dan Cross
-- strict thread matches above, loose matches on Subject: below --
2001-04-12 18:15 jmk
2001-04-12 18:56 ` Dan Cross
2001-04-11 0:40 jmk
2001-04-11 2:00 ` Dan Cross
2001-04-11 2:57 ` Dan Cross
2001-04-11 3:13 ` Jim McKie
2001-04-12 6:06 ` Dan Cross
2001-04-11 0:33 Dan Cross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010412130455.A012D19A01@mail.cse.psu.edu \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).