[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MP and Intel Pro 1000 NIC problem

This may be of interest (maybe not).

I have an Intel SE7501WV2 motherboard (twin Xeon) with twin PRO 1000 network built into it, and both interfaces work fine on the generic 3.6 MP image...

ioapic0 at mainbus0: apid 8 pa 0xfec00000, version 20, 24 pins
ioapic1 at mainbus0: apid 9 pa 0xfec81000, version 20, 24 pins
ioapic2 at mainbus0: apid 10 pa 0xfec81400, version 20, 24 pins
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x254c rev 0x01
"Intel E7500 DRAM" rev 0x01 at pci0 dev 0 function 1 not configured
ppb0 at pci0 dev 3 function 0 "Intel E7500 MCH HI_C vppb 1" rev 0x01
pci1 at ppb0 bus 1
"Intel P64H2 IOxAPIC" rev 0x04 at pci1 dev 28 function 0 not configured
ppb1 at pci1 dev 29 function 0 "Intel 82870P2 P64H2 PCI-PCI" rev 0x04
pci2 at ppb1 bus 2
"Intel P64H2 IOxAPIC" rev 0x04 at pci1 dev 30 function 0 not configured
ppb2 at pci1 dev 31 function 0 "Intel 82870P2 P64H2 PCI-PCI" rev 0x04
pci3 at ppb2 bus 3
em0 at pci3 dev 7 function 0 "Intel PRO/1000MT DP (82546EB)" rev 0x01: apic 9 int 6 (irq 9), address: 00:07:e9:23:87:9a
em1 at pci3 dev 7 function 1 "Intel PRO/1000MT DP (82546EB)" rev 0x01: apic 9 int 7 (irq 9), address: 00:07:e9:23:87:9b
ppb3 at pci3 dev 8 function 0 "DEC 21154 PCI-PCI" rev 0x05
pci4 at ppb3 bus 4
ppb4 at pci4 dev 0 function 0 "DEC 21154 PCI-PCI" rev 0x05
pci5 at ppb4 bus 5
ami0 at pci5 dev 0 function 0 "AMI MegaRAID" rev 0x20: apic 9 int 0 (irq 9) Dell 493/64b/lhc
ami0: FW 196T, BIOS v3.33, 128MB RAM
ami0: 2 channels, 0 FC loops, 1 logical drives
scsibus0 at ami0: 40 targets



Mark Pecaut wrote:
> On Wed, Nov 17, 2004 at 12:28:34PM +0000, phlex wrote:
>>when switching from bsd to bsd.mp kernel in a fresh 3.6 install, my
>>network stops working. 
>>Ifconfig shows correctly configured interfaces, ping to self works,
>>media sensing works to, but the network can't be reached.
> ...
>>isa_intr_establish: no MP mapping found
> I think it's interrupt stuff in the mp kernel.  I used to work on a 
> system with this problem but that was when bsd.mp was still quite 
> experimental and I was waiting for things to settle down to file a 
> bug report.  I don't work there anymore and don't have access to 
> that system.  Of course, now all I can give are vague details of the 
> system (sorry Nick, no dmesg!):
> Dual Intel Xeon,
> fxp0 and em0
> 3ware pos
> Quite similar to your system.  I believe there is a message in the
> archives indicating that the developers are aware of this problem
> but didn't have enough systems exhibiting the problem to fix it.
> Try and file a bug report?
> -mark
My mail describing the problem with the em and fxp nics on the system 
Mark mentions (with dmesg inline) is at:


Jeff Ross

Visit your host, monkey.org