[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot

2019-09-03 Thread Vladislav Rubtsov
I've a similar bug occurring on the following kernel versions: * 5.0.0-23-generic * 5.0.0-25-generic * 5.0.0-27-generic However, quite a few things are different in my case. As seen in logs, "Link is Down" is quickly followed up by "Link is Up" message, but interface fails to serve any packets.

[Kernel-packages] [Bug 1841040] Re: r8169 ethernet sometimes doesn't work after cold boot/boot

2019-09-03 Thread Vladislav Rubtsov
I *think* there is better and more pleasant workaround rather than rebooting every time this bug affects you. Try putting your computer into suspension, then wake it up. In most of the cases Ethernet interface fails to start at all. If it does, then reloading its driver may help it this point:

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2019-09-03 Thread Vladislav Rubtsov
UPD: The same issue, as described in previous post, reappeared when booting the older 5.0.0-25-generic kernel. It seems like data race that can be triggered randomly on certain boots. Again, removing "r8169" didn't help either, but suddenly, putting my laptop to suspension, then repeating the

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2019-09-03 Thread Vladislav Rubtsov
After update to kernel 5.0.0-27-generic, it became even worse. Now Ethernet doesn't work right from the boot, and "modprobe" solution has no effect. What's interesting, Ethernet interface seems up (and visible to NewtworkManager), but doesn't appear to serve packets at all. As far as packet

[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2019-08-25 Thread Vladislav Rubtsov
I can confirm the bug affects kernel version 5.0.0-25-generic (at least, on my machine). The issue started happening after update to this version. It didn't exist on any 4.18.0 version that I previously had. -- You received this bug notification because you are a member of Kernel Packages,