[Group.of.nepali.translators] [Bug 1724862] Re: acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
*** This bug is a duplicate of bug 1700783 *** https://bugs.launchpad.net/bugs/1700783 ** This bug has been marked a duplicate of bug 1700783 acpi-call 1.1.0-3 ADT test failure with linux 4.12.0-4.5 -- 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/1724862 Title: acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 Status in acpi-call package in Ubuntu: Fix Released Status in acpi-call source package in Xenial: Fix Released Status in acpi-call package in Debian: Fix Released Bug description: [Impact] Currently the DKMS package fails to install in supported custom kernels that are based on 4.11 or 4.13. That includes the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom and cloud kernels as well. [Test Case] Install the DKMS package with the 4.13 hwe-edge kernel from -proposed. The package installation should proceed without any errors. [Regression Potential] Although new patches were added, the regression risk is very low since the new changes are conditionally compiled based on the kernel version. Besides that the new package was tested with the following kernels in an amd64 environment: - linux-generic 4.4 - linux-hwe 4.10 - linux-hwe-edge 4.11 - linux-hwe-edge 4.13 (from xenial-proposed) - linux-azure 4.11 - linux-azure-edge 4.13 (which is in process of getting promoted to xenial-proposed) [Original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/a/acpi-call/20171018_121140_0c63b@/log.gz armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/a/acpi-call/20171018_120650_0c63b@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/a/acpi-call/20171018_120646_0c63b@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/a/acpi-call/20171018_120452_0c63b@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1724862/+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 1773905] Re: Support UVC1.5 Camera for Xenial
** Also affects: 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/1773905 Title: Support UVC1.5 Camera for Xenial Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: ===SRU Justification=== [Impact] UVC1.5 USB class is not in UVC driver's device ID, so the driver doesn't get loaded. [Test] See if the uvcvideo module is loaded for UVC1.5 camera. I can confirm with this commit, uvcvideo.ko is loaded. In addition, cheese can use the webcam without issue. [Fix] Add UVC1.5 device id to uvcvideo. [Regression Potential] Low. The short control message is already fixed by another commit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773905/+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 1771283] Re: iperf2 long time run on 40Gb/s NIC crashes
Thanks Manoj & Bob - I'll take a look at sponsoring your upload. Do you mind filing a bug in Debian as well, and linking that bug to this one using "Also affects distribution/package"? That way we'll know when we can drop our diff & resync w/ Debian. ** Also affects: iperf (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: iperf (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: iperf (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: iperf (Ubuntu Bionic) 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/1771283 Title: iperf2 long time run on 40Gb/s NIC crashes Status in iperf package in Ubuntu: New Status in iperf source package in Xenial: New Status in iperf source package in Artful: New Status in iperf source package in Bionic: New Status in iperf source package in Cosmic: New Bug description: ubuntu@recht:~$ iperf -c 192.168.121.2 -P10 -w 130k -t 3600 Client connecting to 192.168.121.2, TCP port 5001 TCP window size: 254 KByte (WARNING: requested 127 KByte) [ 10] local 192.168.121.3 port 40756 connected with 192.168.121.2 port 5001 [ 12] local 192.168.121.3 port 40760 connected with 192.168.121.2 port 5001 [ 11] local 192.168.121.3 port 40758 connected with 192.168.121.2 port 5001 [ 8] local 192.168.121.3 port 40754 connected with 192.168.121.2 port 5001 [ 9] local 192.168.121.3 port 40752 connected with 192.168.121.2 port 5001 [ 7] local 192.168.121.3 port 40750 connected with 192.168.121.2 port 5001 [ 6] local 192.168.121.3 port 40746 connected with 192.168.121.2 port 5001 [ 5] local 192.168.121.3 port 40748 connected with 192.168.121.2 port 5001 [ 3] local 192.168.121.3 port 40744 connected with 192.168.121.2 port 5001 [ 4] local 192.168.121.3 port 40742 connected with 192.168.121.2 port 5001 Segmentation fault (core dumped) Will report more information with gdb attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iperf/+bug/1771283/+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 1724862] Re: acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
** This bug is no longer a duplicate of bug 1700783 acpi-call 1.1.0-3 ADT test failure with linux 4.12.0-4.5 -- 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/1724862 Title: acpi-call 1.1.0-2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 Status in acpi-call package in Ubuntu: Fix Released Status in acpi-call source package in Xenial: Fix Released Status in acpi-call package in Debian: Fix Released Bug description: [Impact] Currently the DKMS package fails to install in supported custom kernels that are based on 4.11 or 4.13. That includes the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom and cloud kernels as well. [Test Case] Install the DKMS package with the 4.13 hwe-edge kernel from -proposed. The package installation should proceed without any errors. [Regression Potential] Although new patches were added, the regression risk is very low since the new changes are conditionally compiled based on the kernel version. Besides that the new package was tested with the following kernels in an amd64 environment: - linux-generic 4.4 - linux-hwe 4.10 - linux-hwe-edge 4.11 - linux-hwe-edge 4.13 (from xenial-proposed) - linux-azure 4.11 - linux-azure-edge 4.13 (which is in process of getting promoted to xenial-proposed) [Original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/a/acpi-call/20171018_121140_0c63b@/log.gz armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/armhf/a/acpi-call/20171018_120650_0c63b@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/a/acpi-call/20171018_120646_0c63b@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/a/acpi-call/20171018_120452_0c63b@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1724862/+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 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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/1774127 Title: linux-gcp: 4.13.0-1019.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774127/+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 1774129] Re: linux-hwe: 4.13.0-45.50~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => 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/1774129 Title: linux-hwe: 4.13.0-45.50~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774129/+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 1770712] Re: It would be nice if cloud-init provides full version in logs
This bug was fixed in the package cloud-init - 18.2-64-gbbcc5e82-0ubuntu1 --- cloud-init (18.2-64-gbbcc5e82-0ubuntu1) cosmic; urgency=medium * debian/rules: update version.version_string to contain packaged version. (LP: #1770712) * New upstream snapshot. - util: add get_linux_distro function to replace platform.dist [Robert Schweikert] (LP: #1745235) - pyflakes: fix unused variable references identified by pyflakes 2.0.0. - - Do not use the systemd_prefix macro, not available in this environment [Robert Schweikert] - doc: Add config info to ec2, openstack and cloudstack datasource docs - Enable SmartOS network metadata to work with netplan via per-subnet routes [Dan McDonald] (LP: #1763512) -- Chad Smith Mon, 04 Jun 2018 12:18:16 -0600 ** Changed in: cloud-init (Ubuntu Cosmic) 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/1770712 Title: It would be nice if cloud-init provides full version in logs Status in cloud-init: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Artful: Confirmed Status in cloud-init source package in Bionic: Confirmed Status in cloud-init source package in Cosmic: Fix Released Bug description: Cloud-init rsyslog has the major version of cloud-init: May 11 17:40:51 maas-enlisting-node cloud-init[550]: Cloud-init v. 18.2 running 'init-local' at Fri, 11 May 2018 17:40:47 +. Up 15.63 seconds. However, it would be nice if it places the whole version, so that we can now exactly what version of cloud-init its running, e.g: May 11 17:40:51 maas-enlisting-node cloud-init[550]: Cloud-init v. 18.2 (27-g6ef92c98-0ubuntu1~18.04.1) running 'init-local' at Fri, 11 May 2018 17:40:47 +. Up 15.63 seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1770712/+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 1768435] Re: aio-dio-extend-stat test in aio_dio_bugs failed on s390x
Fixed the testcases under aio_dio_bugs/src/ on autotest-client-tests repo. ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Artful) Status: New => Invalid ** Changed in: linux (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/1768435 Title: aio-dio-extend-stat test in aio_dio_bugs failed on s390x Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Artful: Invalid Status in linux source package in Bionic: Invalid Bug description: It can be reproduced on zVM, zKVM and Ubuntu on LPAR This should not be considered as a regression, the test suite stopped on the first test in this test suite before. Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-extend-stat file Running 'apt-get install --yes --force-yes build-essential gcc' Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.1ubuntu2). gcc is already the newest version (4:5.3.1-1ubuntu1). The following packages were automatically installed and are no longer required: linux-headers-4.4.0-121 linux-headers-4.4.0-121-generic linux-image-4.4.0-121-generic linux-image-extra-4.4.0-121-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Running 'which gcc' /usr/bin/gcc Dependency libaio successfully built Running 'LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-extend-stat file' write of 1024 bytes @0 finished, expected filesize at least 1024, but got 0 Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/aio_dio_bugs/aio_dio_bugs.py", line 42, in run_once utils.system(var_ld_path + ' ' + cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-extend-stat file Exit status: 1 Duration: 0.10453414917 stdout: write of 1024 bytes @0 finished, expected filesize at least 1024, but got 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-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.16 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. CurrentDmesg: Date: Wed May 2 02:24:25 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 RfKill: Error:
[Group.of.nepali.translators] [Bug 1730895] Re: aio-dio-invalidate-failure test failed with event res -22 on s390x
Fixed the testcases under aio_dio_bugs/src/ on autotest-client-tests
repo.
** No longer affects: linux (Ubuntu)
** No longer affects: linux (Ubuntu Xenial)
** No longer affects: linux (Ubuntu Artful)
** No longer affects: linux (Ubuntu Bionic)
** Changed in: ubuntu-kernel-tests
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/1730895
Title:
aio-dio-invalidate-failure test failed with event res -22 on s390x
Status in ubuntu-kernel-tests:
Fix Released
Bug description:
This bug is for tracking purpose, this is not a regression for current
cycle as this issue exists for a long time.
It can be reproduced on zVM, zKVM and Ubuntu on LPAR
Steps:
1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git
2. make -C autotest-client-tests/aio_dio_bugs/src
3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-invalidate-failure
poo
Result:
event res -22
From the code itself, it's expecting a -EIO return value:
if (event.res == -EIO) {
printf("invalidation returned -EIO, OK\n");
exit(0);
}
The actual return value is -22, which I think is -EINVAL
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-100-generic 4.4.0-100.123
ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95
Uname: Linux 4.4.0-100-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.10
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.
CurrentDmesg:
Date: Wed Nov 8 01:57:40 2017
HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9
crashkernel=196M BOOT_IMAGE=0
RelatedPackageVersions:
linux-restricted-modules-4.4.0-100-generic N/A
linux-backports-modules-4.4.0-100-generic N/A
linux-firmware 1.157.13
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/1730895/+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 1768430] Re: aio-dio-subblock-eof-read test in aio_dio_bugs failed on s390x
Fixed the testcases under aio_dio_bugs/src/ on autotest-client-tests repo. ** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Artful) Status: New => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Triaged => 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/1768430 Title: aio-dio-subblock-eof-read test in aio_dio_bugs failed on s390x Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in linux source package in Artful: Invalid Status in linux source package in Bionic: Invalid Bug description: It can be reproduced on zVM, zKVM and Ubuntu on LPAR This should not be considered as a regression, the test suite stopped on the first test in this test suite before. Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest Running 'apt-get install --yes --force-yes build-essential gcc' Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.1ubuntu2). gcc is already the newest version (4:5.3.1-1ubuntu1). The following packages were automatically installed and are no longer required: linux-headers-4.4.0-121 linux-headers-4.4.0-121-generic linux-image-4.4.0-121-generic linux-image-extra-4.4.0-121-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Running 'which gcc' /usr/bin/gcc Dependency libaio successfully built Running 'LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest' buffered read returned -1, should be 300 Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/aio_dio_bugs/aio_dio_bugs.py", line 42, in run_once utils.system(var_ld_path + ' ' + cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof- read eoftest Exit status: 1 Duration: 0.00215792655945 stdout: buffered read returned -1, should be 300 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-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.16 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. CurrentDmesg: Date: Wed May 2 02:21:12 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
[Group.of.nepali.translators] [Bug 1765007] Re: Xenial update to 4.4.127 stable release
** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1765007 Title: Xenial update to 4.4.127 stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.127 upstream stable stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.127 stable release shall be applied: * Linux 4.4.127 * Revert "ip6_vti: adjust vti mtu according to mtu of lower device" * net: cavium: liquidio: fix up "Avoid dma_unmap_single on uninitialized ndata" * spi: davinci: fix up dma_mapping_error() incorrect patch * Revert "mtip32xx: use runtime tag to initialize command header" * Revert "cpufreq: Fix governor module removal race" * Revert "ARM: dts: omap3-n900: Fix the audio CODEC's reset pin" * Revert "ARM: dts: am335x-pepper: Fix the audio CODEC's reset pin" * Revert "PCI/MSI: Stop disabling MSI/MSI-X in pci_device_shutdown()" * nospec: Kill array_index_nospec_mask_check() * nospec: Move array_index_nospec() parameter checking into separate macro * net: hns: Fix ethtool private flags * md/raid10: reset the 'first' at the end of loop * ARM: dts: am57xx-beagle-x15-common: Add overide powerhold property * ARM: dts: dra7: Add power hold and power controller properties to palmas * Documentation: pinctrl: palmas: Add ti,palmas-powerhold-override property definition * vt: change SGR 21 to follow the standards * Input: i8042 - enable MUX on Sony VAIO VGN-CS series to fix touchpad * Input: i8042 - add Lenovo ThinkPad L460 to i8042 reset list * staging: comedi: ni_mio_common: ack ai fifo error interrupts. * fs/proc: Stop trying to report thread stacks * crypto: x86/cast5-avx - fix ECB encryption when long sg follows short one * crypto: ahash - Fix early termination in hash walk * parport_pc: Add support for WCH CH382L PCI-E single parallel port card. * media: usbtv: prevent double free in error case * mei: remove dev_err message on an unsupported ioctl * USB: serial: cp210x: add ELDAT Easywave RX09 id * USB: serial: ftdi_sio: add support for Harman FirmwareHubEmulator * USB: serial: ftdi_sio: add RT Systems VX-8 cable * usb: dwc2: Improve gadget state disconnection handling * scsi: virtio_scsi: always read VPD pages for multiqueue too * llist: clang: introduce member_address_is_nonnull() * Bluetooth: Fix missing encryption refresh on Security Request * netfilter: x_tables: add and use xt_check_proc_name * netfilter: bridge: ebt_among: add more missing match size checks * xfrm: Refuse to insert 32 bit userspace socket policies on 64 bit systems * net: xfrm: use preempt-safe this_cpu_read() in ipcomp_alloc_tfms() * RDMA/ucma: Introduce safer rdma_addr_size() variants * RDMA/ucma: Don't allow join attempts for unsupported AF family * RDMA/ucma: Check that device exists prior to accessing it * RDMA/ucma: Check that device is connected prior to access it * RDMA/ucma: Ensure that CM_ID exists prior to access it * RDMA/ucma: Fix use-after-free access in ucma_close * RDMA/ucma: Check AF family prior resolving address * xfrm_user: uncoditionally validate esn replay attribute struct * arm64: avoid overflow in VA_START and PAGE_OFFSET * selinux: Remove redundant check for unknown labeling behavior * netfilter: ctnetlink: Make some parameters integer to avoid enum mismatch * tty: provide tty_name() even without CONFIG_TTY * audit: add tty field to LOGIN event * frv: declare jiffies to be located in the .data section * jiffies.h: declare jiffies and jiffies_64 with cacheline_aligned_in_smp * fs: compat: Remove warning from COMPATIBLE_IOCTL * selinux: Remove unnecessary check of array base in selinux_set_mapping() * cpumask: Add helper cpumask_available() * genirq: Use cpumask_available() for check of cpumask variable * netfilter: nf_nat_h323: fix logical-not-parentheses warning * Input: mousedev - fix implicit conversion warning * dm ioctl: remove double parentheses * PCI: Make PCI_ROM_ADDRESS_MASK a 32-bit
[Group.of.nepali.translators] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
--
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/1774225
Title:
netns: unable to follow an interface that moves to another netns
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
The following upstream patches are missing (v4.16):
6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
c36ac8e23073 ("dev: always advertise the new nsid when the netns iface
changes")
38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774225/+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 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd
This bug was fixed in the package debhelper - 11.2.1ubuntu2 --- debhelper (11.2.1ubuntu2) cosmic; urgency=medium * [d24b1734] Support overrides in tmpfiles.d (LP: #1748147) - dh_installsystemd: Use the basename of the "tmpfiles" config files. This makes "systemd-tmpfiles --create" search for it in both /usr/lib/tmpfiles.d and in /etc/tmpfiles.d. With this change the system administrator can now override the "tmpfiles" config shipped by the package in /usr/libtmpfiles.d. - dh_installinit: Ditto. -- Seyeong Kim Thu, 24 May 2018 22:19:34 -0700 ** Changed in: debhelper (Ubuntu) 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/1748147 Title: [SRU] debhelper support override from /etc/tmpfiles.d for systemd Status in debhelper: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in debhelper source package in Xenial: In Progress Status in debhelper source package in Artful: In Progress Status in debhelper source package in Bionic: In Progress Bug description: [Impact] /var/log's Permission is going back to 755 after upgrading systemd if there are rsyslog's configuration on /var/lib/tmpfiles.d/ Affected X, A, B, C This is because rsyslog's pkg has 00rsyslog.conf and copied it on /var/lib/tmpfiles.d/ when it is installing. after upgrading systemd, systemd only refresh it's own tmpfiles so disappear conf for 00rsyslog.conf ( it doesn't remove file itself ) so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back permission to 775 [Test Case] 1. deploy 16.04 vm 2. check ll /var (775) 3. apt install --reinstall systemd 4. check ll /var (755) [Regression Potential] This fix changes debhelper's override process by using absolute path to filename. so if the other pkgs using debhelper e.g systemd are there, It should be re-build with new debhelper after patching. also, pkg like rsyslog which is using systemd's tmpfile system need to be changed to use /etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 00rsyslog.conf. [Others] For this issue, need to fix below pkgs debhelper systemd ( rebuilding with new debhelper is needed ) rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, to support override supported by debhelper ) [Original description] Upgrading or reinstalling the systemd package when using rsyslogd results in bad permissions (0755 instead of 0775) being set on /var/log/. As a consequence of this, rsyslogd can no longer create new files within this directory, resulting in lost log messages. The default configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt
[Group.of.nepali.translators] [Bug 1769888] Re: New upstream microreleases 9.3.23, 9.5.13, 9.6.9 and 10.4
This bug was fixed in the package postgresql-9.6 - 9.6.9-0ubuntu0.17.10 --- postgresql-9.6 (9.6.9-0ubuntu0.17.10) artful; urgency=medium * New upstream release (LP: #1769888) - A dump/restore is not required for those running 9.6.X. However, if you use the adminpack extension, you should update it as per the first changelog entry of the changelog. (CVE-2018-1115) Also, if the function marking mistakes mentioned in the first changelog entry affect you, you will want to take steps to correct your database catalogs. - Details about changes can be found at https://www.postgresql.org/docs/9.6/static/release-9-6-9.html -- Christian Ehrhardt Tue, 08 May 2018 15:17:44 +0200 ** Changed in: postgresql-9.6 (Ubuntu Artful) Status: Fix Committed => Fix Released ** Changed in: postgresql-9.5 (Ubuntu Xenial) 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/1769888 Title: New upstream microreleases 9.3.23, 9.5.13, 9.6.9 and 10.4 Status in postgresql-10 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Invalid Status in postgresql-9.6 package in Ubuntu: Invalid Status in postgresql-9.3 source package in Trusty: Fix Released Status in postgresql-9.5 source package in Xenial: Fix Released Status in postgresql-9.6 source package in Artful: Fix Released Status in postgresql-10 source package in Bionic: Fix Released Bug description: Postgresql stable update Current versions in supported releases: postgresql-9.3 | 9.3.22-0ubuntu0.14.04 trusty postgresql-9.5 | 9.5.12-0ubuntu0.16.04 xenial postgresql-9.6 | 9.6.8-0ubuntu0.17.10 artful postgresql-10 | 10.3-1bionic postgresql-10 | 10.3-2cosmic Special cases: - Cosmic will be synced from Debian which usually releases fast. So no Cosmic upload by us. Last related stable updates: 9.3.23, 9.5.13, 9.6.9, 10.4 So the todo is to pick: MRE: Trusty 9.3.23 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.3.23.tar.gz MRE: Xenial 9.5.13 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.5.13.tar.gz MRE: Artful 9.6.9 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.6.9.tar.gz MRE: Bionic 10.4 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-10.4.tar.gz Sync: Cosmic 10.4 via Debian auto-sync Standing MRE - Consider last updates as template: - pad.lv/1637236 - pad.lv/1664478 - pad.lv/1690730 - pad.lv/1713979 - pad.lv/1730661 - pad.lv/1747676 - pad.lv/1752271 New - this bug - pad.lv/1769888 Test builds and tests took place in PPAs T: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3254 X: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3255 A: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3256 B: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3257 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-10/+bug/1769888/+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 1769888] Re: New upstream microreleases 9.3.23, 9.5.13, 9.6.9 and 10.4
This bug was fixed in the package postgresql-10 - 10.4-0ubuntu0.18.04 --- postgresql-10 (10.4-0ubuntu0.18.04) bionic; urgency=medium * New upstream release (LP: #1769888) - A dump/restore is not required for those running 10.X. However, if you use the adminpack extension, you should update it as per the first changelog entry of the changelog. (CVE-2018-1115) Also, if the function marking mistakes mentioned in the first changelog entry affect you, you will want to take steps to correct your database catalogs. - Details about changes can be found at https://www.postgresql.org/docs/10/static/release-10-4.html -- Christian Ehrhardt Tue, 08 May 2018 15:17:41 +0200 ** Changed in: postgresql-10 (Ubuntu Bionic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-1115 -- 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/1769888 Title: New upstream microreleases 9.3.23, 9.5.13, 9.6.9 and 10.4 Status in postgresql-10 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Invalid Status in postgresql-9.6 package in Ubuntu: Invalid Status in postgresql-9.3 source package in Trusty: Fix Released Status in postgresql-9.5 source package in Xenial: Fix Released Status in postgresql-9.6 source package in Artful: Fix Released Status in postgresql-10 source package in Bionic: Fix Released Bug description: Postgresql stable update Current versions in supported releases: postgresql-9.3 | 9.3.22-0ubuntu0.14.04 trusty postgresql-9.5 | 9.5.12-0ubuntu0.16.04 xenial postgresql-9.6 | 9.6.8-0ubuntu0.17.10 artful postgresql-10 | 10.3-1bionic postgresql-10 | 10.3-2cosmic Special cases: - Cosmic will be synced from Debian which usually releases fast. So no Cosmic upload by us. Last related stable updates: 9.3.23, 9.5.13, 9.6.9, 10.4 So the todo is to pick: MRE: Trusty 9.3.23 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.3.23.tar.gz MRE: Xenial 9.5.13 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.5.13.tar.gz MRE: Artful 9.6.9 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.6.9.tar.gz MRE: Bionic 10.4 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-10.4.tar.gz Sync: Cosmic 10.4 via Debian auto-sync Standing MRE - Consider last updates as template: - pad.lv/1637236 - pad.lv/1664478 - pad.lv/1690730 - pad.lv/1713979 - pad.lv/1730661 - pad.lv/1747676 - pad.lv/1752271 New - this bug - pad.lv/1769888 Test builds and tests took place in PPAs T: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3254 X: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3255 A: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3256 B: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3257 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-10/+bug/1769888/+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 1770650] Re: Update google compute-image-packages to 20180510
This bug was fixed in the package gce-compute-image-packages - 20180510+dfsg1-0ubuntu3~16.04.0 --- gce-compute-image-packages (20180510+dfsg1-0ubuntu3~16.04.0) xenial; urgency=medium * Backport to Xenial * Don't wait for snapd.seeded.service * Keep recommending google-cloud-sdk gce-compute-image-packages (20180510+dfsg1-0ubuntu3) cosmic; urgency=medium * Update prerm to stop google-network-daemon.service rather than the removed ones * Only Provide irqbalance without Breaks and Replaces to ensure smooth upgrades gce-compute-image-packages (20180510+dfsg1-0ubuntu2) cosmic; urgency=medium * debian/patches/0003-order-startup-scripts-after-snap- seeding.service: Ensure that snaps have been seeded before startup scripts run. gce-compute-image-packages (20180510+dfsg1-0ubuntu1) cosmic; urgency=medium [ Balint Reczey ] * Break, Replace and Provide irqbalance. Optimization scripts are conflicting with irqbalance and the set relationships ensure removal of irqbalance when it was accidentally installed. * Depend on virtual system-log-daemon as an alternative of rsyslog * Update copyrights * New upstream version 20180510 (LP: #1770650) * Refresh patches * Adjust tests to changed behaviour * Update symlink to shared library with updated revision * debian/gce-compute-image-packages.preinst: Add debhelper token * Update Lintian overrides [ Google Cloud Team ] * Add module blacklist for GCE * Fix Debian install when migrating to new network daemon gce-compute-image-packages (20180129+dfsg1-0ubuntu3) bionic; urgency=medium * Drop the Recommends: on google-cloud-sdk; this is moving to be a snap for 18.04 and we don't want to continue pulling in a deprecated deb. gce-compute-image-packages (20180129+dfsg1-0ubuntu2) bionic; urgency=medium * No-change rebuild against libcurl4 -- Balint Reczey Wed, 16 May 2018 21:07:04 +0200 ** Changed in: gce-compute-image-packages (Ubuntu Xenial) 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/1770650 Title: Update google compute-image-packages to 20180510 Status in gce-compute-image-packages package in Ubuntu: Fix Released Status in gce-compute-image-packages source package in Trusty: Fix Committed Status in gce-compute-image-packages source package in Xenial: Fix Released Status in gce-compute-image-packages source package in Artful: Fix Released Status in gce-compute-image-packages source package in Bionic: Fix Released Bug description: [Impact] compute-image-packages is provided by Google for installation within guests that run on Google Compute Engine. It is a collection of tools and daemons, packaged as gce-compute-image-packages, that ensure that the Ubuntu images published to GCE run properly on their platform. Cloud platforms evolve at a rate that can't be handled in six-month increments, and they will often develop features that they would like to be available to customers who don't want to upgrade from earlier Ubuntu releases. As such, updating gce-compute-image-packages to more recent upstream releases is required within all Ubuntu releases, so they continue to function properly in their environment. With this release we also add a new binary package to the suite - google-compute-engine-oslogin which is for a future feature of using OS Login on GCE VM instances. [Test Case] When a new version of gce-compute-image-packages is uploaded to -proposed, the following will be done: * an image based on -proposed will be built for GCE and published to the ubuntu-os-cloud-devel project * the CPC team will write new automated tests to cover new testable functionality (if any) in the new package * the automated testing that the CPC team normally runs against GCE images before they are published will be run against the -proposed image * the GCE team will be asked to validate that the new package addresses the issues it is expected to address, and that the image passes their internal image validation. If all the testing indicates that the image containing the new package is acceptable, verification will be considered to be done. [Other Information] This bug is used for tracking of releasing the new upstream version for all supported series, as per the approved policy mentioned in the following MRE: https://wiki.ubuntu.com/gce-compute-image-packages-Updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gce-compute-image-packages/+bug/1770650/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe :
[Group.of.nepali.translators] [Bug 1769888] Re: New upstream microreleases 9.3.23, 9.5.13, 9.6.9 and 10.4
This bug was fixed in the package postgresql-9.5 - 9.5.13-0ubuntu0.16.04 --- postgresql-9.5 (9.5.13-0ubuntu0.16.04) xenial; urgency=medium * New upstream release (LP: #1769888) - A dump/restore is not required for those running 9.5.X. However, if the function marking mistakes mentioned in the first changelog entry affect you, you will want to take steps to correct your database catalogs. - Details about changes can be found at https://www.postgresql.org/docs/9.5/static/release-9-5-13.html -- Christian Ehrhardt Tue, 08 May 2018 15:17:49 +0200 ** Changed in: postgresql-9.3 (Ubuntu Trusty) 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/1769888 Title: New upstream microreleases 9.3.23, 9.5.13, 9.6.9 and 10.4 Status in postgresql-10 package in Ubuntu: Invalid Status in postgresql-9.3 package in Ubuntu: Invalid Status in postgresql-9.5 package in Ubuntu: Invalid Status in postgresql-9.6 package in Ubuntu: Invalid Status in postgresql-9.3 source package in Trusty: Fix Released Status in postgresql-9.5 source package in Xenial: Fix Released Status in postgresql-9.6 source package in Artful: Fix Released Status in postgresql-10 source package in Bionic: Fix Released Bug description: Postgresql stable update Current versions in supported releases: postgresql-9.3 | 9.3.22-0ubuntu0.14.04 trusty postgresql-9.5 | 9.5.12-0ubuntu0.16.04 xenial postgresql-9.6 | 9.6.8-0ubuntu0.17.10 artful postgresql-10 | 10.3-1bionic postgresql-10 | 10.3-2cosmic Special cases: - Cosmic will be synced from Debian which usually releases fast. So no Cosmic upload by us. Last related stable updates: 9.3.23, 9.5.13, 9.6.9, 10.4 So the todo is to pick: MRE: Trusty 9.3.23 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.3.23.tar.gz MRE: Xenial 9.5.13 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.5.13.tar.gz MRE: Artful 9.6.9 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-9.6.9.tar.gz MRE: Bionic 10.4 from https://borka.postgresql.org/staging/cb8f0c2ac40d4189a887fbf076c597239afd5264/postgresql-10.4.tar.gz Sync: Cosmic 10.4 via Debian auto-sync Standing MRE - Consider last updates as template: - pad.lv/1637236 - pad.lv/1664478 - pad.lv/1690730 - pad.lv/1713979 - pad.lv/1730661 - pad.lv/1747676 - pad.lv/1752271 New - this bug - pad.lv/1769888 Test builds and tests took place in PPAs T: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3254 X: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3255 A: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3256 B: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3257 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-10/+bug/1769888/+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 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker
4.13.0-1019.23 - gcp Regression test CMPL, RTB. Issue to note in gcp: libhugetlbfs - 1 failed , 1 killed by signal, 3 bad config ubuntu_kvm_unit_tests - failed due to no KVM support Skipped / blacklisted: * ubuntu_ltp * ubuntu_seccomp * ubuntu_sysdig_smoke_test * ubuntu_zram_smoke_test ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1774127 Title: linux-gcp: 4.13.0-1019.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774127/+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 1739591] Re: lttng-modules-dkms failed to build with 4.14 Azure edge kernel on Xenial
** Also affects: ubuntu-kernel-tests 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/1739591 Title: lttng-modules-dkms failed to build with 4.14 Azure edge kernel on Xenial Status in lttng-modules: New Status in ubuntu-kernel-tests: New Status in lttng-modules package in Ubuntu: Fix Released Status in lttng-modules source package in Xenial: Fix Released Status in lttng-modules source package in Artful: Fix Released Bug description: SRU request, Xenial, Artful [Impact] lttng dkms modules fail to build against newer HWE kernels because of missing 4.14 compat fixes that allow it to build against newer 4.14 kernels. [Fix] Upstream lttng 4.14 compat fixes. [Testcase] Without the fix, running the kernel team autotest lttng regression test suite fails because the module does not build and install. With the fix the lttng smoke tests pass. To run the test: sudo autotest/client/autotest-local autotest/client/tests/ubuntu_lttng_smoke_test/control using git://kernel.ubuntu.com/ubuntu/autotest and git://kernel.ubuntu.com/ubuntu/autotest-client-tests [Regression Potential] lttng fails to build and work against older kernels. As the new code is #if'def'd compat code the 4.14 specific changes are not built into the older kernels, so this risk is small. -- [stdout] Setting up lttng-modules-dkms (2.8.0-1ubuntu1~16.04.3) ... [stdout] Loading new lttng-modules-2.8.0 DKMS files... [stdout] First Installation: checking all kernels... [stdout] Building only for 4.14.0-1002-azure-edge [stdout] Building initial module for 4.14.0-1002-azure-edge [stdout] Error! Bad return status for module build on kernel: 4.14.0-1002-azure-edge (x86_64) [stdout] Consult /var/lib/dkms/lttng-modules/2.8.0/build/make.log for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/lttng-modules/+bug/1739591/+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 1729849] Re: mkfs.xfs complains about /dev/sdb2 is busy on Xenial
** Also affects: ubuntu-kernel-tests 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/1729849 Title: mkfs.xfs complains about /dev/sdb2 is busy on Xenial Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: This issue is reproducible on two different nodes in our testpool, fozzie and rizzo, both with 4.4.0-98-generic amd64. On a clean install system with a scratch drive sdb available. Steps: 1. sudo parted /dev/sdb mklabel -s gpt 2. sudo parted /dev/sdb mkpart -s p1 xfs 1MiB 2MiB 3. sudo parted /dev/sdb mkpart -s p2 xfs 20001MiB 4MiB 4. sudo mkfs.xfs -f /dev/sdb1 5. sudo mkfs.xfs -f /dev/sdb2 Result: mkfs.xfs: cannot open /dev/sdb2: Device or resource busy In my test case, there are 5 partitions from sdb1 to sdb5, only sdb2 will fail with this. And this happens on both nodes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: User Name 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 3 12:07 seq crw-rw 1 root audio 116, 33 Nov 3 12:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 3 12:37:59 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd09/06/2013:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA09:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1729849/+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 1712803] Re: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Xenial) 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/1712803 Title: spapr_hcall from ubuntu_kvm_unit_test failed on ppc64el with Z-hwe kernel Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in qemu source package in Xenial: Fix Released Bug description: [Impact] * Xenial with HWE kernel (matching new relesaes) and qemu without cloud archive (not matching new releases) could trigger hypercalls that are not supported in xenials-qemu. * There is no "real" case other than kvm tests yet to trigger it yet, but it is an easy and well contained fix, so we might fix proactively. [Test Case] 1. deploy xenial + HWE kernel on a ppc64el box 2. sudo apt-get install qemu-kvm -y 3. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 4. cd kvm-unit-tests 5. ./configure --endian=little; make 6. sudo ppc64_cpu --smt=off 7. sudo ./run_tests -v [Regression Potential] * The changes are all upstream since a long time now (lowering the risk of silly mistakes) * The changes are isolated to ppc, so in the worst case only this arch should regress. * We implement new hcalls, so if anything there might be a regression if software expected them to fail, but now breaks by them working (don't think so given the nature of these hcalls). [Other Info] * n/a --- kernel: 4.10.0-33.37~16.04.1 I think this issue was introduced by the old qemu version (similar issue was spotted on Xenial before), will need to investigate this further. qemu-system-ppc64 -machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial stdio -kernel powerpc/spapr_hcall.elf -smp 1 FAIL: hypercall: h_set_sprg0: sprg0 = 0xcafebabedeadbeef FAIL: hypercall: h_set_sprg0: sprg0 = 0x FAIL: hypercall: h_set_sprg0: sprg0 = 0x41a588 FAIL: hypercall: h_page_init: h_zero_page FAIL: hypercall: h_page_init: h_copy_page FAIL: hypercall: h_page_init: h_copy_page+h_zero_page FAIL: hypercall: h_page_init: h_zero_page unaligned dst FAIL: hypercall: h_page_init: h_copy_page unaligned src XFAIL: hypercall: h_random: h-call available SUMMARY: 9 tests, 8 unexpected failures, 1 expected failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1712803/+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 1723904] Re: ubuntu-kvm-unit test failed with sprs test on ppc64le
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: ubuntu-kernel-tests 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/1723904 Title: ubuntu-kvm-unit test failed with sprs test on ppc64le Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in qemu package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in qemu source package in Xenial: Fix Released Bug description: [Impact] * Certain Guest features (SPRS) of power8 isa are not working * This is part of the ongoing LTS HW exploitation and a fixup to some verification tests at the same time. [Test Case] * 1. deploy xenial + HWE kernel on a ppc64el box 2. sudo apt-get install qemu-kvm -y 3. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 4. cd kvm-unit-tests 5. ./configure --endian=little; make 6. sudo ppc64_cpu --smt=off 7. sudo ./run_tests.sh -v [Regression Potential] * The changes are ppc only and provided by IBM so the potential risk is retained to the owner of the Area. Further if these registers are not used they do nothing, so in most cases it will be a nop. OTOH the changes are rather huge (in terms of LOC) so there is some risk left. [Other Info] * n/a --- The sprs test has failed on ppc64le This issue can be spotted on Zesty and Xenial. There is no history for this test on Artful $ sudo /bin/bash -c "MIGRATION=yes TESTNAME=sprs TIMEOUT=90s ACCEL= ./powerpc/run powerpc/sprs.elf -smp 1 -append '-w'" run_migration timeout -k 1s --foreground 90s /usr/bin/qemu-system-ppc64 -nodefaults -machine pseries,accel=kvm -bios powerpc/boot_rom.bin -display none -serial stdio -kernel powerpc/sprs.elf -smp 1 -append -w # -initrd /tmp/tmp.RUTL6E2JSi Settings SPRs to 0xcafefacec0debabe... Now migrate the VM, then press a key or send NMI... Checking SPRs... PASS: SPR 3: 0x00debabe <==> 0x00debabe PASS: SPR 13: 0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 17: 0x00debabe <==> 0x00debabe PASS: SPR 18: 0xc0debabe <==> 0xc0debabe PASS: SPR 19: 0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 29: 0xcafefacec0debabe <==> 0xcafefacec0debabe FAIL: SPR 61: 0x4054504440541014 <==> 00 PASS: SPR 153:0x0a84 <==> 0x0a84 PASS: SPR 157:0xcfcfc0cf <==> 0xcfcfc0cf FAIL: SPR 159:0xc0debabe <==> 00 PASS: SPR 256:0xc0debabe <==> 0xc0debabe PASS: SPR 259:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 274:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 275:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 769:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 770:0xcafefacec006babe <==> 0xcafefacec006babe PASS: SPR 771:0xc0debabe <==> 0xc0debabe PASS: SPR 772:0xc0debabe <==> 0xc0debabe PASS: SPR 773:0xc0debabe <==> 0xc0debabe PASS: SPR 774:0xc0debabe <==> 0xc0debabe PASS: SPR 775:0xc0debabe <==> 0xc0debabe PASS: SPR 776:0xc0debabe <==> 0xc0debabe PASS: SPR 779:0xfa8b1afe <==> 0xfa8b1afe PASS: SPR 780:0xcafefacec0debabc <==> 0xcafefacec0debabc PASS: SPR 781:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 782:0xcafefacec0debabe <==> 0xcafefacec0debabe FAIL: SPR 784:0xcafefacec0debabe <==> 00 PASS: SPR 785:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 786:0xcafefacec006babe <==> 0xcafefacec006babe PASS: SPR 787:0xc0debabe <==> 0xc0debabe PASS: SPR 788:0xc0debabe <==> 0xc0debabe PASS: SPR 789:0xc0debabe <==> 0xc0debabe PASS: SPR 790:0xc0debabe <==> 0xc0debabe PASS: SPR 791:0xc0debabe <==> 0xc0debabe PASS: SPR 792:0xc0debabe <==> 0xc0debabe PASS: SPR 795:0xfa8b1afe <==> 0xfa8b1afe PASS: SPR 796:0xcafefacec0debabc <==> 0xcafefacec0debabc PASS: SPR 797:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 798:0xcafefacec0debabe <==> 0xcafefacec0debabe PASS: SPR 800:0x8000c000 <==> 0x8000c000 PASS: SPR 801:
[Group.of.nepali.translators] [Bug 1710868] Re: memory-hotplug test needs to be fixed
** Changed in: linux (Ubuntu Artful) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) 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/1710868 Title: memory-hotplug test needs to be fixed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Bug description: SRU Justification: Impact: The memory-hotplug test in the kernel tree (tools/testing/selftests/memory-hotplug/) needs to be fixed: 1. The test will pass even the memory blocks are failed to be offlined [1]. 2. It's using a random number generator to decide if each memory block needs to be offlined, which is not ideal for testing as the block it tries to unplug might be different between two runs. 3. The "-r" flag, percent-of-memory-to-offline, does not match what is says. It's being used as the percentage to get a memory block offlined instead. Fix: Apply the following patch from upstream can fix these issues: 593f9278 - selftests: typo correction for memory-hotplug test a34b28c9 - selftests: check hot-pluggagble memory for memory-hotplug test 72441ea5 - selftests: check percentage range for memory-hotplug test 02d8f075 - selftests: add missing test name in memory-hotplug test 5ff0c60b - selftests: fix memory-hotplug test Testcase: Run the script directly, it will fail when all memory blocks are busy. And it will try to unplug memory blocks in a fixed order. Regression Potential: Negligible, it's just affecting this specific test case among those testing tools. [1] https://paste.ubuntu.com/25318445/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1710868/+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 1760638] Re: dccp test in ubuntu_stress_smoke_test failed with 4.4/4.15 KVM kernel
** Also affects: ubuntu-kernel-tests 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/1760638 Title: dccp test in ubuntu_stress_smoke_test failed with 4.4/4.15 KVM kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux-kvm package in Ubuntu: New Status in linux source package in Xenial: Triaged Status in linux-kvm source package in Xenial: New Status in linux source package in Bionic: Triaged Status in linux-kvm source package in Bionic: New Bug description: The test failed with: 16:26:24 DEBUG| [stdout] dccp STARTING 16:26:24 DEBUG| [stdout] dccp RETURNED 2 16:26:24 DEBUG| [stdout] dccp FAILED 16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] 2 processors online, 2 processors configured 16:26:24 DEBUG| [stdout] stress-ng: info: [2228] dispatching hogs: 4 dccp 16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] cache allocate: reducing cache level from L3 (too high) to L2 16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] cache allocate: default cache size: 4096K 16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] starting stressors 16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] 4 stressors spawned 16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: started [2231] (instance 2) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: started [2232] (instance 3) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: started [2229] (instance 0) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: started [2230] (instance 1) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: process [2231] using socket port 10002 16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: process [2229] using socket port 1 16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: process [2232] using socket port 10003 16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: process [2230] using socket port 10001 16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: socket failed, errno=94 (Socket type not supported) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: 0 messages sent 16:26:24 DEBUG| [stdout] stress-ng: debug: [2231] stress-ng-dccp: exited [2231] (instance 2) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2239] stress-ng-dccp: socket failed, errno=94 (Socket type not supported) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: socket failed, errno=94 (Socket type not supported) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: 0 messages sent 16:26:24 DEBUG| [stdout] stress-ng: debug: [2230] stress-ng-dccp: exited [2230] (instance 1) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: socket failed, errno=94 (Socket type not supported) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: 0 messages sent 16:26:24 DEBUG| [stdout] stress-ng: debug: [2232] stress-ng-dccp: exited [2232] (instance 3) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2235] stress-ng-dccp: socket failed, errno=94 (Socket type not supported) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: socket failed, errno=94 (Socket type not supported) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: 0 messages sent 16:26:24 DEBUG| [stdout] stress-ng: debug: [2229] stress-ng-dccp: exited [2229] (instance 0) 16:26:24 DEBUG| [stdout] stress-ng: error: [2228] process 2229 (stress-ng-dccp) terminated with an error, exit status=1 (stress-ng core failure) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] process [2229] terminated 16:26:24 DEBUG| [stdout] stress-ng: error: [2228] process 2230 (stress-ng-dccp) terminated with an error, exit status=1 (stress-ng core failure) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] process [2230] terminated 16:26:24 DEBUG| [stdout] stress-ng: error: [2228] process 2231 (stress-ng-dccp) terminated with an error, exit status=1 (stress-ng core failure) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] process [2231] terminated 16:26:24 DEBUG| [stdout] stress-ng: error: [2228] process 2232 (stress-ng-dccp) terminated with an error, exit status=1 (stress-ng core failure) 16:26:24 DEBUG| [stdout] stress-ng: debug: [2228] process [2232] terminated 16:26:24 DEBUG| [stdout] stress-ng: info: [2228] unsuccessful run completed in 0.01s 16:26:24 DEBUG| [stdout] Steps to reproduce: Deploy the node with Xenial 4.4 kernel, install linux-kvm sudo apt-get install python-minimal git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr
