Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934968AbXK3PBN (ORCPT ); Fri, 30 Nov 2007 10:01:13 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932459AbXK3PA6 (ORCPT ); Fri, 30 Nov 2007 10:00:58 -0500 Received: from rtr.ca ([76.10.145.34]:3030 "EHLO mail.rtr.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754383AbXK3PA5 (ORCPT ); Fri, 30 Nov 2007 10:00:57 -0500 Message-ID: <475025A7.9010107@rtr.ca> Date: Fri, 30 Nov 2007 10:00:55 -0500 From: Mark Lord User-Agent: Thunderbird 2.0.0.9 (X11/20071031) MIME-Version: 1.0 To: Pavel Machek Cc: Alan Cox , Phillip Susi , Tejun Heo , noah , Linux Kernel Mailing List , linux-ide@vger.kernel.org Subject: Re: Possibly SATA related freeze killed networking and RAID References: <20071120220512.46b9e975@the-village.bc.nu> <20071126120649.GC4701@ucw.cz> <474CCA82.7030000@gmail.com> <474F3A4B.3080304@cfl.rr.com> <20071130131344.07b75f45@the-village.bc.nu> <20071126075517.GA4141@ucw.cz> In-Reply-To: <20071126075517.GA4141@ucw.cz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1239 Lines: 32 Pavel Machek wrote: > On Fri 2007-11-30 13:13:44, Alan Cox wrote: >>> Why does a single spurious interrupt cause it to be shut down? I can >> It doesn't. >> >>> see if the interrupt is stuck on and keeps interrupting constantly, but >>> if it's just the occasional spurious interrupt, why not just ignore it >>> and move on? >> The interrupt is usually level triggered so it continues to create >> interrupts until you silence it. The thresholds are about 10,000 >> interrupt events and on newer kernels we also reset the count if we don't >> see any for a while. That works for most stuff except the thinkpad >> bluetooth problem. > > Which is confirmed hw problem now, btw. ... What problem is that, exactly? My Dell has an internal USB BT adapter that briefly appears and then disappears again on resume (or stays if I have "enabled" it via the BIOS key). I wonder if that has anything to do with the (new in) 2.6.23 pauses that machine has on resume (about every 10th time). Cheers - 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/