Can folks affected by this bug test the kernel located at:
http://kernel.ubuntu.com/~jsalisbury/lp1702910/
To test the kernel, please install both the linux-image and linux-image-
extra .deb packages.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Triaged
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => High
--
You
There's a discussion here possibly about the same problem:
https://patchwork.ozlabs.org/patch/801533/
And they referred to this patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?id=242d3a49a2a1a71d8eb9f953db1bcaa9d698ce00
The changes look like they
Were you able to reproduce on a 4.12 kernel? Maybe even a 4.14 kernel
(even though it's just the first rc that's been cut, it is the next
lts). 4.9 is another lts kernel series that could be tested.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Here is additional debug information:
KERNEL: /usr/lib/debug/boot/vmlinux-4.4.0-87-generic
DUMPFILE: dump.201709151609 [PARTIAL DUMP]
CPUS: 12
DATE: Fri Sep 15 16:05:34 2017
UPTIME: 1 days, 17:34:46
LOAD AVERAGE: 4.17, 5.02, 4.48
TASKS: 2572
NODENAME:
I can confirm that this also happens with 4.4.0-87-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/1702910
Title:
System freeze after in6_dev_finish_destroy errors
Status in
Can you also see if this bug happens with the latest upstream stable 4.4
kernel? It is available from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.85/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
We've successfully reproduced the error on a newly built instance.
We'll proceed to run the mainline kernel on the same instance.
Worth noting that it took 441529 seconds (5.1 days) since boot for this
to manifest in this case. On our previous instance the time to failure
was in the order of a
I can confirm the bug:
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320092] [ cut
here ]
Jul 12 16:45:39 k8s-agent-C5675ACA-0 kernel: [117514.320100] WARNING: CPU: 1
PID: 42381 at /build/linux-0uniEn/linux-4.4.0/net/ipv6/addrconf_core.c:159
There is a similar stack trace on
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702665.
--
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/1702910
Title:
System freeze after
We're aiming to reproduce this issue on another instance, then will
switch to the mainline kernel to gather the info you need.
--
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/1702910
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.12 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
With the sysctl net.ipv6.conf.all.disable_ipv6=1 we have still seen
another kernel error as follows:
[97989.224382] [ cut here ]
[97989.224395] WARNING: CPU: 1 PID: 19570 at
/build/linux-lts-xenial-ep3zLI/linux-lts-xenial-4.4.0/net/ipv6/addrconf_core.c:159
Logs are inline. If anything else is needed I'll capture and attach.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
14 matches
Mail list logo
