tech-net archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: problems with PCIX-bus NICs
On Wed, Jul 15, 2009 at 02:26:37PM +0200,
6bone%6bone.informatik.uni-leipzig.de@localhost wrote:
> hello,
>
> I am using a Dell 1850. The onboard Intel NICs works fine.
> Additional PCIX cards are not working correct.
>
> ifconfig wm0
> wm0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>
> capabilities=2bf80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Tx,UDP6CSUM_Tx>
> enabled=0
> address: 00:04:23:c3:96:78
> media: Ethernet autoselect (1000baseT full-duplex)
> status: active
> inet6 2001:638:c:a00a::3 prefixlen 64
> inet6 fe80::204:23ff:fec3:9678%wm0 prefixlen 64 scopeid 0x1
>
> dmesg | grep wm0
> wm0 at pci2 dev 12 function 0: Intel i82546GB 1000BASE-T Ethernet, rev. 3
> wm0: interrupting at ioapic0 pin 16
> wm0: 64-bit 100MHz PCIX bus
> wm0: 256 word (8 address bits) MicroWire EEPROM
> wm0: Ethernet address 00:04:23:c3:96:78
> makphy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY, rev. 5
>
>
> bash-4.0# ping6 2001:638:c:a00a::2
> PING6(56=40+8+8 bytes) 2001:638:c:a00a::3 --> 2001:638:c:a00a::2
> 16 bytes from 2001:638:c:a00a::2, icmp_seq=0 hlim=64 time=15239.578 ms
>[...]
>
> I have changed the Intel NIC and also tested a Broadcom based NIC on
> different PCIX Slots. Always the same behavior.
>
> The same test with a onboard NIC reports a ping time less than 1 ms.
>
>
> Any Ideas what could be the problem?
I also have Dells 1850s at work. They suffers from interrupt routing
problems with NetBSD (what you see here smeels like interrupt from the
adapter are not making it to the driver's interrupt handler).
On a NetBSD 5.0 system I had to disable ACPI to get a add-on SCSI adapter
working.
--
Manuel Bouyer, LIP6, Universite Paris VI.
Manuel.Bouyer%lip6.fr@localhost
NetBSD: 26 ans d'experience feront toujours la difference
--
Home |
Main Index |
Thread Index |
Old Index