From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Greg <gvrose8192@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
jeffrey.t.kirsher@intel.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org
Subject: Re: e1000e on Thinkpad x60: gigabit not available due to "SmartSpeed"
Date: Fri, 2 Sep 2016 12:57:35 -0400 [thread overview]
Message-ID: <20160902165735.GJ14311@csclub.uwaterloo.ca> (raw)
In-Reply-To: <1472767093.3889.4.camel@gmail.com>
On Thu, Sep 01, 2016 at 02:58:13PM -0700, Greg wrote:
> On Thu, 2016-09-01 at 22:14 +0200, Pavel Machek wrote:
> > Hi!
> >
> > I have trouble getting 1000mbit out of my ethernet card.
> >
> > I tried direct connection between two PCs with different cables, and
> > no luck.
> >
> > Today I tried connection to 1000mbit switch, and no luck, either. (Two
> > cables, one was cat6, both short).
> >
> > My computer sees 1000mbit being advertised by the other side, but does
> > not advertise 1000mbit, "Link Speed was downgraded by SmartSpeed".
>
> Check your cables?
>
> https://vmxp.wordpress.com/2015/01/06/1gbe-intel-nic-throttled-to-100mbit-by-smartspeed/
Of course if it isn't the cable, then it could even be a broken pin in
the port. As far as I can tell, anything that causes one of the 3rd
or 4th pairs of wires to not work will degrade to 100Mbit on just the
first 2 pairs of wires and give that message. Some badly implemented
switches can also cause it of course.
--
Len Sorensen
next prev parent reply other threads:[~2016-09-02 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 20:14 e1000e on Thinkpad x60: gigabit not available due to "SmartSpeed" Pavel Machek
2016-09-01 21:58 ` Greg
2016-09-02 16:57 ` Lennart Sorensen [this message]
2016-12-05 10:44 ` Pavel Machek
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=20160902165735.GJ14311@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=gvrose8192@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).