[Group.of.nepali.translators] [Bug 1934910] Re: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux-hwe-5.4/5.4.0-79.88~18.04.1

[Colin Ian King]

** Also affects: zfs-linux (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: linux-hwe-5.4 (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** No longer affects: linux-hwe-5.4 (Ubuntu Groovy)

** Changed in: zfs-linux (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Bionic)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Focal)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Focal)
 Assignee: Colin Ian King (colin-king) => (unassigned)

** Changed in: zfs-linux (Ubuntu Groovy)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Hirsute)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Impish)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Focal)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Hirsute)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Impish)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: zfs-linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: zfs-linux (Ubuntu Focal)
   Status: New => In Progress

** Changed in: zfs-linux (Ubuntu Groovy)
   Status: New => In Progress

** Changed in: zfs-linux (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: zfs-linux (Ubuntu Impish)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1934910

Title:
  zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux-
  hwe-5.4/5.4.0-79.88~18.04.1

Status in linux-hwe-5.4 package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  In Progress
Status in zfs-linux source package in Xenial:
  In Progress
Status in linux-hwe-5.4 source package in Bionic:
  New
Status in zfs-linux source package in Bionic:
  In Progress
Status in zfs-linux source package in Focal:
  In Progress
Status in zfs-linux source package in Groovy:
  In Progress
Status in zfs-linux source package in Hirsute:
  In Progress
Status in zfs-linux source package in Impish:
  In Progress

Bug description:
  == zfs-linux SRU ==

  IMPISH, HIRSUTE, GROOVY, FOCAL, BIONIC, XENIAL

  [Impact]

  The zfs debian scrub test sometimes times out on slower test systems
  because scrub can take a while to complete and the scrub test can
  time out.  The test needs some more intelligence to detect this
  and a longer time out for slower systems.

  The fix now polls the scrub completion more thoroughly and increases
  timeout to 15 minutes.

  [Test Plan]

  Run the test with autopkgtest on slow file systems. With the fix the test
  has longer timeout and will pass rather than fail with a timeout. e.g.

  autopkgtest zfs-linux_2.0.3-8ubuntu5.dsc -- null

  
  [Where problems could occur]

  The timeout is hard coded to 15 minutes. This should be enough for slow
  devices with the small ZFS volume set used by this test. However, it may
  still fail if the backing store is really slow. However, we don't want the
  test to be blocked indefinitely waiting for a timeout, so a 15 minute
  scrub timeout seems to be long enough to be more than reasonable. Any longer 
and it's highly likely that the scrub has hung.

  [Other Info]

  This test is almost identical to the same scrub test run from the kernel
  team autotest zfs smoke test, so it has been exercised regularly and is
  known to reliably.

  -

  
  This is a scripted bug report about ADT failures while running zfs-linux 
tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused 
by the dep8 tests of the tested source or the kernel has yet to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343

[Group.of.nepali.translators] [Bug 1934910] Re: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux-hwe-5.4/5.4.0-79.88~18.04.1

[Colin Ian King]

** No longer affects: zfs-linux (Ubuntu Groovy)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1934910

Title:
  zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux-
  hwe-5.4/5.4.0-79.88~18.04.1

Status in linux-hwe-5.4 package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  New
Status in zfs-linux source package in Xenial:
  New
Status in linux-hwe-5.4 source package in Bionic:
  New
Status in zfs-linux source package in Bionic:
  New
Status in zfs-linux source package in Focal:
  New
Status in zfs-linux source package in Hirsute:
  New
Status in zfs-linux source package in Impish:
  New

Bug description:
  == zfs-linux SRU ==

  IMPISH, HIRSUTE, GROOVY, FOCAL, BIONIC, XENIAL

  [Impact]

  The zfs debian scrub test sometimes times out on slower test systems
  because scrub can take a while to complete and the scrub test can
  time out.  The test needs some more intelligence to detect this
  and a longer time out for slower systems.

  The fix now polls the scrub completion more thoroughly and increases
  timeout to 15 minutes.

  [Test Plan]

  Run the test with autopkgtest on slow file systems. With the fix the test
  has longer timeout and will pass rather than fail with a timeout. e.g.

  autopkgtest zfs-linux_2.0.3-8ubuntu5.dsc -- null

  
  [Where problems could occur]

  The timeout is hard coded to 15 minutes. This should be enough for slow
  devices with the small ZFS volume set used by this test. However, it may
  still fail if the backing store is really slow. However, we don't want the
  test to be blocked indefinitely waiting for a timeout, so a 15 minute
  scrub timeout seems to be long enough to be more than reasonable. Any longer 
and it's highly likely that the scrub has hung.

  [Other Info]

  This test is almost identical to the same scrub test run from the kernel
  team autotest zfs smoke test, so it has been exercised regularly and is
  known to reliably.

  -

  
  This is a scripted bug report about ADT failures while running zfs-linux 
tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused 
by the dep8 tests of the tested source or the kernel has yet to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz

  This is a similar issue as reported on bug 1885289, which was fixed on
  autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests
  don't use autotest, the test script run comes from the zfs-linux dkms
  source package, debian/tests/kernel-smoke-test-scrub.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1934910] Re: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux-hwe-5.4/5.4.0-79.88~18.04.1

[Colin Ian King]

