← Back to team overview

canonical-ubuntu-qa team mailing list archive

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

[Bug 2073098] [NEW] ubuntu_stress_smoke_tests unable to finish properly on T-3.13

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

This issue can be found since Trusty 3.13.0-170

The dev test will take longer than usual, it looks like it will finish
properly but there are some process in uninterruptible sleep state.

$ sudo ./stress-ng -v -t 5 --dev 4 --dev-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable 
stress-ng: debug: [23274] invoked with './stress-ng -v -t 5 --dev 4 --dev-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable' by user 0 'root'
stress-ng: debug: [23274] stress-ng 0.18.00 g5afb941f405e
stress-ng: debug: [23274] system: Linux t-l-ll-3-13-e2hcpu8-u-stress-smk-test 3.13.0-198-lowlatency #249-Ubuntu SMP PREEMPT Fri Jul 5 14:30:47 UTC 2024 x86_64, gcc 4.8.4, glibc 2.19, little endian
stress-ng: debug: [23274] RAM total: 7.8G, RAM free: 6.8G, swap free: 1024.0M
stress-ng: debug: [23274] temporary file path: '/home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng', filesystem type: ext2 (1619209 blocks available)
stress-ng: debug: [23274] 8 processors online, 8 processors configured
stress-ng: info:  [23274] setting to a 5 secs run per stressor
stress-ng: debug: [23274] CPU data cache: L1: 32K, L2: 512K, L3: 16384K
stress-ng: debug: [23274] cache allocate: shared cache buffer size: 16384K
stress-ng: info:  [23274] dispatching hogs: 4 dev
stress-ng: debug: [23274] starting stressors
stress-ng: debug: [23275] dev: [23275] started (instance 0 on CPU 6)
stress-ng: debug: [23274] 4 stressors started
stress-ng: debug: [23277] dev: [23277] started (instance 2 on CPU 1)
stress-ng: debug: [23276] dev: [23276] started (instance 1 on CPU 5)
stress-ng: debug: [23278] dev: [23278] started (instance 3 on CPU 7)
stress-ng: debug: [23276] dev: [23276] exited (instance 1 on CPU 5)
stress-ng: debug: [23277] dev: [23277] exited (instance 2 on CPU 5)
stress-ng: debug: [23278] dev: cannot kill PID 23284 after 10 minutes, giving up
stress-ng: debug: [23278] dev: [23284] cmdline: stress-ng-dev:/dev/console                                                                    
stress-ng: debug: [23278] dev: [23284] syscall: 16 0x8 0x540a 0x0 0x7f31e8c9efe0 0x7ffef73932e0 0x7ffef7390f98 0x7ffef7393098 0x7f31e89d2ea7
stress-ng: debug: [23278] dev: [23284] stack: [<ffffffff8146c060>] tty_ldisc_ref_wait+0x20/0x50
stress-ng: debug: [23278] dev: [23284] stack: [<ffffffff81465078>] tty_ioctl+0x6b8/0xc10
stress-ng: debug: [23278] dev: [23284] stack: [<ffffffff811e0d13>] do_vfs_ioctl+0x2e3/0x4d0
stress-ng: debug: [23278] dev: [23284] stack: [<ffffffff811e0f81>] SyS_ioctl+0x81/0xa0
stress-ng: debug: [23278] dev: [23284] stack: [<ffffffff81751c89>] system_call_fastpath+0x26/0x2b
stress-ng: debug: [23278] dev: [23284] stack: [<ffffffffffffffff>] 0xffffffffffffffff
stress-ng: debug: [23278] dev: [23284] wchan: tty_ldisc_ref_wait
stress-ng: debug: [23278] dev: [23278] exited (instance 3 on CPU 2)
stress-ng: debug: [23275] dev: cannot kill PID 23279 after 10 minutes, giving up
stress-ng: debug: [23275] dev: [23279] cmdline: stress-ng-dev:/dev/console                                                                    
stress-ng: debug: [23275] dev: [23279] syscall: 16 0x4 0x5401 0x7ffef73932a0 0x7f31e8c9efe0 0x7f31e8a58640 0x7ffef7390f98 0x7ffef7391030 0x7f31e89d2ea7
stress-ng: debug: [23275] dev: [23279] stack: [<ffffffff8146c060>] tty_ldisc_ref_wait+0x20/0x50
stress-ng: debug: [23275] dev: [23279] stack: [<ffffffff81465078>] tty_ioctl+0x6b8/0xc10
stress-ng: debug: [23275] dev: [23279] stack: [<ffffffff811e0d13>] do_vfs_ioctl+0x2e3/0x4d0
stress-ng: debug: [23275] dev: [23279] stack: [<ffffffff811e0f81>] SyS_ioctl+0x81/0xa0
stress-ng: debug: [23275] dev: [23279] stack: [<ffffffff81751c89>] system_call_fastpath+0x26/0x2b
stress-ng: debug: [23275] dev: [23279] stack: [<ffffffffffffffff>] 0xffffffffffffffff
stress-ng: debug: [23275] dev: [23279] wchan: tty_ldisc_ref_wait
stress-ng: info:  [23275] dev: 29 of 70 devices opened and exercised
stress-ng: debug: [23275] dev: [23275] exited (instance 0 on CPU 4)
stress-ng: debug: [23274] dev: [23275] terminated (success)
stress-ng: debug: [23274] dev: [23276] terminated (success)
stress-ng: debug: [23274] dev: [23277] terminated (success)
stress-ng: debug: [23274] dev: [23278] terminated (success)
stress-ng: debug: [23274] metrics-check: all stressor metrics validated and sane
stress-ng: info:  [23274] skipped: 0
stress-ng: info:  [23274] passed: 4: dev (4)
stress-ng: info:  [23274] failed: 0
stress-ng: info:  [23274] metrics untrustworthy: 0
stress-ng: info:  [23274] successful run completed in 19 mins, 56.11 secs

