sysdig smoke test failed on AMD speedway, Raw capture file is 0 Mbytes

Bug #1717884 reported by Po-Hsu Lin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Colin Ian King

Bug Description

This issue can be reproduced on 4.12 and 4.13 kernel.
And it's only happening on node lodygin (AMD speedway).

  == sysdig smoke test to trace dd, cat, read and writes ==
  Limiting raw capture file to 16384 blocks
  Try 1 of 10
  Raw capture file is 0 Mbytes
  Converted events file is 0 Mbytes
  (repeat for 10 times)
  Found:
     0 sysdig events
     0 dd context switches
     0 cat context switches
     0 reads from /dev/zero by dd
     0 writes to /dev/null by dd
  FAILED (trace at least 25 context switches involving dd)
  FAILED (trace at least 25 context switches involving cat)
  FAILED (trace at least 25 reads of /dev/zero by dd)
  FAILED (trace at least 25 writes to /dev/null by dd)

  stderr:
  /home/ubuntu/autotest/client/tests/ubuntu_sysdig_smoke_test/ubuntu_sysdig_smoke_test.sh: line 115: 3738 Killed sysdig --unbuffered -w ${TMPFILE}.raw &> /dev/null
  stat: cannot stat '/home/ubuntu/autotest/client/results/default/ubuntu_sysdig_smoke_test.sysdig-smoke-testsysdig-kernel-trace-3735.tmp.raw': No such file or directory

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-11-generic 4.13.0-11.12
ProcVersionSignature: User Name 4.13.0-11.12-generic 4.13.1
Uname: Linux 4.13.0-11-generic x86_64
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Sep 18 09:39 seq
 crw-rw---- 1 root audio 116, 33 Sep 18 09:39 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:

Date: Mon Sep 18 09:41:01 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: AMD Corporation Speedway
PciMultimedia:

ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic root=UUID=e54320fc-c0c6-4801-843e-13288cad433e ro
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-11-generic N/A
 linux-backports-modules-4.13.0-11-generic N/A
 linux-firmware 1.168
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/24/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: RSW1001E
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Speedway
dmi.board.vendor: AMD Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: To be filled by O.E.M.
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRSW1001E:bd07/24/2017:svnAMDCorporation:pnSpeedway:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnSpeedway:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct17:cvrTobefilledbyO.E.M.:
dmi.product.family: Default string
dmi.product.name: Speedway
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: AMD Corporation

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Changed in linux (Ubuntu):
assignee: nobody → Colin Ian King (colin-king)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

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 1717884

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
Revision history for this message
Colin Ian King (colin-king) wrote :

Looks like the timeout for the capture occurs before sysdig manages to start. Need to add a polling delay that checks if sysdig is up and ready before we kick off the capture timeout.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Tested with Colin's patch on two amd64 systems with Artful kernel. They both passed.

Changed in linux (Ubuntu):
status: Incomplete → Fix Committed
importance: Undecided → Medium
Revision history for this message
Colin Ian King (colin-king) wrote :
Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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