linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@mcmartin.ca>
To: Al Niessner <Al.Niessner@jpl.nasa.gov>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where is the interrupt going?
Date: Wed, 21 Nov 2007 21:20:04 -0500	[thread overview]
Message-ID: <20071122022004.GB9265@fattire.cabal.ca> (raw)
In-Reply-To: <1195693710.5544.240.camel@morte.jpl.nasa.gov>

On Wed, Nov 21, 2007 at 05:08:30PM -0800, Al Niessner wrote:
> On with the detailed technical information. I developed a kernel module
> for an PCI card back in 2.4, moved it to 2.6.3, then 2.6.11 or so and
> now I am trying to move it to 2.6.22. When I began the to move to
> 2.6.22, I changed all of the deprecated calls for finding the card on
> the PCI bus, modified the interrupt handler prototype, and changed my
> readvv/writev to aio_read/aio_write following
> http://lwn.net/Articles/202449/. So initialization looks like this:
> 

Hi Al,

>From the sounds of it, you might have an interrupt routing problem. Can
you describe the machine you have this plugged into? Possibly attaching
a copy of "dmesg" and "/proc/interrupts"?

Feel free to attach the driver source to your email if the size is
reasonable (which it sounds like it is.)

As a "big hammer" in case it is an APIC problem, please try booting the
kernel with the "noapic" parameter.

cheers,
	Kyle

  parent reply	other threads:[~2007-11-22  2:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-22  1:08 Where is the interrupt going? Al Niessner
2007-11-22  1:56 ` Alan Cox
2007-11-22  2:14   ` Kyle McMartin
2007-11-22  2:16 ` Jesper Juhl
2007-11-22 23:56   ` niessner
2007-11-22  2:20 ` Kyle McMartin [this message]
2007-11-23  0:48   ` niessner
2007-11-23  1:25     ` Alan Cox
2007-11-23  1:58       ` Bartlomiej Zolnierkiewicz
2007-11-23 10:36         ` Alan Cox
2007-11-23  3:18     ` Marin Mitov
2007-11-23  4:31       ` niessner
2007-11-23  8:16       ` Jiri Slaby
2007-11-22  2:50 ` Arjan van de Ven
2007-11-23 21:53 ` Benjamin Herrenschmidt
2007-11-26 22:49   ` Al Niessner
     [not found] <fa.KsmqgW5tYuaXUkIKwnbJk9eJIAI@ifi.uio.no>
     [not found] ` <fa.JGl5fAfWYHut6bLbEcD35M84qbY@ifi.uio.no>
     [not found]   ` <fa.4GMGd+vtd9BoH5cWYyPKXdddZG4@ifi.uio.no>
2007-11-23  1:20     ` Robert Hancock

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=20071122022004.GB9265@fattire.cabal.ca \
    --to=kyle@mcmartin.ca \
    --cc=Al.Niessner@jpl.nasa.gov \
    --cc=linux-kernel@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).