$ ps aux | grep stress
root     23279  0.1  0.0 354060  1056 pts/4    Dl   07:37   0:05 stress-ng-dev:/dev/console                                                                   
root     23284  0.0  0.0 354060  1056 pts/4    Dl   07:37   0:00 stress-ng-dev:/dev/console                                                                   
ubuntu   23792  0.0  0.0  10504   892 pts/4    S+   08:27   0:00 grep --color=auto stress

Bisect in stress-ng shows commit 6f6419d is the first bad commit. Revert to 6f6419d^ can make this test pass.
Colin thinks this is a kernel issue [1], however since this is already an ESM kernel, I am not sure if we are going to fix this. I will discuss this with the cranker and cycle lead.

[1] https://github.com/ColinIanKing/stress-ng/issues/357

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


** Tags: 3.13 trusty ubuntu-stress-smoke-test

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

Title:
  ubuntu_stress_smoke_tests unable to finish properly on T-3.13

Status in ubuntu-kernel-tests:
  New

Bug description:
  This issue can be found since Trusty 3.13.0-170

  The dev test will take longer than usual, it looks like it will finish
  properly but there are some process in uninterruptible sleep state.

  $ sudo ./stress-ng -v -t 5 --dev 4 --dev-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable 
  stress-ng: debug: [23274] invoked with './stress-ng -v -t 5 --dev 4 --dev-ops 3000 --ignite-cpu --syslog --verbose --verify --oomable' by user 0 'root'
  stress-ng: debug: [23274] stress-ng 0.18.00 g5afb941f405e
  stress-ng: debug: [23274] system: Linux t-l-ll-3-13-e2hcpu8-u-stress-smk-test 3.13.0-198-lowlatency #249-Ubuntu SMP PREEMPT Fri Jul 5 14:30:47 UTC 2024 x86_64, gcc 4.8.4, glibc 2.19, little endian
  stress-ng: debug: [23274] RAM total: 7.8G, RAM free: 6.8G, swap free: 1024.0M
  stress-ng: debug: [23274] temporary file path: '/home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng', filesystem type: ext2 (1619209 blocks available)
  stress-ng: debug: [23274] 8 processors online, 8 processors configured
  stress-ng: info:  [23274] setting to a 5 secs run per stressor
  stress-ng: debug: [23274] CPU data cache: L1: 32K, L2: 512K, L3: 16384K
  stress-ng: debug: [23274] cache allocate: shared cache buffer size: 16384K
  stress-ng: info:  [23274] dispatching hogs: 4 dev
  stress-ng: debug: [23274] starting stressors
  stress-ng: debug: [23275] dev: [23275] started (instance 0 on CPU 6)
  stress-ng: debug: [23274] 4 stressors started
  stress-ng: debug: [23277] dev: [23277] started (instance 2 on CPU 1)
  stress-ng: debug: [23276] dev: [23276] started (instance 1 on CPU 5)
  stress-ng: debug: [23278] dev: [23278] started (instance 3 on CPU 7)
  stress-ng: debug: [23276] dev: [23276] exited (instance 1 on CPU 5)
  stress-ng: debug: [23277] dev: [23277] exited (instance 2 on CPU 5)
  stress-ng: debug: [23278] dev: cannot kill PID 23284 after 10 minutes, giving up
  stress-ng: debug: [23278] dev: [23284] cmdline: stress-ng-dev:/dev/console                                                                    
  stress-ng: debug: [23278] dev: [23284] syscall: 16 0x8 0x540a 0x0 0x7f31e8c9efe0 0x7ffef73932e0 0x7ffef7390f98 0x7ffef7393098 0x7f31e89d2ea7
  stress-ng: debug: [23278] dev: [23284] stack: [<ffffffff8146c060>] tty_ldisc_ref_wait+0x20/0x50
  stress-ng: debug: [23278] dev: [23284] stack: [<ffffffff81465078>] tty_ioctl+0x6b8/0xc10
  stress-ng: debug: [23278] dev: [23284] stack: [<ffffffff811e0d13>] do_vfs_ioctl+0x2e3/0x4d0
  stress-ng: debug: [23278] dev: [23284] stack: [<ffffffff811e0f81>] SyS_ioctl+0x81/0xa0
  stress-ng: debug: [23278] dev: [23284] stack: [<ffffffff81751c89>] system_call_fastpath+0x26/0x2b
  stress-ng: debug: [23278] dev: [23284] stack: [<ffffffffffffffff>] 0xffffffffffffffff
  stress-ng: debug: [23278] dev: [23284] wchan: tty_ldisc_ref_wait
  stress-ng: debug: [23278] dev: [23278] exited (instance 3 on CPU 2)
  stress-ng: debug: [23275] dev: cannot kill PID 23279 after 10 minutes, giving up
  stress-ng: debug: [23275] dev: [23279] cmdline: stress-ng-dev:/dev/console                                                                    
  stress-ng: debug: [23275] dev: [23279] syscall: 16 0x4 0x5401 0x7ffef73932a0 0x7f31e8c9efe0 0x7f31e8a58640 0x7ffef7390f98 0x7ffef7391030 0x7f31e89d2ea7
  stress-ng: debug: [23275] dev: [23279] stack: [<ffffffff8146c060>] tty_ldisc_ref_wait+0x20/0x50
  stress-ng: debug: [23275] dev: [23279] stack: [<ffffffff81465078>] tty_ioctl+0x6b8/0xc10
  stress-ng: debug: [23275] dev: [23279] stack: [<ffffffff811e0d13>] do_vfs_ioctl+0x2e3/0x4d0
  stress-ng: debug: [23275] dev: [23279] stack: [<ffffffff811e0f81>] SyS_ioctl+0x81/0xa0
  stress-ng: debug: [23275] dev: [23279] stack: [<ffffffff81751c89>] system_call_fastpath+0x26/0x2b
  stress-ng: debug: [23275] dev: [23279] stack: [<ffffffffffffffff>] 0xffffffffffffffff
  stress-ng: debug: [23275] dev: [23279] wchan: tty_ldisc_ref_wait
  stress-ng: info:  [23275] dev: 29 of 70 devices opened and exercised
  stress-ng: debug: [23275] dev: [23275] exited (instance 0 on CPU 4)
  stress-ng: debug: [23274] dev: [23275] terminated (success)
  stress-ng: debug: [23274] dev: [23276] terminated (success)
  stress-ng: debug: [23274] dev: [23277] terminated (success)
  stress-ng: debug: [23274] dev: [23278] terminated (success)
  stress-ng: debug: [23274] metrics-check: all stressor metrics validated and sane
  stress-ng: info:  [23274] skipped: 0
  stress-ng: info:  [23274] passed: 4: dev (4)
  stress-ng: info:  [23274] failed: 0
  stress-ng: info:  [23274] metrics untrustworthy: 0
  stress-ng: info:  [23274] successful run completed in 19 mins, 56.11 secs

  $ ps aux | grep stress
  root     23279  0.1  0.0 354060  1056 pts/4    Dl   07:37   0:05 stress-ng-dev:/dev/console                                                                   
  root     23284  0.0  0.0 354060  1056 pts/4    Dl   07:37   0:00 stress-ng-dev:/dev/console                                                                   
  ubuntu   23792  0.0  0.0  10504   892 pts/4    S+   08:27   0:00 grep --color=auto stress

  Bisect in stress-ng shows commit 6f6419d is the first bad commit. Revert to 6f6419d^ can make this test pass.
  Colin thinks this is a kernel issue [1], however since this is already an ESM kernel, I am not sure if we are going to fix this. I will discuss this with the cranker and cycle lead.

  [1] https://github.com/ColinIanKing/stress-ng/issues/357

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