** Also affects: zfs-linux (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: linux-hwe-5.4 (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

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

** Also affects: zfs-linux (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: linux-hwe-5.4 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: zfs-linux (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: linux-hwe-5.4 (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: zfs-linux (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: linux-hwe-5.4 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** No longer affects: linux-hwe-5.4 (Ubuntu Xenial)

** No longer affects: linux-hwe-5.4 (Ubuntu Focal)

** No longer affects: linux-hwe-5.4 (Ubuntu Groovy)

** No longer affects: linux-hwe-5.4 (Ubuntu Hirsute)

** No longer affects: linux-hwe-5.4 (Ubuntu Impish)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1934910

Title:
  zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux-
  hwe-5.4/5.4.0-79.88~18.04.1

Status in linux-hwe-5.4 package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  New
Status in zfs-linux source package in Xenial:
  New
Status in linux-hwe-5.4 source package in Bionic:
  New
Status in zfs-linux source package in Bionic:
  New
Status in zfs-linux source package in Focal:
  New
Status in zfs-linux source package in Groovy:
  New
Status in zfs-linux source package in Hirsute:
  New
Status in zfs-linux source package in Impish:
  New

Bug description:
  This is a scripted bug report about ADT failures while running zfs-
  linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether
  this is caused by the dep8 tests of the tested source or the kernel
  has yet to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz

  This is a similar issue as reported on bug 1885289, which was fixed on
  autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests
  don't use autotest, the test script run comes from the zfs-linux dkms
  source package, debian/tests/kernel-smoke-test-scrub.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1873448] Re: stress-ng in xenial segfaults on dup stressor on arm64

[Colin Ian King]

** Changed in: stress-ng (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1873448

Title:
  stress-ng in xenial segfaults on dup stressor on arm64

Status in stress-ng package in Ubuntu:
  Won't Fix
Status in stress-ng source package in Xenial:
  Won't Fix

Bug description:
  == SRU justification, Xenial ==

  When running the --dup stressor with stress-ng with a process that is
  allowed to open more than 64K file descriptors we trigger a segfault
  because of an array overflow.

  == Fix ==

  A simple fix is required, just a bounds check on the maximum size
  max_fd to limit it to the size of the fds array.

  == Testcase ==

  stress-ng on arm64 with the --dup stressor will trigger this quite
  easily. The bug was found during regression testing of the previous
  xenial stress-ng upload.

  stress-ng --dup

  without the fix this will segfault. with the fix it works correctly.

  == Regression Potential ==

  Low. This affects one stress case in stress-ng, the fix is localized
  and it a backport from an upstream stress-ng fix that has been working
  for several years w/o problem.

  

  
  Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
  stress-ng: info:  [10979] defaulting to a 86400 second run per stressor
  stress-ng: info:  [10979] dispatching hogs: 1 dup
  stress-ng: info:  [10979] cache allocate: using built-in defaults as unable 
to determine cache details
  stress-ng: info:  [10979] cache allocate: default cache size: 2048K
  [New process 10982]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
  65536 1048573

  Thread 2.1 "stress-ng-dup" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0xb7ff1000 (LWP 10982)]
  0x004191f0 in stress_dup (counter=0xb7cbee78, instance=, max_ops=0, name=)
  at stress-dup.c:63
  63fds[i] = dup(fds[0]);

  This requires a fix  from commit:

  67d872611b860a79b03dca8c7549e5cee7fec4eb Mon Sep 17 00:00:00 2001
  From: Colin Ian King 
  Date: Tue, 8 Nov 2016 15:50:20 +
  Subject: [PATCH] treewide: remove messy #if defined() build checks

  diff --git a/stress-dup.c b/stress-dup.c
  index 2fe2d6a6..0ac13fee 100644
  --- a/stress-dup.c
  +++ b/stress-dup.c
  @@ -45,7 +45,7 @@ int stress_dup(
  const char *name)
   {
  int fds[STRESS_FD_MAX];
  -   const size_t max_fd = stress_get_file_limit();
  +   size_t max_fd = stress_get_file_limit();
  size_t i;
   #if defined(__linux__)
  bool do_dup3 = true;
  @@ -53,6 +53,9 @@ int stress_dup(

  (void)instance;

  +   if (max_fd > SIZEOF_ARRAY(fds))
  +   max_fd =  SIZEOF_ARRAY(fds);
  +
  fds[0] = open("/dev/zero", O_RDONLY);
  if (fds[0] < 0) {
  pr_fail_dbg(name, "open on /dev/zero");

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1873448/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1813749] Re: zfs-linux 0.6.5.6-0ubuntu26 ADT test failure with linux-snapdragon 4.4.0-1107.112

[Colin Ian King]

** Changed in: zfs-linux (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1813749

Title:
  zfs-linux 0.6.5.6-0ubuntu26 ADT test failure with linux-snapdragon
  4.4.0-1107.112

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  ADT Testing failed with xenial/linux-snapdragon on:
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/z/zfs-linux/20190125_170958_97a22@/log.gz

  The debian test script (debian/tests/kernel-smoke-test) doesn't load
  the zfs module causing the tests to fail.

  [Test Case]
  Run autopkgtest of zfs-linux package with xenial/linux-snapdragon kernel.

  Alternatively one can install the zfs-dkms package, download the zfs-linux 
source from version 0.6.5.6-0ubuntu26 and run:
  $ sudo ./debian/tests/kernel-smoke-test

  Making sure the modules are not loaded before running the test
  manually.

  [Fix]
  The solution is to load the zfs module before starting the tests, as done by 
the test script shipped by the packages for Bionic and later series.

  [Regression Potential] 
  Low. The fix changes only the debian test script, so no impact on regular 
users.

  [Other Info]
  The tests were not failing before. I suspect that's being caused by a change 
in the order that the packages are installed before the tests start. With 
previous ADT runs, the zfsutils-linux package was installed after zfs-dkms, so 
that caused systemd to start the zfs-import-scan service, which loaded the 
modules. On these later ADT failed runs, zfs-dkms is installed last, so the 
service is not reloaded and the modules stay unloaded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1813749/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1873448] Re: stress-ng in xenial segfaults on dup stressor on arm64

[Colin Ian King]

** Changed in: stress-ng (Ubuntu Xenial)
   Status: In Progress => Fix Released

** Changed in: stress-ng (Ubuntu Xenial)
   Status: Fix Released => Fix Committed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1873448

Title:
  stress-ng in xenial segfaults on dup stressor on arm64

Status in stress-ng package in Ubuntu:
  New
Status in stress-ng source package in Xenial:
  Fix Committed

Bug description:
  == SRU justification, Xenial ==

  When running the --dup stressor with stress-ng with a process that is
  allowed to open more than 64K file descriptors we trigger a segfault
  because of an array overflow.

  == Fix ==

  A simple fix is required, just a bounds check on the maximum size
  max_fd to limit it to the size of the fds array.

  == Testcase ==

  stress-ng on arm64 with the --dup stressor will trigger this quite
  easily. The bug was found during regression testing of the previous
  xenial stress-ng upload.

  stress-ng --dup

  without the fix this will segfault. with the fix it works correctly.

  == Regression Potential ==

  Low. This affects one stress case in stress-ng, the fix is localized
  and it a backport from an upstream stress-ng fix that has been working
  for several years w/o problem.

  

  
  Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
  stress-ng: info:  [10979] defaulting to a 86400 second run per stressor
  stress-ng: info:  [10979] dispatching hogs: 1 dup
  stress-ng: info:  [10979] cache allocate: using built-in defaults as unable 
to determine cache details
  stress-ng: info:  [10979] cache allocate: default cache size: 2048K
  [New process 10982]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
  65536 1048573

  Thread 2.1 "stress-ng-dup" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0xb7ff1000 (LWP 10982)]
  0x004191f0 in stress_dup (counter=0xb7cbee78, instance=, max_ops=0, name=)
  at stress-dup.c:63
  63fds[i] = dup(fds[0]);

  This requires a fix  from commit:

  67d872611b860a79b03dca8c7549e5cee7fec4eb Mon Sep 17 00:00:00 2001
  From: Colin Ian King 
  Date: Tue, 8 Nov 2016 15:50:20 +
  Subject: [PATCH] treewide: remove messy #if defined() build checks

  diff --git a/stress-dup.c b/stress-dup.c
  index 2fe2d6a6..0ac13fee 100644
  --- a/stress-dup.c
  +++ b/stress-dup.c
  @@ -45,7 +45,7 @@ int stress_dup(
  const char *name)
   {
  int fds[STRESS_FD_MAX];
  -   const size_t max_fd = stress_get_file_limit();
  +   size_t max_fd = stress_get_file_limit();
  size_t i;
   #if defined(__linux__)
  bool do_dup3 = true;
  @@ -53,6 +53,9 @@ int stress_dup(

  (void)instance;

  +   if (max_fd > SIZEOF_ARRAY(fds))
  +   max_fd =  SIZEOF_ARRAY(fds);
  +
  fds[0] = open("/dev/zero", O_RDONLY);
  if (fds[0] < 0) {
  pr_fail_dbg(name, "open on /dev/zero");

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1873448/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1873448] [NEW] stress-ng in xenial segfaults on dup stressor on arm64

[Colin Ian King]

Public bug reported:

Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
stress-ng: info:  [10979] defaulting to a 86400 second run per stressor
stress-ng: info:  [10979] dispatching hogs: 1 dup
stress-ng: info:  [10979] cache allocate: using built-in defaults as unable to 
determine cache details
stress-ng: info:  [10979] cache allocate: default cache size: 2048K
[New process 10982]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
65536 1048573

Thread 2.1 "stress-ng-dup" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7ff1000 (LWP 10982)]
0x004191f0 in stress_dup (counter=0xb7cbee78, instance=, max_ops=0, name=)
at stress-dup.c:63
63  fds[i] = dup(fds[0]);

This requires a fix  from commit:

67d872611b860a79b03dca8c7549e5cee7fec4eb Mon Sep 17 00:00:00 2001
From: Colin Ian King 
Date: Tue, 8 Nov 2016 15:50:20 +
Subject: [PATCH] treewide: remove messy #if defined() build checks

diff --git a/stress-dup.c b/stress-dup.c
index 2fe2d6a6..0ac13fee 100644
--- a/stress-dup.c
+++ b/stress-dup.c
@@ -45,7 +45,7 @@ int stress_dup(
const char *name)
 {
int fds[STRESS_FD_MAX];
-   const size_t max_fd = stress_get_file_limit();
+   size_t max_fd = stress_get_file_limit();
size_t i;
 #if defined(__linux__)
bool do_dup3 = true;
@@ -53,6 +53,9 @@ int stress_dup(

(void)instance;

+   if (max_fd > SIZEOF_ARRAY(fds))
+   max_fd =  SIZEOF_ARRAY(fds);
+
fds[0] = open("/dev/zero", O_RDONLY);
if (fds[0] < 0) {
pr_fail_dbg(name, "open on /dev/zero");

** Affects: stress-ng (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: stress-ng (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Changed in: stress-ng
   Status: New => In Progress

** Changed in: stress-ng
   Importance: Undecided => Medium

** Changed in: stress-ng
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Also affects: stress-ng (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: stress-ng

** Also affects: stress-ng (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1873448

Title:
  stress-ng in xenial segfaults on dup stressor on arm64

Status in stress-ng package in Ubuntu:
  New
Status in stress-ng source package in Xenial:
  New

Bug description:
  Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
  stress-ng: info:  [10979] defaulting to a 86400 second run per stressor
  stress-ng: info:  [10979] dispatching hogs: 1 dup
  stress-ng: info:  [10979] cache allocate: using built-in defaults as unable 
to determine cache details
  stress-ng: info:  [10979] cache allocate: default cache size: 2048K
  [New process 10982]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
  65536 1048573

  Thread 2.1 "stress-ng-dup" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0xb7ff1000 (LWP 10982)]
  0x004191f0 in stress_dup (counter=0xb7cbee78, instance=, max_ops=0, name=)
  at stress-dup.c:63
  63fds[i] = dup(fds[0]);

  This requires a fix  from commit:

  67d872611b860a79b03dca8c7549e5cee7fec4eb Mon Sep 17 00:00:00 2001
  From: Colin Ian King 
  Date: Tue, 8 Nov 2016 15:50:20 +
  Subject: [PATCH] treewide: remove messy #if defined() build checks

  diff --git a/stress-dup.c b/stress-dup.c
  index 2fe2d6a6..0ac13fee 100644
  --- a/stress-dup.c
  +++ b/stress-dup.c
  @@ -45,7 +45,7 @@ int stress_dup(
  const char *name)
   {
  int fds[STRESS_FD_MAX];
  -   const size_t max_fd = stress_get_file_limit();
  +   size_t max_fd = stress_get_file_limit();
  size_t i;
   #if defined(__linux__)
  bool do_dup3 = true;
  @@ -53,6 +53,9 @@ int stress_dup(

  (void)instance;

  +   if (max_fd > SIZEOF_ARRAY(fds))
  +   max_fd =  SIZEOF_ARRAY(fds);
  +
  fds[0] = open("/dev/zero", O_RDONLY);
  if (fds[0] < 0) {
  pr_fail_dbg(name, "open on /dev/zero");

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1873448/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1853832] Re: stress-ng --timer-slack option should be a zero arg option, it current eats the next arg

[Colin Ian King]

** Description changed:

- == SRU [Disco][Eoan] ==
+ == SRU [Bionic][Disco][Eoan] ==
  
  stress-ng --timer 1 --timer-freq 10 --timer-slack -t 1 runs for a
  whole day and not 1 second. The timer-slack option eats the -t1 arg
  because it is defined as having an arg when in fact it is a zero arg
  option.
  
  == Fix ==
  
  Upstream fix (in Focal):
  
  commit e044133ed6ebdbac16775d8ae0d130bc2dac96ea
  Author: Colin Ian King 
  Date:   Mon Nov 25 12:05:30 2019 +
  
  Fix --timer-slack from consuming the following arg (LP: #1853832)
  
  == Test ==
  
  stress-ng --timer 1 --timer-freq 10 --timer-slack -t 1
  
  Without the fix, this will run by default for 24 hours.  With the fix
  the -t option is parsed and it will run for 1 second as intended.
  
  == Regression Potential ==
  
  This is a one line arg parsing change so change set is really limited to
  this one --timer-slack option.  Users may find the behaviour now changes
  because it no longer consumes the next arg and hence the next arg works
  and hence changes functionality.

** Also affects: stress-ng (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: stress-ng (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: stress-ng (Ubuntu Xenial)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1853832

Title:
  stress-ng --timer-slack option should be a zero arg option, it current
  eats the next arg

Status in stress-ng package in Ubuntu:
  Fix Released
Status in stress-ng source package in Xenial:
  New
Status in stress-ng source package in Bionic:
  New
Status in stress-ng source package in Disco:
  New
Status in stress-ng source package in Eoan:
  In Progress

Bug description:
  == SRU [Bionic][Disco][Eoan] ==

  stress-ng --timer 1 --timer-freq 10 --timer-slack -t 1 runs for a
  whole day and not 1 second. The timer-slack option eats the -t1 arg
  because it is defined as having an arg when in fact it is a zero arg
  option.

  == Fix ==

  Upstream fix (in Focal):

  commit e044133ed6ebdbac16775d8ae0d130bc2dac96ea
  Author: Colin Ian King 
  Date:   Mon Nov 25 12:05:30 2019 +

  Fix --timer-slack from consuming the following arg (LP: #1853832)

  == Test ==

  stress-ng --timer 1 --timer-freq 10 --timer-slack -t 1

  Without the fix, this will run by default for 24 hours.  With the fix
  the -t option is parsed and it will run for 1 second as intended.

  == Regression Potential ==

  This is a one line arg parsing change so change set is really limited
  to this one --timer-slack option.  Users may find the behaviour now
  changes because it no longer consumes the next arg and hence the next
  arg works and hence changes functionality.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1853832/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1845005] Re: rmap stressor should return EXIT_NO_RESOURCE when out of free space

[Colin Ian King]

** Also affects: stress-ng (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: stress-ng (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: stress-ng (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: stress-ng (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: stress-ng (Ubuntu Disco)
   Importance: Undecided
   Status: New

** No longer affects: stress-ng

** Changed in: stress-ng (Ubuntu Eoan)
   Importance: Undecided => Medium

** Changed in: stress-ng (Ubuntu Eoan)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: stress-ng (Ubuntu Eoan)
   Status: New => Fix Committed

** Changed in: stress-ng (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: stress-ng (Ubuntu Bionic)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: stress-ng (Ubuntu Disco)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** No longer affects: stress-ng (Ubuntu Xenial)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1845005

Title:
  rmap stressor should return EXIT_NO_RESOURCE when out of free space

Status in stress-ng package in Ubuntu:
  Fix Committed
Status in stress-ng source package in Bionic:
  New
Status in stress-ng source package in Disco:
  New
Status in stress-ng source package in Eoan:
  Fix Committed

Bug description:
  The rmap stressor should return EXIT_NO_RESOURCE and not EXIT_FAILURE
  when attempting to fallocate a file to rmap onto. This makes it a non-
  critical failure based on lack of resources rather than a stress test
  failure because rmap failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1845005/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1480349] Re: thermald breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 v3

[Colin Ian King]

The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history.  This bug has already been fixed
and the verification for bionic can be ignored.

** No longer affects: thermald (Ubuntu Bionic)

** Tags removed: verification-needed verification-needed-bionic
** Tags added: verifcation-done

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1480349

Title:
  thermald breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 v3

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Trusty:
  Fix Released
Status in thermald source package in Vivid:
  Won't Fix
Status in thermald source package in Wily:
  Fix Released
Status in thermald source package in Xenial:
  Fix Released

Bug description:
  SRU Justification Wily, Vivid, Trusty

  CPU scaling on a class of Intel CPUs is not functioning correctly,
  causing the CPU to be throttled back to the lowest CPU frequency

  [FIX]
  Upstream cherry picks, as recommended by Intel
  f4e316ef4d8d8c9a558ef5bfa74e25303c46a985 ("Add white list of the cpu ids")
  18d1574230c6b9b4e8876c0b6739c074a24205e6 ("Move parser init to thd_engine")
  6749427098434ccad81fa8c5f2a3e102fc1644f7 ("Remove wild card for loading")
  ba4fe1e7bb77d09530544cda860fba559603ec83 ("Error recovery when sysfs attrib 
read fails")

  Plus 4 changes to allow clean and simpler patching of the above 4 fix
  to reduce the risk of breaking thermald with a complex backport:

  Remove trailing ':' from THD engine failure message
  Remove !! from "No coretemp sysfs found"
  Add new option for config file
  Support target state

  Essentially we now have a white list of valid CPUs to run thermald on,
  so we can exclude the issues on a wider class of CPUs.

  [TEST CASE]
  With the buggy thermald, CPU is pegged at the lowest CPU frequency.  With the 
fixed thermald, CPU scaling now works.

  [REGRESSION POTENTIAL]
  We are allowing thermald now to run on a strict set of CPUs, so we are hoping 
that the whitelist covers the class that we can legitimately run thermald 
against.

  --

  When I boot with this installed frequency scaling is no longer
  behaving as expected.

  It seems that with this installed, the OS loses control of the
  scaling.

  It seems that scaling is performed, though. And very much to the
  purpose of power saving.

  Performance is terrible because of this. And I do mean terrible.

  The default governor is powersave.

  Setting the governor to performance (yes, on all cores) doesn't seem
  to change to scaling behavior. The frequency doesn't pass 800MHz.

  I would like to use Intel's microcode updates, but I have to have my
  CPU running at the speed for which it costs so damn much.

  Any suggestions?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: intel-microcode 3.20150121.1
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 31 17:56:39 2015
  InstallationDate: Installed on 2010-10-12 (1753 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: intel-microcode
  UpgradeStatus: Upgraded to wily on 2014-11-11 (262 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1480349/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1656528] Re: thermald spamming syslog with 'sysfs write failed constraint_0_power_limit_uw'

[Colin Ian King]

The bionic SRU test message occurred because I accidentally uploaded the
package with the entire old history.  This bug has already been fixed
and the verification for bionic can be ignored.

** No longer affects: thermald (Ubuntu Bionic)

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1656528

Title:
  thermald spamming syslog with 'sysfs write failed
  constraint_0_power_limit_uw'

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  Fix Released
Status in thermald source package in Yakkety:
  Fix Released
Status in thermald source package in Zesty:
  Fix Released

Bug description:
  [SRU REQUEST, Xenial, Yakkety]

  Thermald is spamming the log with error messages on sysfs write
  failure messages.  Demote these to debug level errors so that they
  aren't logged unless running in debug mode.

  [FIX]

  See comment #24, with the fix the messages are not logged when in
  normal non-debug running mode.

  [REGRESSION POTENIAL]

  Minimal, this just reduces the logging spam by turning messages into
  debug only for when running in debug mode.

  ---

  
  This seems somewhat related to 
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1543046

  For some reason thermald is writing the message "sysfs write failed
  constraint_0_power_limit_uw" to the syslog every few seconds. However,
  there's nothing in the kernel log.

  $ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.10
  DISTRIB_CODENAME=yakkety
  DISTRIB_DESCRIPTION="Ubuntu 16.10"

  $ uname -a
  Linux graham-desktop 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

  $ dpkg -l | grep thermald
  ii  thermald   1.5.3-4amd64Thermal monitoring and controlling 
daemon

  $ grep "sysfs write failed constraint_0_power_limit_uw" /var/log/syslog | wc 
-l
  14160

  $ grep thermald /var/log/kern.log | wc -l
  0

  I'm an experienced Linux user but not an experienced bug submitter, so
  please let me know if I have failed to provide any necessary info. Am
  happy to attach additional logs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1656528/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1833410] Re: idle-page oopses when accessing page frames that are out of range

[Colin Ian King]

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1833410

Title:
  idle-page oopses when accessing page frames that are out of range

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released

Bug description:
  == SRU [Xenial][Bionic][Cosmic][Disco] ==

  == Justification ==

  When accessing page frames that are greater than max_pfn using the
  idle-page sysfs interface an oops is triggered that kills the process
  that writes to the sysfs interface.

  == Fix ==

  Upstream fix currently in linux-next:

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/mm/page_idle.c?id=d96d6145d9796d5f1eac242538d45559e9a23404

  This fixes the maximum pfn threshold allowed.

  == Test ==

  sudo stress-ng --idle-page 0

  this should trigger the oops in ~50% of the cases due to the way the
  threshold calculation in the kernel was handling the maximum threshold
  based on pfn alignments. 31 of 63 of the times it may be under the
  threshold so no oops occurs.  If it does not, increase or decrease the
  number of available pages in a system to trigger the sweet spot of the
  bug.

  == Regression Potential ==

  Minimal, this touches a sysfs kernel interface that is not used much.
  The fix narrows the scope of touching specific page frames, so the
  page frame scope is reduced by the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833410/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1838014] Re: random segfaults in gawk on ppc64el xenial, gawk 1:4.1.3+dfsg-0.1

[Colin Ian King]

I cannot reproduce this issue on other H/W and/or clean installs, so I
think this is due to a fault on a host machine that I'm building on.
Apologies for the noise. Closing this bug.

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

** Changed in: gawk (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: gawk (Ubuntu Bionic)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1838014

Title:
  random segfaults in gawk on ppc64el xenial, gawk 1:4.1.3+dfsg-0.1

Status in gawk package in Ubuntu:
  Invalid
Status in gawk source package in Xenial:
  Invalid
Status in gawk source package in Bionic:
  Invalid

Bug description:
  When building fwts 19.07.00 in a VM or a chroot on Xenial ppc64el, I'm
  seeing segfaults in awk:

  ./configure: line 10171: 15840 Done$LD --help 2>&1
   15842 Segmentation fault  (core dumped) | $EGREP ': supported 
targets:.* elf' > /dev/null

  awk: cmd. line:1: (FILENAME=- FNR=1) fatal error: internal error:
  segfault

  I've also seen segfaults in grep, so I think this may be a recent
  dependency change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gawk/+bug/1838014/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1813749] Re: zfs-linux 0.6.5.6-0ubuntu26 ADT test failure with linux-snapdragon 4.4.0-1107.112

[Colin Ian King]

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1813749

Title:
  zfs-linux 0.6.5.6-0ubuntu26 ADT test failure with linux-snapdragon
  4.4.0-1107.112

Status in zfs-linux package in Ubuntu:
  New
Status in zfs-linux source package in Xenial:
  New

Bug description:
  Testing failed on:
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/arm64/z/zfs-linux/20190125_170958_97a22@/log.gz

  The debian test script (debian/tests/kernel-smoke-test) doesn't load
  the zfs module causing the tests to fail.

  However, the tests were not failing before. I suspect that's being
  caused by a change in the order that the packages are installed before
  the tests start. With previous ADT runs, the zfsutils-linux package
  was installed after zfs-dkms, so that caused systemd to start the zfs-
  import-scan service, which loaded the modules. On these later ADT
  failed runs, zfs-dkms is installed last, so the service is not
  reloaded and the modules stay unloaded.

  The solution is to load the zfs module before starting the tests, as
  done by the test script shipped by the packages for Bionic and later
  series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1813749/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

[Colin Ian King]

** Changed in: thermald (Ubuntu Xenial)
   Status: New => Won't Fix

** Changed in: thermald (Ubuntu Xenial)
 Assignee: Colin Ian King (colin-king) => (unassigned)

** Changed in: thermald (Ubuntu Xenial)
   Importance: High => Undecided

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1803360

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  Won't Fix
Status in thermald source package in Bionic:
  In Progress
Status in thermald source package in Cosmic:
  In Progress
Status in thermald source package in Disco:
  Fix Released

Bug description:
  == SRU Justification, Cosmic, Bionic, Xenial ==

  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

  == Fix ==
   
  Upstream fix 
https://github.com/intel/thermal_daemon/commit/97976782dd26b4d592ccb97eb89c2a3a871a22a9

  == Testing ==

  Exercise CPUs on a fanless INT340X device with _CRT ACPI objects and
  try and reach the trip point. Without the fix thermal overrun occurs
  and this trips CPU shutdown. With the fix, thermald will start to
  throttle the system and get it out of the thermal overrun zone.

  == Regression Potential ==

  This modifies the behavior for just INT340X devices with ACPI _CRT
  objects, specifically, now to honor this setting.  This is a small
  subset of devices with these objects and the change will in face make
  thermald catch systems before they hit thermal overrun, so the risk of
  regression is small. This fix also has been reviewed by the thermal
  experts at Intel, so it seems like a very reasonable workaround for
  these specific use cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1803360] Re: Fanless systems with DPTF shutdown before using any passive cooling device

[Colin Ian King]

** Also affects: thermald (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: thermald (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: thermald (Ubuntu Disco)
   Importance: High
 Assignee: Colin Ian King (colin-king)
   Status: In Progress

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1803360

Title:
  Fanless systems with DPTF shutdown before using any passive cooling
  device

Status in thermald package in Ubuntu:
  In Progress
Status in thermald source package in Xenial:
  New
Status in thermald source package in Bionic:
  New
Status in thermald source package in Cosmic:
  New
Status in thermald source package in Disco:
  In Progress

Bug description:
  There are some new fanless platforms use DPTF's virtual sensor instead
  of INT340X devices.

  Because of that, the _PSV is no longer in use, at least not directly,
  hence its value may set higher then _CRT. To a fanless system that means
  no cooling device gets activated before _CRT, so the system will be
  considered overheated by Linux kernel, and gets shutdown by the kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1803360/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1793464] Re: Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel

[Colin Ian King]

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1793464

Title:
  Kernel panic after the ubuntu_nbd_smoke_test on Xenial kernel

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  == SRU Justification ==

  When running the Ubuntu nbd autotest regression test we trip a hang
  and then a little later a panic message.  There are two upstream
  fixes required as this is actually two issues in one. One fix is to 
  not to shutdown the sock when IRQs are disable and a second to fix is
  to race in the nbd ioctl.

  == Fix ==

  Upstream commits:

  23272a6754b81ff6503e09c743bb4ceeeab39997
nbd: Remove signal usage

  1f7b5cf1be4351e60cf8ae7aab976503dd73c5f8
nbd: Timeouts are not user requested disconnects

  0e4f0f6f63d3416a9e529d99febfe98545427b81
nbd: Cleanup reset of nbd and bdev after a disconnect

  c261189862c6f65117eb3b1748622a08ef49c262
nbd: don't shutdown sock with irq's disabled

  97240963eb308d8d21a89c0459822f7ea98463b4
nbd: fix race in ioctl

  The first 3 patches are prerequisites required for the latter two fixes to 
apply and work correctly.  Most of these backports are minor patch wiggles
  required because later patches have been applied to the driver in earlier 
fixes to this driver.
 

  == Regression Potential ==

  These fixes just touch nbd, so the regression potential is just
  limited to this. Secondly, we are pulling in upstream fixes that exist
  in Bionic and Cosmic kernels, so these are tried and tested fixes.

  == Test Case ==

1. Deploy a node with 4.4 Xenial
2. Run the ubuntu_nbd_smoke_test

  Without the fix, we get hang/crashes.  With the fix one can run this test
  multiple times without any issues at all.

  
  

  This issue can be reproduced on AMD64 KVM //bare-metal node, s390x
  zKVM node

  The test itself will pass, but the system will hang after a few
  second.

  Steps:
    1. Deploy a node with 4.4 Xenial
    2. Run the ubuntu_nbd_smoke_test

  If you have access to the console, you will see that this system
  actually bumped into a kernel panic:

   Unable to handle kernel pointer dereference in virtual kernel address space
   failing address: 03ff802c1000 TEID: 03ff802c1803
   Fault in home space mode while using kernel ASCE.
   Log here (s390x KVM): https://pastebin.ubuntu.com/p/dNmtvbGjmz/

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-136-generic 4.4.0-136.162
  ProcVersionSignature: Ubuntu 4.4.0-136.162-generic 4.4.144
  Uname: Linux 4.4.0-136-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.18
  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.
  Date: Thu Sep 20 03:46:00 2018
  HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 
crashkernel=196M
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-136-generic N/A
   linux-backports-modules-4.4.0-136-generic  N/A
   linux-firmware 1.157.20
  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-kernel-tests/+bug/1793464/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1769937] Re: Error reported when creating ZFS pool with "-t" option, despite successful pool creation

[Colin Ian King]

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

** Also affects: zfs-linux (Ubuntu Cosmic)
   Importance: Medium
 Assignee: Colin Ian King (colin-king)
   Status: In Progress

** Also affects: zfs-linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Bionic)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1769937

Title:
  Error reported when creating ZFS pool with "-t" option, despite
  successful pool creation

Status in linux package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in zfs-linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in zfs-linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in zfs-linux source package in Cosmic:
  In Progress

Bug description:
  When creating a pool with the -t option on Ubuntu 18.04 LTS, it will
  report an error and return a non-zero exit code, but the pool appears
  to be successfully created.

  For example:

  # zpool create -O canmount=off -O mountpoint=none -R /mnt/rpool-25582 -t 
rpool-25582 rpool /dev/mapper/loop2p1
  cannot create 'rpool': no such pool or dataset
  # zpool list
  NAME  SIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  
ALTROOT
  rpool-25582  69.5G  92.5K  69.5G - 0% 0%  1.00x  ONLINE  
/mnt/rpool-25582
  # zpool export rpool-25582
  # zpool import rpool
  # zpool list
  NAMESIZE  ALLOC   FREE  EXPANDSZ   FRAGCAP  DEDUP  HEALTH  ALTROOT
  rpool  69.5G   134K  69.5G - 0% 0%  1.00x  ONLINE  -

  I opened an upstream bug against ZFS on Linux, here:
  https://github.com/zfsonlinux/zfs/issues/7502

  And it has been recently fixed, here:
  https://github.com/zfsonlinux/zfs/pull/7509

  Can this upstream fix be pulled into the Ubuntu 18.04 LTS packages?

  Thanks,
  Prakash

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769937/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1772563] Re: False alarms raised in bionic because 4.15 kernel needs "pm_debug_messages" to be enabled

[Colin Ian King]

** Changed in: fwts/xenial
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1772563

Title:
  False alarms raised in bionic because 4.15 kernel needs
  "pm_debug_messages" to be enabled

Status in Firmware Test Suite:
  Fix Released
Status in Firmware Test Suite bionic series:
  Fix Released
Status in Firmware Test Suite cc series:
  Fix Released
Status in Firmware Test Suite xenial series:
  Fix Released
Status in fwts package in Ubuntu:
  Fix Released
Status in fwts source package in Xenial:
  Fix Released
Status in fwts source package in Bionic:
  Fix Released

Bug description:
  == SRU justfication, BIONIC (and XENIAL too) ==

  [ update - doing the SRU for XENIAL too, Fri, 10th Aug 2018 ]

  While performing Hibernate stress tests on a device with 18.04 server
  installed, we got some failures with FWTS and reported them in
  lp:1769809.

  Even though some of these original failures are due to a bug in
  Checkbox, some others are due to the fact that the Bionic kernel 4.15
  has a parameter "pm_debug_messages" that needs to be enabled.

  If you run the stress tests on this device, you will end up with 4
  PASS and 2 FAIL. But if you run this command before running the stress
  tests:

   $ echo 1 | sudo tee -a /sys/power/pm_debug_messages

  then all tests are marked as PASSED.

  (see comment #9 in the bug above for more information)

  It looks like this is something that should be taked into account by
  FWTS. (but I might be wrong!)

  Thanks!

  == Fix ==

  Upstream commits:

  lib: fwts_set: fix API for fwts_set, add fwts_set_int
  lib: add small helpers top get/set
  acpi: s3: force enable /sys/power/pm_debug_messages (LP: #1772563)
  acpi: s4: also check for file based swap files
  acpi: s4: force enable /sys/power/pm_debug_messages (LP: #1772563)
  acpi: s3power: force enable /sys/power/pm_debug_messages (LP: #1772563)

  == Regression Potential ==

  Minimal, this fix enables a setting in /sys/power/pm_debug_messages
  and then returns it back to the initial saved value. At most this
  could leave debug on if fwts aborts during the test, but this will not
  affect the behavior of a running system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwts/+bug/1772563/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1781364] Re: Kernel error "task zfs:pid blocked for more than 120 seconds"

[Colin Ian King]

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

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

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1781364

Title:
  Kernel error "task zfs:pid blocked for more than 120 seconds"

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in zfs-linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in zfs-linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  In Progress
Status in zfs-linux source package in Cosmic:
  Fix Released

Bug description:
  == SRU Justification, BIONIC ==

  Exercising ZFS with lxd with many mount/umounts can cause lockups and
  120 second timeout messages.

  == How to reproduce bug ==

  In a VM, 2 CPUs, 16GB of memory running Bionic:

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux
  sudo lxd init

  (and with the default init options)

  then run:

  lxd-benchmark launch --count 96 --parallel 96

  This will reliably show the lockup every time without the fix.  With
  the fix (detailed below) one cannot reproduce the lockup.

  == Fix ==

  Upstream ZFS commit

  commit ac09630d8b0bf6c92084a30fdaefd03fd0adbdc1
  Author: Brian Behlendorf 
  Date: Wed Jul 11 15:49:10 2018 -0700

  Fix zpl_mount() deadlock

  == Regression Potential ==

  This just changes the locking in the mount path of ZFS and will only
  affect ZFS mount/unmounts.  The regression potential is small as this
  touches a very small code path that has been exhaustively exercises
  this code under multiple thread/CPU contention and shown not to break.

  --

  ZFS bug report: https://github.com/zfsonlinux/zfs/issues/7691

  "I am using LXD containers that are configured to use a ZFS storage backend.
  I create many containers using a benchmark tool, which probably stresses the 
use of ZFS.
  In two out of four attempts, I got

  [  725.970508] INFO: task lxd:4455 blocked for more than 120 seconds.
  [  725.976730]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  725.983551] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  725.991624] INFO: task txg_sync:4202 blocked for more than 120 seconds.
  [  725.998264]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.005071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.013313] INFO: task lxd:99919 blocked for more than 120 seconds.
  [  726.019609]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.026418] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.034560] INFO: task zfs:100513 blocked for more than 120 seconds.
  [  726.040936]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.047746] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  726.055791] INFO: task zfs:100584 blocked for more than 120 seconds.
  [  726.062170]   Tainted: P   O 4.15.0-20-generic #21-Ubuntu
  [  726.068979] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  Describe how to reproduce the problem

  Start an Ubuntu 18.04 LTS server.
  Install LXD if not already installed.

  sudo apt update
  sudo apt install lxd lxd-client lxd-tools zfsutils-linux

  Configure LXD with sudo lxd init. When prompted for the storage
  backend, select ZFS and specify an empty disk.

  $ sudo lxd init
  Would you like to use LXD clustering? (yes/no) [default=no]:
   Do you want to configure a new storage pool? (yes/no) [default=yes]:
   Name of the new storage pool [default=default]:
   Name of the storage backend to use (dir, zfs) [default=zfs]:
   Create a new ZFS pool? (yes/no) [default=yes]:
   Would you like to use an existing block device? (yes/no) [default=no]: yes
   Path to the existing block device: /dev/sdb
   Would you like to connect to a MAAS server? (yes/no) [default=no]:
   Would you like to create a new local network bridge? (yes/no) [default=yes]: 
no
   Would you like to configure LXD to use an existing bridge or host interface? 
(yes/no) [default=no]: no
   Would you like LXD to be available over the network? (yes/no) [default=no]:
   Would you like stale cached images to be updated automatically? (yes/no) 
[default=yes]
   Would you like a YAML "lxd init" preseed to be printed? (yes/no) 
[default=no]:

  Now run the following to launch 48 containers in batches of 12.

  lxd-benchmark launch --count 48 --parallel 12

  In two out of four attempts, I got the kernel errors.

  I also tried

  echo 1 

[Group.of.nepali.translators] [Bug 1759848] Re: Allow multiple mounts of zfs datasets

[Colin Ian King]

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** No longer affects: linux (Ubuntu Artful)

** No longer affects: zfs-linux (Ubuntu Artful)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1759848

Title:
  Allow multiple mounts of zfs datasets

Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in zfs-linux source package in Xenial:
  New
Status in linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  Pull upstream fix https://trello.com/c/l89Ygj28/352-allow-multiple-
  mounts-of-zfs-datasets to allow multiple mounts

  An attempt to mount an already mounted zfs dataset should return a new
  mount referencing the existing super block, but instead it returns an
  error. Operations such as bind mounts and unsharing mount namespaces
  create new mounts for the sb, which can cause operations to fail which
  involve unmounting and remounting the dataset.  This fix from Seth
  addresses this issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1759848/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1760173] Re: zfs, zpool commands hangs for 10 seconds without a /dev/zfs

[Colin Ian King]

I'd rather not change the default behaviour for non-container
environments as I want to be conservative here, so instead, I'm going to
check if $container exits and set the timeout to zero for this specific
case.

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

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

** Also affects: zfs-linux (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: lxd (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: zfs-linux (Ubuntu Cosmic)
   Importance: High
 Assignee: Colin Ian King (colin-king)
   Status: Triaged

** Also affects: lxd (Ubuntu Cosmic)
   Importance: Undecided
   Status: Invalid

** Also affects: zfs-linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: lxd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** No longer affects: lxd (Ubuntu Xenial)

** No longer affects: lxd (Ubuntu Artful)

** No longer affects: lxd (Ubuntu Bionic)

** No longer affects: lxd (Ubuntu Cosmic)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1760173

Title:
  zfs, zpool commands hangs for 10 seconds without a /dev/zfs

Status in lxd package in Ubuntu:
  Invalid
Status in zfs-linux package in Ubuntu:
  Triaged
Status in zfs-linux source package in Xenial:
  New
Status in zfs-linux source package in Artful:
  New
Status in zfs-linux source package in Bionic:
  New
Status in zfs-linux source package in Cosmic:
  Triaged

Bug description:
  1. # lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2. # apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu19
Candidate: 0.6.5.6-0ubuntu19
Version table:
   *** 0.6.5.6-0ubuntu19 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. When inside a lxd container with zfs storage, zfs list or zpool
  status either return or report what's going on.

  4. When inside a lxd container with zfs storage, zfs list or zpool
  status appears to hang, no output for 10 seconds.

  strace reveals that without a /dev/zfs the tools wait for it to appear
  for 10 seconds but do not provide a command line switch to disable or
  make it more verbose.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu19
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Mar 30 18:09:29 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1760173/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1688890] Re: initramfs-zfs should support misc /dev dirs

[Colin Ian King]

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

** Also affects: zfs-linux (Ubuntu Bionic)
   Importance: Undecided
   Status: Confirmed

** Changed in: zfs-linux (Ubuntu Bionic)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1688890

Title:
  initramfs-zfs should support misc /dev dirs

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  New
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  Right now 'zfs-initramfs', i.e. /usr/share/initramfs-tools/scripts/zfs
  does not support any other directory than /dev for "zpool import ...".
  Therefore even if a pool gets created from a different directory like
  /dev, say /dev/disk/by-id or /dev/chassis/SYS on next reboot /dev will
  be used and thus zpool status will show the /dev/sd* etc. on
  successful import. Beside that now a user does not see the original
  names used in "zpool create ..." the unstable names like "/dev/sd*"
  are shown, which is explicitly NOT recommended.

  The following patch introduces the "pseudo" kernel param named "zdirs"
  - a comma separated list of dev dirs to scan on import - which gets
  used by /usr/share/initramfs-tools/scripts/zfs to honor it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1688890/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1754584] Re: zfs system process hung on container stop/delete

[Colin Ian King]

** Information type changed from Private to Public

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

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

** Changed in: linux (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: zfs-linux (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: zfs-linux (Ubuntu Artful)
   Status: New => In Progress

** Changed in: zfs-linux (Ubuntu Xenial)
   Status: Invalid => In Progress

** Changed in: linux (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Artful)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: zfs-linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: zfs-linux (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux (Ubuntu Bionic)
     Assignee: (unassigned) => Colin Ian King (colin-king)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1754584

Title:
  zfs system process hung on container stop/delete

Status in Native ZFS for Linux:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in zfs-linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in zfs-linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Fix Committed
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  Summary:
  On a Bionic system running 4.15.0-10-generic, after attempting to build 
libaio in a Bionic daily container I cannot stop or delete the container. dmesg 
shows a variety of hung tasks

  Steps to Reproduce:
  Use the following script and watch for the the hang. At that point attempt to 
stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/

  Originally filed against LXD: https://github.com/lxc/lxd/issues/4314

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  powersj2414 F pulseaudio
   /dev/snd/controlC0:  powersj2414 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 09:19:11 2018
  HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb
  InstallationDate: Installed on 2018-02-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  Lsusb:
   Bus 001 Device 002: ID 8087:8001 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20BSCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET42W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:

[Group.of.nepali.translators] [Bug 1727275] Re: ubuntu_sysdig_smoke_test failed on azure 4.11 kernel

[Colin Ian King]

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
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/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1718388] Re: Fix OpenNSL GPL bugs found by CoverityScan static analysis

[Colin Ian King]

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1718388

Title:
  Fix OpenNSL GPL bugs found by CoverityScan static analysis

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

Bug description:
  Static analysis on the ubuntu/opennsl drivers in Xenial have picked up
  various bugs. These need fixing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718388/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1550301] Re: ZFS: Set elevator=noop on disks in the root pool

[Colin Ian King]

Since this affects root on ZFS and the original patch no longer applies
(and ZFS on root) is not currently supported, I am reluctantly going to
close is issue. If a clean fix for ZFS on root for newer Zesty+
initramfs scripts is available I am happy to re-apply them for newer
releases. However, I am not going to forward port the original changes
since the delta is too large and I am not able to test these (as we
don't have ZFS on root by default).

** Changed in: zfs-linux (Ubuntu Zesty)
   Status: Confirmed => Won't Fix

** Changed in: zfs-linux (Ubuntu)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1550301

Title:
  ZFS: Set elevator=noop on disks in the root pool

Status in zfs-linux package in Ubuntu:
  Won't Fix
Status in zfs-linux source package in Xenial:
  Fix Released
Status in zfs-linux source package in Zesty:
  Won't Fix

Bug description:
  ZFS-on-Linux has its own I/O scheduler, so it sets the "noop" elevator
  on whole disks used in a pool.
  https://github.com/zfsonlinux/zfs/issues/90

  It does not set the scheduler for a disk if a partition is used in a
  pool out of respect for the possibility that there are non-ZFS
  partitions on the same disk.
  https://github.com/zfsonlinux/zfs/issues/152

  For regular pools, the recommendation is to use whole disks. For a
  root pools, it's just the opposite. The typical case is that
  partitions are used. And, for root pools, it is unlikely that the same
  disks have non-ZFS filesystems.

  The debdiff in comment #5 applies cleanly to the latest package and
  functions correctly. This is an important change for root-on-ZFS
  users. It has no effect on non-root-on-ZFS installs, because the code
  is only in the zfs-initramfs package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1550301/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1711401] Re: accessing /dev/hvc1 with stress-ng on Ubuntu xenial causes crash

[Colin Ian King]

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1711401

Title:
  accessing /dev/hvc1 with stress-ng on Ubuntu xenial causes crash

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

Bug description:
  [SRU REQUEST][XENIAL]

  When running stress-ng --dev stressor accessing /dev/hvc1 causes the
  stressor to lock up and never terminal.

  [FIX]
  Upstream commmit:From bbc3dfe8805de86874b1a1b1429a002e8670043e Mon Sep 17 
00:00:00 2001
  From: Sam Mendoza-Jonas 
  Date: Mon, 11 Jul 2016 13:38:57 +1000
  Subject: [PATCH] tty/hvc: Use IRQF_SHARED for OPAL hvc consoles

  [TESTING]
  Without the fix, stress-ng --dev run as root hangs, and one gets an irq 
failed error and an oops:

  [ 2096.476610] hvc_open: request_irq failed with rc -16.
  [ 2096.476634] Unable to handle kernel paging request for data at address 
0x00a8
  [ 2096.476641] Faulting instruction address: 0xc0b0d8a4
  [ 2096.476647] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2096.476650] SMP NR_CPUS=2048 NUMA PowerNV

  With the fix, the stressor runs w/o any issues

  [REGRESSION POTENTIAL]
  This is specific to one driver for ppc64el, so the risk potential is limited. 
The fix has limited regression potential as it essentially marks a flag to 
allow interrupt to be shared and fundamentally this is a very minor change to  
the interrupt handling functionality in the driver.

  ---

  stress-ng run as root, --dev stressor, accessing /dev/hvc1:

  [ 2096.476610] hvc_open: request_irq failed with rc -16.
  [ 2096.476634] Unable to handle kernel paging request for data at address 
0x00a8
  [ 2096.476641] Faulting instruction address: 0xc0b0d8a4
  [ 2096.476647] Oops: Kernel access of bad area, sig: 11 [#1]
  [ 2096.476650] SMP NR_CPUS=2048 NUMA PowerNV
  [ 2096.476657] Modules linked in: kvm_hv kvm_pr kvm cuse userio hci_vhci 
bluetooth uhid hid vhost_net vhost macvtap macvlan snd_seq snd_seq_device 
snd_timer snd soundcore ipmi_powernv ipmi_msghandler vmx_crypto leds_powernv 
uio_pdrv_genirq uio powernv_rng ibmpowernv ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_round_robin ses 
enclosure ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath
  [ 2096.476718] CPU: 74 PID: 23074 Comm: stress-ng-dev Not tainted 
4.4.0-92-generic #115-Ubuntu
  [ 2096.476724] task: c00fe8499030 ti: c00f0fa0c000 task.ti: 
c00f0fa0c000
  [ 2096.476728] NIP: c0b0d8a4 LR: c069648c CTR: 
c0696450
  [ 2096.476732] REGS: c00f0fa0f6b0 TRAP: 0300   Not tainted  
(4.4.0-92-generic)
  [ 2096.476736] MSR: 90009033   CR: 2248  
XER: 
  [ 2096.476749] CFAR: c0008468 DAR: 00a8 DSISR: 4000 
SOFTE: 0
     GPR00: c069648c c00f0fa0f930 c15f8000 
00a8
     GPR04: c00ff0082400 0002 001ffe7d 
0036
     GPR08: c3236b90  804a 
c01e4e568880
     GPR12: c0696450 cfb6bf00 000f 
010023d22660
     GPR16: 3fff9ca5 0080 c01e43dde100 
c00fe459c800
     GPR20:  0001 0e51 
00010004
     GPR24: 00010800  f000 
c1892448
     GPR28: c00fef98da28 c00fe459c800 0001 
00a8
  [ 2096.476805] NIP [c0b0d8a4] _raw_spin_lock_irqsave+0x44/0x130
  [ 2096.476812] LR [c069648c] hvc_open+0x3c/0x1a0
  [ 2096.476815] Call Trace:
  [ 2096.476818] [c00f0fa0f930] [c00f0fa0f970] 0xc00f0fa0f970 
(unreliable)
  [ 2096.476824] [c00f0fa0f970] [c069648c] hvc_open+0x3c/0x1a0
  [ 2096.476829] [c00f0fa0f9f0] [c066c514] tty_open+0x194/0x7c0
  [ 2096.476836] [c00f0fa0fa90] [c02ec234] chrdev_open+0x114/0x270
  [ 2096.476841] [c00f0fa0faf0] [c02e1480] 
do_dentry_open+0x2c0/0x460
  [ 2096.476846] [c00f0fa0fb50] [c02f9aa8] do_last+0x178/0xff0
  [ 2096.476851] [c00f0fa0fc10] [c02fab3c] path_openat+0xcc/0x3c0
  [ 2096.476857] [c00f0fa0fc90] [c02fca5c] do_filp_open+0xfc/0x170
  [ 2096.476861] [c00f0fa0fdb0] [c02e3270] do_sys_open+0x1c0/0x3b0
  [ 2096.476867] [c00f0fa0fe30] [c0009204] system_call+0x38/0xb4
  [ 2096.476870] Instruction dump:
  [ 

[Group.of.nepali.translators] [Bug 1596835] Re: libnvpair.so.1 should be in /lib/, not /usr/lib/

[Colin Ian King]

This is indeed fixed in 17.04 Zesty onwards.  I'll SRU this sometime in
the future for earlier releases

** Changed in: zfs-linux (Ubuntu Zesty)
   Status: New => Fix Released

** Changed in: zfs-linux (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Xenial)
   Status: New => Triaged

** Changed in: zfs-linux (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Artful)
   Status: New => Fix Committed

** Changed in: zfs-linux (Ubuntu Artful)
   Status: Fix Committed => Fix Released

** Changed in: zfs-linux (Ubuntu Artful)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1596835

Title:
  libnvpair.so.1 should be in /lib/, not /usr/lib/

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Triaged
Status in zfs-linux source package in Zesty:
  Fix Released
Status in zfs-linux source package in Artful:
  Fix Released

Bug description:
  Currently, in Ubuntu 16.04, the package libnvpair1linux puts
  libnvpair.so.1 in /usr/lib/, however, tools like zpool and zfs which
  are installed in /sbin/ need this library. According to the FHS this
  means the required libraries should be in /lib/ in order to allow the
  user to install /usr/ on a separate partition that is not immediately
  available after boot.

  This turns out to be a problem indeed. On one of my systems I had
  /usr/ on a ZFS filesystem (and /, /lib/, /sbin/, /bin/ on a separate
  ext4 partition). However, the system failed to boot: it hung while
  mounting the ZFS partitions which failed because zpool import didn't
  work as it couldn't find libnvpair.so.1.

  $ apt-cache policy libnvpair1linux 
  libnvpair1linux:
Installed: 0.6.5.6-0ubuntu9
Candidate: 0.6.5.6-0ubuntu9
Version table:
   *** 0.6.5.6-0ubuntu9 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  $ apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu9
Candidate: 0.6.5.6-0ubuntu9
Version table:
   *** 0.6.5.6-0ubuntu9 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   0.6.5.6-0ubuntu8 500
  500 http://nl.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1596835/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1614789] Re: zfs.target should not require zfs-share.service

[Colin Ian King]

** Changed in: zfs-linux (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1614789

Title:
  zfs.target should not require zfs-share.service

Status in zfs-linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  == SRU Xenial ==

  [Justification]

  Currently package zfsutils-linux contains systemd target file 
/lib/systemd/system/zfs.target that specifies following dependencies:
  Requires=zfs-mount.service
  Requires=zfs-share.service
  Wants=zed.service

  zfs-share.service is not essential in setups where file sharing is not
  used, or when it is configured without the use of the zfs utility. The
  user may therefore choose to mask this service. However, doing so has
  an unexpected and confusing effect, preventing zfs from starting on
  boot at all. This is because zfs.target is the only zfs-related unit
  that is wanted by multi-user.target, and if one of its required
  services is masked, zfs.target is skipped, together with zfs-
  mount.service. A solution is to replace "Requires=zfs-share.service"
  with "Wants=zfs-share.service".

  [Testcase]
  Steps to reproduce:
  systemctl mask zfs-share.service
  reboot

  Expected results:
  Module zfs is loaded
  zfs-mount.service is active and ZFS filesystems are mounted
  ZFS filesystems are not shared

  Observed results:
  Module zfs is not loaded
  ZFS filesystems are not mounted
  zpool status produces an error:
  "The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them."

  With the fix, the modules are loaded and zfs filesystems are mounted

  [Fix]
  A solution is to replace "Requires=zfs-share.service" with 
"Wants=zfs-share.service".

  [Regression Potential]
  Minimal, this affects the start up of a service that should be starting and 
currently isn't. Limited to just this specific scenario.

  -

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  $ apt-cache policy zfsutils-linux
  zfsutils-linux:
    Installed: 0.6.5.6-0ubuntu10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1614789/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1571761] Re: zfs-import-cache.service slows boot by 60 seconds

[Colin Ian King]

Since this seems to be closed against bug 1595302, I'm going to mark
this bug as fix released too.

** Changed in: zfs-linux (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: zfs-linux (Ubuntu Xenial)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1571761

Title:
  zfs-import-cache.service slows boot by 60 seconds

Status in cloud-init package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  Fresh uvt-kvm guest, then
  $ sudo apt-get install zfsutils-linux
  $ sudo reboot

  The reboot will show on console waiting for tasks, then after ~ 60 seconds it 
continues boot.
  Logging in shows:

  $ sudo systemd-analyze critical-chain zfs-mount.service
  The time after the unit is active or started is printed after the "@" 
character.
  The time the unit takes to start is printed after the "+" character.

  zfs-mount.service +81ms
  └─zfs-import-cache.service @1min 786ms +272ms
└─systemd-udev-settle.service @494ms +1min 275ms
  └─systemd-udev-trigger.service @415ms +55ms
└─systemd-udevd-control.socket @260ms
  └─-.mount @124ms
└─system.slice @129ms
  └─-.slice @124ms

  Seems possibly related / or some discussion at
  https://github.com/zfsonlinux/zfs/issues/2368

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: zfsutils-linux 0.6.5.6-0ubuntu8
  ProcVersionSignature: User Name 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  Date: Mon Apr 18 16:42:35 2016
  ProcEnviron:
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.sudoers.d.zfs: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1571761/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1684731] Re: zfs-share.service: Failed at step EXEC spawning /usr/bin/rm: No such file or directory

[Colin Ian King]

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

** Also affects: zfs-linux (Ubuntu Yakkety)
   Importance: Undecided
   Status: New

** Also affects: zfs-linux (Ubuntu Artful)
   Importance: High
 Assignee: Colin Ian King (colin-king)
   Status: Incomplete

** Also affects: zfs-linux (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: zfs-linux (Ubuntu Zesty)
   Importance: Undecided => High

** Changed in: zfs-linux (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: zfs-linux (Ubuntu Yakkety)
   Importance: Undecided => High

** Changed in: zfs-linux (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu Zesty)
 Assignee: (unassigned) => Colin Ian King (colin-king)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1684731

Title:
  zfs-share.service: Failed at step EXEC spawning /usr/bin/rm: No such
  file or directory

Status in zfs-linux package in Ubuntu:
  Incomplete
Status in zfs-linux source package in Xenial:
  New
Status in zfs-linux source package in Yakkety:
  New
Status in zfs-linux source package in Zesty:
  New
Status in zfs-linux source package in Artful:
  Incomplete

Bug description:
  wrong `rm` path on /lib/systemd/system/zfs-share.service

  ExecStartPre=-/usr/bin/rm -f /etc/dfs/sharetab

  there is no file such /usr/bin/rm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1684731/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1614789] Re: zfs.target should not require zfs-share.service

[Colin Ian King]

I was wrong, just Xenial requires this fix.

** No longer affects: zfs-linux (Ubuntu Yakkety)

** Changed in: zfs-linux (Ubuntu Xenial)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1614789

Title:
  zfs.target should not require zfs-share.service

Status in zfs-linux package in Ubuntu:
  In Progress
Status in zfs-linux source package in Xenial:
  In Progress

Bug description:
  Currently package zfsutils-linux contains systemd target file 
/lib/systemd/system/zfs.target that specifies following dependencies:
  Requires=zfs-mount.service
  Requires=zfs-share.service
  Wants=zed.service

  zfs-share.service is not essential in setups where file sharing is not
  used, or when it is configured without the use of the zfs utility. The
  user may therefore choose to mask this service. However, doing so has
  an unexpected and confusing effect, preventing zfs from starting on
  boot at all. This is because zfs.target is the only zfs-related unit
  that is wanted by multi-user.target, and if one of its required
  services is masked, zfs.target is skipped, together with zfs-
  mount.service. A solution is to replace "Requires=zfs-share.service"
  with "Wants=zfs-share.service".

  Steps to reproduce:
  systemctl mask zfs-share.service
  reboot

  Expected results:
  Module zfs is loaded
  zfs-mount.service is active and ZFS filesystems are mounted
  ZFS filesystems are not shared

  Observed results:
  Module zfs is not loaded
  ZFS filesystems are not mounted
  zpool status produces an error:
  "The ZFS modules are not loaded.
  Try running '/sbin/modprobe zfs' as root to load them."

  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  $ apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.6-0ubuntu10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1614789/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1677126] Re: ubuntu_lttng_smoke_test failed on z-hwe: Kernel tracer not available

[Colin Ian King]

** Changed in: lttng-modules (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: linux-hwe-edge (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1677126

Title:
  ubuntu_lttng_smoke_test failed on z-hwe: Kernel tracer not available

Status in linux-hwe-edge package in Ubuntu:
  Fix Released
Status in lttng-modules package in Ubuntu:
  Fix Released
Status in linux-hwe-edge source package in Xenial:
  New
Status in lttng-modules source package in Xenial:
  Fix Released

Bug description:
  == SRU REQUEST [Xenial] ==

  We are getting lttng module build failures on the HWE 4.10.0 kernel
  because we are missing the 4.9 and 4.10 compatibility patches to build
  for a 4.10 kernel.

  == Fix ==

  Apply minimal set of upstream patches to enable 4.9 + 4.10 builds:

  769b62a02f62ff8db93f109d9f63a1df6ea9990b
   Fix-unregister-cpu-hotplug-notifier-on-buffer-alloc-.patch

  489de24bfb835022b64c2e71d717eaf333ab3633
   Add-load-unload-messages-to-kernel-log.patch

  3e86016420272ce5ef0139ad52f20c83305f0f15
   Fix-update-scsi-instrumentation-for-4.7-kernels.patch

  f3166f27f5e2d2210cec32d68c277940a7473281
   btrfs-instrumentation-update-to-4.10-kernel.patch

  507143bc5de50c0e5493d63fb5c300fa42326842
   timer-instrumentation-adapt-to-ktime_t-without-union.patch

  1e36732678d7cc650940b4508031acf2f6ffcd1b
   Adapt-lttng-modules-to-Linux-4.10-cpu-hotplug-state-.patch

  da3b99a6386302158785e1f8fd1679c106850d0e
   Fix: only include linux/cpuhotplug.h for kernels >= 4.10

  ce4a2f0c273d4077c6eb9e6e0f28379ddaf61382
   Fix: 4.10 hotplug adaptation backward compat

  == Testing ==

  Without the fix, lttng modules won't install and build on HWE 4.10
  kernels.  With the fix, the lttng modules build and also pass the
  ubuntu kernel team autotest lttng smoke tests.

  Should be tested with xenial 4.4 kernel to ensure backward
  compatibility is not broken on the default Xenial kernels

  == Regression potential ==

  Can potential break lttng.

  -

  Test failed with "Kernel tracer not available"

  root@michael:/home/ubuntu/autotest-client-tests/ubuntu_lttng_smoke_test# 
./ubuntu_lttng_smoke_test.sh
  == lttng smoke test of session create/destroy ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-12675-session
  PASSED (lttng create)
  Session test-kernel-session destroyed
  PASSED (lttng destroy)

  == lttng smoke test list kernel events ==
  Error: Unable to list kernel events: Kernel tracer not available
  Error: Command error
  FAILED (lttng list --kernel)
  FAILED (lttng list --kernel more output expected)

  == lttng smoke test trace open/close system calls ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-12675-session
  PASSED (lttng create)
  Error: Event open: Kernel tracer not available (channel channel0, session 
test-kernel-session)
  Error: Event openat: Kernel tracer not available (channel channel0, session 
test-kernel-session)
  Error: Event close: Kernel tracer not available (channel channel0, session 
test-kernel-session)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed

  == lttng smoke test trace context switches ==
  Session test-kernel-session created.
  Traces will be written in /tmp/lttng-kernel-trace-12675-session
  PASSED (lttng create)
  Error: Event sched_switch: Kernel tracer not available (channel channel0, 
session test-kernel-session)
  FAILED (lttng enable-event)
  Session test-kernel-session destroyed

  Summary: 4 passed, 4 failed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-14.16~16.04.1-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Mar 29 06:08:00 2017
  SourcePackage: linux-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-edge/+bug/1677126/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1656259] Re: Linux ZFS port doesn't respect RLIMIT_FSIZE

[Colin Ian King]

This was also fixed in Zesty with the kernel 4.10.0-9.11

commit d177712eb2130b8c53f9d4fd9b5b756b70fc4f35
Author: Colin Ian King <colin.k...@canonical.com>
Date:   Thu Feb 16 10:36:16 2017 +

UBUNTU: SAUCE: (noup) Update spl to 0.6.5.9-1, zfs to 0.6.5.9-2

Signed-off-by: Colin Ian King <colin.k...@canonical.com>
Signed-off-by: Tim Gardner <tim.gard...@canonical.com>


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

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1656259

Title:
  Linux ZFS port doesn't respect RLIMIT_FSIZE

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in zfs-linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in zfs-linux source package in Zesty:
  Fix Released

Bug description:
  == SRU Request, Yakkety, Xenial ==

  bash -c 'ulimit -f 1024; yes | head -n2097152'
  >/path/on/filesystem/under/test

  On ext4, this test case prints something along the lines of:

    bash: line 1: 11274 Broken pipe yes
     11275 File size limit exceeded(core dumped) | head -n2097152

  On ZFS, this test case incorrectly exits zero with no output,
  demonstrating that ZFS does not respect RLIMIT_FSIZE.

  I asked a friend to run this on Solaris 5.10 and FreeBSD 10.0-CURRENT,
  and on those systems this test case correctly generates SIGXFSZ; so it
  seems that this is a bug in the Linux port of ZFS.

  (This was discovered while tracking down Launchpad test suite failures
  under LXD on ZFS.  Launchpad uses RLIMIT_FSIZE in one place to guard
  against bugs that cause debdiff to generate arbitrarily large amounts
  of output and fill the disk.)

  == Fix ==

  Upstream fix
  
https://github.com/behlendorf/zfs/commit/230c03e59d3d13d9b60125f73cf3fff327b45c21

  == Test case ==

  With the fix:

  bash -c 'ulimit -f 1024; yes | head -n2097152'
  >/path/on/filesystem/under/test

  should report:

bash: line 1: 11274 Broken pipe yes
 11275 File size limit exceeded(core dumped) | head -n2097152

  == Regression Potential ==

  Could break read/writes semantics to zfs

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 13 10:01:36 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=139ad421-b014-4c34-ae8c-dd1d15205875
  InstallationDate: Installed on 2013-03-01 (1413 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1)
  MachineType: LENOVO 20BXCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed 
root=UUID=12c52021-a1ab-4984-9dd7-63cf0dcaac16 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET49WW (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1656259/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1672819] Re: exec'ing a setuid binary from a threaded program sometimes fails to setuid

[Colin Ian King]

This bug has been around since at least 2009.

Kernel Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=195453


** Bug watch added: Linux Kernel Bug Tracker #195453
   http://bugzilla.kernel.org/195453

** Also affects: linux via
   http://bugzilla.kernel.org/195453
   Importance: Unknown
   Status: Unknown

** Bug watch added: Linux Kernel Bug Tracker #195453
   http://bugzilla.kernel.org/195453

** Bug watch added: Linux Kernel Bug Tracker #195453
   http://bugzilla.kernel.org/195453

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1672819

Title:
  exec'ing a setuid binary from a threaded program sometimes fails to
  setuid

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  In Progress

Bug description:
  This can be reproduced with
  https://gist.github.com/chipaca/806c90d96c437444f27f45a83d00a813

  With that, and go 1.8, if you run “make” and then

  for i in `seq 99`; do ./a_go; done

  you'll see a variable number of ”GOT 1000” (or whatever your user id
  is). If you don't, add one or two more 9s on there.

  That's a simple go reproducer. You can also use “a_p” instead of
  “a_go” to see one that only uses pthreads. “a_c” is a C version that
  does *not* reproduce the issue.

  But it's not pthreads: if in a_go.go you comment out the “import "C"”,
  you'll still see the “GOT 1000” messages, in a static binary that uses
  no pthreads, just clone(2). You'll also see a bunch of warnings
  because it's not properly handling an EAGAIN from clone, but that's
  unrelated.

  If you pin the process to a single thread using taskset, you don't get
  the issue from a_go; a_p continues to reproduce the issue. In some
  virtualized environments we haven't been able to reproduce the issue
  either (e.g. some aws instances), but kvm works (you need -smp to see
  the issue from a_go).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   john   2354 F...m pulseaudio
   /dev/snd/controlC0:  john   2354 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar 14 17:17:23 2017
  HibernationDevice: RESUME=UUID=b9fd155b-dcbe-4337-ae77-6daa6569beaf
  InstallationDate: Installed on 2014-04-27 (1051 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Latitude E6510
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/ubuntu--vg-root ro enable_mtrr_cleanup mtrr_spare_reg_nr=8 
mtrr_gran_size=32M mtrr_chunk_size=32M quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  UpgradeStatus: Upgraded to xenial on 2015-06-18 (634 days ago)
  dmi.bios.date: 12/05/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1672819/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1656259] Re: Linux ZFS port doesn't respect RLIMIT_FSIZE

[Colin Ian King]

** Changed in: zfs-linux (Ubuntu Zesty)
   Status: New => Fix Released

** Changed in: zfs-linux (Ubuntu Zesty)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Zesty)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Released

** Changed in: zfs-linux (Ubuntu Zesty)
   Importance: Medium => High

** Changed in: linux (Ubuntu Zesty)
   Status: Fix Released => Fix Committed

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1656259

Title:
  Linux ZFS port doesn't respect RLIMIT_FSIZE

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  New
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  New
Status in zfs-linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in zfs-linux source package in Zesty:
  Fix Released

Bug description:
bash -c 'ulimit -f 1024; yes | head -n2097152'
  >/path/on/filesystem/under/test

  On ext4, this test case prints something along the lines of:

bash: line 1: 11274 Broken pipe yes
 11275 File size limit exceeded(core dumped) | head -n2097152

  On ZFS, this test case incorrectly exits zero with no output,
  demonstrating that ZFS does not respect RLIMIT_FSIZE.

  I asked a friend to run this on Solaris 5.10 and FreeBSD 10.0-CURRENT,
  and on those systems this test case correctly generates SIGXFSZ; so it
  seems that this is a bug in the Linux port of ZFS.

  (This was discovered while tracking down Launchpad test suite failures
  under LXD on ZFS.  Launchpad uses RLIMIT_FSIZE in one place to guard
  against bugs that cause debdiff to generate arbitrarily large amounts
  of output and fill the disk.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-57-generic 4.4.0-57.78
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 13 10:01:36 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=139ad421-b014-4c34-ae8c-dd1d15205875
  InstallationDate: Installed on 2013-03-01 (1413 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1)
  MachineType: LENOVO 20BXCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed 
root=UUID=12c52021-a1ab-4984-9dd7-63cf0dcaac16 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-generic N/A
   linux-backports-modules-4.4.0-57-generic  N/A
   linux-firmware1.157.6
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET49WW (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1656259/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1640547] Re: stress-ng based disk tests failing

[Colin Ian King]

** Changed in: stress-ng
   Status: In Progress => Fix Committed

** Changed in: stress-ng
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1640547

Title:
  stress-ng based disk tests failing

Status in Stress-ng:
  Fix Released
Status in plainbox-provider-checkbox package in Ubuntu:
  Triaged
Status in plainbox-provider-checkbox source package in Xenial:
  Triaged

Bug description:
  When running the stress-ng disk test, we are seeing the following
  failures as well as I/O lockup:

  /dev/sda is a block device
  Found largest partition: "/dev/sda2"
  Test will use /dev/sda2, mounted at "/", using "ext4"
  test_dir is /tmp/disk_stress_ng
  Estimated total run time is 4560 seconds

  Running stress-ng aio stressor for 240 seconds
  stress-ng: info:  [4305] dispatching hogs: 160 aio
  stress-ng: info:  [4305] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [4305] cache allocate: default cache size: 2048K
  stress-ng: info:  [4305] successful run completed in 240.27s (4 mins, 0.27 
secs)
  return_code is 0
  Running stress-ng aiol stressor for 240 seconds
  stress-ng: info:  [4917] dispatching hogs: 160 aio-linux
  stress-ng: info:  [4917] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [4917] cache allocate: default cache size: 2048K
  stress-ng: fail:  [5002] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5012] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5020] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5018] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5019] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5013] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [4959] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5032] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5041] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5017] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5022] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5016] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5038] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5040] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5026] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5027] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5031] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5049] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5021] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5045] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5047] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5044] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5052] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5029] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5015] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5053] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5051] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5063] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5058] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5054] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5061] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5059] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5055] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5023] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5036] 

