From: "Eric C. Cooper" <ecc@cmu.edu>
To: linux-kernel@vger.kernel.org
Subject: problems with CONFIG_PCI_USE_VECTOR in 2.6.1
Date: Fri, 9 Jan 2004 23:21:08 -0500 [thread overview]
Message-ID: <20040110042108.GB313@localhost> (raw)
When I tried a 2.6.1 kernel with CONFIG_PCI_USE_VECTOR, my onboard
Ethernet (sis900) produced nothing but watchdog timeouts. It worked
fine with the old IRQ routing.
When I looked in /var/log/syslog, I noticed that the Ethernet driver
was using a different IRQ, so I suspected the vector routing. I found
the following suspicious entries:
Jan 9 20:09:08 jaguar kernel: PCI: PCI BIOS revision 2.10 entry at 0xf11b0, last bus=1
Jan 9 20:09:08 jaguar kernel: PCI: Using configuration type 1
Jan 9 20:09:08 jaguar kernel: mtrr: v2.0 (20020519)
Jan 9 20:09:08 jaguar kernel: ACPI: Subsystem revision 20031002
Jan 9 20:09:08 jaguar kernel: IOAPIC[0]: Set PCI routing entry (2-20 -> 0xa9 -> IRQ 20 Mode:1 Active:1)
Jan 9 20:09:08 jaguar kernel: ACPI: SCI (IRQ20) allocation failed
Jan 9 20:09:08 jaguar kernel: ACPI-0133: *** Error: Unable to install System Control Interrupt Handler, AE_NOT_ACQUIRED
Jan 9 20:09:08 jaguar kernel: ACPI: Unable to start the ACPI Interpreter
Jan 9 20:09:08 jaguar kernel: Trying to free free IRQ20
Jan 9 20:09:08 jaguar kernel: ACPI: ACPI tables contain no PCI IRQ routing entries
Jan 9 20:09:08 jaguar kernel: PCI: Invalid ACPI-PCI IRQ routing table
Jan 9 20:09:08 jaguar kernel: PCI: Probing PCI hardware
Jan 9 20:09:08 jaguar kernel: PCI: Probing PCI hardware (bus 00)
Jan 9 20:09:08 jaguar kernel: Enabling SiS 96x SMBus.
Jan 9 20:09:08 jaguar kernel: PCI: Using IRQ router default [1039/0963] at 0000:00:02.0
Jan 9 20:09:08 jaguar kernel: PCI BIOS passed nonexistent PCI bus 0!
Jan 9 20:09:08 jaguar last message repeated 9 times
Jan 9 20:09:08 jaguar kernel: PCI BIOS passed nonexistent PCI bus 1!
Jan 9 20:09:08 jaguar kernel: PCI BIOS passed nonexistent PCI bus 0!
If anyone needs more information (kernel configs, syslog from the
non-USE_VECTOR kernel, etc) or if I can help in any way by trying
something out, please let me know.
--
Eric C. Cooper e c c @ c m u . e d u
next reply other threads:[~2004-01-10 4:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 4:21 Eric C. Cooper [this message]
2004-01-10 5:26 ` problems with CONFIG_PCI_USE_VECTOR in 2.6.1 Martin Schlemmer
2004-01-10 20:42 ` Eric C. Cooper
-- strict thread matches above, loose matches on Subject: below --
2004-01-10 15:36 Nakajima, Jun
2004-01-10 20:20 ` Eric C. Cooper
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=20040110042108.GB313@localhost \
--to=ecc@cmu.edu \
--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.