[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: (Repeat) Incessant Random Eth Disconnect/Reconnect



On Thursday 28 January 2016 13:13:42 you wrote:
> On Thu, Jan 28, 2016 at 08:08:50PM +0200, David Baron wrote:
> > Royal pain in the ...
> > What do I do about this?
> > 
> > Running on up-to-date 64-bit Sid box, running through netgear router.
> > 
> > (Saw something about network manager/netcfg conflict but I do not have
> > netcfg.)
> 
> 1. Get more information.
> - dmesg output?
> - hardware info about the NIC?
> - ethtool or mii-tool info?
> - /proc/interrupts investigation
> 
> 2. Change variables one at a time, noting any changed behavior
> - can you swap the cable?
> - can you test a different NIC, or a different computer
>   entirely?
> - can you connect the same NIC to something other than the
>   netgear?
> 
> -dsr-

Thanks for you reply. I tried the cables. Have no other HW NIC machine 
available.

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?


Reply to: