From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergei Shtylyov Subject: Re: no DRQ after issuing MULTWRITE_EXT ? Date: Thu, 01 Feb 2007 16:39:34 +0300 Message-ID: <45C1ED96.3030701@ru.mvista.com> References: <45C1B079.3080704@imc-berlin.de> <45C1E5CD.8010707@ru.mvista.com> <45C1EC18.5040802@imc-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from gateway-1237.mvista.com ([63.81.120.155]:54041 "EHLO imap.sh.mvista.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1422850AbXBANjg (ORCPT ); Thu, 1 Feb 2007 08:39:36 -0500 In-Reply-To: <45C1EC18.5040802@imc-berlin.de> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Steven Scholz Cc: linux-ide@vger.kernel.org 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