public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Paris <jim@jtan.com>
To: linux-kernel@vger.kernel.org
Subject: PCI IRQ problems -- update
Date: Sat, 11 Dec 2004 12:35:38 -0500	[thread overview]
Message-ID: <20041211173538.GA21216@jim.sh> (raw)

This is an update on my laptop's IRQ problem I mentioned back in Oct:
  http://lkml.org/lkml/2004/10/15/20
    
In short, all PCI IRQs are routed via ACPI to PIC IRQ 9.  When the
PIIX IDE device is enabled, it pulls on that interrupt until it gets
disabled ("nobody cared").  ide0 then continues to work on IRQ 14, but
all other devices are broken since IRQ 9 is disabled.

My previous solution was to use Alan Cox's "irqpoll" patch which
allowed the other devices to still function.  That's a hack and I
wanted to find a real way to fix it.

It turns out that IDE is the only device connected to LNKC.  I changed
the ACPI DSDT so that LNKC points to the unused IRQ 5, and all of my
problems magically went away.  This is still a hack, but seems to work.

I'm not sure how to get to the root cause of the problem, though.  For
starters: where _should_ the INTA of the IDE card go, if anywhere?  If
my laptop's IDE is routed to and pulling on IRQ 9, how can it still be
functioning on IRQ 14?  Or, if the routing doesn't matter, is there
anything I can do to prevent it from pulling on 9?

-jim

             reply	other threads:[~2004-12-11 17:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-11 17:35 Jim Paris [this message]
2004-12-11 16:45 ` PCI IRQ problems -- update Alan Cox
2004-12-11 20:02   ` Jim Paris
2004-12-12 11:32     ` Alan Cox
2004-12-11 20:23   ` Jim Paris
2004-12-11 22:03     ` [PATCH] " Jim Paris
2004-12-12 11:43       ` Alan Cox
2004-12-12 11:29     ` Alan Cox

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=20041211173538.GA21216@jim.sh \
    --to=jim@jtan.com \
    --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