*** This bug is a duplicate of bug 1679823 ***
https://bugs.launchpad.net/bugs/1679823
** This bug has been marked a duplicate of bug 1679823
bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)
--
You received this bug notification because you are a member of Ker
@Joseph Salisbury,
Hi.
It looks as if the Ubuntu kernel source has diverged from stable in a
significant way. In particular,
as has already been noted, on 3/10/2017, Canonical cherry-picked several
patches from 4.11-pre, apparently relating to:
http://bugs.launchpad.net/bugs/1671613
Somewher
@Patrick Salisbury,
Hi. I have yet to experience the BUG with 4.10.0-8:
$ uname -a
Linux titanic 4.10.0-8-generic #10-Ubuntu SMP Mon Feb 13 14:04:59 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
$ uptime
17:54:47 up 6 days, 2:57, 1 user, load average: 0.24, 0.45, 0.61
I had run this kernel for so
@Patrick Salisbury,
As a P.S., If you are able to confirm that Ubuntu 4.10.0-14 is the first
version affected, that would be consistent with a hypothesis that the
patch series associated with: http://bugs.launchpad.net/bugs/1671613 may
be a factor in the regression:
* POWER9: Additional power9
I'm seeing stable behavior with @Seth Forshee's kernel:
$ uname -a
Linux titanic 4.10.0-20-generic #22+lp1674838v201705030839 SMP Wed May 3
13:41:02 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ uptime
14:41:08 up 4 days, 2 min, 1 user, load average: 0.12, 0.25, 0.13
What is the next step in gett
@Seth Forshee,
Thanks again for your patch series and test kernel, which has resulted
in my system running stably for over a week now.
Although your patch series was ACK'd on the Ubuntu kernel mailing list,
I thought it worth mentioning that it doesn't yet appear to have been
applied to master-ne
I am also experiencing the problem with 4.10.0-19-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1674838
Title:
kernel BUG at /build/linux-
7LGLH_/linux-4.10.0/include/linux/s
Joseph,
Hi. I have been running with your test kernel:
$ uname -a
Linux titanic 4.10.0-20-generic #22~lp1674838 SMP Mon Apr 24 18:50:06 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
Unfortunately, it appears that this kernel is still subject to the BUG.
Please see the attached dmesg snippet.
** At
@Joseph,
Hi again. FYI, the bug never triggered when I tried your suggestion
from #24 to test the following early Zesty kernel:
https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+build/12001523
But as noted in my previous comment, the BUG did alas trigger in my
environment while
@Ehsan,
Hi. You are running the original test kernel for this BUG, which turned
out not to resolve the problem.
Please switch to @Seth Forshee's kernel as linked to #108:
http://people.canonical.com/~sforshee/lp1674838/
That kernel identifies itself as: 4.10.0-20-generic
#22+lp1674838v20170503
10 matches
Mail list logo
