Bug 680370 - pcnet32 network drivers do not allow speed/duplex query
Summary: pcnet32 network drivers do not allow speed/duplex query
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: i386
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Neil Horman
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-25 10:08 UTC by taipan_yh
Modified: 2011-09-30 18:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-30 18:16:17 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description taipan_yh 2011-02-25 10:08:14 UTC
Description of problem:
If your network adapter uses the pcnet32 drivers, there is no way to get the interface speed and duplex.

Version-Release number of selected component (if applicable):

How reproducible:
I managed to reproduce this on a VMware VM, but i guess it could be reproduce on any system that uses the pcnet32 drivers for the network adapter.

To reproduce in VMware, just make sure you select "Flexible" for "Adapter Type". If you do this, RHEL6 will use the pcnet32 drivers for the network adapter.

  
Actual results:
[root@localhost ~]# dmesg | grep eth
eth0: registered as PCnet/PCI II 79C970A
udev: renamed network interface eth0 to eth3
eth3: link up
eth3: no IPv6 routers present

[root@localhost ~]# ethtool eth3
Settings for eth3:
        Current message level: 0x00000007 (7)
        Link detected: yes

[root@localhost ~]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:50:56:9e:00:80 brd ff:ff:ff:ff:ff:ff

UNKNOWN is where the duplex should be

[root@localhost ~]# lsmod 
Module                  Size  Used by
ipv6                  264702  12 
dm_mirror              11620  0 
dm_region_hash         10127  1 dm_mirror
dm_log                  8520  2 dm_mirror,dm_region_hash
ppdev                   7335  0 
parport_pc             19348  0 
parport                31019  2 ppdev,parport_pc
pcnet32                29208  0 
mii                     4289  1 pcnet32
vmware_balloon          5785  0 
i2c_piix4              11098  0 
i2c_core               25799  1 i2c_piix4
sg                     24778  0 
ext3                  117020  2 
jbd                    44054  1 ext3
mbcache                 5918  1 ext3
sr_mod                 14187  0 
cdrom                  34035  1 sr_mod
sd_mod                 33344  4 
crc_t10dif              1191  1 sd_mod
pata_acpi               2487  0 
ata_generic             2555  0 
ata_piix               19016  0 
mptspi                 14637  3 
mptscsih               30378  1 mptspi
mptbase                84672  2 mptspi,mptscsih
scsi_transport_spi     20340  1 mptspi
dm_mod                 63859  2 dm_mirror,dm_log


Expected results:
You should be able to see the speed/duplex using the ethtool command for example. On the exact same system from where i extracted the above information, i added another network adapter, but instead of "Flexible" i selected "E1000" for "Adapter Type", this way the RHEL6 system will use the e1000 drivers instead of pcnet32. Everything works fine with the e1000 drivers

[root@localhost ~]# dmesg | grep eth0
e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
udev: renamed network interface eth0 to eth4

[root@localhost ~]# ethtool eth4
Settings for eth4:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: d
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes

[root@localhost ~]# lsmod 
Module                  Size  Used by
sit                     8292  0 
tunnel4                 2089  1 sit
ipv6                  264702  13 sit
dm_mirror              11620  0 
dm_region_hash         10127  1 dm_mirror
dm_log                  8520  2 dm_mirror,dm_region_hash
ppdev                   7335  0 
parport_pc             19348  0 
parport                31019  2 ppdev,parport_pc
e1000                  95440  0 
vmware_balloon          5785  0 
i2c_piix4              11098  0 
i2c_core               25799  1 i2c_piix4
sg                     24778  0 
ext3                  117020  2 
jbd                    44054  1 ext3
mbcache                 5918  1 ext3
sd_mod                 33344  4 
crc_t10dif              1191  1 sd_mod
sr_mod                 14187  0 
cdrom                  34035  1 sr_mod
mptspi                 14637  3 
mptscsih               30378  1 mptspi
mptbase                84672  2 mptspi,mptscsih
scsi_transport_spi     20340  1 mptspi
pata_acpi               2487  0 
ata_generic             2555  0 
ata_piix               19016  0 
dm_mod                 63859  2 dm_mirror,dm_log



Additional info:

Comment 1 taipan_yh 2011-02-25 10:10:34 UTC
Forgot to add, this is my system:
[root@localhost ~]# uname -a
Linux localhost.localdomain 2.6.32-71.el6.i686 #1 SMP Wed Sep 1 01:26:34 EDT 2010 i686 i686 i386 GNU/Linux

[root@localhost ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.0 (Santiago)

Comment 3 RHEL Program Management 2011-04-04 02:48:38 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 4 Neil Horman 2011-07-18 12:34:11 UTC
Can you strace the ethtool command when you run it please, and post the results here?  Also, can you please tell me what the values of /sys/class/net/eth3/[speed|duplex] are on the affected guest?  Thanks.

Comment 5 taipan_yh 2011-08-26 12:23:44 UTC
Sorry, i didn't have time to work on this. But if anyone else has a vmware machine available it's very simple. Just set the network adapter type on Flexible.

If not, i'll try to find time to reproduce it.

Comment 6 Neil Horman 2011-08-29 14:45:38 UTC
Please do.

Comment 7 Neil Horman 2011-09-15 12:23:16 UTC
ping any feedback?

Comment 8 Neil Horman 2011-09-30 18:16:17 UTC
ok, no response in a month, closing.


Note You need to log in before you can comment on or make changes to this bug.