From: Holger Schurig <holgerschurig@gmail.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
intel-wired-lan <intel-wired-lan@lists.osuosl.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] igb: reconnecting of cable not always detected
Date: Fri, 27 Apr 2018 12:39:42 +0200 [thread overview]
Message-ID: <87o9i53pch.fsf@gmail.com> (raw)
In-Reply-To: <CAKgT0Udtw2ZffwmPf16efcKPKz=C0BVZaJ_DofnyF6LxbH_nPw@mail.gmail.com>
Hi Alex,
> The first are the following 2 lines from your dump:
> Apr 26 10:42:49 kernel: igb 0000:02:00.0 eth0: igb: eth0 NIC Link is
> Up 1000 Mbps Half Duplex, Flow Control: RX
> Apr 26 10:42:49 kernel: igb 0000:02:00.0: EEE Disabled: unsupported at
> half duplex. Re-enable using ethtool when at full duplex.
Can it be the case that this is just a follow-up error?
In one of the mails from yesterday I showed you my patch to disable 1000
MB/s ... and still I had the link-always-down.
Similarly when I used a 10/100 MB/s switch only.
Both scenarios disabled 1000 MB/s, one more strictly than the other :-)
WARNING: multiple messages have this Message-ID (diff)
From: Holger Schurig <holgerschurig@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [BUG] igb: reconnecting of cable not always detected
Date: Fri, 27 Apr 2018 12:39:42 +0200 [thread overview]
Message-ID: <87o9i53pch.fsf@gmail.com> (raw)
In-Reply-To: <CAKgT0Udtw2ZffwmPf16efcKPKz=C0BVZaJ_DofnyF6LxbH_nPw@mail.gmail.com>
Hi Alex,
> The first are the following 2 lines from your dump:
> Apr 26 10:42:49 kernel: igb 0000:02:00.0 eth0: igb: eth0 NIC Link is
> Up 1000 Mbps Half Duplex, Flow Control: RX
> Apr 26 10:42:49 kernel: igb 0000:02:00.0: EEE Disabled: unsupported at
> half duplex. Re-enable using ethtool when at full duplex.
Can it be the case that this is just a follow-up error?
In one of the mails from yesterday I showed you my patch to disable 1000
MB/s ... and still I had the link-always-down.
Similarly when I used a 10/100 MB/s switch only.
Both scenarios disabled 1000 MB/s, one more strictly than the other :-)
next prev parent reply other threads:[~2018-04-27 10:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 15:14 [BUG] igb: reconnecting of cable not always detected Holger Schurig
2018-04-24 15:14 ` [Intel-wired-lan] " Holger Schurig
2018-04-24 18:09 ` Alexander Duyck
2018-04-24 18:09 ` [Intel-wired-lan] " Alexander Duyck
2018-04-25 3:30 ` Richard Cochran
2018-04-25 3:30 ` [Intel-wired-lan] " Richard Cochran
2018-04-25 9:47 ` Holger Schurig
2018-04-25 9:47 ` [Intel-wired-lan] " Holger Schurig
2018-04-25 16:01 ` Alexander Duyck
2018-04-25 16:01 ` [Intel-wired-lan] " Alexander Duyck
2018-04-26 7:54 ` Holger Schurig
2018-04-26 7:54 ` [Intel-wired-lan] " Holger Schurig
2018-04-26 9:08 ` Holger Schurig
2018-04-26 9:08 ` [Intel-wired-lan] " Holger Schurig
2018-04-26 16:02 ` Alexander Duyck
2018-04-26 16:02 ` [Intel-wired-lan] " Alexander Duyck
2018-04-27 10:39 ` Holger Schurig [this message]
2018-04-27 10:39 ` Holger Schurig
2018-05-18 7:35 ` Holger Schurig
2018-05-18 7:35 ` [Intel-wired-lan] " Holger Schurig
2019-01-17 21:55 ` Jeff Kirsher
2019-01-17 21:55 ` Jeff Kirsher
2018-06-09 17:15 Thomas Netousek
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=87o9i53pch.fsf@gmail.com \
--to=holgerschurig@gmail.com \
--cc=alexander.duyck@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.