Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1163711AbWLGXEI (ORCPT ); Thu, 7 Dec 2006 18:04:08 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1163742AbWLGXEI (ORCPT ); Thu, 7 Dec 2006 18:04:08 -0500 Received: from iabervon.org ([66.92.72.58]:1332 "EHLO iabervon.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1163711AbWLGXEF (ORCPT ); Thu, 7 Dec 2006 18:04:05 -0500 Date: Thu, 7 Dec 2006 18:04:04 -0500 (EST) From: Daniel Barkalow To: Greg KH cc: Jeff Garzik , Linus Torvalds , linux-kernel@vger.kernel.org Subject: Re: Disable INTx when enabling MSI In-Reply-To: <20061207223949.GA18477@suse.de> Message-ID: References: <20061207223949.GA18477@suse.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 885 Lines: 21 On Thu, 7 Dec 2006, Greg KH wrote: > Care to take Jeff's proposed patch, verify that it works and forward it > on to me? I'll test it tomorrow. Testing disables my network, and making sure the problem exists without the patch kills my disk controller, so I need to sit at the computer for a while. I assume that I've got the only known device that demonstrates the need for this? Off topic: would it be wise as a general rule to somehow shut down devices whose interrupts get disabled by the "nobody cared!" code? Or maybe call their interrupt handlers periodically to keep them alive? -Daniel *This .sig left intentionally blank* - 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/