[Group.of.nepali.translators] [Bug 1634496] Re: proc_keys_show crash when reading /proc/keys

[Colin Ian King]

** Changed in: linux (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1634496

Title:
  proc_keys_show crash when reading /proc/keys

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  Running stress-ng /proc test trips the following crash:

  [ 5315.044206] Kernel panic - not syncing: stack-protector: Kernel stack is 
corrupted in: 8956b1ae
  [ 5315.044206] 
  [ 5315.044883] CPU: 0 PID: 4820 Comm:  Tainted: P   OE   
4.8.0-25-generic #27-Ubuntu
  [ 5315.045361] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu2 04/01/2014
  [ 5315.045911]  0086 b337622b 8fe574f37c78 
8962f5d2
  [ 5315.046371]  b3405b00 89e83530 8fe574f37d00 
8939e71c
  [ 5315.046841]  8fe50010 8fe574f37d10 8fe574f37ca8 
b337622b
  [ 5315.047305] Call Trace:
  [ 5315.047457]  [] dump_stack+0x63/0x81
  [ 5315.047763]  [] panic+0xe4/0x226
  [ 5315.048049]  [] ? proc_keys_show+0x3ce/0x3d0
  [ 5315.048398]  [] __stack_chk_fail+0x19/0x30
  [ 5315.048735]  [] proc_keys_show+0x3ce/0x3d0
  [ 5315.049072]  [] ? key_validate+0x50/0x50
  [ 5315.049396]  [] ? key_default_cmp+0x20/0x20
  [ 5315.049737]  [] seq_read+0x102/0x3c0
  [ 5315.050042]  [] proc_reg_read+0x42/0x70
  [ 5315.050363]  [] __vfs_read+0x18/0x40
  [ 5315.050674]  [] vfs_read+0x96/0x130
  [ 5315.050977]  [] SyS_read+0x55/0xc0
  [ 5315.051275]  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  [ 5315.051735] Kernel Offset: 0x820 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [ 5315.052563] ---[ end Kernel panic - not syncing: stack-protector: Kernel 
stack is corrupted in: 8956b1ae
  [ 5315.052563] 

  "The proc_keys_show function in security/keys/proc.c in the Linux
  kernel through 4.8.2, when the GNU Compiler Collection (gcc) stack
  protector is enabled, uses an incorrect buffer size for certain
  timeout data, which allows local users to cause a denial of service
  (stack memory corruption and panic) by reading the /proc/keys file."

  Fix detailed in: https://bugzilla.redhat.com/show_bug.cgi?id=1373966
  see: https://bugzilla.redhat.com/attachment.cgi?id=1200212=diff

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1634496/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1640547] Re: stress-ng tests failing

[Colin Ian King]

** Also affects: stress-ng
   Importance: Undecided
   Status: New

** Changed in: stress-ng
   Importance: Undecided => High

** Changed in: stress-ng
   Status: New => Fix Committed

** Changed in: stress-ng
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Colin Ian King (colin-king) => (unassigned)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1640547

Title:
  stress-ng tests failing

Status in Stress-ng:
  Fix Committed
Status in plainbox-provider-checkbox package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Incomplete
Status in plainbox-provider-checkbox source package in Xenial:
  New

Bug description:
  When running the stress-ng disk test, we are seeing the following
  failures as well as I/O lockup:

  /dev/sda is a block device
  Found largest partition: "/dev/sda2"
  Test will use /dev/sda2, mounted at "/", using "ext4"
  test_dir is /tmp/disk_stress_ng
  Estimated total run time is 4560 seconds

  Running stress-ng aio stressor for 240 seconds
  stress-ng: info:  [4305] dispatching hogs: 160 aio
  stress-ng: info:  [4305] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [4305] cache allocate: default cache size: 2048K
  stress-ng: info:  [4305] successful run completed in 240.27s (4 mins, 0.27 
secs)
  return_code is 0
  Running stress-ng aiol stressor for 240 seconds
  stress-ng: info:  [4917] dispatching hogs: 160 aio-linux
  stress-ng: info:  [4917] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: info:  [4917] cache allocate: default cache size: 2048K
  stress-ng: fail:  [5002] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5012] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5020] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5018] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5019] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5013] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [4959] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5032] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5041] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5017] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5022] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5016] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5038] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5040] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5026] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5027] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5031] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5049] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5021] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5045] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5047] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5044] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5052] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5029] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5015] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5053] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5051] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5063] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5058] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5054] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  stress-ng: fail:  [5061] stress-ng-aio-linux: io_setup failed, errno=1 
