mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Grzegorz Kulewski <kangur@polcom.net>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Assuming someone else called the IRQ
Date: Sat, 26 Jun 2004 19:20:23 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0406261911530.30521@alpha.polcom.net> (raw)
In-Reply-To: <200406261808.31860.s0348365@sms.ed.ac.uk>

On Sat, 26 Jun 2004, Alistair John Strachan wrote:

> Hi,
> 
> Every kernel in the 2.6 serious so far has exhibited the same problem; after 
> some time of running my desktop system, I get:
> 
> Assuming someone else called the IRQ

Maybe it is just some debug that can be safely ignored and removed from 
source? If two or more devices share an IRQ this is normal that when IRQ  
happens all of these drivers' IRQ routine is called. So maybe one of the 
drivers checks that this is not its device and prints this debug?


>  19:    8748235   IO-APIC-level  ohci1394, yenta, eth0

Maybe you are using eth0 and yenta is printing this debug...
Do you think that assigning the same IRQ for eth0 and yenta is good idea?  
Some network cards seem to raise _many_ IRQs...

Try to grep kernel source for this string and ask the maintainer for the 
driver that produces this message.

Hope this will help a little.


Grzegorz Kulewski


  parent reply	other threads:[~2004-06-26 17:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-26 17:08 Alistair John Strachan
2004-06-26 17:15 ` Russell King
2004-06-26 17:39   ` Alistair John Strachan
2004-06-27 16:22     ` Luis R. Rodriguez
2004-06-26 17:20 ` Grzegorz Kulewski [this message]
2004-06-26 17:42   ` Alistair John Strachan
2004-06-27  8:02 Margit Schubert-While

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=Pine.LNX.4.58.0406261911530.30521@alpha.polcom.net \
    --to=kangur@polcom.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s0348365@sms.ed.ac.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®