To reproduce (on an 8 CPU VM):
sudo apt-get update && sudo apt-get dist-upgrade
sudo apt-get build-dep stress-ng
git clone git://kernel.ubuntu.com/cking/stress-ng
cd stress-ng
make
sudo ./stress-ng --vm-segv 0 -t 10 -v
Comment out a ptrace line and rebuild and re-run and the hang does not
occur. So it's ptrace releated.
diff --git a/stress-vm-segv.c b/stress-vm-segv.c
index 39e4cbeb..54d590cd 100644
--- a/stress-vm-segv.c
+++ b/stress-vm-segv.c
@@ -129,7 +129,7 @@ kill_child:
stress_process_dumpable(false);
#if defined(HAVE_PTRACE)
- (void)ptrace(PTRACE_TRACEME);
+ //(void)ptrace(PTRACE_TRACEME);
kill(getpid(), SIGSTOP);
#endif
(void)sigemptyset(&set);
--
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/1864063
Title:
vm-segv from ubuntu_stress_smoke_test failed on B
Status in Stress-ng:
Incomplete
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
Issue found on node onibi, with kernel 4.15.0-89.89/ 4.15.0-89.89~16.04.1
Reproduce rate: 2/2 on generic kernel, 2/2 on lowlatency kernel, 2/2 on X-hwe
generic kernel
Test hang with vm-segv:
05:58:36 DEBUG| [stdout] vm-addr PASSED
05:58:36 DEBUG| [stdout] vm-rw STARTING
05:58:41 DEBUG| [stdout] vm-rw RETURNED 0
05:58:41 DEBUG| [stdout] vm-rw PASSED
05:58:41 DEBUG| [stdout] vm-segv STARTING
+
ARCHIVE=/var/lib/jenkins/jobs/smoke__B_amd64-generic__using_onibi__for_kernel/builds/2/archive
+ scp -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o
LogLevel=quiet -r ubuntu@onibi:kernel-test-results
/var/lib/jenkins/jobs/smoke__B_amd64-generic__using_onibi__for_kernel/builds/2/archive
To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1864063/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
