igb on a Nehalem system, buildworld stats

Jack Vogel jfvogel at gmail.com
Thu Jan 8 09:16:47 PST 2009


I have not seen a problem like this ever, what is the link partner
of each NIC and if you switch the ports what happens?

We have Nehalem's in the validation lab but I have not had an
excuse to install on one so far, I guess now I do :)

Jack

On Thu, Jan 8, 2009 at 6:16 AM, Mars G Miro <spry at anarchy.in.the.ph> wrote:

> Hi guys,
>
>   I just got on my hands today a NEHALEM system:
>
> 2 x 5560 Nehalem CPU (2.8GHz, 8MB cache memory, 6.4GT/sec [QPI])
> 12GB 1333Mhz DDR3 Memory
> 1 x 500GB SATA HDD
>
>  FreeBSD 7.1-RELEASE/amd64 install fine, however I seemed to be
> having problems w/ its built-in Intel NICs:
>
> igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>        options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
>        ether 00:30:48:c5:db:e2
>        inet6 fe80::230:48ff:fec5:dbe2%igb0 prefixlen 64 scopeid 0x1
>        media: Ethernet autoselect (100baseTX <full-duplex>)
>        status: active
> igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>        options=19b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4>
>        ether 00:30:48:c5:db:e3
>        inet6 fe80::230:48ff:fec5:dbe3%igb1 prefixlen 64 scopeid 0x2
>        inet 172.17.32.32 netmask 0xffff0000 broadcast 172.17.255.255
>        media: Ethernet autoselect (1000baseTX <full-duplex>)
>        status: active
>
> The first NIC would always want 100baseTX no matter how I'd ifconfig
> down/up it, so I just had to use the 2nd NIC. Unfortunately, this too
> is having problems. Like being unable to 'see' some machines on the
> same network segment. Some other machines are accessible. And yes I've
> double-checked the network stuff (cables, switch, IP settings) and my
> conclusion is b0rky NICs.
>
> pciconf -lvc:
> igb0 at pci0:1:0:0:        class=0x020000 card=0x10c915d9 chip=0x10c98086
> rev=0x01 hdr=0x00
>    vendor     = 'Intel Corporation'
>    class      = network
>    subclass   = ethernet
>    cap 01[40] = powerspec 3  supports D0 D3  current D0
>    cap 05[50] = MSI supports 1 message, 64 bit, vector masks
>    cap 11[70] = MSI-X supports 10 messages in map 0x1c enabled
>    cap 10[a0] = PCI-Express 2 endpoint
> igb1 at pci0:1:0:1:        class=0x020000 card=0x10c915d9 chip=0x10c98086
> rev=0x01 hdr=0x00
>    vendor     = 'Intel Corporation'
>    class      = network
>    subclass   = ethernet
>    cap 01[40] = powerspec 3  supports D0 D3  current D0
>    cap 05[50] = MSI supports 1 message, 64 bit, vector masks
>    cap 11[70] = MSI-X supports 10 messages in map 0x1c enabled
>    cap 10[a0] = PCI-Express 2 endpoint
>
> So anyone else having igb problems? I'm downloading 200812-CURRENT now
> (is tehre gonna be a 200901-CURRENT ISO soon? :-p), I'd like to try
> that, but checking cvs seem only a handful of changes.
>
> Also I did some buildworlds:
>  make -j8 buildworld
>    2846.900u 2266.188s 15:50.43 537.9%     6375+2082k 10084+7937io
> 1482pf+0w
>  make -j16 buildworld
>    3518.254u 2175.593s 14:23.29 659.5%     6656+2147k 26165+8546io
> 4300pf+0w
>  make -j32 buildworld
>    3582.897u 4437.710s 18:03.88 739.9%     6528+2125k 5725+7930io 1555pf+0w
>
> Verbose dmesg: http://pastebin.com/f5f799561
>
> Thanks!
>
>
> --
> cheers
> mars
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>


More information about the freebsd-stable mailing list