(Operation not permitted)
  st

[Group.of.nepali.translators] [Bug 1635502] Re: segment fault when running fwts method test

[Colin Ian King]

** No longer affects: fwts/xenial

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1635502

Title:
  segment fault when running fwts method test

Status in Firmware Test Suite:
  Fix Committed
Status in fwts package in Ubuntu:
  Fix Released
Status in fwts source package in Trusty:
  New
Status in fwts source package in Xenial:
  Fix Committed
Status in fwts source package in Yakkety:
  Fix Committed

Bug description:
  [SRU Justification][YAKKETY]

  fwts segfaults when running a fwts method test because of a double
  unlock on a pthread mutex.

  [FIX]
  Upstream commit 
https://lists.ubuntu.com/archives/fwts-devel/2016-October/008679.html - don't 
do double unlocking

  [TEST CASE]
  run fwts method - on the firmware and we get a double unlock on method 
invocation accounting and a segfault occurs. With the fix there is no segfault.

  [REGRESSION POTENTIAL]
  Minimal impact; this affects method invocation accounting and just the fwts 
method execution.  The fix only changes the accounting and will not affect 
other fwts test components.

  

  
  Test 46 of 192: Test _OFF (Set resource off).
  PASSED: Test 46, \_SB_.PCI0.PEG0.PEGP._OFF returned no values as expected.
  Caught SIGNAL 11 (Segmentation fault), aborting.
  Backtrace:
  0x7f09c3fc9dd4 /usr/local/lib/fwts/libfwts.so.1(+0xfdd4)
  0x7f09c3a1b4a0 /lib/x86_64-linux-gnu/libc.so.6(+0x354a0)
  0x7f09c3363960 /lib/x86_64-linux-gnu/libpthread.so.0(+0x12960)
  0x7f09c42196b0 
