Re: (Repeat) Incessant Random Eth Disconnect/Reconnect
On Thursday 28 January 2016 15:41:50 Dan Ritter wrote:
> On Thu, Jan 28, 2016 at 08:58:37PM +0200, David Baron wrote:
> > Here is dmesg | grep eth. I had only one set like this so may not be
> > relevant since the disconnect/reconnect happens repeated.
> >
> > h
> > [ 0.854438] r8169 0000:02:00.0 eth0: RTL8168c/8111c at
> > 0xffffc90000634000, 00:e0:4c:68:00:c5, XID 1c4000c0 IRQ 27
> > [ 0.854445] r8169 0000:02:00.0 eth0: jumbo features [frames: 6128
> > bytes, tx checksumming: ko]
> > [ 0.855148] r8169 0000:03:00.0 eth1: RTL8168c/8111c at
> > 0xffffc90000636000, 00:e0:4c:68:00:c6, XID 1c4000c0 IRQ 28
> > [ 0.855155] r8169 0000:03:00.0 eth1: jumbo features [frames: 6128
> > bytes, tx checksumming: ko]
> > [ 26.942601] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> > [ 26.953369] r8169 0000:02:00.0 eth0: link down
> > [ 26.953372] r8169 0000:02:00.0 eth0: link down
> > [ 26.953485] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> > [ 26.957431] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
> > [ 26.969361] r8169 0000:03:00.0 eth1: link down
> > [ 26.969435] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
> > [ 28.612791] r8169 0000:02:00.0 eth0: link up
> > [ 28.612809] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> >
> > There is no eth1 active. IPv6 the problem?
>
> No, IPv6 is just reporting on what it tries to do after it notes
> that the link is bouncing.
>
> According to your dmesg, you have two ethernet ports and both
> are being configured. eth1 never comes up, but eth0 bounces.
>
> First check: mii-tool or ethtool to investigate and/or set
> properties such as duplex, 10/100/1000 speed, and jumbo frame
> size. I recommend setting it to 1000 full duplex no jumbo
> frames, i.e. frame size of 1500 bytes or so.
>
> What do they report?
>
> -dsr-
Note: The reported dmesg sequence is on start up, not on expiry problem.
~$ sudo ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Transmit-only
Link partner advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: yes
~$ sudo ethtool eth1
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: no
Attempts to set values get "cannot advertise ..."
The two ports are on-board, one in use. Maybe I can hide eth1 in BIOS setup.
Reply to: