[Kernel-packages] [Bug 1788385] Re: vfork in ubuntu_stress_smoke test failed on KVM node with B-KVM kernel

2018-08-23 Thread Po-Hsu Lin
** Changed in: stress-ng
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1788385

Title:
  vfork in ubuntu_stress_smoke test failed on KVM node with B-KVM kernel

Status in Stress-ng:
  Fix Released
Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid

Bug description:
  Fail rate 2 out of 2, failed on a kvm node "gummo", with 1G ram

  uname -vr : 4.15.0-1020-kvm #20-Ubuntu SMP Thu Aug 16 16:46:26 UTC 2018
  Bionic 18.04
  arch: amd64

  DEBUG - 11:24:24 DEBUG| [stdout] vfork STARTING
  DEBUG - 11:24:24 DEBUG| [stdout] vfork STARTING
  DEBUG - 11:24:26 DEBUG| [stdout] vfork RETURNED 2
  DEBUG - 11:24:26 DEBUG| [stdout] vfork RETURNED 2
  DEBUG - 11:24:26 DEBUG| [stdout] vfork FAILED
  DEBUG - 11:24:26 DEBUG| [stdout] vfork FAILED
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 2 
processors online, 2 processors configured
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 2 
processors online, 2 processors configured
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: info:  [1437] 
dispatching hogs: 4 vfork
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: info:  [1437] 
dispatching hogs: 4 vfork
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: reducing cache level from L3 (too high) to L2
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: reducing cache level from L3 (too high) to L2
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: default cache size: 4096K
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: default cache size: 4096K
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 
starting stressors
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 
starting stressors
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1438] 
stress-ng-vfork: started [1438] (instance 0)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1438] 
stress-ng-vfork: started [1438] (instance 0)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 4 
stressors spawned
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 4 
stressors spawned
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1439] 
stress-ng-vfork: started [1439] (instance 1)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1439] 
stress-ng-vfork: started [1439] (instance 1)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1440] 
stress-ng-vfork: started [1440] (instance 2)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1440] 
stress-ng-vfork: started [1440] (instance 2)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1441] 
stress-ng-vfork: started [1441] (instance 3)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1441] 
stress-ng-vfork: started [1441] (instance 3)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1438] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1438] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  

[Kernel-packages] [Bug 1788385] Re: vfork in ubuntu_stress_smoke test failed on KVM node with B-KVM kernel

2018-08-23 Thread Po-Hsu Lin
Passed with 3 run on the same node with the updated repo.
Thank you!

** Changed in: ubuntu-kernel-tests
   Status: New => Fix Released

** Changed in: linux-kvm (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1788385

Title:
  vfork in ubuntu_stress_smoke test failed on KVM node with B-KVM kernel

Status in Stress-ng:
  In Progress
Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid

Bug description:
  Fail rate 2 out of 2, failed on a kvm node "gummo", with 1G ram

  uname -vr : 4.15.0-1020-kvm #20-Ubuntu SMP Thu Aug 16 16:46:26 UTC 2018
  Bionic 18.04
  arch: amd64

  DEBUG - 11:24:24 DEBUG| [stdout] vfork STARTING
  DEBUG - 11:24:24 DEBUG| [stdout] vfork STARTING
  DEBUG - 11:24:26 DEBUG| [stdout] vfork RETURNED 2
  DEBUG - 11:24:26 DEBUG| [stdout] vfork RETURNED 2
  DEBUG - 11:24:26 DEBUG| [stdout] vfork FAILED
  DEBUG - 11:24:26 DEBUG| [stdout] vfork FAILED
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 2 
processors online, 2 processors configured
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 2 
processors online, 2 processors configured
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: info:  [1437] 
dispatching hogs: 4 vfork
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: info:  [1437] 
dispatching hogs: 4 vfork
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: reducing cache level from L3 (too high) to L2
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: reducing cache level from L3 (too high) to L2
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: default cache size: 4096K
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: default cache size: 4096K
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 
starting stressors
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 
starting stressors
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1438] 
stress-ng-vfork: started [1438] (instance 0)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1438] 
stress-ng-vfork: started [1438] (instance 0)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 4 
stressors spawned
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 4 
stressors spawned
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1439] 
stress-ng-vfork: started [1439] (instance 1)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1439] 
stress-ng-vfork: started [1439] (instance 1)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1440] 
stress-ng-vfork: started [1440] (instance 2)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1440] 
stress-ng-vfork: started [1440] (instance 2)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1441] 
stress-ng-vfork: started [1441] (instance 3)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1441] 
stress-ng-vfork: started [1441] (instance 3)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1438] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1438] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 

