canonical-ubuntu-qa team mailing list archive

[Jürg Häfliger <1825089@xxxxxxxxxxxxxxxxxx>]

** Tags added: kernel-daily-bug

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

Title:
  enosys test in ubuntu_stress_smoke_test won't terminate after the test
  has finished

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

Bug description:
  On a s390x Bionic / Cosmic KVM, the enosys test is still running even
  the test has completed

  $ ps uax| grep stress
  ubuntu    2037  0.0  0.4  93020  9564 ?        Ssl  03:46   0:00 python3 ckct/runner --cloud maas ubuntu_stress_smoke_test
  root      2383  0.0  0.6  24248 13416 ?        S    03:46   0:00 /usr/bin/python -u autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_stress_smoke_test/control
  root      2384  0.0  0.6  24248 13416 ?        S    03:46   0:00 /usr/bin/python -u autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_stress_smoke_test/control
  ubuntu   13161  0.0  0.0   6072   696 ttysclp0 S+   05:31   0:00 grep --color=auto stress
  root     19352  0.0  0.0  16460   752 ?        S    03:51   0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root     19395  0.0  0.0  16460   752 ?        S    03:51   0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root     19449  0.0  0.0  16460   752 ?        S    03:51   0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable
  root     19481  0.0  0.0  16460   752 ?        S    03:51   0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable

  04:03:13 INFO | enosys STARTING
  04:03:13 INFO | enosys RETURNED 0
  04:03:13 INFO | enosys PASSED
  ....
  04:03:13 WARNI| Please verify /home/ubuntu/autotest/client/results/default/ubuntu_stress_smoke_test.stress-smoke-test/debug/crash.stress-ng-bad-a.13395 for more info
  04:03:13 INFO | 		GOOD	ubuntu_stress_smoke_test.stress-smoke-test	ubuntu_stress_smoke_test.stress-smoke-test	timestamp=1555473793	localtime=Apr 17 04:03:13	completed successfully
  04:03:13 INFO | 	END GOOD	ubuntu_stress_smoke_test.stress-smoke-test	ubuntu_stress_smoke_test.stress-smoke-test	timestamp=1555473793	localtime=Apr 17 04:03:13
  04:03:13 DEBUG| Persistent state client._record_indent now set to 1
  04:03:13 DEBUG| Persistent state client.unexpected_reboot deleted
  04:03:13 INFO | END GOOD	----	----	timestamp=1555473793	localtime=Apr 17 04:03:13
  04:03:13 DEBUG| Persistent state client._record_indent now set to 0

  And the job on jenkins will eventually times out.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: User Name 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic s390x
  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.9-0ubuntu7.6
  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: Wed Apr 17 05:28:14 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=690e3389-e7e5-4fce-a58c-c7df1314da25
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware                             1.173.3
  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/1825089/+subscriptions