ubuntu_sysdig_smoke_test failed on azure 4.11 kernel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Colin Ian King | ||
Xenial |
New
|
Undecided
|
Unassigned | ||
sysdig (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[SRU sysdig XENIAL for 4.11 and 4.13 kernel support]
sysdig DKMS fails to build because of API changes in 4.11, 4.13
[FIX]
Apply the following upstream sysdig commits for various kernel compat fixes:
- [5fef96] Fix for kernel < 3.9 with CPU_ACCOUNTING_
- [29c40f] Fix cputime for kernel 3.8 and 2.6.18
- [4596f0] Make sure to unlock mutex during error paths
- [460f6e] Update probe module for kernel 4.11 (#829)
[TEST]
from kernel team autotests:
sudo autotest/
Without the fixes, these will fail. With the fixes, the regression tests pass. Run this 4.4, 4.8, 4.11 azure and 4.13-hwe kernels, must pass on all three kernel versions.
[REGRESSION POTENTIAL]
This affects just the sysdig driver. Could break on pre-4.13 older kernels, so needs regression checking on supported kernel versions.
-------
azure : 4.11.0-1014.14
== sysdig smoke test to trace dd, cat, read and writes ==
Limiting raw capture file to 16384 blocks
Try 1 of 10
Could not find start of capture message, maybe sysdig didn't start?
Raw capture file is 0 Mbytes
Converted events file is 0 Mbytes
Try 2 of 10
Could not find start of capture message, maybe sysdig didn't start?
Raw capture file is 0 Mbytes
Converted events file is 0 Mbytes
Try 3 of 10
Could not find start of capture message, maybe sysdig didn't start?
Raw capture file is 0 Mbytes
Converted events file is 0 Mbytes
Try 4 of 10
Could not find start of capture message, maybe sysdig didn't start?
Raw capture file is 0 Mbytes
Converted events file is 0 Mbytes
Try 5 of 10
Could not find start of capture message, maybe sysdig didn't start?
Raw capture file is 0 Mbytes
Converted events file is 0 Mbytes
Try 6 of 10
Could not find start of capture message, maybe sysdig didn't start?
Raw capture file is 0 Mbytes
Converted events file is 0 Mbytes
Try 7 of 10
Could not find start of capture message, maybe sysdig didn't start?
Raw capture file is 0 Mbytes
Converted events file is 0 Mbytes
Try 8 of 10
Could not find start of capture message, maybe sysdig didn't start?
Raw capture file is 0 Mbytes
Converted events file is 0 Mbytes
Try 9 of 10
Could not find start of capture message, maybe sysdig didn't start?
Raw capture file is 0 Mbytes
Converted events file is 0 Mbytes
Try 10 of 10
Could not find start of capture message, maybe sysdig didn't start?
Raw capture file is 0 Mbytes
Converted events file is 0 Mbytes
Found:
0 sysdig events
0 context switches
0 reads from /dev/zero by dd
0 writes to /dev/null by dd
FAILED (trace at least 25 context switches)
FAILED (trace at least 25 reads of /dev/zero by dd)
FAILED (trace at least 25 writes to /dev/null by dd)
Summary: 0 passed, 3 failed
Changed in linux (Ubuntu): | |
assignee: | nobody → Colin Ian King (colin-king) |
tags: | added: patch |
Changed in sysdig (Ubuntu): | |
status: | New → Fix Released |
Changed in linux (Ubuntu): | |
status: | In Progress → Fix Released |
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 1727275
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.