[Kernel-packages] [Bug 1788385] Re: vfork in ubuntu_stress_smoke test failed on KVM node with B-KVM kernel

2018-08-23 Thread Colin Ian King
This is not a kernel error; it's a bug in stress-ng when running with
the --verify option on systems where memory is low and EAGAIN or ENOMEM
occurs.  I've fixed this in stress-ng with commit:

http://kernel.ubuntu.com/git/cking/stress-
ng.git/commit/?id=8ab0ac7ce995517c0cb10db60bee5a19b7b8

Do you mind running a re-test to see if this fixes the issue.  Apologies
for this stress-ng bug. My bad.

** Changed in: stress-ng
   Importance: Undecided => High

** Changed in: stress-ng
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: stress-ng
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1788385

Title:
  vfork in ubuntu_stress_smoke test failed on KVM node with B-KVM kernel

Status in Stress-ng:
  In Progress
Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Fail rate 2 out of 2, failed on a kvm node "gummo", with 1G ram

  uname -vr : 4.15.0-1020-kvm #20-Ubuntu SMP Thu Aug 16 16:46:26 UTC 2018
  Bionic 18.04
  arch: amd64

  DEBUG - 11:24:24 DEBUG| [stdout] vfork STARTING
  DEBUG - 11:24:24 DEBUG| [stdout] vfork STARTING
  DEBUG - 11:24:26 DEBUG| [stdout] vfork RETURNED 2
  DEBUG - 11:24:26 DEBUG| [stdout] vfork RETURNED 2
  DEBUG - 11:24:26 DEBUG| [stdout] vfork FAILED
  DEBUG - 11:24:26 DEBUG| [stdout] vfork FAILED
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 2 
processors online, 2 processors configured
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 2 
processors online, 2 processors configured
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: info:  [1437] 
dispatching hogs: 4 vfork
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: info:  [1437] 
dispatching hogs: 4 vfork
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: reducing cache level from L3 (too high) to L2
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: reducing cache level from L3 (too high) to L2
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: default cache size: 4096K
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: default cache size: 4096K
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 
starting stressors
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 
starting stressors
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1438] 
stress-ng-vfork: started [1438] (instance 0)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1438] 
stress-ng-vfork: started [1438] (instance 0)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 4 
stressors spawned
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 4 
stressors spawned
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1439] 
stress-ng-vfork: started [1439] (instance 1)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1439] 
stress-ng-vfork: started [1439] (instance 1)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1440] 
stress-ng-vfork: started [1440] (instance 2)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1440] 
stress-ng-vfork: started [1440] (instance 2)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1441] 
stress-ng-vfork: started [1441] (instance 3)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1441] 
stress-ng-vfork: started [1441] (instance 3)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1438] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1438] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: 

[Kernel-packages] [Bug 1788385] Re: vfork in ubuntu_stress_smoke test failed on KVM node with B-KVM kernel

2018-08-23 Thread Po-Hsu Lin
Tested multiple time on the same node with both Bionic generic / kvm
kernel:

4.15.0-32.35: failed 0/3
4.15.0.1019.19: failed 2/3

Test was executed 3 times consecutively without reboot, output from syslog when 
it fails:
Aug 23 06:18:59 gummo kernel: Adding 1478652k swap on /swap.img.  Priority:-2 
extents:3 across:1830908k 
Aug 23 06:18:59 gummo kernel: Adding 1048572k swap on 
/home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng/swap.img.
  Priority:-3 extents:3 across:7340032k 
