From: folkert@vanheusden.com (Folkert van Heusden)
To: Bill Davidsen <davidsen@tmr.com>
Cc: Rog?rio Brito <rbrito@ime.usp.br>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.11rc4: irq 5, nobody cared
Date: Thu, 24 Feb 2005 17:44:15 +0100 [thread overview]
Message-ID: <20050224164407.GC5138@vanheusden.com> (raw)
In-Reply-To: <421CF352.2090200@tmr.com>
> >>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).
> 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.
Folkert van Heusden
Op zoek naar een IT of Finance baan? Mail me voor de mogelijkheden!
+------------------------------------------------------------------+
|UNIX admin? Then give MultiTail (http://vanheusden.com/multitail/)|
|a try, it brings monitoring logfiles to a different level! See |
|http://vanheusden.com/multitail/features.html for a feature list. |
+------------------------------------------= www.unixsoftware.nl =-+
Phone: +31-6-41278122, PGP-key: 1F28D8AE
next prev parent reply other threads:[~2005-02-24 16:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 15:56 2.6.11rc4: irq 5, nobody cared Folkert van Heusden
2005-02-20 16:40 ` Rogério Brito
2005-02-20 17:19 ` Matthias-Christian Ott
2005-02-20 18:05 ` Rogério Brito
2005-02-20 20:00 ` Matthias-Christian Ott
2005-02-21 18:43 ` Bartlomiej Zolnierkiewicz
2005-02-21 18:50 ` Jeff Garzik
2005-02-21 19:42 ` Wichert Akkerman
2005-02-21 20:32 ` Jeff Garzik
2005-02-21 21:48 ` Wichert Akkerman
2005-02-23 21:41 ` Bill Davidsen
2005-02-21 19:02 ` Rogério Brito
2005-02-23 21:19 ` Bill Davidsen
2005-02-24 16:44 ` Folkert van Heusden [this message]
2005-02-24 21:37 ` Bill Davidsen
2005-02-20 16:43 ` Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050224164407.GC5138@vanheusden.com \
--to=folkert@vanheusden.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rbrito@ime.usp.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.