From: Holger Schurig <holgerschurig@gmail.com>
To: jeffrey.t.kirsher@intel.com, intel-wired-lan@lists.osuosl.org,
linux-kernel@vger.kernel.org
Subject: [BUG] igb: reconnecting of cable not always detected
Date: Tue, 24 Apr 2018 17:14:58 +0200 [thread overview]
Message-ID: <87h8o0ocul.fsf@gmail.com> (raw)
Hi all,
I'm on kernel 4.16.4 and have an issue with eth0, driver is igb. When I
remove the ethernet cable, this is always detected:
[ 2.772360] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
[ 2.772363] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 3.023707] igb 0000:02:00.0: added PHC on eth0
[ 3.023710] igb 0000:02:00.0: Intel(R) Gigabit Ethernet Network Connection
[ 3.023713] igb 0000:02:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 00:13:95:1a:54:33
[ 3.023758] igb 0000:02:00.0: eth0: PBA No: 000300-000
[ 3.023762] igb 0000:02:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
[ 7.984921] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 11.184593] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Down
Sometimes, plugging the cable back in is detected ...
[ 43.736922] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
... but sometimes this is *NOT* detected. I can put the cable in and
even after two minutes nothing has been detected.
But when I run "rmmod igb" followed by "modpobe igb", the link is
detected again:
[ 100.528609] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Down
[ 2336.583244] igb 0000:02:00.0: removed PHC on eth0
[ 2339.693521] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
[ 2339.693524] igb: Copyright (c) 2007-2014 Intel Corporation.
[ 2339.990553] pps pps0: new PPS source ptp0
[ 2339.990561] igb 0000:02:00.0: added PHC on eth0
[ 2339.990565] igb 0000:02:00.0: Intel(R) Gigabit Ethernet Network Connection
[ 2339.990569] igb 0000:02:00.0: eth0: (PCIe:2.5Gb/s:Width x1) 00:13:95:1a:54:33
[ 2339.990611] igb 0000:02:00.0: eth0: PBA No: 000300-000
[ 2339.990615] igb 0000:02:00.0: Using MSI-X interrupts. 4 rx queue(s), 4 tx queue(s)
[ 2343.001114] igb 0000:02:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
(In above dmesg snippet the ethernet cable was the whole time inserted).
Any tips on how I can debug this further?
PS: I already tried a different switch and also a direct connection from
device-to-device, without a switch.
next reply other threads:[~2018-04-24 15:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 15:14 Holger Schurig [this message]
2018-04-24 18:09 ` [BUG] igb: reconnecting of cable not always detected Alexander Duyck
2018-04-25 3:30 ` Richard Cochran
2018-04-25 9:47 ` Holger Schurig
2018-04-25 16:01 ` Alexander Duyck
2018-04-26 7:54 ` Holger Schurig
2018-04-26 9:08 ` Holger Schurig
2018-04-26 16:02 ` Alexander Duyck
2018-04-27 10:39 ` Holger Schurig
2018-05-18 7:35 ` Holger Schurig
2019-01-17 21:55 ` [Intel-wired-lan] " Jeff Kirsher
-- strict thread matches above, loose matches on Subject: below --
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=87h8o0ocul.fsf@gmail.com \
--to=holgerschurig@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 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).