canonical-ubuntu-qa team mailing list archive

Thread
Date
[Bug 2068932] [NEW] ubuntu_stress_smoke_test sleep -- nanosleeps for 11111 nanosecs to less than 8583.07 nanosecs to complete

To: canonical-ubuntu-qa@xxxxxxxxxxxxxxxxxxx
From: Jacob Martin <2068932@xxxxxxxxxxxxxxxxxx>
Date: Mon, 10 Jun 2024 18:18:30 -0000
Reply-to: Bug 2068932 <2068932@xxxxxxxxxxxxxxxxxx>
Sender: noreply@xxxxxxxxxxxxx
Public bug reported:

Seen on jammy:linux-nvidia-6.5, version 6.5.0-1021.22, cycle 2024.04.29.

Failed on:
- gunyolk (arm64)
- hinyari (arm64)

Passed on:
- akis (amd64)
- blanka (amd64)
- hidon (amd64)
- appleton-kernel (arm64)

ubuntu_stress_smoke_test.sleep fails with the following output, full log
attached:

 stress-ng: debug: [202525] invoked with './stress-ng -v -t 5 --sleep 4 --sleep-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable' by user 0 'root'
 stress-ng: debug: [202525] stress-ng 0.18.00 gea5b6cd62237
 stress-ng: debug: [202525] system: Linux gunyolk 6.5.0-1021-nvidia #22-Ubuntu SMP PREEMPT_DYNAMIC Thu May 30 18:54:56 UTC 2024 aarch64, gcc 11.4.0, glibc 2.35, little endian
 stress-ng: debug: [202525] RAM total: 471.1G, RAM free: 467.6G, swap free: 750.8M
 stress-ng: debug: [202525] temporary file path: '/home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng', filesystem type: ext2 (217049764 blocks available)
 stress-ng: debug: [202525] CPU has 1 idle state: LPI-0
 stress-ng: debug: [202525] 144 processors online, 144 processors configured
 stress-ng: info:  [202525] setting to a 5 secs run per stressor
 stress-ng: debug: [202525] CPU data cache: L1: 64K, L2: 1024K, L3: 116736K
 stress-ng: debug: [202525] cache allocate: shared cache buffer size: 233472K (LLC size x 2 NUMA nodes)
 stress-ng: info:  [202525] dispatching hogs: 4 sleep
 stress-ng: debug: [202525] starting stressors
 stress-ng: debug: [202526] sleep: [202526] started (instance 0 on CPU 24)
 stress-ng: debug: [202527] sleep: [202527] started (instance 1 on CPU 25)
 stress-ng: debug: [202525] 4 stressors started
 stress-ng: debug: [202528] sleep: [202528] started (instance 2 on CPU 26)
 stress-ng: debug: [202529] sleep: [202529] started (instance 3 on CPU 27)
 stress-ng: fail:  [202528] sleep: nanosleeps for 11111 nanosecs to less than 8583.07 nanosecs to complete
 stress-ng: fail:  [202528] sleep: nanosleeps for 11111 nanosecs to less than 10013.58 nanosecs to complete
 stress-ng: fail:  [202528] sleep: nanosleeps for 11111 nanosecs to less than 10728.84 nanosecs to complete
 stress-ng: fail:  [202527] sleep: nanosleeps for 11111 nanosecs to less than 10013.58 nanosecs to complete
 stress-ng: fail:  [202527] sleep: nanosleeps for 11111 nanosecs to less than 10967.25 nanosecs to complete
 stress-ng: fail:  [202526] sleep: nanosleeps for 11111 nanosecs to less than 10967.25 nanosecs to complete
 stress-ng: fail:  [202527] sleep: nanosleeps for 11111 nanosecs to less than 10967.25 nanosecs to complete
 stress-ng: fail:  [202529] sleep: nanosleeps for 11111 nanosecs to less than 8583.07 nanosecs to complete
 stress-ng: fail:  [202529] sleep: nanosleeps for 11111 nanosecs to less than 9059.91 nanosecs to complete
 stress-ng: fail:  [202529] sleep: nanosleeps for 11111 nanosecs to less than 9536.74 nanosecs to complete
 stress-ng: fail:  [202526] sleep: nanosleeps for 11111 nanosecs to less than 10728.84 nanosecs to complete
 stress-ng: fail:  [202526] sleep: nanosleeps for 11111 nanosecs to less than 9298.32 nanosecs to complete
 stress-ng: fail:  [202526] sleep: nanosleeps for 11111 nanosecs to less than 9536.74 nanosecs to complete
 stress-ng: fail:  [202528] sleep: nanosleeps for 11111 nanosecs to less than 9536.74 nanosecs to complete
 stress-ng: fail:  [202527] sleep: nanosleeps for 11111 nanosecs to less than 9059.91 nanosecs to complete
 stress-ng: fail:  [202529] sleep: nanosleeps for 11111 nanosecs to less than 9775.16 nanosecs to complete
 stress-ng: fail:  [202529] sleep: nanosleeps for 11111 nanosecs to less than 8821.49 nanosecs to complete
 stress-ng: fail:  [202529] sleep: nanosleeps for 11111 nanosecs to less than 10728.84 nanosecs to complete
 info: 5 failures reached, aborting stress process
 stress-ng: fail:  [202526] sleep: nanosleeps for 11111 nanosecs to less than 9059.91 nanosecs to complete
 info: 5 failures reached, aborting stress process
 stress-ng: fail:  [202527] sleep: nanosleeps for 11111 nanosecs to less than 10013.58 nanosecs to complete
 info: 5 failures reached, aborting stress process
 stress-ng: fail:  [202528] sleep: nanosleeps for 11111 nanosecs to less than 10490.42 nanosecs to complete
 info: 5 failures reached, aborting stress process
 stress-ng: fail:  [202529] sleep: detected 6 sleep underruns
 stress-ng: debug: [202529] sleep: [202529] exited (instance 3 on CPU 27)
 stress-ng: fail:  [202526] sleep: detected 5 sleep underruns
 stress-ng: fail:  [202527] sleep: detected 5 sleep underruns
 stress-ng: debug: [202526] sleep: [202526] exited (instance 0 on CPU 26)
 stress-ng: debug: [202527] sleep: [202527] exited (instance 1 on CPU 29)
 stress-ng: error: [202525] sleep: [202526] terminated with an error, exit status=2 (stressor failed)
 stress-ng: debug: [202525] sleep: [202526] terminated (stressor failed)
 stress-ng: error: [202525] sleep: [202527] terminated with an error, exit status=2 (stressor failed)
 stress-ng: debug: [202525] sleep: [202527] terminated (stressor failed)
 stress-ng: fail:  [202528] sleep: detected 5 sleep underruns
 stress-ng: debug: [202528] sleep: [202528] exited (instance 2 on CPU 23)
 stress-ng: error: [202525] sleep: [202528] terminated with an error, exit status=2 (stressor failed)
 stress-ng: debug: [202525] sleep: [202528] terminated (stressor failed)
 stress-ng: error: [202525] sleep: [202529] terminated with an error, exit status=2 (stressor failed)
 stress-ng: debug: [202525] sleep: [202529] terminated (stressor failed)
 stress-ng: debug: [202525] metrics-check: all stressor metrics validated and sane
 stress-ng: info:  [202525] skipped: 0
 stress-ng: info:  [202525] passed: 0
 stress-ng: info:  [202525] failed: 4: sleep (4)
 stress-ng: info:  [202525] metrics untrustworthy: 0
 stress-ng: info:  [202525] unsuccessful run completed in 0.05 secs
  
  
  
 Summary:
   Stressors run: 1
   Skipped: 0, 
   Failed:  1,  sleep
   Oopsed:  0, 
   Oomed:   0, 
   Passed:  0, 
   Badret:  0, 
  
 Tests took 0 seconds to run

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


