I could not reproduce the bug with 4.4.0-102-generic or
4.10.0-41-generic
** Tags removed: verification-needed-xenial verification-needed-zesty
** Tags added: verification-done-xenial verification-done-zesty
--
You received this bug notification because you are a member of Kernel
Packages, which
Hello Dan,
thanks for the analysis!
That the startup of containers is delayed is annoying.
The much bigger issue is that it can reproducible cause a kernel Oops and crash
a whole machine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
According to https://github.com/moby/moby/issues/35068 the crash is
fixed by:
https://patchwork.ozlabs.org/patch/801533/
https://patchwork.ozlabs.org/patch/778449/
** Bug watch added: github.com/moby/moby/issues #35068
https://github.com/moby/moby/issues/35068
--
You received this bug notifi
Ok, seems that I'm than in the wrong ticket with my issues. :-)
Should separate Ubuntu bug reports be created (if they don't exist already)
regarding the kernel
crashes?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
Public bug reported:
When running 2 docker containers, one as samba server and another one as
samba client that mounts and umounts a smb share a kernel OOps can be
triggered on multiple kernels.
The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
shows up, s
** Attachment added: "Kernel log from Oops with
linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002526/+files/kernoops-4.10.0-32.txt
--
You received this bug notification because you are a member of Kernel
Packages
** Attachment added: "Kernel log from Oops with
linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002525/+files/kernoops-4.4.0-93.txt
--
You received this bug notification because you are a member of Kernel
Packages,
** Attachment added: "Kernel log from Oops with
linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002527/+files/kernoops-4.11.0-14.txt
--
You received this bug notification because you are a member of Kernel
Packages
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1729637/+attachment/5002897/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1729637/+attachment/5002898/+files/Lspci.txt
--
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/1729637
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1729637/+attachment/5002903/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Tags added: apport-collected uec-images xenial
** Description changed:
When running 2 docker containers, one as samba server and another one as
samba client that mounts and umounts a smb share a kernel OOps can be
triggered on multiple kernels.
The kernel message
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1729637/+attachment/5002900/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1729637/+attachment/5002901/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
The collected apport informations are from a fresh start of the machine
because the bugs causes the machine to crash.
Attached are the logs of a kernel crash that happened by the described
method.
** Attachment added: "Logs from kernel Oops on
linux-image-4.10.0-37-generic=4.10.0-37.41~16.04.1"
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1729637/+attachment/5002899/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1729637/+attachment/5002902/+files/UdevDb.txt
--
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/1729637
Thanks for the fast reply.
I tried both kernels and was not able to trigger an Oops.
On the 4.4.0-98.121~lp1729637-generic kernel a hung task warning
happened:
[ +0.750497] unregister_netdevice: waiting for lo to become free. Usage count
= 1
[ +0.992665] aufs au_opts_verify:1597:dockerd[1620]
No, the hung task warning is bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407
Without the patches the kernel probably crashed during my tests before
the hung task could happen.
On artful the hung task warning does not happen.
--
You received this bug notification because you ar
With https://github.com/fho/docker-samba-loop I was able to reproduce
kernel Oopses on a clean Ubuntu 16.0.4 installation with:
- linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
- linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1
On 4.11.0-14 it was much harder to reproduce. Sometimes only a
Attached are the logs for an Oops on Ubuntu 14.04 on kernel linux-
image-4.4.0-93-generic=4.4.0-93.116~14.04.1
** Attachment added: "kernoops-4.4.0-93.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+attachment/4941963/+files/kernoops-4.4.0-93.txt
--
You received this bug n
I could not reproduce the bug with the described method with kernel
4.4.0-81-generic and neither with 4.13.0-041300rc7-generic. 4.4.0-81
logged a hung tasks but does not Oops.
So the bug might have been reintroduced between 4.4.0-82 and 4.4.0-93
and 4.13 seems to contain a fix.
--
You received t
22 matches
Mail list logo
