From: Mark Lord <lkml@rtr.ca>
To: Nick Warne <nick@linicks.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hda: irq timeout: status=0xd0 DMA question
Date: Sun, 26 Feb 2006 09:09:13 -0500 [thread overview]
Message-ID: <4401B689.5050106@rtr.ca> (raw)
In-Reply-To: <200602261308.47513.nick@linicks.net>
Nick Warne wrote:
..
> Feb 19 14:05:31 quake kernel: hda: irq timeout: status=0xd0 { Busy }
> Feb 19 14:05:31 quake kernel:
> Feb 19 14:05:31 quake smartd[405]: Device: /dev/hda, not capable of SMART
> self-check
> Feb 19 14:05:31 quake smartd[405]: Sending warning via mail to
> root@localhost ...
> Feb 19 14:05:31 quake kernel: hda: status timeout: status=0xd0 { Busy }
> Feb 19 14:05:31 quake kernel:
> Feb 19 14:05:31 quake kernel: hda: DMA disabled
> Feb 19 14:05:31 quake kernel: hda: drive not ready for command
> Feb 19 14:05:33 quake kernel: ide0: reset: success
..
> I dunno what happened to the drive that time (this is the only logs of the
> incident) and I turned DMA back on with hdparm - but my question is why is
> DMA turned off and then left off after a reset?
When I wrote that code in the mid-1990s, the number one causes of drives
getting confused (and needing to be reset again), were improper DMA timings,
cablings, and buggy DMA firmware.
So at the time, since DMA was a newish feature for IDE, we figured that
turning it off after reset was a Good Thing(tm).
And it was. A more modern implementation might try being more clever about
such stuff, and Tejun is working on something like that for libata.
In the meanwhile, you could have a shell script just loop in the background,
turning DMA back on periodically. If you care.
Cheers
next prev parent reply other threads:[~2006-02-26 14:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 13:08 hda: irq timeout: status=0xd0 DMA question Nick Warne
2006-02-26 14:09 ` Mark Lord [this message]
2006-02-26 14:15 ` Jesper Juhl
2006-02-26 17:01 ` Nick Warne
2006-02-26 17:07 ` Mark Lord
2006-02-26 17:17 ` Jesper Juhl
2006-02-26 17:20 ` Nick Warne
2006-02-26 17:35 ` Jesper Juhl
2006-02-26 18:10 ` Henrik Persson
2006-02-26 21:10 ` Nick Warne
2006-02-27 13:32 ` Mark Lord
2006-02-27 18:32 ` Nick Warne
2006-03-02 10:32 ` Nick Warne
[not found] <5KtPb-2oP-9@gated-at.bofh.it>
[not found] ` <5Kxzs-7M7-19@gated-at.bofh.it>
[not found] ` <5KxJa-7XQ-31@gated-at.bofh.it>
[not found] ` <5KxT2-8a6-15@gated-at.bofh.it>
[not found] ` <5KyFa-RL-1@gated-at.bofh.it>
2006-02-26 18:43 ` Robert Hancock
2006-02-26 18:49 ` Jesper Juhl
2006-02-26 20:32 ` Mark Lord
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=4401B689.5050106@rtr.ca \
--to=lkml@rtr.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@linicks.net \
/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).