** Tags: arm64 sru-20240429 ubuntu-stress-smoke-test

** Attachment added: "ubuntu_stress_smoke_test.sleep-gunyolk.log"
   https://bugs.launchpad.net/bugs/2068932/+attachment/5788057/+files/ubuntu_stress_smoke_test.sleep-gunyolk.log

-- 
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/2068932

Title:
  ubuntu_stress_smoke_test sleep -- nanosleeps for 11111 nanosecs to
  less than 8583.07 nanosecs to complete

Status in ubuntu-kernel-tests:
  New

Bug description:
  Seen on jammy:linux-nvidia-6.5, version 6.5.0-1021.22, cycle
  2024.04.29.

  Failed on:
  - gunyolk (arm64)
  - hinyari (arm64)

  Passed on:
  - akis (amd64)
  - blanka (amd64)
  - hidon (amd64)
  - appleton-kernel (arm64)

  ubuntu_stress_smoke_test.sleep fails with the following output, full
  log attached:

   stress-ng: debug: [202525] invoked with './stress-ng -v -t 5 --sleep 4 --sleep-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable' by user 0 'root'
   stress-ng: debug: [202525] stress-ng 0.18.00 gea5b6cd62237
   stress-ng: debug: [202525] system: Linux gunyolk 6.5.0-1021-nvidia #22-Ubuntu SMP PREEMPT_DYNAMIC Thu May 30 18:54:56 UTC 2024 aarch64, gcc 11.4.0, glibc 2.35, little endian
   stress-ng: debug: [202525] RAM total: 471.1G, RAM free: 467.6G, swap free: 750.8M
   stress-ng: debug: [202525] temporary file path: '/home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng', filesystem type: ext2 (217049764 blocks available)
   stress-ng: debug: [202525] CPU has 1 idle state: LPI-0
   stress-ng: debug: [202525] 144 processors online, 144 processors configured
   stress-ng: info:  [202525] setting to a 5 secs run per stressor
   stress-ng: debug: [202525] CPU data cache: L1: 64K, L2: 1024K, L3: 116736K
   stress-ng: debug: [202525] cache allocate: shared cache buffer size: 233472K (LLC size x 2 NUMA nodes)
   stress-ng: info:  [202525] dispatching hogs: 4 sleep
   stress-ng: debug: [202525] starting stressors
   stress-ng: debug: [202526] sleep: [202526] started (instance 0 on CPU 24)
   stress-ng: debug: [202527] sleep: [202527] started (instance 1 on CPU 25)
   stress-ng: debug: [202525] 4 stressors started
   stress-ng: debug: [202528] sleep: [202528] started (instance 2 on CPU 26)
   stress-ng: debug: [202529] sleep: [202529] started (instance 3 on CPU 27)
   stress-ng: fail:  [202528] sleep: nanosleeps for 11111 nanosecs to less than 8583.07 nanosecs to complete
   stress-ng: fail:  [202528] sleep: nanosleeps for 11111 nanosecs to less than 10013.58 nanosecs to complete
   stress-ng: fail:  [202528] sleep: nanosleeps for 11111 nanosecs to less than 10728.84 nanosecs to complete
   stress-ng: fail:  [202527] sleep: nanosleeps for 11111 nanosecs to less than 10013.58 nanosecs to complete
   stress-ng: fail:  [202527] sleep: nanosleeps for 11111 nanosecs to less than 10967.25 nanosecs to complete
   stress-ng: fail:  [202526] sleep: nanosleeps for 11111 nanosecs to less than 10967.25 nanosecs to complete
   stress-ng: fail:  [202527] sleep: nanosleeps for 11111 nanosecs to less than 10967.25 nanosecs to complete
   stress-ng: fail:  [202529] sleep: nanosleeps for 11111 nanosecs to less than 8583.07 nanosecs to complete
   stress-ng: fail:  [202529] sleep: nanosleeps for 11111 nanosecs to less than 9059.91 nanosecs to complete
   stress-ng: fail:  [202529] sleep: nanosleeps for 11111 nanosecs to less than 9536.74 nanosecs to complete
   stress-ng: fail:  [202526] sleep: nanosleeps for 11111 nanosecs to less than 10728.84 nanosecs to complete
   stress-ng: fail:  [202526] sleep: nanosleeps for 11111 nanosecs to less than 9298.32 nanosecs to complete
   stress-ng: fail:  [202526] sleep: nanosleeps for 11111 nanosecs to less than 9536.74 nanosecs to complete
   stress-ng: fail:  [202528] sleep: nanosleeps for 11111 nanosecs to less than 9536.74 nanosecs to complete
   stress-ng: fail:  [202527] sleep: nanosleeps for 11111 nanosecs to less than 9059.91 nanosecs to complete
   stress-ng: fail:  [202529] sleep: nanosleeps for 11111 nanosecs to less than 9775.16 nanosecs to complete
   stress-ng: fail:  [202529] sleep: nanosleeps for 11111 nanosecs to less than 8821.49 nanosecs to complete
   stress-ng: fail:  [202529] sleep: nanosleeps for 11111 nanosecs to less than 10728.84 nanosecs to complete
   info: 5 failures reached, aborting stress process
   stress-ng: fail:  [202526] sleep: nanosleeps for 11111 nanosecs to less than 9059.91 nanosecs to complete
   info: 5 failures reached, aborting stress process
   stress-ng: fail:  [202527] sleep: nanosleeps for 11111 nanosecs to less than 10013.58 nanosecs to complete
   info: 5 failures reached, aborting stress process
   stress-ng: fail:  [202528] sleep: nanosleeps for 11111 nanosecs to less than 10490.42 nanosecs to complete
   info: 5 failures reached, aborting stress process
   stress-ng: fail:  [202529] sleep: detected 6 sleep underruns
   stress-ng: debug: [202529] sleep: [202529] exited (instance 3 on CPU 27)
   stress-ng: fail:  [202526] sleep: detected 5 sleep underruns
   stress-ng: fail:  [202527] sleep: detected 5 sleep underruns
   stress-ng: debug: [202526] sleep: [202526] exited (instance 0 on CPU 26)
   stress-ng: debug: [202527] sleep: [202527] exited (instance 1 on CPU 29)
   stress-ng: error: [202525] sleep: [202526] terminated with an error, exit status=2 (stressor failed)
   stress-ng: debug: [202525] sleep: [202526] terminated (stressor failed)
   stress-ng: error: [202525] sleep: [202527] terminated with an error, exit status=2 (stressor failed)
   stress-ng: debug: [202525] sleep: [202527] terminated (stressor failed)
   stress-ng: fail:  [202528] sleep: detected 5 sleep underruns
   stress-ng: debug: [202528] sleep: [202528] exited (instance 2 on CPU 23)
   stress-ng: error: [202525] sleep: [202528] terminated with an error, exit status=2 (stressor failed)
   stress-ng: debug: [202525] sleep: [202528] terminated (stressor failed)
   stress-ng: error: [202525] sleep: [202529] terminated with an error, exit status=2 (stressor failed)
   stress-ng: debug: [202525] sleep: [202529] terminated (stressor failed)
   stress-ng: debug: [202525] metrics-check: all stressor metrics validated and sane
   stress-ng: info:  [202525] skipped: 0
   stress-ng: info:  [202525] passed: 0
   stress-ng: info:  [202525] failed: 4: sleep (4)
   stress-ng: info:  [202525] metrics untrustworthy: 0
   stress-ng: info:  [202525] unsuccessful run completed in 0.05 secs
    
    
    
   Summary:
     Stressors run: 1
     Skipped: 0, 
     Failed:  1,  sleep
     Oopsed:  0, 
     Oomed:   0, 
     Passed:  0, 
     Badret:  0, 
    
   Tests took 0 seconds to run

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2068932/+subscriptions
Follow ups

[Bug 2068932] Re: ubuntu_stress_smoke_test sleep -- nanosleeps for 11111 nanosecs to less than 8583.07 nanosecs to complete
From: Po-Hsu Lin, 2024-09-16
[Bug 2068932] Re: ubuntu_stress_smoke_test sleep -- nanosleeps for 11111 nanosecs to less than 8583.07 nanosecs to complete
From: Po-Hsu Lin, 2024-06-13
[Bug 2068932] Re: ubuntu_stress_smoke_test sleep -- nanosleeps for 11111 nanosecs to less than 8583.07 nanosecs to complete
From: Po-Hsu Lin, 2024-06-12