/usr/local/lib/fwts/libfwtsacpica.so.1(fwts_acpica_sem_count_get+0x40)
  0x0041efef fwts()
  0x0041f195 fwts()
  0x00421210 fwts()
  0x7f09c3fcf441 /usr/local/lib/fwts/libfwts.so.1(+0x15441)
  0x7f09c3fd0bc3 /usr/local/lib/fwts/libfwts.so.1(fwts_framework_args+0x793)
  0x0040519a fwts()
  0x7f09c3a06830 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)
  0x00406079 fwts()

To manage notifications about this bug go to:
https://bugs.launchpad.net/fwts/+bug/1635502/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1587686] Re: ZFS: Running ztest repeatedly for long periods of time eventually results in "zdb: can't open 'ztest': No such file or directory"

[Colin Ian King]

** Changed in: zfs-linux (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: zfs-linux (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** No longer affects: zfs-linux (Ubuntu)

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1587686

Title:
  ZFS: Running ztest repeatedly for long periods of time eventually
  results in "zdb: can't open 'ztest': No such file or directory"

Status in Native ZFS for Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux source package in Xenial:
  Fix Released

Bug description:
  [SRU Justification][XENIAL]

  Problem: Running ztest repeatedly for long periods of time eventually
  results in "zdb: can't open 'ztest': No such file or directory"

  [FIX]

  Upstream commit
  
https://github.com/zfsonlinux/zfs/commit/151f84e2c32f690b92c424d8c55d2dfccaa76e51

  [TEST CASE]
  Without the fix, the ztest will fail after hours of soak testing. With the 
fix, the issue can't be reproduced.

  [REGRESSION POTENTIAL]

  This fix is an upstream fix and therefore passed the ZFS integration
  tested.  I have also tested this thoroughly with the kernel team ZFS
  regression tests and not found any issues, so the regression potential
  is slim to zero.

  --


  Problem: Running ztest repeatedly for long periods of time eventually
  results in "zdb: can't open 'ztest': No such file or directory"

  This bug affects the xenial kernel built-in ZFS as well as the package
  zfs-dkms. I don't believe ZFS 0.6.3-stable or 0.6.4-release are
  effected, 0.6.5-release seems to have included the offending commit.
  Sorry for excessive "Affects" tagging, I'm still new to this and
  unsure of the proper packages to report this against and/or how to
  properly add the upstream issues/commits.

  Upstream bug report: https://github.com/zfsonlinux/zfs/issues/4129
  "ztest can occasionally fail because zdb cannot locate the pool after several 
hours of run time. This appears to be caused be an empty cache file."

  How to reproduce: run ztest repeatedly such as a command like this and it 
will eventually fail:
  ztest -T 3600 && rm /tmp/z* && sleep 3 && ztest -T 3600 && rm /tmp/z* && 
sleep 3 && ztest -T 3600 && rm /tmp/z* && sleep 3 && ztest -T 3600 && rm 
/tmp/z* && sleep 3 && ztest -T 3600 && rm /tmp/z* && sleep 3 && ztest -T 3600 
&& rm /tmp/z* && sleep 3 && ztest -T 3600 && rm /tmp/z* && sleep 3 && ztest -T 
3600 && rm /tmp/z* && sleep 3 && ztest -T 3600 && rm /tmp/z* && sleep 3 && 
ztest -T 3600 && rm /tmp/z* && sleep 3 && ztest -T 3600 && rm /tmp/z* && sleep 
3 && ztest -T 3600 && rm /tmp/z*
  (I have /tmp mounted on tmpfs with a 10G limit but I don't believe this is 
related in any way, and I've confirmed it's not running out of space)

  Upstream fix: 
https://github.com/zfsonlinux/zfs/commit/151f84e2c32f690b92c424d8c55d2dfccaa76e51
  Description: Fix ztest truncated cache file
  "Commit efc412b updated spa_config_write() for Linux 4.2 kernels to
  truncate and overwrite rather than rename the cache file.  This is
  the correct fix but it should have only been applied for the kernel
  build.  In user space rename(2) is needed because ztest depends on
  the cache file."
  Associated pull request for above commit: 
https://github.com/zfsonlinux/zfs/pull/4130

  I'm not sure why this wasn't backported to release but it's in zfs
  master. I've Reproduced this bug on xenial kernels 4.4.0-22-generic,
  4.4.0-23-generic, 4.4.0-22-lowlatency, and 4.4.0-23-lowlatency as well
  as various xenial master-next builds. After applying the above commit
  patch to kernel and building/installing kernel manually, ztest runs
  fine. I've also separately tested the commit patch on zfs-dkms package
  which also appears to fix the issue. Note however, there may still be
  some other outstanding ztest related issues upstream - especially when
  preempt and hires timers are used. I'm currently testing more heavily
  against lowlatency builds and master-next.

  (I'm unsure how to associate this bug with multiple packages but zfs-
  dkms and linux-image-* packages both are affected).

  P.S. Also of note is
  
https://github.com/zfsonlinux/zfs/commit/60a4ea3f948f1596b92b666fc7dd21202544edbb
  "Fix inverted logic on none elevator comparison" - which interestingly
  was signed-off-by canonical but curiously not included in the xenial
  kernel or zfs-dkms packages. It was however, backporte

[Group.of.nepali.translators] [Bug 1582982] Re: thermald 1.5-2ubuntu1 failures in ubuntu16.04

[Colin Ian King]

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

** Changed in: thermald (Ubuntu Xenial)
   Status: New => In Progress

** No longer affects: thermald (Ubuntu Trusty)

** Changed in: thermald (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: thermald (Ubuntu Xenial)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1582982

Title:
  thermald 1.5-2ubuntu1 failures in ubuntu16.04

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Xenial:
  In Progress

Bug description:
  [SRU][XENIAL] Justification:

  thermald is reporting non-critical errors whereas these should be
  downgraded and being reported as warnings so as not to alarm users.

  [FIX]
  Upstream 
commit,https://github.com/01org/thermal_daemon/commit/8280fd7ec6cff6db6463c8a1b01d2e427e418226

  this is already in thermald in Yakkety and working fine.

  [Regression Potential]
  Minimal, this changes the status levels of various error messages, so core 
thermald functional is not touched at all by this fix.

  

  Hi. I am still getting the same failure message despite using the
  latest thermald version. Can you tell me how to solve these failures.

  May 18 10:08:11 Eliot thermald[1012]: failed to open /dev/acpi_thermal_rel
  May 18 10:08:11 Eliot thermald[1012]: failed to open /dev/acpi_thermal_rel
  May 18 10:08:11 Eliot thermald[1012]: TRT/ART read failed
  May 18 10:08:12 Eliot thermald[1012]: sysfs read failed 
constraint_0_max_power_uw
  May 18 10:08:12 Eliot thermald[1012]: sysfs write failed trip_point_0_temp
  May 18 10:08:12 Eliot thermald[1012]: sysfs write failed trip_point_0_temp

  $: dpkg -l thermald
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name Version Architecture Description
  
+++-=-===-===-===
  ii thermald 1.5-2ubuntu1 amd64 Thermal monitoring and controlling daemon

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  $ apt-cache policy thermald
  thermald:
    Installed: 1.5-2ubuntu1
    Candidate: 1.5-2ubuntu1
    Version table:
   *** 1.5-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.5-2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1582982/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1558120] Re: Kernel can be oopsed using remap_file_pages

[Colin Ian King]

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Released

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

** Changed in: linux (Ubuntu Wily)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Xenial)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1558120

Title:
  Kernel can be oopsed using remap_file_pages

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [SRU][WILY][XENIAL]

  [JUSTIFICATION]
  Running stress-ng --remap 4 will trip an oops on the remap.

  The bug is introduced by the mm/mmap.c changes in patch
  d15bd6cdbb1c2080fb1fca0035e5af1994f4d14f ("UBUNTU: SAUCE: AUFS").
  AUFS introduced a subtle bug into remap_file_pages; calls to
  do_mmap_pgoff can lead to a change of the vma->vm_file and so the
  vma_fput(vma) on the file is incorrect; we should instead fput on the
  original file.

  [FIX]
  fput the original file rather than the vma->vm_file.  Without the fix, 
stress-ng --remap 4 will produce an oops in a few seconds, with the fix it is 
rock solid.

  [REGRESSION POTENTIAL]
  This only changes the deprecated system call remap_file_pages which is not 
used much and it is also deprecated, so it should be avoided by user space 
applications anyhow.

  

  While faffing around with the deprecated system call remap_file_pages
  I was able to trigger an OOPs that can be reproduced every time.

  uname -a
  Linux lenovo 4.4.0-13-generic #29-Ubuntu SMP Fri Mar 11 19:31:18 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  [   27.298469] mmap: stress-ng-remap (4061) uses deprecated 
remap_file_pages() syscall. See Documentation/vm/remap_file_pages.txt.
  [   28.956497] BUG: unable to handle kernel NULL pointer dereference at 
0228
  [   28.956555] IP: [] shmem_fault+0x38/0x1e0
  [   28.956594] PGD aded1067 PUD add32067 PMD 0
  [   28.956625] Oops:  [#1] SMP
  [   28.956649] Modules linked in: nls_iso8859_1 drbg ansi_cprng xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter ip_tables x_tables binfmt_misc zfs(PO) zunicode(PO) 
zcommon(PO) znvpair(PO) spl(O) zavl(PO) uvcvideo intel_rapl 
x86_pkg_temp_thermal intel_powerclamp videobuf2_vmalloc coretemp 
videobuf2_memops crct10dif_pclmul videobuf2_v4l2 crc32_pclmul videobuf2_core 
v4l2_common snd_hda_codec_hdmi videodev aesni_intel snd_hda_codec_realtek 
snd_hda_codec_generic media aes_x86_64 lrw snd_seq_midi gf128mul glue_helper 
ablk_helper snd_seq_midi_event cryptd snd_hda_intel snd_hda_codec snd_hda_core
  [   28.957162]  snd_hwdep snd_rawmidi joydev input_leds arc4 serio_raw 
rtl8192ce rtl_pci rtl8192c_common snd_pcm rtlwifi snd_seq mac80211 
thinkpad_acpi nvram cfg80211 snd_seq_device mei_me mei lpc_ich snd_timer shpchp 
snd soundcore mac_hid kvm_intel kvm irqbypass parport_pc ppdev lp parport 
autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mmc_block i915 
psmouse i2c_algo_bit drm_kms_helper e1000e ahci syscopyarea libahci sdhci_pci 
sysfillrect sysimgblt sdhci ptp fb_sys_fops pps_core drm wmi fjes video
  [   28.957570] CPU: 2 PID: 4061 Comm: stress-ng-remap Tainted: P   O  
  4.4.0-13-generic #29-Ubuntu
  [   28.957623] Hardware name: LENOVO 2320CTO/2320CTO, BIOS G2ET31WW (1.11 ) 
05/24/2012
  [   28.957666] task: 8800add2ee00 ti: 8800adf7c000 task.ti: 
8800adf7c000
  [   28.957707] RIP: 0010:[]  [] 
shmem_fault+0x38/0x1e0
  [   28.957754] RSP: :8800adf7fd38  EFLAGS: 00010246
  [   28.957780] RAX: 880194f06900 RBX:  RCX: 
0054
  [   28.957820] RDX:  RSI: 8800adf7fda8 RDI: 
8800a990f0c8
  [   28.957860] RBP: 8800adf7fd98 R08:  R09: 
8800adf7fe68
  [   28.957899] R10:  R11: 3000 R12: 
8800a990f0c8
  [   28.957939] R13: 8800adf7fe68 R14: 8800adf0de90 R15: 
7f83ba57b000
  [   28.957979] FS:  7f83bc46c740() GS:88019e28() 
knlGS:
  [   28.958024] CS:  0010 DS:  ES:  CR0: 80050033
  [   28.958056] CR2: 0228 CR3: ade92000 CR4: 
001406e0
  [   28.958096] Stack:
  [   28.958109]  8800aafb3840 0200adf7fd68 8800adfaf108 
8800adfaf190
  [   28.958158]  81a25e80 8800adfaf190  
b7865150
  [   28.958206]  

[Group.of.nepali.translators] [Bug 1569468] Re: stress-ng mmap failing on zVM and LPAR

[Colin Ian King]

** Also affects: stress-ng (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: stress-ng (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: stress-ng (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: stress-ng (Ubuntu Xenial)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1569468

Title:
  stress-ng mmap failing on zVM and LPAR

Status in stress-ng package in Ubuntu:
  Fix Committed
Status in stress-ng source package in Xenial:
  In Progress

Bug description:
  [SRU, Xenial]

  When running stress-ng on zVM and LPAR we are hitting SIGBUS errors
  because we have a sparsely allocated mmap'd backing file which due to
  over commit and a full file system causes pages not to be mapped in
  and causes memory accesses on unbacked pages to trigger a SIGBUS.

  [REPRODUCER + FIX]
  Run stress-ng --mmap 64 --maximize on a filesystem that is very nearly full 
and the SIGBUS triggers and the stressor exits early with SIGBUS.  With the 
fix, the SIGBUS is caught and the stressor can continue without premature early 
exit.

  [REGRESSION POTENTIAL]
  I am requesting syncing with 0.05.24 micro release as this contains the fix 
plus a few SIGSEGV stack trapping fixes.  stress-ng is a universe leaf project 
and the fixes touch just a few of the stress tests. These have been regression 
checked on various architectures and the code passes static analysis on 
cppcheck, CoverityScan and clang's scan-build, so regression potential is 
minimal.


  --

  Running stress-ng on s390 in all three modes.  This seems to work ok
  in z/KVM, however, on zVM and LPAR as of a few days ago on Xenial the
  mmap stressor has started failing.

  I tried to get detailed logs but either don't know the correct
  switches or they simply aren't there.

  Here is the output when I used --log-file and --verbose on an LPAR:
  root@s1lp10-jefflane:~# less stress-ng-mmap-fail.log
  stress-ng: debug: [179421] 4 processors online, 4 processors configured
  stress-ng: info:  [179421] dispatching hogs: 4 mmap
  stress-ng: debug: [179421] cache allocate: reducing cache level from L3 (too 
high) to L2
  stress-ng: info:  [179421] cache allocate: default cache size: 2048K
  stress-ng: debug: [179421] starting stressors
  stress-ng: debug: [179422] stress-ng-mmap: started [179422] (instance 0)
  stress-ng: debug: [179423] stress-ng-mmap: started [179423] (instance 1)
  stress-ng: debug: [179424] stress-ng-mmap: started [179424] (instance 2)
  stress-ng: debug: [179421] 4 stressors spawned
  stress-ng: debug: [179425] stress-ng-mmap: started [179425] (instance 3)
  stress-ng: debug: [179424] stress-ng-mmap: exited [179424] (instance 2)
  stress-ng: debug: [179422] stress-ng-mmap: exited [179422] (instance 0)
  stress-ng: debug: [179421] process [179422] terminated
  stress-ng: debug: [179421] process 179423 (stress-ng-mmap) terminated on 
signal: 7 (Bus error)
  stress-ng: debug: [179421] process [179423] terminated
  stress-ng: debug: [179421] process [179424] terminated
  stress-ng: debug: [179421] process 179425 (stress-ng-mmap) terminated on 
signal: 7 (Bus error)
  stress-ng: debug: [179421] process [179425] terminated
  stress-ng: info:  [179421] unsuccessful run completed in 300.68s (5 mins, 
0.68 secs)

  That is the only info I have for the failure, unfortunately.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: stress-ng 0.05.23-1
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic s390x
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: s390x
  Date: Tue Apr 12 12:47:49 2016
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: stress-ng
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1569468/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1573117] Re: stress-ng: clone system calls randomly fail with -EINVAL on aarch64

[Colin Ian King]

SRU: package: https://launchpad.net/~colin-king/+archive/ubuntu/stress-
ng-xenial-sru/+packages

Debdiff: https://launchpadlibrarian.net/255152031/stress-
ng_0.05.23-1_0.05.23-1ubuntu1.diff.gz


** Description changed:

+ [SRU] Xenial
+ 
  Getting -EINVAL on stressors that call clone() on aarch64. Turns out
  that the clone() thread's stack has to be 16 byte aligned.
+ 
+ [REPODUCER + FIX]
+ For example, run:
+ 
+ stress-ng --vm-rw 1 -v
+ 
+ Without the fix, this can randomly exit with -EINVAL when the stack
+ being passed to the clone() system call is not aligned on a 16 byte
+ boundary.
+ 
+ With the fix, the clone() system call works fine and the stressor will
+ run.
+ 
+ [REGRESSION POTENIAL]
+ Minimal. I have exhaustively tested this on multiple platforms/architectures 
and the fix ensures that the stack is aligned correctly.  stress-ng is a leaf 
project in universe and this fix only touches 3 of the stress-ng stressors that 
use the clone() system call.

** Also affects: stress-ng (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: stress-ng (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: stress-ng (Ubuntu Xenial)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: stress-ng (Ubuntu Xenial)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1573117

Title:
  stress-ng: clone system calls randomly fail with -EINVAL on aarch64

Status in stress-ng package in Ubuntu:
  Fix Committed
Status in stress-ng source package in Xenial:
  In Progress

Bug description:
  [SRU] Xenial

  Getting -EINVAL on stressors that call clone() on aarch64. Turns out
  that the clone() thread's stack has to be 16 byte aligned.

  [REPODUCER + FIX]
  For example, run:

  stress-ng --vm-rw 1 -v

  Without the fix, this can randomly exit with -EINVAL when the stack
  being passed to the clone() system call is not aligned on a 16 byte
  boundary.

  With the fix, the clone() system call works fine and the stressor will
  run.

  [REGRESSION POTENIAL]
  Minimal. I have exhaustively tested this on multiple platforms/architectures 
and the fix ensures that the stack is aligned correctly.  stress-ng is a leaf 
project in universe and this fix only touches 3 of the stress-ng stressors that 
use the clone() system call.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1573117/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1546092] Re: computer freezes frequently

[Colin Ian King]

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => Won't Fix

** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1546092

Title:
  computer freezes frequently

Status in linux package in Ubuntu:
  Won't Fix
Status in linux source package in Xenial:
  Won't Fix

Bug description:
  Running Xenial. Freezes seem to happen every 5 to 45 minutes. I have
  not been able to create any repro steps, it feels quite random.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-4-generic 4.4.0-4.19
  ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
  Uname: Linux 4.4.0-4-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rick   1780 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Feb 16 08:26:12 2016
  HibernationDevice: RESUME=UUID=36268acb-4215-452f-9778-754c015d00d8
  InstallationDate: Installed on 2016-02-02 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131)
  MachineType: TOSHIBA Satellite L15W-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic.efi.signed 
root=UUID=ed019e52-c90e-48b7-bbe4-ae5d39fea067 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-4-generic N/A
   linux-backports-modules-4.4.0-4-generic  N/A
   linux-firmware   1.155
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.00
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 0670
  dmi.board.vendor: FF40
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.00:bd07/16/2015:svnTOSHIBA:pnSatelliteL15W-B:pvrPSKVUU-00S01U:rvnFF40:rn0670:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Satellite L15W-B
  dmi.product.version: PSKVUU-00S01U
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546092/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1480349] Re: thermald breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 v3

[Colin Ian King]

Thanks Philipp.

Anyone care to test Wily? I'd like to get that one released too.

** Changed in: thermald (Ubuntu Vivid)
   Status: In Progress => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1480349

Title:
  thermald breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 v3

Status in thermald package in Ubuntu:
  Fix Released
Status in thermald source package in Trusty:
  Fix Committed
Status in thermald source package in Vivid:
  Won't Fix
Status in thermald source package in Wily:
  Fix Committed
Status in thermald source package in Xenial:
  Fix Released

Bug description:
  SRU Justification Wily, Vivid, Trusty

  CPU scaling on a class of Intel CPUs is not functioning correctly,
  causing the CPU to be throttled back to the lowest CPU frequency

  [FIX]
  Upstream cherry picks, as recommended by Intel
  f4e316ef4d8d8c9a558ef5bfa74e25303c46a985 ("Add white list of the cpu ids")
  18d1574230c6b9b4e8876c0b6739c074a24205e6 ("Move parser init to thd_engine")
  6749427098434ccad81fa8c5f2a3e102fc1644f7 ("Remove wild card for loading")
  ba4fe1e7bb77d09530544cda860fba559603ec83 ("Error recovery when sysfs attrib 
read fails")

  Plus 4 changes to allow clean and simpler patching of the above 4 fix
  to reduce the risk of breaking thermald with a complex backport:

  Remove trailing ':' from THD engine failure message
  Remove !! from "No coretemp sysfs found"
  Add new option for config file
  Support target state

  Essentially we now have a white list of valid CPUs to run thermald on,
  so we can exclude the issues on a wider class of CPUs.

  [TEST CASE]
  With the buggy thermald, CPU is pegged at the lowest CPU frequency.  With the 
fixed thermald, CPU scaling now works.

  [REGRESSION POTENTIAL]
  We are allowing thermald now to run on a strict set of CPUs, so we are hoping 
that the whitelist covers the class that we can legitimately run thermald 
against.

  --

  When I boot with this installed frequency scaling is no longer
  behaving as expected.

  It seems that with this installed, the OS loses control of the
  scaling.

  It seems that scaling is performed, though. And very much to the
  purpose of power saving.

  Performance is terrible because of this. And I do mean terrible.

  The default governor is powersave.

  Setting the governor to performance (yes, on all cores) doesn't seem
  to change to scaling behavior. The frequency doesn't pass 800MHz.

  I would like to use Intel's microcode updates, but I have to have my
  CPU running at the speed for which it costs so damn much.

  Any suggestions?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: intel-microcode 3.20150121.1
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 31 17:56:39 2015
  InstallationDate: Installed on 2010-10-12 (1753 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: intel-microcode
  UpgradeStatus: Upgraded to wily on 2014-11-11 (262 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1480349/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1480349] Re: thermald breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 v3

[Colin Ian King]

** Also affects: intel-microcode (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: thermald (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: thermald (Ubuntu Trusty)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: thermald (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: thermald (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: thermald (Ubuntu Wily)
   Status: New => In Progress

** Also affects: intel-microcode (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: thermald (Ubuntu Vivid)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1480349

Title:
  thermald breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 v3

Status in intel-microcode package in Ubuntu:
  In Progress
Status in thermald package in Ubuntu:
  Fix Released
Status in intel-microcode source package in Trusty:
  New
Status in thermald source package in Trusty:
  In Progress
Status in intel-microcode source package in Vivid:
  New
Status in thermald source package in Vivid:
  New
Status in intel-microcode source package in Wily:
  New
Status in thermald source package in Wily:
  In Progress
Status in intel-microcode source package in Xenial:
  In Progress
Status in thermald source package in Xenial:
  Fix Released

Bug description:
  SRU Justification Wily

  CPU scaling on a class of Intel CPUs is not functioning correctly,
  causing the CPU to be throttled back to the lowest CPU frequency

  [FIX]
  Upstream cherry picks, as recommended by Intel
  f4e316ef4d8d8c9a558ef5bfa74e25303c46a985 ("Add white list of the cpu ids")
  18d1574230c6b9b4e8876c0b6739c074a24205e6 ("Move parser init to thd_engine")
  6749427098434ccad81fa8c5f2a3e102fc1644f7 ("Remove wild card for loading")
  ba4fe1e7bb77d09530544cda860fba559603ec83 ("Error recovery when sysfs attrib 
read fails")

  Plus 4 changes to allow clean and simpler patching of the above 4 fix
  to reduce the risk of breaking thermald with a complex backport:

  Remove trailing ':' from THD engine failure message
  Remove !! from "No coretemp sysfs found"
  Add new option for config file
  Support target state

  Essentially we now have a white list of valid CPUs to run thermald on,
  so we can exclude the issues on a wider class of CPUs.

  [TEST CASE]
  With the buggy thermald, CPU is pegged at the lowest CPU frequency.  With the 
fixed thermald, CPU scaling now works.

  [REGRESSION POTENTIAL]
  We are allowing thermald now to run on a strict set of CPUs, so we are hoping 
that the whitelist covers the class that we can legitimately run thermald 
against.

  --

  When I boot with this installed frequency scaling is no longer
  behaving as expected.

  It seems that with this installed, the OS loses control of the
  scaling.

  It seems that scaling is performed, though. And very much to the
  purpose of power saving.

  Performance is terrible because of this. And I do mean terrible.

  The default governor is powersave.

  Setting the governor to performance (yes, on all cores) doesn't seem
  to change to scaling behavior. The frequency doesn't pass 800MHz.

  I would like to use Intel's microcode updates, but I have to have my
  CPU running at the speed for which it costs so damn much.

  Any suggestions?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: intel-microcode 3.20150121.1
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Jul 31 17:56:39 2015
  InstallationDate: Installed on 2010-10-12 (1753 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: intel-microcode
  UpgradeStatus: Upgraded to wily on 2014-11-11 (262 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1480349/+subscriptions

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp