Indeed we did get a "proper" timeout now \o/
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-yakkety/yakkety/amd64/l/linux/20161018_180219_53396@/log.gz
So closing this one, and using bug 1634519 for the new timeout.
** Changed in: linux
It's better now -- in my local QEMU test the last output is now
14:46:41 DEBUG| [stdout] Test icebp [Ok]
14:46:41 DEBUG| [stdout] Test int 3 trap [Ok]
14:46:41 DEBUG| [stdout] selftests: breakpoint_test [PASS]
and since then (1 hour) it's hung. But now I still can log into ttyS0.
dmesg is almost
So I've added a fix to the autotest client tests that modify the
wakealarm sleep time to 30 seconds and test VM now gets woken up and the
test no longer hangs forever at the point reported in comment #3.
Fix committed:
http://kernel.ubuntu.com/git/ubuntu/autotest-client-
So the linux kernel regression test
./linux/tools/testing/selftests/breakpoints/step_after_suspend_test is
being run and does not return. However, running this in a clean
instance it does pass. It basically sets the RTC to wake in 5 seconds
and does a suspend and the RTC wakealarm wakes it up.
OK, so S3 sleep works OK in the VM, going to debug step_after_susp
/sys/power/state
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632252
Title:
linux autopkgtest kills sshd in testbed
To manage
I'm not able to reproduce the issues you are seeing, however I do see:
16:01:15 DEBUG| [stdout] Test read watchpoint 3 with len: 8 local: 1 global: 1
[Ok]
16:01:15 DEBUG| [stdout] Test icebp [Ok]
16:01:15 DEBUG| [stdout] Test int 3 trap [Ok]
16:01:15 DEBUG| [stdout] selftests: breakpoint_test
..and the last things to be exec'd are:
16:01:15 exit 1165 00.037 ./breakpoint_test
16:01:15 exit 1164 00.043 /bin/sh -c for TEST in breakpoint_test
step_after_suspend_test; do (./$TEST && echo "selftests: $TEST [PASS]") || echo
"selftests: $TEST [FAIL]"; done;
16:01:15
With the QEMU runner this gets further, but it fails for me with
14:33:01 DEBUG| Running 'git clone
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/yakkety
linux'
14:33:01 ERROR| [stderr] Cloning into 'linux'...
autopkgtest [16:02:54]: ERROR: timed out on command "..." (kind:
** Changed in: linux (Ubuntu Yakkety)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632252
Title:
linux autopkgtest kills sshd in testbed
After the hang, even SysRq doesn't work (I tried "sync" with Ctrl+A b s
-- Ctrl+A b is the QEMU console key combo for sending SysRq, see Ctrl-A
?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632252
I am able to reproduce this locally by using the "ssh" runner on a
manually started QEMU instance, instead of the "qemu" runner directly;
so this is much easier to investigate.
First this needs a small new feature in autopkgtest's ssh runner:
It is still happening. I was running journalctl -f on the testbed while
it ran, and was able to copy the last 9000 lines of scrollback from
tmux.
** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632252/+attachment/4762321/+files/journal.txt
--
You
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.8 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
13 matches
Mail list logo
