Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262507AbVBXVtg (ORCPT ); Thu, 24 Feb 2005 16:49:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262506AbVBXVtg (ORCPT ); Thu, 24 Feb 2005 16:49:36 -0500 Received: from mail.tmr.com ([216.238.38.203]:24072 "EHLO gatekeeper.tmr.com") by vger.kernel.org with ESMTP id S262507AbVBXVsx (ORCPT ); Thu, 24 Feb 2005 16:48:53 -0500 Date: Thu, 24 Feb 2005 16:37:26 -0500 (EST) From: Bill Davidsen To: Folkert van Heusden cc: Rog?rio Brito , linux-kernel@vger.kernel.org Subject: Re: 2.6.11rc4: irq 5, nobody cared In-Reply-To: <20050224164407.GC5138@vanheusden.com> Message-ID: 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: 1854 Lines: 46 On Thu, 24 Feb 2005, Folkert van Heusden wrote: > > >>My linux laptop says: > > >>irq 5: nobody cared! > > >(...) > > >>Does anyone care? :-) > > >Well, I'm getting similar stack traces with my system and those are sure > > >scary, but it seems that my e-mails to the list are simply ignored, > > >unfortunately. > > I posted a similar thing, but the problem is not that you get the > > message. It means your hardware generated an unexpected interrupt. The > > kernel is reporting that fact as it should. > > The problem I had (not resolved) is that after the message > > DISABLING IRQ NN > > I continued to get interrupts! So the logic to disable the IRQ is not > > working correctly. > > In my case, the interrupt should NOT be disabled as my WIFI-interface is > behind it (via ndiswrappers). Well, that's debatable. The warnings mean that either the WiFi driver isn't catching them as it should, or that something else is generating the same (shared) IRQ. But what bothers me is that the kernel is trying to disable the IRQ and not doing it. I think that's an issue, since on my hardware that meant the system did nothing but write wrror messages to the log. > > > as you note, because the hardware is generating the condition, no one > > seems to care, even though there clearly is a problem in the disable > > logic. I found a way to fix my hardware thanks to some pointers I got, > > so I'm running, but I haven't heard that the base problem is fixed. > > Aight. -- bill davidsen CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. - 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/