From: Steven Scholz <steven.scholz@imc-berlin.de>
To: "Eric D. Mudama" <edmudama@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: no DRQ after issuing MULTWRITE_EXT ?
Date: Thu, 01 Feb 2007 10:30:18 +0100 [thread overview]
Message-ID: <45C1B32A.80606@imc-berlin.de> (raw)
In-Reply-To: <311601c90702010125k788a681fv2ec27de98ab05a72@mail.gmail.com>
Eric,
>> I am seeing kernel messages like
>>
>> [ 1284.480000] hda: status timeout: status=0xd0 { Busy }
>> [ 1284.480000] ide: failed opcode was: unknown
>> [ 1284.480000] hda: no DRQ after issuing MULTWRITE_EXT
>> [ 1284.490000] ide0: unexpected interrupt, status=0x80, count=1
>> [ 1284.830000] ide0: reset: success
>> ...
>
> Do you see this on every multiblock PIO write? Or just occasionally?
Only occasionally.
--
Steven
next prev parent reply other threads:[~2007-02-01 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 9:18 no DRQ after issuing MULTWRITE_EXT ? Steven Scholz
2007-02-01 9:25 ` Eric D. Mudama
2007-02-01 9:30 ` Steven Scholz [this message]
2007-02-01 13:06 ` Sergei Shtylyov
2007-02-01 13:33 ` Steven Scholz
2007-02-01 13:39 ` Sergei Shtylyov
2007-02-01 16:02 ` Steven Scholz
2007-02-01 16:06 ` Sergei Shtylyov
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=45C1B32A.80606@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=edmudama@gmail.com \
--cc=linux-ide@vger.kernel.org \
/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).