These have held up throughout the night \o/
I added the workaround to the worker setup script:
https://git.launchpad.net/~ubuntu-release/+git/autopkgtest-
cloud/commit/?id=50583f06
** Changed in: auto-package-testing
Status: Triaged => Fix Released
** Changed in: auto-package-testing
Colin had the hunch that this actually happens if the CPUs do *not* have
anything to do, i. e. want to go into a low freq/power state. We
successfully ran the full stress-ng test suite on the instance without
triggering any of this, but a few minutes after it was done it started
hung processes star
Neither did this trigger on two trusty 4-cpu instances so far.
--
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/1531768
Title:
[arm64] locks up some time after booting
Status in Auto Pack
This happens without any --user-data or any particular interaction, just
by plainly booting a standard image.
--
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/1531768
Title:
[arm64] locks
One box completely froze again (ssh does not respond any more),
attaching dmesg. However, I'm not sure that this actually contains what
you were looking for -- there is a lot of the usual chatter from
starting/stopping containers, and then some traces about hung tasks when
trying to flush the file
I installed the debug kernel on one arm64 box last night, and it has now
run for 12 hours. lxd is still running, no hung processes, and dmesg
shows nothing unusual, i. e. no extra debug messages. Yay heisenbug?
The other box with the standard xenial kernel has locked up as always;
I'll install the
Hi Martin, I've built a Xenial kernel now with a load of debug enabled,
it may catch some kind of issue or provide a hint of what's going on.
http://kernel.ubuntu.com/~cking/lp1531768/4.4-debug/
Care to try this out. It won't fix anything, but it may capture some
interesting bug info if it sees a
> I now let one box run with 4.6.0, let's see how long it'll hold up.
Checking again, I got a dozen auto-reboots from the watchdog, and after
disabling the watchdog and inspecting the box after 4 hours I see
exactly the same symptoms.
--
You received this bug notification because you are a membe
After installing the 4.6 kernel and rebooting, lxd-bridge.service failed
the same way on two boxes:
May 17 11:27:26 lxd-armhf1 lxd-bridge.start[2112]: Failed to setup lxd-bridge.
May 17 11:27:26 lxd-armhf1 lxd-bridge.start[2129]: RTNETLINK answers: Operation
not supported
May 17 11:27:26 lxd-armh
OK, that's not so great. Can you see if the latest 4.6 kernel shows any
improvement?
http://kernel.ubuntu.com/~cking/lp1531768/4.6
--
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/1531768
T
Two boxes (lxd-armhf{1,2}) have been running for three days with cking's
kernel, 3 is running the standard xenial kernel. 1 and 3 don't respond
to ssh connections any more; 2 still does, but several processes are in
'D' state:
root47 0.0 0.0 0 0 ?DMay13 0:00 [fsnot
Colin Ian King [2016-05-13 11:07 -]:
> Martin, I've going on a hunch, can you try the kernels to see if these
> help:
>
> http://kernel.ubuntu.com/~cking/lp1531768/
I installed that on two out of three lxd hosts. I'll watch the
notification emails of my watchdog and will let you know next wee
Martin, I've going on a hunch, can you try the kernels to see if these
help:
http://kernel.ubuntu.com/~cking/lp1531768/
--
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/1531768
Title:
[ar
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
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/1531768
Title:
[arm64] locks up some time after bo
This is a syslog from one boot up to the point where I hard-rebooted the
instance because it was completely hanging. The kernel errors still
look by and large like the ones from the original report (in
JournalErrors.txt).
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/
15 matches
Mail list logo
