This bug was fixed in the package stress-ng - 0.09.29-1

---------------
stress-ng (0.09.29-1) unstable; urgency=medium

  * Makefile: bump version
  * Manual: fix spelling mistakes and update date
  * stress-sigfpe: remove need for fp_zero
  * stress-sigfpe: cater for systems without SA_SIGINFO
  * stress-socket: fix warning on unused variable ret
  * stress-sigfpe: remove feenableexcept, it is extraneous
  * stress-sigfpe: fix verify mode, match exception with error code
  * stress-sigfpe: zero siginfo struct
  * stress-apparmor: kill child processes aggressively
  * stress-sigfpe: reset fp exception states to fix math issues
  * stress-apparmor: add more yield point checking
  * Makefile.config: move pthread library to end to fix static linking
    issues
  * Fix typo in manual, --mmapfixedA-ops -> --mmapfixed-ops
  * stress-sigfpe: force more fpe exceptions, exercise handler more
  * stress-socket: use TCP_QUICKACK if available
  * stress-socket: add FIONREAD size peeking
  * stress-userfaultfd: exercise /proc/$pid/fdinfo/$timerfd proc file
  * stress-timerfd: exercise /proc/$pid/fdinfo/$timerfd proc file
  * Rename g_terminate_signum to terminate_signum and make it static
  * Renaming symbols to indicate they are used in process termination
  * Remove some unused old struct typedefs
  * Make some functions static
  * Deconstify some const pointers (ughh)
  * Add deconstifier helper.
  * remove redundant and shadowing variable ret
  * stress-dccp: add missing ,
  * Move the class info into the stressor_info_t for each stressor
  * Rename class_t to class_info_t
  * stress-cpu: fix bitops checksum
  * stress-access: fix build warning on Solaris with %o on mode_t
  * stress-memthrash: restore accidentally removed function
    stress_set_memthrash_method
  * stress-mergesort: fix missing {
  * affinity: fix prototype of set_cpu_affinity
  * stress-cyclic: fix build warning on non-linux systems
  * Point to stress_not_implemented rather than wrapping each time
  * Add stressor_info_t for stress specific info
  * Clean up optarg handling, make it more table driven
  * Revert Add pr_* logging sleepy locks (LP: #1774571)
  * Add pr_* logging sleepy locks

 -- Colin King <colin.k...@canonical.com>  Fri, 8 jun 2018 11:30:00
+0100

** Changed in: stress-ng (Ubuntu)
       Status: Fix Committed => Fix Released

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

Title:
  sigq test from stress-ng will get stuck with Artful kernel

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

Bug description:
  This issue can be spotted on s390x, ARM64 and AMD64 Artful kernel.

  10:02:39 DEBUG| [stdout] sigpending STARTING
  10:02:44 DEBUG| [stdout] sigpending RETURNED 0
  10:02:44 DEBUG| [stdout] sigpending PASSED
  10:02:44 DEBUG| [stdout] sigpipe STARTING
  10:02:49 DEBUG| [stdout] sigpipe RETURNED 0
  10:02:49 DEBUG| [stdout] sigpipe PASSED
  10:02:49 DEBUG| [stdout] sigq STARTING
  ...

  This is the last entry related to stress-ng in syslog of a s390x node:
  May 31 10:46:39 s2lp6g004 stress-ng: system: 's2lp6g004' Linux 
4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:21:19 UTC 2018 s390x
  May 31 10:46:39 s2lp6g004 stress-ng: memory (MB): total 1805.91, free 
1409.97, shared 6.06, buffer 134.56, swap 2001.63, free swap 1890.19
  May 31 10:46:39 s2lp6g004 stress-ng: info:  [20125] dispatching hogs: 4 sigq

  No more stress-ng related message after this.

  ubuntu@s2lp6g004:/tmp$ cat stress-9234.log 
  stress-ng: debug: [20125] 2 processors online, 2 processors configured
  stress-ng: info:  [20125] dispatching hogs: 4 sigq
  stress-ng: debug: [20125] cache allocate: reducing cache level from L3 (too 
high) to L2
  stress-ng: debug: [20125] cache allocate: default cache size: 2048K
  stress-ng: debug: [20125] starting stressors
  stress-ng: debug: [20126] stress-ng-sigq: started [20126] (instance 0)
  stress-ng: debug: [20125] 4 stressors spawned
  stress-ng: debug: [20129] stress-ng-sigq: started [20129] (instance 3)
  stress-ng: debug: [20128] stress-ng-sigq: started [20128] (instance 2)
  stress-ng: debug: [20127] stress-ng-sigq: started [20127] (instance 1)
  stress-ng: debug: [20126] stress-ng-sigq: parent sent termination notice
  stress-ng: debug: [20130] stress-ng-sigq: child got termination notice

  ubuntu@s2lp6g004:/tmp$ ps aux | grep stress-ng
  root      5948  0.0  0.0  11456   712 ?        S    May31   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root      7654  0.0  0.0  11456   712 ?        S    May31   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root      7728  0.0  0.0  11456   712 ?        S    May31   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root      7740  0.0  0.0  11456   712 ?        S    May31   0:00 ./stress-ng 
-v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root     20125  0.0  0.2  13612  5008 ?        SL   May31   0:00 ./stress-ng 
-v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable
  root     20126  1.0  0.1  13612  1852 ?        S    May31  12:03 ./stress-ng 
-v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable
  root     20127  1.0  0.1  13612  1852 ?        S    May31  12:11 ./stress-ng 
-v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable
  root     20128  1.0  0.1  13612  1852 ?        S    May31  12:04 ./stress-ng 
-v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable
  root     20129  1.0  0.1  13612  1852 ?        S    May31  12:06 ./stress-ng 
-v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable
  root     20131  0.0  0.0  13612   312 ?        S    May31   0:00 ./stress-ng 
-v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable
  root     20132  0.0  0.0  13612   312 ?        S    May31   0:00 ./stress-ng 
-v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable
  root     20133  0.0  0.0  13612   312 ?        S    May31   0:00 ./stress-ng 
-v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-45-generic 4.13.0-45.50
  ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16
  Uname: Linux 4.13.0-45-generic s390x
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.9
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Fri Jun  1 05:29:54 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=d86dc8de-6ac8-4e4b-aba8-92872a209a8c 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-45-generic N/A
   linux-backports-modules-4.13.0-45-generic  N/A
   linux-firmware                             1.169.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774571/+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

Reply via email to