[Kernel-packages] [Bug 1732651] Re: lttng-smoke-test failed on Xenial s390x

2017-11-19 Thread Po-Hsu Lin
Thanks for debugging this and the detailed information, Colin!
I will take this is a green light for the test result.

Since we only have a few systems that won't be re-deployed, I will try
to run the sed command next time when encounter this again.


** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  lttng-smoke-test failed on Xenial s390x

Status in linux package in Ubuntu:
  Invalid

Bug description:
  With lttng-module-dkms version 2.8.0-1ubuntu1~16.04.3, this test will
  failed on s390x instances.

  == lttng smoke test of session create/destroy ==
  Spawning a session daemon
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-113358-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)
   
  == lttng smoke test list kernel events ==
  FAILED (lttng list --kernel)
  FAILED (lttng list --kernel more output expected)
   
  lttng smoke test trace open/close system calls SKIPPED for s390x
   
  == lttng smoke test trace context switches ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-113358-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed
   
  Summary: 3 passed, 3 failed
  stderr:
  Error: Unable to list kernel events: Kernel tracer not available
  Error: Command error
  Error: Event sched_switch: Kernel tracer not available (channel channel0, 
session test-kernel-session)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-101-generic 4.4.0-101.124
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  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'
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [ 1758.314033] docker0: port 1(veth38d28b9) entered disabled state
   [ 1758.314450] device veth38d28b9 left promiscuous mode
   [ 1758.314452] docker0: port 1(veth38d28b9) entered disabled state
  Date: Thu Nov 16 04:21:00 2017
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-101-generic N/A
   linux-backports-modules-4.4.0-101-generic  N/A
   linux-firmware 1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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


[Kernel-packages] [Bug 1732651] Re: lttng-smoke-test failed on Xenial s390x

2017-11-17 Thread Colin Ian King
I tried the machine where this had failed to pass and observed that the
DKMS modules for lttng had not been built by DKMS for some reason.

Looking at /var/log/apt/history.log the following happened:

1. lttng 2.8.0-1ubuntu1~16.04.2 was installed
2. new kernel 4.4.0-101 was installed
3. possibly failed to build lttng for 4.4.0-101
4. update, pulled in lttng 2.8.0-1ubuntu1~16.04.3
5. this didn't build for 4.4.0-101 
6. lttng test fail because there were no lttng built modules

I just ran sudo apt-get install --reinstall lttng-modules-dkms to ensure
it got rebuild and then I was able to run the tests perfectly well.

Looking at https://wiki.kubuntu.org/Kernel/Dev/DKMSPackaging it states:

"Limitation of DKMS

1. DKMS may not work well after a large change of kernel ABI - Using DKMS on a 
stable release kernel will be a better idea.
2. Make sure the we have toolchains and kernel header installed.
3. Using DKMS on a netbook is not a smart idea - It takes too much time to 
build the kernel module after kernel upgrading.
4. DKMS modules will not be loaded if there are another ones in initrd."

I wonder if the change in ABI was the issue.


I suspect the following is necessary if a large ABI change occurs:

ls /usr/src/linux-headers-* -d | sed -e 's/.*linux-headers-//' | \
> sort -V | tac | sudo xargs -n1 /usr/lib/dkms/dkms_autoinstaller start

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

Title:
  lttng-smoke-test failed on Xenial s390x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With lttng-module-dkms version 2.8.0-1ubuntu1~16.04.3, this test will
  failed on s390x instances.

  == lttng smoke test of session create/destroy ==
  Spawning a session daemon
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-113358-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)
   
  == lttng smoke test list kernel events ==
  FAILED (lttng list --kernel)
  FAILED (lttng list --kernel more output expected)
   
  lttng smoke test trace open/close system calls SKIPPED for s390x
   
  == lttng smoke test trace context switches ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-113358-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed
   
  Summary: 3 passed, 3 failed
  stderr:
  Error: Unable to list kernel events: Kernel tracer not available
  Error: Command error
  Error: Event sched_switch: Kernel tracer not available (channel channel0, 
session test-kernel-session)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-101-generic 4.4.0-101.124
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  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'
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [ 1758.314033] docker0: port 1(veth38d28b9) entered disabled state
   [ 1758.314450] device veth38d28b9 left promiscuous mode
   [ 1758.314452] docker0: port 1(veth38d28b9) entered disabled state
  Date: Thu Nov 16 04:21:00 2017
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-101-generic N/A
   linux-backports-modules-4.4.0-101-generic  N/A
   linux-firmware 1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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


[Kernel-packages] [Bug 1732651] Re: lttng-smoke-test failed on Xenial s390x

2017-11-17 Thread Colin Ian King
Hrm, tried this on an s390x VM:

$ uname -a
Linux ckingvm2 4.4.0-101-generic #124-Ubuntu SMP Fri Nov 10 18:29:39 UTC 2017 
s390x s390x s390x GNU/Linux

dpkg -l | grep lttng
ii  liblttng-ctl0:s390x  2.7.1-2ubuntu1 
s390xLTTng control and utility library
ii  liblttng-ust-ctl2:s390x  2.7.1-1
s390xLTTng 2.0 Userspace Tracer (trace control library)
ii  liblttng-ust-dev:s390x   2.7.1-1
s390xLTTng 2.0 Userspace Tracer (development files)
ii  liblttng-ust-python-agent0:s390x 2.7.1-1
s390xLTTng 2.0 Userspace Tracer (Python agent native library)
ii  liblttng-ust0:s390x  2.7.1-1
s390xLTTng 2.0 Userspace Tracer (tracing libraries)
ii  lttng-modules-dkms   2.8.0-1ubuntu1~16.04.3 
all  Linux Trace Toolkit (LTTng) kernel modules (DKMS)
ii  lttng-tools  2.7.1-2ubuntu1 
s390xLTTng control and utility programs

