[Kernel-packages] [Bug 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

2017-11-23 Thread Colin Ian King 
** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

Status in linux package in Ubuntu:
  Fix Released
Status in sysdig package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in sysdig source package in Xenial:
  Fix Released

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_NATIVE disabled.
  - [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/client/autotest-local
  autotest/client/tests/ubuntu_sysdig_smoke_test/control

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727275/+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 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

2017-11-09 Thread Launchpad Bug Tracker 
This bug was fixed in the package sysdig - 0.8.0-1ubuntu3

---
sysdig (0.8.0-1ubuntu3) xenial; urgency=medium

  * Fix build issues with 4.11 kernel headers (LP: #1727275)
backports from upstream sysdig to support 4.11 and HWE 4.13
kernels using the following commits:
- [5fef96] Fix for kernel < 3.9 with CPU_ACCOUNTING_NATIVE disabled.
- [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)

 -- Colin Ian King   Fri, 27 Oct 2017 15:13:11
+0100

** Changed in: sysdig (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

Status in linux package in Ubuntu:
  In Progress
Status in sysdig package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in sysdig source package in Xenial:
  Fix Released

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_NATIVE disabled.
  - [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/client/autotest-local
  autotest/client/tests/ubuntu_sysdig_smoke_test/control

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727275/+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 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

2017-11-09 Thread Po-Hsu Lin 
Hi Łukasz,

I have tested with 3.13, 4.4, 4.10 kernel, also on 4.11 azure.
Thanks

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

Title:
  ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

Status in linux package in Ubuntu:
  In Progress
Status in sysdig package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in sysdig source package in Xenial:
  Fix Committed

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_NATIVE disabled.
  - [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/client/autotest-local
  autotest/client/tests/ubuntu_sysdig_smoke_test/control

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727275/+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 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

2017-11-08 Thread Łukasz Zemczak 
@Po-Hsu Lin: did you do regression checking on supported kernel versions
as per what was written in the [Regression Potential] field?

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

Title:
  ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

Status in linux package in Ubuntu:
  In Progress
Status in sysdig package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in sysdig source package in Xenial:
  Fix Committed

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_NATIVE disabled.
  - [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/client/autotest-local
  autotest/client/tests/ubuntu_sysdig_smoke_test/control

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727275/+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 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

2017-11-01 Thread Po-Hsu Lin 
Verified with sysdig 0.8.0-1ubuntu3 on azure kernel, it works as expected.
Thanks

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

** Tags removed: verification-needed

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

Title:
  ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

Status in linux package in Ubuntu:
  In Progress
Status in sysdig package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in sysdig source package in Xenial:
  Fix Committed

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_NATIVE disabled.
  - [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/client/autotest-local
  autotest/client/tests/ubuntu_sysdig_smoke_test/control

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727275/+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 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

2017-10-31 Thread Łukasz Zemczak 
Hello Po-Hsu, or anyone else affected,

Accepted sysdig into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/sysdig/0.8.0-1ubuntu3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: sysdig (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

Status in linux package in Ubuntu:
  In Progress
Status in sysdig package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in sysdig source package in Xenial:
  Fix Committed

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_NATIVE disabled.
  - [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/client/autotest-local
  autotest/client/tests/ubuntu_sysdig_smoke_test/control

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727275/+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 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

2017-10-31 Thread Łukasz Zemczak 
** Also affects: sysdig (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: sysdig (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: sysdig (Ubuntu)
   Status: New => Fix Released

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

Title:
  ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

Status in linux package in Ubuntu:
  In Progress
Status in sysdig package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in sysdig source package in Xenial:
  New

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_NATIVE disabled.
  - [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/client/autotest-local
  autotest/client/tests/ubuntu_sysdig_smoke_test/control

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727275/+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 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

2017-10-31 Thread Po-Hsu Lin 
Verified with Colin's ppa, the test has passed with the dkms.

08:08:39 INFO | == sysdig smoke test to trace dd, cat, read and writes ==
08:08:39 INFO | Limiting raw capture file to 16384 blocks
08:08:39 INFO | Try 1 of 10
08:08:39 INFO | Sysdig capture started after 1 seconds wait
08:08:39 INFO | Raw capture file is 0 Mbytes
08:08:39 INFO | Converted events file is 0 Mbytes
08:08:39 INFO | Try 2 of 10
08:08:39 INFO | Sysdig capture started after 1 seconds wait
08:08:39 INFO | Raw capture file is 16 Mbytes
08:08:39 INFO | Converted events file is 19 Mbytes
08:08:39 INFO | Found:
08:08:39 INFO |187531 sysdig events
08:08:39 INFO |14705 context switches
08:08:39 INFO |18759 reads from /dev/zero by dd
08:08:39 INFO |18747 writes to /dev/null by dd
08:08:39 INFO | PASSED (trace at least 25 context switches)
08:08:39 INFO | PASSED (trace at least 25 reads of /dev/zero by dd)
08:08:39 INFO | PASSED (trace at least 25 writes to /dev/null by dd)
08:08:39 INFO |  
08:08:39 INFO | Summary: 3 passed, 0 failed

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

Title:
  ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

Status in linux package in Ubuntu:
  In Progress

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_NATIVE disabled.
  - [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/client/autotest-local
  autotest/client/tests/ubuntu_sysdig_smoke_test/control

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727275/+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 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

2017-10-27 Thread Colin Ian King 
Sam, so you mind testing my fix using the PPA below:

sudo add-apt-repository ppa:colin-king/amber
sudo apt-get update
sudo apt-get install sysdig-dkms

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

Title:
  ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

Status in linux package in Ubuntu:
  In Progress

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_NATIVE disabled.
  - [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/client/autotest-local
  autotest/client/tests/ubuntu_sysdig_smoke_test/control

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727275/+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 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

2017-10-27 Thread Ubuntu Foundations Team Bug Bot 
** Tags added: patch

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

Title:
  ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

Status in linux package in Ubuntu:
  In Progress

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_NATIVE disabled.
  - [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/client/autotest-local
  autotest/client/tests/ubuntu_sysdig_smoke_test/control

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727275/+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 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

2017-10-27 Thread Colin Ian King 
Debdiff

** Patch added: "debdiff.diff"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727275/+attachment/4997947/+files/debdiff.diff

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

Title:
  ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

Status in linux package in Ubuntu:
  In Progress

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_NATIVE disabled.
  - [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/client/autotest-local
  autotest/client/tests/ubuntu_sysdig_smoke_test/control

  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727275/+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 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

2017-10-27 Thread Colin Ian King 
Tested on 4.4, 4.8 and 4.13 HWE kernels on Xenial. Passes regression
tests. Should work fine now on all kernels from 4.4..4.13

** Description changed:

+ [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_NATIVE disabled.
+ - [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/client/autotest-local
+ autotest/client/tests/ubuntu_sysdig_smoke_test/control
+ 
+ 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)
-   
+   == 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
+   

[Kernel-packages] [Bug 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

2017-10-27 Thread Colin Ian King 
Package built OK: https://launchpad.net/~colin-
king/+archive/ubuntu/amber/+packages

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

Title:
  ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

Status in linux package in Ubuntu:
  In Progress

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_NATIVE disabled.
  - [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/client/autotest-local
  autotest/client/tests/ubuntu_sysdig_smoke_test/control

  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

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