From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: linux-ide@vger.kernel.org
Subject: Re: no DRQ after issuing MULTWRITE_EXT ?
Date: Thu, 01 Feb 2007 16:39:34 +0300 [thread overview]
Message-ID: <45C1ED96.3030701@ru.mvista.com> (raw)
In-Reply-To: <45C1EC18.5040802@imc-berlin.de>
Hello.
Steven Scholz wrote:
>>>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
>>
>> Looks like a spurious interrupt... Is your IDE IRQ shared with other
>>devices?
> No.
> But IIUC then first the HDD times out, the ide driver handles this and then
> an irq occurs which is probably the irq the driver was waiting for. And
The driver is *not* waiting for any IRQ after issuing MULTWRITE_EXT, that's
why it's "unexpected".
> since the driver already handled the timeout that (delayed) irq is of course
> "unexpected" ... (Just a guess)
>> Doubt it. The old ATA standard specified the maximum DRQ assertion
>>time of 20 ms.
> I know.
>>>And will the request issued again after the reset of the drive?
>> It should be.
> Thanks.
> Steven
MBR, Sergei
next prev parent reply other threads:[~2007-02-01 13:39 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
2007-02-01 13:06 ` Sergei Shtylyov
2007-02-01 13:33 ` Steven Scholz
2007-02-01 13:39 ` Sergei Shtylyov [this message]
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=45C1ED96.3030701@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=linux-ide@vger.kernel.org \
--cc=steven.scholz@imc-berlin.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.