From: Reid Hekman <reid.hekman@ndsu.nodak.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: PCI SCSI interrupt clash
Date: 08 Jan 2002 04:17:41 -0600 [thread overview]
Message-ID: <1010485105.2044.2.camel@zeus> (raw)
In-Reply-To: <5.1.0.14.0.20020108203421.00af4940@pop-server.bigpond.net.au>
In-Reply-To: <5.1.0.14.0.20020108203421.00af4940@pop-server.bigpond.net.au>
On Tue, 2002-01-08 at 03:46, Glenn Geers wrote:
> enclose the win2k interrupt allocation for your perusal and comment (it's
> weird!)
...
> System Information report written at: 08/01/2002 08:44:11 PM
> [IRQs]
>
> IRQ Number Device
> 5 Sound Blaster 16 or AWE32 or compatible (WDM)
> 128 Matrox Millennium G400 DualHead MAX
> 14 Primary IDE Channel
> 15 Secondary IDE Channel
> 11 Intel 82371AB/EB PCI to USB Universal Host Controller
> 36 Adaptec AHA-2940U2/U2W PCI SCSI Controller
> 52 Realtek RTL8139/810X Family PCI Fast Ethernet NIC
> 56 Hauppauge Win/TV 878/9 VFW Video Driver
> 56 Hauppauge Win/TV 878/9 VFW Audio Driver
> 60 Creative SB Live! Value (WDM)
> 64 Texas Instruments OHCI Compliant IEEE 1394 Host Controller
> 1 PC/AT Enhanced PS/2 Keyboard (101/102-Key)
> 4 Communications Port (COM1)
> 3 Communications Port (COM2)
> 6 Standard floppy disk controller
> 8 System CMOS/real time clock
> 13 Numeric data processor
> 12 Other Logitech Mouse PS/2
>
> I hope someone can shed some light on the very high (>20) interrupt
> numbers. I'd really like and will help to get to the bottom of the problem.
Win2k with the ACPI HAL will reroute IRQ's to 256 "virtual" IRQ's, hence
the high numbers.
What happens if you twiddle ACPI/PnP OS in the BIOS?
And do you really expect a PCI bus overclocked past 37MHz to survive
with 5 PCI cards? You get 40 lashes with a wet noodle >:-(
Regards,
Reid
prev parent reply other threads:[~2002-01-08 10:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-08 9:46 PCI SCSI interrupt clash Glenn Geers
2002-01-08 10:17 ` Reid Hekman [this message]
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=1010485105.2044.2.camel@zeus \
--to=reid.hekman@ndsu.nodak.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox