On 10 August 2018 at 12:49, Heiner Kallweit <email address hidden>
wrote:
> @Steve, there's some resistance amongst kernel maintainers against
> additional module parameters. Each new parameter increases complexity and
> makes maintenance harder.
> Most likely it would result in a NAK when trying to fix an issue with one
> broken exotic (sorry..) system in the kernel, especially if a userspace
> workaround is available (disabling MSI via sysfs for the network device).
>
> --
> 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
>
Can we cherry-pick /git.kernel. org/pub/ scm/linux/ kernel/ git/davem/ net-next. git/commit/ ?id=7c53a722459 c1d6ffb0f5b2058 c06ca8980b8600
https:/
for bionic?
On 10 August 2018 at 12:49, Heiner Kallweit <email address hidden>
wrote:
> @Steve, there's some resistance amongst kernel maintainers against /bugs.launchpad .net/bugs/ 1779817 /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/ +subscriptions
> additional module parameters. Each new parameter increases complexity and
> makes maintenance harder.
> Most likely it would result in a NAK when trying to fix an issue with one
> broken exotic (sorry..) system in the kernel, especially if a userspace
> workaround is available (disabling MSI via sysfs for the network device).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> r8169 no internet after suspending
>
> To manage notifications about this bug go to:
> https:/
> 1779817/
>