← Back to team overview

canonical-ubuntu-qa team mailing list archive

  1. canonical-ubuntu-qa team
  2. Mailing list archive
  3. Message #07990

[Bug 2129721] [NEW] ubuntu_stress_smoke_test:pthread flaky on openstack amd64-vm running focal:linux-ibm

  Thread Previous • Date Previous • • Thread Next 
Public bug reported:

ubuntu_stress_smoke_test:pthread failed 3 times in a row on openstack
amd64-vm running focal:linux-ibm. On the 4th try, it passed. I haven't
found any recordings of this test failing any other time, but it was
consistent enough to fail three times in a row.

It's not completely clear what the issue is, but most likely a segfault
on the stressor thread. This is according to "stressor terminated with
unexpected signal 11 'SIGSEGV'", although none of the test lines are
prefixed with "fail:".

Failing test logs:
pthread STARTING
pthread RETURNED 2
pthread FAILED
stress-ng: debug: [134252] invoked with './stress-ng -v -t 5 --pthread 4 --pthread-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable' by user 0 'root'
stress-ng: debug: [134252] stress-ng 0.19.03 g20e0f48cf0ca
stress-ng: debug: [134252] system: Linux kt-f-libm-ibm-5-4-u-stress-smk-test-amd64 5.4.0-1098-ibm #103-Ubuntu SMP Tue Oct 14 22:42:56 UTC 2025 x86_64, gcc 9.4.0, glibc 2.31, little endian
stress-ng: debug: [134252] RAM total: 3.8G, RAM free: 2.9G, swap free: 1023.8M
stress-ng: debug: [134252] temporary file path: '/home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng', filesystem type: ext4 (4080774 blocks available, QEMU HARDDISK)
stress-ng: debug: [134252] 2 processors online, 2 processors configured
stress-ng: info:  [134252] setting to a 5 secs run per stressor
stress-ng: debug: [134252] CPU data cache: L1: 32K, L2: 512K, L3: 16384K
stress-ng: debug: [134252] cache allocate: shared cache buffer size: 16384K
stress-ng: info:  [134252] dispatching hogs: 4 pthread
stress-ng: debug: [134252] starting stressors
stress-ng: debug: [134252] 4 stressors started
stress-ng: debug: [134253] pthread: [134253] started (instance 0 on CPU 1)
stress-ng: debug: [134256] pthread: [134256] started (instance 3 on CPU 0)
stress-ng: debug: [134255] pthread: [134255] started (instance 2 on CPU 0)
stress-ng: debug: [134254] pthread: [134254] started (instance 1 on CPU 0)
stress-ng: debug: [134253] pthread: [134253] exited (instance 0 on CPU 0)
stress-ng: warn:  [134253] pthread: WARNING: finished prematurely after just 0.59 sec
stress-ng: info:  [134253] stressor terminated with unexpected signal 11 'SIGSEGV'
stress-ng: debug: [134255] pthread: [134255] exited (instance 2 on CPU 1)
stress-ng: warn:  [134255] pthread: WARNING: finished prematurely after just 0.59 sec
stress-ng: debug: [134252] pthread: [134253] aborted via a termination signal
stress-ng: debug: [134252] pthread: [134253] terminated (killed by signal)
stress-ng: debug: [134256] pthread: [134256] exited (instance 3 on CPU 0)
stress-ng: debug: [134254] pthread: [134254] exited (instance 1 on CPU 0)
stress-ng: warn:  [134254] pthread: WARNING: finished prematurely after just 0.61 sec
stress-ng: debug: [134252] pthread: [134254] terminated (success)
stress-ng: debug: [134252] pthread: [134255] terminated (success)
stress-ng: debug: [134252] pthread: [134256] terminated (success)
stress-ng: debug: [134252] metrics-check: all stressor metrics validated and sane
stress-ng: info:  [134252] skipped: 0
stress-ng: info:  [134252] passed: 3: pthread (3)
stress-ng: info:  [134252] failed: 1: pthread (1)
stress-ng: info:  [134252] metrics untrustworthy: 0
stress-ng: info:  [134252] unsuccessful run completed in 0 secs

The only serial logs after boot completes are:
[  373.718826] device-mapper: ioctl: Invalid data size in the ioctl structure: 4294967295
[  373.730782] device-mapper: ioctl: Invalid data size in the ioctl structure: 4294967295
[  663.644520] debugfs: Directory 'loop3' with parent 'block' already present!
[  666.676021] debugfs: Directory 'loop4' with parent 'block' already present!
[ 1147.936715] Unable to find swap-space signature
[ 1148.700347] Unable to find swap-space signature
[ 1151.375400] Unable to find swap-space signature

** Affects: ubuntu-kernel-tests
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2129721

