Re: platform-linux: do-change-link[2]: failure changing link: failure 22 (Invalid argument)

On 25/03/2018 15:09, Brian J. Murrell wrote:
On Sun, 2018-03-25 at 14:27 +0200, Thomas Haller wrote:
Hi Thomas,

try enable level=TRACE logging. See
hints how to do that. Then look at the logfile or send it.
Looked at it.  Not sure I'm really seeing why the "failure changing
link: failure 22 (Invalid argument)".  The whole log can be found at:

Unrelatedly I did notice:

Mar 25 08:46:53 NetworkManager[976]: <debug>
[1521982013.8717] dhcp6 (enp2s0): running: /sbin/dhclient -d -q -6 -N
-sf /usr/libexec/nm-dhcp-helper -pf /var/run/ -lf
/var/lib/NetworkManager/dhclient6-90f5409c-bd23-48f2-b03f-325333198827- -cf /var/lib/NetworkManager/dhclient6-enp2s0.conf enp2s0

That's a waste of time.  There is no DHCP6 server in this network and
if there were, it would be this machine.  How can I disable this waste
of time?

Ultimately, nm-online did not return until 08:47:39 which is 1:34 after
NetworkManager started.  I think eliminating that dhclient run would go
a long way toward that.


networkmanager-list mailing list
networkmanager-list gnome org
Can I ask a stupid question? I see multiple references to r8169 in the log. Is you NIC by any chance an RTL8111/8168/8411? Do an "lspci -k | grep Eth -A 3". If it is, I've seen it give so many different issues when it is used with the r8169 driver, but it works really well with the r8168 driver. ElRepo ( maintain a kmod compatible version. I am wondering if this may also be solved by using the better driver.


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