Comment 30 for bug 1779817

I still think there are multiple bugs here. Some of us have a network that
absolutely will not come back up after suspend with kernel version
>4.15.0-23, even after reloading the driver. So there is a very clear
regression that I would really like see resolved / rolled back. Breaking
stuff in an LTS release for multiple users isn't much fun :(

On 3 August 2018 at 10:45, Jan Rathmann <email address hidden> wrote:

> Ok, I can confirm what I wrote on #28 on another installation.
>
> Very hard for me to tackle this down - since bisecting obviously didn't
> work.
>
> Here is a summary of what I found out about this bug:
>
> - Artful (or any other previous Ubuntu version) was not affected (at least
> not to that extend, see below).
> - Debian 9 is also not affected.
> - On previous Ubuntu versions, I could observe something regarding
> networking and suspend, that may also be a bug, but had a much less severe
> impact on daily usage: In ~1 out of 10 cases, the network connection was
> down after suspend, but it could be relatively easily be enabled again by
> deactivating the network and activating it again (either via graphical
> NetworkManager-icon or via terminal commands 'nmcli networking off|on').
> The difference to the current bug is that it was not necessary to reload
> the kernel driver.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1779817
>
> Title:
> r8169 no internet after suspending
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1779817/+subscriptions
>