netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stéphane Glondu" <glondu@debian.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: 709616@bugs.debian.org, e1000-devel@lists.sourceforge.net,
	netdev <netdev@vger.kernel.org>
Subject: Bug#709616: floods the network with pause packets
Date: Sun, 26 May 2013 11:02:47 +0200	[thread overview]
Message-ID: <51A1CFB7.1080808@debian.org> (raw)
In-Reply-To: <1369533273.3469.301.camel@deadeye.wl.decadent.org.uk>

Le 26/05/2013 03:54, Ben Hutchings a écrit :
> I forgot, e1000e still doesn't report autoneg state completely through
> ethtool.  How about 'mii-tool -v eth0'?

# mii-tool -v eth0
SIOCGMIIREG on eth0 failed: Input/output error
SIOCGMIIREG on eth0 failed: Input/output error
eth0: negotiated 100baseTx-FD flow-control, link ok
  product info: vendor 00:55:00, model 9 rev 0
  basic mode:   autonegotiation enabled
  basic status: autonegotiation complete, link ok
  capabilities: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD
  advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
  link partner: 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD
10baseT-HD flow-control


I am not sure about who to put in CC of this mail; I've just put the
Debian bug.


Cheers,

-- 
Stéphane

  reply	other threads:[~2013-05-26  9:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130524124059.12781.51344.reportbug@wencory.loria.fr>
     [not found] ` <20130524160727.GM4752@decadent.org.uk>
     [not found]   ` <51A07081.5010104@debian.org>
2013-05-26  1:54     ` Bug#709616: floods the network with pause packets Ben Hutchings
2013-05-26  9:02       ` Stéphane Glondu [this message]
2013-05-26 16:10         ` Ben Hutchings
2013-05-30  9:21           ` Stéphane Glondu
2013-05-30 12:58             ` Ben Hutchings
2013-05-30 13:07               ` Stéphane Glondu

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=51A1CFB7.1080808@debian.org \
    --to=glondu@debian.org \
    --cc=709616@bugs.debian.org \
    --cc=ben@decadent.org.uk \
    --cc=e1000-devel@lists.sourceforge.net \
    --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).