From mboxrd@z Thu Jan 1 00:00:00 1970 From: Phillip Susi Subject: Re: Possibly SATA related freeze killed networking and RAID Date: Mon, 03 Dec 2007 12:15:19 -0500 Message-ID: <475439A7.6060108@cfl.rr.com> References: <20071120220512.46b9e975@the-village.bc.nu> <20071126120649.GC4701@ucw.cz> <474CCA82.7030000@gmail.com> <474F3A4B.3080304@cfl.rr.com> <474F530D.8090302@gmail.com> <47505A63.8070507@cfl.rr.com> <4750A33C.4080509@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from iriserv.iradimed.com ([72.242.190.170]:58561 "EHLO iradimed.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750866AbXLCRPR (ORCPT ); Mon, 3 Dec 2007 12:15:17 -0500 In-Reply-To: <4750A33C.4080509@gmail.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Tejun Heo Cc: Pavel Machek , Alan Cox , noah , Linux Kernel Mailing List , linux-ide@vger.kernel.org Tejun Heo wrote: > Surprise, surprise. There's no way to tell whether the controller > raised interrupt or not if command is not in progress. As I said > before, there's no IRQ pending bit. While processing commands, you can > tell by looking at other status registers but when there's nothing in > flight and the controller determines it's a good time to raise a > spurious interrupt, there's no way you can tell. That dang SFF > interface is like 15+ years old. > > But we can still make things pretty robust. We're working on it. > > Thanks. > It sounds like you mean that you know the controller did NOT raise the interrupt ( intentionally/correctly ) if there was no command in progress, as opposed to not being able to tell. Unless there is some condition under which it is valid for the controller to raise an interrupt when it had no commands in progress? And if that's the case and there's know way to know WHY, that's a broken design.