Title:
  ubuntu_stress_smoke_test:pthread flaky on openstack amd64-vm running
  focal:linux-ibm

Status in ubuntu-kernel-tests:
  New

Bug description:
  ubuntu_stress_smoke_test:pthread failed 3 times in a row on openstack
  amd64-vm running focal:linux-ibm. On the 4th try, it passed. I haven't
  found any recordings of this test failing any other time, but it was
  consistent enough to fail three times in a row.

  It's not completely clear what the issue is, but most likely a
  segfault on the stressor thread. This is according to "stressor
  terminated with unexpected signal 11 'SIGSEGV'", although none of the
  test lines are prefixed with "fail:".

  Failing test logs:
  pthread STARTING
  pthread RETURNED 2
  pthread FAILED
  stress-ng: debug: [134252] invoked with './stress-ng -v -t 5 --pthread 4 --pthread-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable' by user 0 'root'
  stress-ng: debug: [134252] stress-ng 0.19.03 g20e0f48cf0ca
  stress-ng: debug: [134252] system: Linux kt-f-libm-ibm-5-4-u-stress-smk-test-amd64 5.4.0-1098-ibm #103-Ubuntu SMP Tue Oct 14 22:42:56 UTC 2025 x86_64, gcc 9.4.0, glibc 2.31, little endian
  stress-ng: debug: [134252] RAM total: 3.8G, RAM free: 2.9G, swap free: 1023.8M
  stress-ng: debug: [134252] temporary file path: '/home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng', filesystem type: ext4 (4080774 blocks available, QEMU HARDDISK)
  stress-ng: debug: [134252] 2 processors online, 2 processors configured
  stress-ng: info:  [134252] setting to a 5 secs run per stressor
  stress-ng: debug: [134252] CPU data cache: L1: 32K, L2: 512K, L3: 16384K
  stress-ng: debug: [134252] cache allocate: shared cache buffer size: 16384K
  stress-ng: info:  [134252] dispatching hogs: 4 pthread
  stress-ng: debug: [134252] starting stressors
  stress-ng: debug: [134252] 4 stressors started
  stress-ng: debug: [134253] pthread: [134253] started (instance 0 on CPU 1)
  stress-ng: debug: [134256] pthread: [134256] started (instance 3 on CPU 0)
  stress-ng: debug: [134255] pthread: [134255] started (instance 2 on CPU 0)
  stress-ng: debug: [134254] pthread: [134254] started (instance 1 on CPU 0)
  stress-ng: debug: [134253] pthread: [134253] exited (instance 0 on CPU 0)
  stress-ng: warn:  [134253] pthread: WARNING: finished prematurely after just 0.59 sec
  stress-ng: info:  [134253] stressor terminated with unexpected signal 11 'SIGSEGV'
  stress-ng: debug: [134255] pthread: [134255] exited (instance 2 on CPU 1)
  stress-ng: warn:  [134255] pthread: WARNING: finished prematurely after just 0.59 sec
  stress-ng: debug: [134252] pthread: [134253] aborted via a termination signal
  stress-ng: debug: [134252] pthread: [134253] terminated (killed by signal)
  stress-ng: debug: [134256] pthread: [134256] exited (instance 3 on CPU 0)
  stress-ng: debug: [134254] pthread: [134254] exited (instance 1 on CPU 0)
  stress-ng: warn:  [134254] pthread: WARNING: finished prematurely after just 0.61 sec
  stress-ng: debug: [134252] pthread: [134254] terminated (success)
  stress-ng: debug: [134252] pthread: [134255] terminated (success)
  stress-ng: debug: [134252] pthread: [134256] terminated (success)
  stress-ng: debug: [134252] metrics-check: all stressor metrics validated and sane
  stress-ng: info:  [134252] skipped: 0
  stress-ng: info:  [134252] passed: 3: pthread (3)
  stress-ng: info:  [134252] failed: 1: pthread (1)
  stress-ng: info:  [134252] metrics untrustworthy: 0
  stress-ng: info:  [134252] unsuccessful run completed in 0 secs

  The only serial logs after boot completes are:
  [  373.718826] device-mapper: ioctl: Invalid data size in the ioctl structure: 4294967295
  [  373.730782] device-mapper: ioctl: Invalid data size in the ioctl structure: 4294967295
  [  663.644520] debugfs: Directory 'loop3' with parent 'block' already present!
  [  666.676021] debugfs: Directory 'loop4' with parent 'block' already present!
  [ 1147.936715] Unable to find swap-space signature
  [ 1148.700347] Unable to find swap-space signature
  [ 1151.375400] Unable to find swap-space signature

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2129721/+subscriptions
  Thread Previous • Date Previous • • Thread Next