lttng-smoke test failed on i386 4.18 kernel

Bug #1802495 reported by Po-Hsu Lin on 2018-11-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Medium
Colin Ian King
linux (Ubuntu)
Undecided
Unassigned
Cosmic
Undecided
Unassigned

Bug Description

There is one failure in the lttng-smoke test.

FAILED (did not trace any open system calls)

  == lttng smoke test of session create/destroy ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-15702-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)

  == lttng smoke test list kernel events ==
  PASSED (lttng list --kernel)

  == lttng smoke test trace open/close system calls ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-15702-session
  PASSED (lttng create)
  Kernel event open created in channel channel0
  Kernel event openat created in channel channel0
  Kernel event close created in channel channel0
  PASSED (lttng enable-event)
  Tracing started for session test-kernel-session
  PASSED (lttng start)
  Waiting for data availability.....
  Tracing stopped for session test-kernel-session
  PASSED (lttng stop)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)
  FAILED (did not trace any open system calls)

  == lttng smoke test trace context switches ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-15702-session
  PASSED (lttng create)
  Kernel event sched_switch created in channel channel0
  PASSED (lttng enable-event)
  Tracing started for session test-kernel-session
  PASSED (lttng start)
  Waiting for data availability.....
  Tracing stopped for session test-kernel-session
  PASSED (lttng stop)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)
  Found 21349 dd and 73100 context switches
  PASSED (simple system call tracing with babeltrace)

  Summary: 13 passed, 1 failed

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-10-generic 4.18.0-10.11
ProcVersionSignature: User Name 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic i686
NonfreeKernelModules: lttng_probe_writeback lttng_probe_workqueue lttng_probe_v4l2 lttng_probe_vmscan lttng_probe_udp lttng_probe_timer lttng_probe_sunrpc lttng_probe_statedump lttng_probe_sock lttng_probe_skb lttng_probe_signal lttng_probe_scsi lttng_probe_sched lttng_probe_regulator lttng_probe_rcu lttng_probe_random lttng_probe_printk lttng_probe_power lttng_probe_net lttng_probe_napi lttng_probe_module lttng_probe_kvm lttng_probe_kmem lttng_probe_jbd2 lttng_probe_irq lttng_probe_gpio lttng_probe_compaction lttng_probe_block lttng_probe_asoc lttng_ring_buffer_metadata_mmap_client lttng_ring_buffer_client_mmap_overwrite lttng_ring_buffer_client_mmap_discard lttng_ring_buffer_metadata_client lttng_ring_buffer_client_overwrite lttng_ring_buffer_client_discard lttng_tracer lttng_statedump lttng_kprobes lttng_clock lttng_lib_ring_buffer lttng_kretprobes
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Nov 9 11:35 seq
 crw-rw---- 1 root audio 116, 33 Nov 9 11:35 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu13
Architecture: i386
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:

Date: Fri Nov 9 11:51:45 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Dell Inc. PowerEdge R310
PciMultimedia:

ProcFB: 0 mgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=ded56b2d-3057-4d58-a1e5-422853291ffd ro console=ttyS0,115200n8
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-10-generic N/A
 linux-backports-modules-4.18.0-10-generic N/A
 linux-firmware 1.175
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/17/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.8.2
dmi.board.name: 05XKKK
dmi.board.vendor: Dell Inc.
dmi.board.version: A05
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R310
dmi.sys.vendor: Dell Inc.

Po-Hsu Lin (cypressyew) wrote :
summary: - lttng-smoke test failed on i386
+ lttng-smoke test failed on i386 Cosmic

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1802495

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Po-Hsu Lin (cypressyew) on 2018-11-29
Changed in ubuntu-kernel-tests:
status: New → Confirmed

After the lttng module build issue solved (bug 1802443). This issue can be found on B-hwe (4.18.0-13.14~18.04.1) as well.

summary: - lttng-smoke test failed on i386 Cosmic
+ lttng-smoke test failed on i386 Cosmic / B-hwe
summary: - lttng-smoke test failed on i386 Cosmic / B-hwe
+ lttng-smoke test failed on i386 4.18 kernel
Po-Hsu Lin (cypressyew) on 2019-05-20
description: updated
Changed in ubuntu-kernel-tests:
importance: Undecided → Medium
assignee: nobody → Colin Ian King (colin-king)
Colin Ian King (colin-king) wrote :

It appears that syscalls are not available on i386, got zero syscalls on bionic, cosmic, disco. It works OK on xenial.

sudo lttng list --kernel --syscall

..produces zero syscalls.

Colin Ian King (colin-king) wrote :

And for amd64 bionic+ it fails to generate syscall info too.

Colin Ian King (colin-king) wrote :

Course bisect, this does not work with stock upstream kernels since at least 4.7-rc1. For now I'm going to disabled this part of the lttng tests until I can get it to work again with stock 4.8+ kernels.

@Sam, am I missing something, but has this been failing for a while and it's not been noticed?

Po-Hsu Lin (cypressyew) wrote :

This is something that's failing for a while (was affected by bug 1802443, and then this one since 4.18.0-13.14~18.04.1)

Colin Ian King (colin-king) wrote :

I've reported this to the upstream lttng project: https://bugs.lttng.org/issues/1184

Brad Figg (brad-figg) on 2019-07-24
tags: added: cscc
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.