Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755383AbYLGS5a (ORCPT ); Sun, 7 Dec 2008 13:57:30 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753090AbYLGS5U (ORCPT ); Sun, 7 Dec 2008 13:57:20 -0500 Received: from idcmail-mo1so.shaw.ca ([24.71.223.10]:7310 "EHLO idcmail-mo1so.shaw.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752969AbYLGS5T (ORCPT ); Sun, 7 Dec 2008 13:57:19 -0500 X-Cloudmark-SP-Filtered: true X-Cloudmark-SP-Result: v=1.0 c=0 a=YgUFFZ79AAAA:8 a=-kRHijCJ5Q3qL_3XY7cA:9 a=q0g5g2MXn4dlLtandWxHQR6JrXYA:4 a=eIAGP7Fk3jIA:10 a=21q54A0nAXQA:10 Message-ID: <493C1C8F.5070003@shaw.ca> Date: Sun, 07 Dec 2008 12:57:19 -0600 From: Robert Hancock User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: Stefan Richter CC: Frans Pop , "Rafael J. Wysocki" , linux-kernel Subject: Re: [patch] ohci1394: don't leave interrupts enabled during suspend/resume References: <200812061316.38460.elendil@planet.nl> <200812061536.47894.elendil@planet.nl> <493AE8B3.7090000@shaw.ca> <493B42D1.7090600@shaw.ca> <493B953F.3070504@s5r6.in-berlin.de> In-Reply-To: <493B953F.3070504@s5r6.in-berlin.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1054 Lines: 24 Stefan Richter wrote: > Robert Hancock wrote: >> Stefan Richter wrote: >>> reg_write(ohci, OHCI1394_IntMaskClear, 0xffffffff); >>> >>> in ohci1394's .suspend() switches interrupts off. >> Presumably it should.. but the fact remains that if free_irq helps >> anything, then the device must be generating interrupts for some reason, > > Or another device: > http://www.gossamer-threads.com/lists/linux/kernel/896053 > > Questions for Frans, quoting tglx: > Do you have CONFIG_NET_POLL_CONTROLLER enabled in your .config? If yes, > can you please disable it and check whether the problem persists? Hmm, that case sounds like disable_irq on an MSI device redirecting the interrupts to the legacy INTx interrupt instead of actually disabling them? If this is what's happening here, then that's the bug.. -- 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/