netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: lqs_xting@sohu.com
Cc: bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
	Auke Kok <auke-jan.h.kok@intel.com>,
	Jesse Brandeburg <jesse.brandeburg@intel.com>,
	"Ronciak, John" <john.ronciak@intel.com>
Subject: Re: [Bugme-new] [Bug 10322] New: e1000 is not auto-negotiating to 1GB full duplex speed even there is 1GB speed availble
Date: Tue, 25 Mar 2008 12:36:54 -0700	[thread overview]
Message-ID: <20080325123654.91f80b00.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-10322-10286@http.bugzilla.kernel.org/>


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).


On Tue, 25 Mar 2008 07:29:56 -0700 (PDT)
bugme-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=10322
> 
>            Summary: e1000 is not auto-negotiating to 1GB full duplex speed
>                     even there is 1GB speed availble
>            Product: Drivers
>            Version: 2.5
>      KernelVersion: 2.6.23
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Network
>         AssignedTo: jgarzik@pobox.com
>         ReportedBy: lqs_xting@sohu.com
>                 CC: lqs_xting@sohu.com
> 
> 
> Latest working kernel version: 2.6.23.9
> Earliest failing kernel version: 2.6.21

err, according to this, we had the bug in 2.6.21 and then fixed it in
2.6.23.9, so this is a report of an already fixed bug ;)

Can you please clarify the version numbers here?

> Distribution:
> Hardware Environment: e1000 with 82571 chip
> Software Environment: CentOS 4.5
> Problem Description:
> We have a machine with the e1000(82571) driver which could not detect the
> correct link mode with a switch supports 1000 Mbps/s. I just find that the
> ethtool can't support 10 Mbps/s Half and 1000 Mbps/s Full mode. Therefore, the
> e1000 code should be fixed by add all modes at the 216 lines in
> e1000_ethtool.c. It is as follow:
> 
> hw->autoneg_advertised |= ecmd->advertising |
>                          ADVERTISED_TP |
>                          ADVERTISED_Autoneg;
> 
> 
> Steps to reproduce:
> 1. Add a entry ' ETHTOOL_OPTS="autoneg on" ' in the
> /etc/sysconfig/network-scripts/ifcfg-eth0;
> 2. Run '/etc/init.d/network restart';
> 3. Run 'ethtool eth0', it displays the speed is 100 Mbps/s. But the real link
> mode should be 1000 Mbps/s


       reply	other threads:[~2008-03-25 19:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10322-10286@http.bugzilla.kernel.org/>
2008-03-25 19:36 ` Andrew Morton [this message]
2008-03-25 22:02   ` [Bugme-new] [Bug 10322] New: e1000 is not auto-negotiating to 1GB full duplex speed even there is 1GB speed availble Kok, Auke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080325123654.91f80b00.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=auke-jan.h.kok@intel.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=lqs_xting@sohu.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).