All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Walter <srwalter@hapablap.dyn.dhs.org>
To: linux-kernel@vger.kernel.org
Subject: "No IRQ known for interrupt pin A..." error message
Date: Sat, 18 Nov 2000 18:11:10 -0600	[thread overview]
Message-ID: <20001118181110.A424@hapablap.dyn.dhs.org> (raw)

During boot, I get the message:

PCI: No IRQ known for interrupt pin A of device 00:00.1. Please try
using pci=biosirq.

If I boot with pci=biosirq, as the error message suggests, I get the
same error, save the part about trying with pci=biosirq.  This is with
version 2.4.0-test11-pre7 and as far back at least as test10-final.  I
don't remember seeing this error on earlier versions, though I may have
glossed over it.  Another possibly relevant part of the boot messages
is:

PCI: PCI BIOS revision 2.10 entry at 0xfdb81, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Using IRQ router default [1039/0008] at 00:01.0
PCI: Cannot allocate resource region 9 of bridge 00:02.0

My motherboard uses the SiS530 chipset, and the bridge at 00:02.0 is the
AGP bridge.  If anyone's interested, I have the entire boot log.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-11-19  0:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-19  0:11 Steven Walter [this message]
2000-11-19 19:20 ` "No IRQ known for interrupt pin A..." error message Martin Mares
2000-11-19 20:01   ` Alex Romosan
2000-11-20  0:18     ` Gerhard Mack
2000-11-20  1:32       ` Alex Romosan
2000-11-19 21:18   ` Steven Walter
2000-11-21 15:09   ` rob
  -- strict thread matches above, loose matches on Subject: below --
2000-11-19 21:50 Pavel Rabel

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=20001118181110.A424@hapablap.dyn.dhs.org \
    --to=srwalter@hapablap.dyn.dhs.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.