I have a device driver for a fibre channel HBA that works correctly
with a PCI device but not a PCI-X device. The problem with the PCI-X
device is that the interrupt handler never gets involked eventhough
the chip status indicates that it is interrupting. This is using
4.7-RELEASE on a dual Xeon based system (E7500 mother board) from
SuperMicro. I loaded another OS with this same system/HBA and don't
observe this problem.
Below is an edited mptable dump. The problematic PCI-X device is
pci2:1:0 and pci2:1:1. pci3:3:0 is the PCI version of the product
which uses the same driver and does get its interrupt handler
called.
Is there any other info people want to see? Has anyone seen a problem
like this before? If not, any idea where I should start looking?
MP Config Table Header:
physical address: 0x0009fd70
signature: 'PCMP'
base table length: 380
version: 1.4
checksum: 0x55
OEM ID: ' '
Product ID: 'Kings Canyon'
OEM table pointer: 0x00000000
OEM table size: 0
entry count: 36
local APIC address: 0xfee00000
extended table length: 0
extended table checksum: 0
-------------------------------------------------------------------------------
MP Config Base Table Entries:
---
Processors: APIC ID Version State Family Model Step Flags
6 0x14 BSP, usable 15 2 4 0x3febfbff
0 0x14 AP, usable 15 2 7 0xbfebfbff
1 0x14 AP, usable 15 2 7 0xbfebfbff
7 0x14 AP, usable 15 2 4 0x3febfbff
---
Bus: Bus ID Type
0 PCI
1 PCI
2 PCI
3 PCI
4 PCI
5 ISA
---
I/O APICs: APIC ID Version State Address
2 0x20 usable 0xfec00000
3 0x20 usable 0xfec80000
4 0x20 usable 0xfec80400
---
I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN#
ExtINT active-hi edge 5 0 2 0
...
INT active-lo level 2 1:A 4 0
INT active-lo level 2 1:B 4 1
INT active-lo level 3 3:A 3 4
--
Chuck Tuffli <chuck_tuffli AT NO_SPAM agilent DOT com>
Agilent Technologies, Storage and Networking
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
