From: Mike Frisch <mfrisch@saturn.tlug.org>
To: linux-kernel@vger.kernel.org
Subject: IRQ problems w/VIA Apollo VP2/97 & NCR 53c875
Date: Tue, 12 Jun 2001 20:46:47 -0400 [thread overview]
Message-ID: <20010612204647.A14088@saturn.tlug.org> (raw)
Summary: IRQ conflict on VIA Apollo VP2/97-based motherboard between
dual controllers on NCR 53c875 (Diamond Fireport 40). Kernel version is
2.4.5-ac9.
--- cut here ---
00:00.0 Host bridge: VIA Technologies, Inc. VT82C595/97 [Apollo VP2/97]
(rev 04)
Flags: bus master, 66Mhz, medium devsel, latency 64
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA
[Apollo VP] (rev 25)
Flags: bus master, medium devsel, latency 0
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 06)
(prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 64
I/O ports at 6000 [size=16]
--- cut here ---
When I attempt to mobprobe the ncr53c8xx module, I get the following
output:
SCSI subsystem driver Revision: 1.00
PCI: Found IRQ 11 for device 00:0b.0
IRQ routing conflict in pirq table for device 00:0b.0
IRQ routing conflict in pirq table for device 00:0b.1
It appears that something is getting confused and doesn't want to allow
the two controllers of this card to share the same IRQ.
Here is the relevent output from 'lspci -v':
--- cut here ---
00:0b.0 SCSI storage controller: Symbios Logic Inc. (formerly NCR)
53c875 (rev 14)
Subsystem: Diamond Multimedia Systems FirePort 40 Dual SCSI
Controller
Flags: bus master, medium devsel, latency 144, IRQ 10
I/O ports at 6c00 [size=256]
Memory at e2001000 (32-bit, non-prefetchable) [size=256]
Memory at e2002000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at <unassigned> [disabled] [size=64K]
00:0b.1 SCSI storage controller: Symbios Logic Inc. (formerly NCR)
53c875 (rev 14)
Subsystem: Diamond Multimedia Systems FirePort 40 Dual SCSI
Controller
Flags: bus master, medium devsel, latency 144, IRQ 10
I/O ports at 7000 [size=256]
Memory at e2003000 (32-bit, non-prefetchable) [size=256]
Memory at e2004000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at <unassigned> [disabled] [size=64K]
--- cut here --
There are no other devices using IRQ10. Is this a lost cause? This
controller and drives in their current configuration can be moved to an
Intel based machine and works flawlessly. I have yet to see this
controller work on this VIA motherboard.
Any assistance is appreciated.
Thanks,
Mike.
reply other threads:[~2001-06-13 0:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010612204647.A14088@saturn.tlug.org \
--to=mfrisch@saturn.tlug.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).