mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Alistair John Strachan <s0348365@sms.ed.ac.uk>,
	mcgrof@ruslug.rutgers.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: Assuming someone else called the IRQ
Date: Sat, 26 Jun 2004 18:15:52 +0100	[thread overview]
Message-ID: <20040626181552.C30532@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200406261808.31860.s0348365@sms.ed.ac.uk>; from s0348365@sms.ed.ac.uk on Sat, Jun 26, 2004 at 06:08:31PM +0100

On Sat, Jun 26, 2004 at 06:08:31PM +0100, Alistair John Strachan wrote:
> 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
>...
>  19:    8748235   IO-APIC-level  ohci1394, yenta, eth0

You don't say what eth0 is.  At a guess, it's a prism54 card, because the
only place I find that message in the kernel is in the prism54 driver:

drivers/net/wireless/prism54/islpci_dev.c:
	printk(KERN_DEBUG "Assuming someone else called the IRQ\n");

I'd imagine that the OHCI1394 generates a fair number of interrupts,
so... this highlights the problem of leaving debugging printk's,
even at KERN_DEBUG level in a driver interrupt path.

At a guess, Luis R. Rodriguez may be the maintainer for prism54,
so...

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

  reply	other threads:[~2004-06-26 17:15 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 [this message]
2004-06-26 17:39   ` Alistair John Strachan
2004-06-27 16:22     ` Luis R. Rodriguez
2004-06-26 17:20 ` Grzegorz Kulewski
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=20040626181552.C30532@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@ruslug.rutgers.edu \
    --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®