Aug 23 06:18:59 gummo stress-ng: invoked with './stress-n' by user 0
Aug 23 06:18:59 gummo stress-ng: system: 'gummo' Linux 4.15.0-1019-kvm 
#19-Ubuntu SMP Fri Aug 10 10:24:21 UTC 2018 x86_64
Aug 23 06:18:59 gummo stress-ng: memory (MB): total 996.66, free 7.01, shared 
0.50, buffer 11.73, swap 2467.99, free swap 2467.99
Aug 23 06:18:59 gummo stress-ng: info:  [823] dispatching hogs: 4 vfork
Aug 23 06:19:01 gummo stress-ng: fail:  [827] stress-ng-vfork: fork failed
Aug 23 06:19:01 gummo stress-ng: fail:  [825] stress-ng-vfork: fork failed
Aug 23 06:19:01 gummo stress-ng: message repeated 4 times: [ fail:  [825] 
stress-ng-vfork: fork failed]
Aug 23 06:19:01 gummo stress-ng: fail:  [827] stress-ng-vfork: fork failed
Aug 23 06:19:01 gummo stress-ng: message repeated 3 times: [ fail:  [827] 
stress-ng-vfork: fork failed]
Aug 23 06:19:02 gummo stress-ng: fail:  [824] stress-ng-vfork: fork failed
Aug 23 06:19:02 gummo stress-ng: message repeated 4 times: [ fail:  [824] 
stress-ng-vfork: fork failed]
Aug 23 06:19:02 gummo stress-ng: fail:  [826] stress-ng-vfork: fork failed
Aug 23 06:19:02 gummo stress-ng: error: [823] process 824 (stress-ng-vfork) 
terminated with an error, exit status=1 (stress-ng core failure)
Aug 23 06:19:02 gummo stress-ng: error: [823] process 825 (stress-ng-vfork) 
terminated with an error, exit status=1 (stress-ng core failure)
Aug 23 06:19:04 gummo stress-ng: fail:  [826] stress-ng-vfork: fork failed
Aug 23 06:19:04 gummo stress-ng: message repeated 3 times: [ fail:  [826] 
stress-ng-vfork: fork failed]
Aug 23 06:19:04 gummo stress-ng: error: [823] process 826 (stress-ng-vfork) 
terminated with an error, exit status=1 (stress-ng core failure)
Aug 23 06:19:04 gummo stress-ng: error: [823] process 827 (stress-ng-vfork) 
terminated with an error, exit status=1 (stress-ng core failure)
Aug 23 06:19:04 gummo stress-ng: info:  [823] unsuccessful run completed in 
4.51s

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1788385

Title:
  vfork in ubuntu_stress_smoke test failed on KVM node with B-KVM kernel

