Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755881Ab0HCKXZ (ORCPT ); Tue, 3 Aug 2010 06:23:25 -0400 Received: from cantor.suse.de ([195.135.220.2]:47464 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755801Ab0HCKXY (ORCPT ); Tue, 3 Aug 2010 06:23:24 -0400 Message-ID: <4C57EC58.4020301@suse.de> Date: Tue, 03 Aug 2010 12:15:52 +0200 From: Tejun Heo User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.2.7) Gecko/20100713 Thunderbird/3.1.1 MIME-Version: 1.0 To: Thomas Gleixner Cc: lkml , Jeff Garzik , Greg KH Subject: Re: [GIT PULL tip/genirq] Please pull from lost-spurious-irq References: <4C5033D9.7030800@kernel.org> <4C50349F.7020002@suse.de> <4C529F59.3020404@suse.de> <4C56E42D.5010300@suse.de> <4C56E5C7.90206@suse.de> <4C572327.7040801@suse.de> In-Reply-To: X-Enigmail-Version: 1.1.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1085 Lines: 28 Hello, On 08/03/2010 12:06 PM, Thomas Gleixner wrote: >> These problems do happen on intel chipset machines and is something >> which can be worked around with some effort. Eh, let's talk on the >> other reply. > > So you're saying that the ATA problem is restricted to Intel chipsets? > Do we know the root cause ? The original sentence is missing an 'also'. Severals have been root caused and worked around. For SATA, one of the notable problems was misinterpretation of nIEN (interrupt block bit on the ATA device side) on both device and host sides. In traditional IDE API, the interrupt bit is primarily under the control of the device, so it's pretty difficult to guarantee reliable operation from driver side only. For PATA, the device actually has full control of the interrupt line, so it's much worse. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/