ubuntu@ckingvm2:~$ sudo autotest/client/autotest-local 
autotest/client/tests/ubuntu_lttng_smoke_test/control
11:29:35 INFO | Writing results to /home/ubuntu/autotest/client/results/default
11:29:35 INFO | START   timestamp=1510918175localtime=Nov 
17 11:29:35   
11:29:35 INFO | START   ubuntu_lttng_smoke_test.lttng-smoke-test
ubuntu_lttng_smoke_test.lttng-smoke-testtimestamp=1510918175
localtime=Nov 17 11:29:35   
11:29:40 ERROR| [stderr] [warning] Tracer discarded 1340 events between 
[11:29:38.065061128] and [11:29:38.150240071] in trace UUID 
6614a11b486b459bce703191741816, at path: 
"/tmp/lttng-kernel-trace-1494-session/kernel", within stream id 0, at relative 
path: "channel0_0". You should consider recording a new trace with larger 
buffers or with fewer events enabled.
11:29:40 INFO | == lttng smoke test of session create/destroy ==
11:29:40 INFO | Session test-kernel-session created.
11:29:40 INFO | Traces will be written in /tmp/lttng-kernel-trace-1494-session
11:29:40 INFO | PASSED (lttng create)
11:29:40 INFO | Session test-kernel-session destroyed
11:29:40 INFO | PASSED (lttng destroy)
11:29:40 INFO |  
11:29:40 INFO | == lttng smoke test list kernel events ==
11:29:40 INFO | PASSED (lttng list --kernel)
11:29:40 INFO |  
11:29:40 INFO | lttng smoke test trace open/close system calls SKIPPED for s390x
11:29:40 INFO |  
11:29:40 INFO | == lttng smoke test trace context switches ==
11:29:40 INFO | Session test-kernel-session created.
11:29:40 INFO | Traces will be written in /tmp/lttng-kernel-trace-1494-session
11:29:40 INFO | PASSED (lttng create)
11:29:40 INFO | Kernel event sched_switch created in channel channel0
11:29:40 INFO | PASSED (lttng enable-event)
11:29:40 INFO | Tracing started for session test-kernel-session
11:29:40 INFO | PASSED (lttng start)
11:29:40 INFO | Waiting for data availability.
11:29:40 INFO | Tracing stopped for session test-kernel-session
11:29:40 INFO | PASSED (lttng stop)
11:29:40 INFO | Session test-kernel-session destroyed
11:29:40 INFO | PASSED (lttng destroy)
11:29:40 INFO | Found 19932 dd and 44645 context switches
11:29:40 INFO | PASSED (simple system call tracing with babeltrace)
11:29:40 INFO |  
11:29:40 INFO | Summary: 8 passed, 0 failed
11:29:40 INFO | GOOD
ubuntu_lttng_smoke_test.lttng-smoke-test
ubuntu_lttng_smoke_test.lttng-smoke-testtimestamp=1510918180
localtime=Nov 17 11:29:40   completed successfully
11:29:40 INFO | END GOOD
ubuntu_lttng_smoke_test.lttng-smoke-test
ubuntu_lttng_smoke_test.lttng-smoke-testtimestamp=1510918180
localtime=Nov 17 11:29:40   
11:29:40 INFO | END GOODtimestamp=1510918180
localtime=Nov 17 11:29:40   
11:29:40 INFO | Report successfully generated at 
/home/ubuntu/autotest/client/results/default/job_report.html

I just can't seem reproduce this issue.

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

Title:
  lttng-smoke-test failed on Xenial s390x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With lttng-module-dkms version 2.8.0-1ubuntu1~16.04.3, this test will
  failed on s390x instances.

  == lttng smoke test of session create/destroy ==
  Spawning a session daemon
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-113358-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)
   
  == lttng smoke test list kernel events ==
  FAILED (lttng list --kernel)
  FAILED (lttng list --kernel more output expected)
   
  lttng smoke test trace open/close system calls SKIPPED for s390x
   
  == lttng smoke test 

[Kernel-packages] [Bug 1732651] Re: lttng-smoke-test failed on Xenial s390x

2017-11-16 Thread Po-Hsu Lin
This issue can be found on azure 4.11 as well, but the interesting thing
is that this is not failing on all the instances. Some of them has
passed the test during the same period.

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

Title:
  lttng-smoke-test failed on Xenial s390x

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With lttng-module-dkms version 2.8.0-1ubuntu1~16.04.3, this test will
  failed on s390x instances.

  == lttng smoke test of session create/destroy ==
  Spawning a session daemon
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-113358-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)
   
  == lttng smoke test list kernel events ==
  FAILED (lttng list --kernel)
  FAILED (lttng list --kernel more output expected)
   
  lttng smoke test trace open/close system calls SKIPPED for s390x
   
  == lttng smoke test trace context switches ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-113358-session
  PASSED (lttng create)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed
   
  Summary: 3 passed, 3 failed
  stderr:
  Error: Unable to list kernel events: Kernel tracer not available
  Error: Command error
  Error: Event sched_switch: Kernel tracer not available (channel channel0, 
session test-kernel-session)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-101-generic 4.4.0-101.124
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  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'
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   [ 1758.314033] docker0: port 1(veth38d28b9) entered disabled state
   [ 1758.314450] device veth38d28b9 left promiscuous mode
   [ 1758.314452] docker0: port 1(veth38d28b9) entered disabled state
  Date: Thu Nov 16 04:21:00 2017
  HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-101-generic N/A
   linux-backports-modules-4.4.0-101-generic  N/A
   linux-firmware 1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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