Status in Stress-ng:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Fail rate 2 out of 2, failed on a kvm node "gummo", with 1G ram

  uname -vr : 4.15.0-1020-kvm #20-Ubuntu SMP Thu Aug 16 16:46:26 UTC 2018
  Bionic 18.04
  arch: amd64

  DEBUG - 11:24:24 DEBUG| [stdout] vfork STARTING
  DEBUG - 11:24:24 DEBUG| [stdout] vfork STARTING
  DEBUG - 11:24:26 DEBUG| [stdout] vfork RETURNED 2
  DEBUG - 11:24:26 DEBUG| [stdout] vfork RETURNED 2
  DEBUG - 11:24:26 DEBUG| [stdout] vfork FAILED
  DEBUG - 11:24:26 DEBUG| [stdout] vfork FAILED
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 2 
processors online, 2 processors configured
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 2 
processors online, 2 processors configured
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: info:  [1437] 
dispatching hogs: 4 vfork
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: info:  [1437] 
dispatching hogs: 4 vfork
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: reducing cache level from L3 (too high) to L2
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: reducing cache level from L3 (too high) to L2
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: default cache size: 4096K
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: default cache size: 4096K
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 
starting stressors
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 
starting stressors
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1438] 
stress-ng-vfork: started [1438] (instance 0)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1438] 
stress-ng-vfork: started [1438] (instance 0)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 4 
stressors spawned
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 4 
stressors spawned
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1439] 
stress-ng-vfork: started [1439] (instance 

[Kernel-packages] [Bug 1788385] Re: vfork in ubuntu_stress_smoke test failed on KVM node with B-KVM kernel

2018-08-22 Thread Po-Hsu Lin
Sorry was in a hurry, info updated in the bug description.

** Description changed:

  Fail rate 2 out of 2, failed on a kvm node "gummo", with 1G ram
+ 
+ uname -vr : 4.15.0-1020-kvm #20-Ubuntu SMP Thu Aug 16 16:46:26 UTC 2018
+ Bionic 18.04
  
  DEBUG - 11:24:24 DEBUG| [stdout] vfork STARTING
  DEBUG - 11:24:24 DEBUG| [stdout] vfork STARTING
  DEBUG - 11:24:26 DEBUG| [stdout] vfork RETURNED 2
  DEBUG - 11:24:26 DEBUG| [stdout] vfork RETURNED 2
  DEBUG - 11:24:26 DEBUG| [stdout] vfork FAILED
  DEBUG - 11:24:26 DEBUG| [stdout] vfork FAILED
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 2 
processors online, 2 processors configured
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 2 
processors online, 2 processors configured
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: info:  [1437] 
dispatching hogs: 4 vfork
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: info:  [1437] 
dispatching hogs: 4 vfork
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: reducing cache level from L3 (too high) to L2
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: reducing cache level from L3 (too high) to L2
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: default cache size: 4096K
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: default cache size: 4096K
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 
starting stressors
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 
starting stressors
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1438] 
stress-ng-vfork: started [1438] (instance 0)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1438] 
stress-ng-vfork: started [1438] (instance 0)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 4 
stressors spawned
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 4 
stressors spawned
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1439] 
stress-ng-vfork: started [1439] (instance 1)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1439] 
stress-ng-vfork: started [1439] (instance 1)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1440] 
stress-ng-vfork: started [1440] (instance 2)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1440] 
stress-ng-vfork: started [1440] (instance 2)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1441] 
stress-ng-vfork: started [1441] (instance 3)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1441] 
stress-ng-vfork: started [1441] (instance 3)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1438] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1438] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] info: 5 failures reached, 
aborting stress process
  DEBUG - 11:24:26 DEBUG| [stdout] info: 5 failures reached, 
aborting stress process
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1441] 
stress-ng-vfork: exited 

[Kernel-packages] [Bug 1788385] Re: vfork in ubuntu_stress_smoke test failed on KVM node with B-KVM kernel

2018-08-22 Thread Colin Ian King
Do you mind providing information on the architecture and kernel version
+ release that is being tested.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1788385

Title:
  vfork in ubuntu_stress_smoke test failed on KVM node with B-KVM kernel

Status in Stress-ng:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Fail rate 2 out of 2, failed on a kvm node "gummo", with 1G ram

  DEBUG - 11:24:24 DEBUG| [stdout] vfork STARTING
  DEBUG - 11:24:24 DEBUG| [stdout] vfork STARTING
  DEBUG - 11:24:26 DEBUG| [stdout] vfork RETURNED 2
  DEBUG - 11:24:26 DEBUG| [stdout] vfork RETURNED 2
  DEBUG - 11:24:26 DEBUG| [stdout] vfork FAILED
  DEBUG - 11:24:26 DEBUG| [stdout] vfork FAILED
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 2 
processors online, 2 processors configured
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 2 
processors online, 2 processors configured
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: info:  [1437] 
dispatching hogs: 4 vfork
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: info:  [1437] 
dispatching hogs: 4 vfork
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: reducing cache level from L3 (too high) to L2
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: reducing cache level from L3 (too high) to L2
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: default cache size: 4096K
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] cache 
allocate: default cache size: 4096K
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 
starting stressors
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 
starting stressors
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1438] 
stress-ng-vfork: started [1438] (instance 0)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1438] 
stress-ng-vfork: started [1438] (instance 0)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 4 
stressors spawned
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1437] 4 
stressors spawned
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1439] 
stress-ng-vfork: started [1439] (instance 1)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1439] 
stress-ng-vfork: started [1439] (instance 1)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1440] 
stress-ng-vfork: started [1440] (instance 2)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1440] 
stress-ng-vfork: started [1440] (instance 2)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1441] 
stress-ng-vfork: started [1441] (instance 3)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: debug: [1441] 
stress-ng-vfork: started [1441] (instance 3)
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1438] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1438] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1440] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork failed
  DEBUG - 11:24:26 DEBUG| [stdout] stress-ng: fail:  [1441] 
stress-ng-vfork: fork