SCIENTIFIC-LINUX-USERS Archives

April 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Raimondo Giammanco [VKICC]" <[log in to unmask]>
Reply To:
Raimondo Giammanco [VKICC]
Date:
Fri, 1 Apr 2011 22:34:51 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (156 lines)
Hello Alan,

  The other box where i tried the second e1g44etblk is a normal desktop 
with a single pci-e slot, the motherboard is a common  DQ965GF.

  I've installed the el-repo repository: the version of the driver is 
2.4.13, the same of the one I've installed with the intel tar.gz and 
rpmbuild on the supermicro.

  I've installed the driver as for your suggestion, rebooted the machine 
and tried iperf with this new driver:

before the iperf:
#############
lspci | grep -i ether
00:19.0 Ethernet controller: Intel Corporation 82566DM Gigabit Network 
Connection (rev 02)
03:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network 
Connection (rev 01)
03:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network 
Connection (rev 01)
04:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network 
Connection (rev 01)
04:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network 
Connection (rev 01)
############

############
  ethtool -i eth1
driver: igb
version: 2.4.13
firmware-version: 1.2-1
bus-info: 0000:03:00.0
###########

###########
  rpm -qa | grep kmod
kmod-igb-2.4.13-1.el6.elrepo.x86_64
###########

after the iperf:

###########
 From the machine from which I was doing the iperf -c:

when doing on eth0 (the onboard nic iwth e1000 driver)
[  4] local 10.1.0.134 port 5001 connected with 10.1.0.131 port 49729
[  4]  0.0-10.0 sec  1.10 GBytes   942 Mbits/sec
when doing on eth1 (the e1g44etblk)
[  5] local 10.1.0.134 port 5001 connected with 10.1.0.134 port 51211
[  5]  0.0-259.1 sec  86.1 MBytes  2.79 Mbits/sec

again a lot of errors in ifconfig:
eth1      Link encap:Ethernet  HWaddr 00:1B:21:7C:4E:0C
           inet addr:10.1.0.134  Bcast:10.1.7.255  Mask:255.255.248.0
           UP BROADCAST MULTICAST  MTU:1500  Metric:1
           RX packets:66919 errors:1322849926860 dropped:330712481715 
overruns:330712797030 frame:1322849926860
           TX packets:16073 errors:661424963430 dropped:0 overruns:0 
carrier:661424963430
           collisions:330712481715 txqueuelen:1000
           RX bytes:94263829 (89.8 MiB)  TX bytes:1061138 (1.0 MiB)

lspci changes as well:
00:19.0 Ethernet controller: Intel Corporation 82566DM Gigabit Network 
Connection (rev 02)
03:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network 
Connection (rev ff)
03:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network 
Connection (rev ff)
04:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network 
Connection (rev ff)
04:00.1 Ethernet controller: Intel Corporation 82576 Gigabit Network 
Connection (rev ff)

even if ethtool -i seems correct:
###############
ethtool -i eth1
driver: igb
version: 2.4.13
firmware-version: 1.2-1
bus-info: 0000:03:00.0
###############

Could it be related to the kernel version? In the standard repos there 
are no updated kernels, at least that I can see. Can you suggest any 
newer kernel version and where to find it?

Thanks again.

  Raimondo





On 01/04/2011 18:12, Alan Bartlett wrote:
> On 1 April 2011 16:47, Raimondo Giammanco [VKICC]<[log in to unmask]>  wrote:
>
>>   Currently I have the original box up and running with the pci card in
>> "hanged" mode.
>> 06:00.1 "Ethernet controller" "Intel Corporation" "82576 Gigabit Network
>> Connection" -rff -pff "" ""
>> 06:00.1 0200: 8086:10e8 (rev ff)
>> 09:00.0 "Ethernet controller" "Intel Corporation" "82576 Gigabit Network
>> Connection" -r01 "Super Micro Computer Inc" "Device 10c9"
> That is interesting.
>
> As I do not, at present, have access to a SL 6.0 system I've tested on
> my RHEL 6.0 based laptop. By using the "double grep" technique I see
> --
>
> [quote]
> [ajb@Duo2 ~]$ grep 8086 /lib/modules/*/modules.alias | grep -i 10c9
> /lib/modules/2.6.32-71.18.2.el6.x86_64/modules.alias:alias
> pci:v00008086d000010C9sv*sd*bc*sc*i* igb
> /lib/modules/2.6.32-71.el6.x86_64/modules.alias:alias
> pci:v00008086d000010C9sv*sd*bc*sc*i* igb
> [ajb@Duo2 ~]$ grep 8086 /lib/modules/*/modules.alias | grep -i 10e8
> /lib/modules/2.6.32-71.18.2.el6.x86_64/modules.alias:alias
> pci:v00008086d000010E8sv*sd*bc*sc*i* igb
> /lib/modules/2.6.32-71.el6.x86_64/modules.alias:alias
> pci:v00008086d000010E8sv*sd*bc*sc*i* igb
> [/quote]
>
> -- where the 8086:10c9 device is "good" and the 8086:01eb device is
> "bad". So the distro igb driver should be appropriate for both
> devices.
>
> You mention that you have another system with 8086:01eb devices. Does
> that system also suffer from the same "hanging" issue? What I am
> trying to determine is whether it is a general problem with the distro
> igb driver and 8086:01eb devices or if it is just a problem with the
> 8086:01eb device in the Super Micro based system.
>
> Even before I see your response, I will mention that there is an
> updated igb driver available as a kernel independent, kABI tracking
> kmod package in the elrepo repository. Assuming you have the standard
> SL 6.0 installation, the following would allow you to install the
> updated driver --
>
> [code]
> yum --disablerepo \* --enablerepo elrepo install kmod-igb
> telinit 6
> [/code]
>
> If, after testing, the issue is still present then the removal of the
> updated driver would be the inverse of the above --
>
> [code]
> yum remove kmod-igb
> telinit 6
> [/code]
>
> Alan.

ATOM RSS1 RSS2