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: "nobody cared!"
Date: Fri, 15 Oct 2004 04:37:22 -0400	[thread overview]
Message-ID: <20041015083722.GA3315@jim.sh> (raw)

I'm having some strange PCI IRQ problems on my new laptop (Panasonic
Toughbook CF-M34UTVZKM) under 2.6.8-1-686 (Debian).  I'm at a loss to
figure out their source, other than the fact that Toughbooks seem to
have a particularly crappy BIOS.

The errors are something like this (taken from default.txt, link below):
irq 9: nobody cared!
 [<c010841a>] __report_bad_irq+0x2a/0x90
 [<c0108510>] note_interrupt+0x70/0xb0
 [<c01087f0>] do_IRQ+0x120/0x130
 [<c0106a20>] common_interrupt+0x18/0x20
 [<c01200fe>] __do_softirq+0x2e/0x80
 [<c01b3b60>] acpi_irq+0x0/0x16
 [<c0120177>] do_softirq+0x27/0x30
 [<c01087cb>] do_IRQ+0xfb/0x130
 [<c0106a20>] common_interrupt+0x18/0x20
 [<c02124a2>] pci_conf1_write+0x92/0xf0
 [<c01b3e86>] acpi_os_write_pci_configuration+0x69/0x76
...

It seems that once some particular piece of PCI hardware gets
initialized, it causes a flood of unexpected interrupts.  The kernel
then disables IRQ 9, which basically breaks most of my devices because
that's the one they all share.

I captured the following boots for different command lines.  The ACPI
and non-ACPI cases die at different points, but with the same result.

root=/dev/hda1 ro console=ttyS0,115200n8
   https://jim.sh/svn/jim/devl/toughbook/log/default.txt

root=/dev/hda1 ro console=ttyS0,115200n8 acpi=off
   https://jim.sh/svn/jim/devl/toughbook/log/acpioff.txt

root=/dev/hda1 ro console=ttyS0,115200n8 acpi=off pci=usepirqmask
   https://jim.sh/svn/jim/devl/toughbook/log/usepirqmask.txt

lspci, lspci -vxxxn, and /proc/interrupts:
   https://jim.sh/svn/jim/devl/toughbook/log/lspci.txt

Could someone who knows more than me about PCI IRQs take a quick look
at those dumps and tell me if there's anything obvious that I'm
missing, or some way to work around the problem?

-jim

             reply	other threads:[~2004-10-15  8:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-15  8:37 Jim Paris [this message]
2004-10-15 13:19 ` PCI IRQ problems: "nobody cared!" Alan Cox
2004-10-15 18:51   ` Jim Paris
2004-10-16  5:55 ` Len Brown
2004-10-17  0:12   ` Jim Paris

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=20041015083722.GA3315@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