[Group.of.nepali.translators] [Bug 1765176] Re: linux-azure-edge: 4.15.0-1006.6~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Description changed: This bug is for tracking the 4.15.0-1006.6~16.04.1 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 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 20. April 2018 22:06 UTC ** Description changed: This bug is for tracking the 4.15.0-1006.6~16.04.1 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 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 20. April 2018 22:06 UTC + bugs-spammed: true + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1765176 Title: linux-azure-edge: 4.15.0-1006.6~16.04.1 -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: 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 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: Confirmed Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure-edge package in Ubuntu: Invalid Status in linux-azure-edge source package in Xenial: Confirmed Bug description: This bug is for tracking the 4.15.0-1006.6~16.04.1 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 bugs-spammed: true 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/1765176/+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 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'
The function was slightly in Trusty but the attached debdiff should fix the crash seen in the Error Tracker. ** Also affects: apport (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Trusty) Status: New => In Progress ** Changed in: apport (Ubuntu Trusty) Assignee: (unassigned) => Brian Murray (brian-murray) ** Patch added: "bug-1733366-trusty.patch" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1733366/+attachment/5124395/+files/bug-1733366-trusty.patch -- 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/1733366 Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Trusty: In Progress Status in apport source package in Xenial: Fix Released Status in apport source package in Zesty: Fix Released Status in apport source package in Artful: Fix Released Status in apport source package in Bionic: Fix Released Bug description: https://errors.ubuntu.com/problem/b6b178fe6ed572189dbfe2627876ed9e9d59ace2 --- It appears that after login this was the first action performed by the system which resulted in the generation of the crash report. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.8-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash Date: Mon Nov 20 01:59:46 2017 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop Experience Bionic Beaver" InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102 ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102'] PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SourcePackage: apport Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1733366/+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 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
** Bug watch added: Debian Bug tracker #896433 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896433 ** Also affects: ifupdown (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896433 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #896434 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896434 ** Also affects: vlan (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896434 Importance: Unknown Status: Unknown -- 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/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion Status in ifupdown package in Ubuntu: In Progress Status in vlan package in Ubuntu: In Progress Status in ifupdown source package in Trusty: In Progress Status in vlan source package in Trusty: In Progress Status in ifupdown source package in Xenial: In Progress Status in vlan source package in Xenial: In Progress Status in ifupdown source package in Artful: In Progress Status in vlan source package in Artful: In Progress Status in ifupdown source package in Bionic: In Progress Status in vlan source package in Bionic: In Progress Status in ifupdown package in Debian: Unknown Status in vlan package in Debian: Unknown Bug description: When upgrading from version 1.9-3ubuntu10.1, a previously working machine can't successfully reboot completely. ifup is hanging indefinitely, with this process structure (from "pstree -a 1299"): ifup,1299 -a └─run-parts,1501 /etc/network/if-pre-up.d └─bridge,1502 /etc/network/if-pre-up.d/bridge └─bridge,1508 /etc/network/if-pre-up.d/bridge └─vlan,1511 /etc/network/if-pre-up.d/vlan └─ifup,1532 eth0 auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.10.65 netmask 255.255.255.192 gateway 192.168.10.66 auto eth0.11 address 192.168.11.1 netmask 255.255.255.0 auto br1134 iface br1134 inet manual bridge_ports eth0.1134 bridge_stp off bridge_fd 0 The underlying interface eth0.1134 is not explicitly defined, but was previously auto-created during "ifup -a" execution. This apparently fails now. Reverting back to the 10.1 version re-establishes old behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+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 1701023] Re: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion
** Also affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Changed in: ifupdown (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: ifupdown (Ubuntu Trusty) Status: New => In Progress ** Changed in: ifupdown (Ubuntu Trusty) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: ifupdown (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: ifupdown (Ubuntu Xenial) Status: New => In Progress ** Changed in: ifupdown (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: ifupdown (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: ifupdown (Ubuntu Artful) Status: New => In Progress ** Changed in: ifupdown (Ubuntu Artful) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: ifupdown (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: ifupdown (Ubuntu Bionic) Status: New => In Progress ** Changed in: ifupdown (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) -- 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/1701023 Title: (on trusty) version 1.9-3ubuntu10.4 regression blocking boot completion Status in ifupdown package in Ubuntu: In Progress Status in vlan package in Ubuntu: In Progress Status in ifupdown source package in Trusty: In Progress Status in vlan source package in Trusty: In Progress Status in ifupdown source package in Xenial: In Progress Status in vlan source package in Xenial: In Progress Status in ifupdown source package in Artful: In Progress Status in vlan source package in Artful: In Progress Status in ifupdown source package in Bionic: In Progress Status in vlan source package in Bionic: In Progress Bug description: When upgrading from version 1.9-3ubuntu10.1, a previously working machine can't successfully reboot completely. ifup is hanging indefinitely, with this process structure (from "pstree -a 1299"): ifup,1299 -a └─run-parts,1501 /etc/network/if-pre-up.d └─bridge,1502 /etc/network/if-pre-up.d/bridge └─bridge,1508 /etc/network/if-pre-up.d/bridge └─vlan,1511 /etc/network/if-pre-up.d/vlan └─ifup,1532 eth0 auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 192.168.10.65 netmask 255.255.255.192 gateway 192.168.10.66 auto eth0.11 address 192.168.11.1 netmask 255.255.255.0 auto br1134 iface br1134 inet manual bridge_ports eth0.1134 bridge_stp off bridge_fd 0 The underlying interface eth0.1134 is not explicitly defined, but was previously auto-created during "ifup -a" execution. This apparently fails now. Reverting back to the 10.1 version re-establishes old behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1701023/+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 1741978] Re: Add support for ARM events
** Also affects: rasdaemon (Ubuntu Bionic) Importance: High Status: 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/1741978 Title: Add support for ARM events Status in rasdaemon package in Ubuntu: Fix Released Status in rasdaemon source package in Xenial: Fix Committed Status in rasdaemon source package in Zesty: Won't Fix Status in rasdaemon source package in Artful: Fix Committed Status in rasdaemon source package in Bionic: Fix Released Status in rasdaemon package in Debian: Fix Released Bug description: [IMPACT] The UEFI 2.6 spec added support for ARM processor errors and errors that have unrecognized CPER section types. rasdaemon needs to support ARM kernel trace events. [FIX] The following patches add support for ARM events to rasdaemon: rasdaemon: add support for non standard CPER section events rasdaemon: add support for ARM events ARM support was added to rasdaemon in version 0.6.0 release. [TESTING] The patches were applied to rasdaemon 0.5.8 and 0.5.6 versions and tested on Artful and Xenial. Test results are attached to comments below. [REGRESSION POTENTIAL] None. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rasdaemon/+bug/1741978/+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 1761459] Re: linux-azure: 4.13.0-1014.17 -proposed tracker
Our testing is complete. Please publish. ** Changed in: kernel-sru-workflow/stakeholder-signoff 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/1761459 Title: linux-azure: 4.13.0-1014.17 -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 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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 stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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: 1761456 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/1761459/+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 1764956] Re: Guests using IBRS incur a large performance penalty
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Tags added: kernel-da-key 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/1764956 Title: Guests using IBRS incur a large performance penalty Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Hello! As of Linux 4.4.0-119, when a KVM guest is using IBRS, this incurs a very large performance penalty on the hosts and other guests. From my understanding, the patch f676aa34b4027d1a7a4bbcc58b81b20c68c7ce0c is incomplete. If host doesn't handle IBRS itself (which is now the case by default since 4.4.0-116: it relies on retpoline instead) but the guest does (eg running an earlier kernel), the guest will set IBRS for the CPU it is running on from time to time but if it gets preempted at some point, the IBRS bit will stay, incurring a major performance penalty for all other users of the CPU (host userland, host kernel and other guests not caring about IBRS). The equivalent patch in mainline (d28b387fb74da95d69d2615732f50cceb38e9a4d) ensure the appropriate MSR is correctly restored when switching from one guest to another or from one guest to host. The issue is easy to reproduce: host running 4.4.0-119, exposing "spec_ctrl" to a guest running CentOS 7.4 with its January kernel. Wait a few minutes and the host will become pretty slow. A simple shell loop will take 10 more times to execute. Executing "sysctl -w kernel.ibrs_dump=1" will show that most real cores have now their IBRS bit set to 1. A workaround is to reeanble IBRS on the host (sysctl -w kernel.ibrs_enabled=1). This way, IBRS will be correctly disabled when changing context. A long term solution would be to properly backport the patch from mainline. It is not part of the 4.4 stable branch and it seems not trivial to port. A mid term solution could be to remove the faulty patch (not exposing IBRS), since most VM don't need it anymore. This also salvage the ability to use IBPB (which doesn't seem to alter performance that much) but it isn't believed to be essential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764956/+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 1761444] Re: linux-euclid: 4.4.0-9026.28 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: block-proposed -- 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/1761444 Title: linux-euclid: 4.4.0-9026.28 -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: Fix Released 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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-euclid package in Ubuntu: Invalid Status in linux-euclid 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: 1763687 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/1761444/+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 1763687] Re: linux: 4.4.0-121.145 -proposed tracker
4.4.0-121.145 - lowlatency Regression test CMPL. Issue to note in amd64: monotonic_time - gtod failed on rumford ubuntu_bpf_jit - Unable to insert test_bpf module on Xenial (bug 1765698) ubuntu_kvm_unit_tests - 29 failed on amaura, 18 failed on harpo, 20 failed on michael, 27 failed on pepe ubuntu_lxc - lxc-test-ubuntu (Failed to start networking in ubuntu-cloud container) xfstests - xfs generic/475 failed Issue to note in i386: monotonic_time - gtod tend to fail on onibi ubuntu_kvm_unit_tests - failed to build (bug 1765366) xfstests - xfs generic/308 timed out, bug 1738152 4.4.0-121.145 - generic Regression test CMPL. Issue to note in amd64: ubuntu_bpf_jit - Unable to insert test_bpf module on Xenial (bug 1765698) ubuntu_kvm_unit_tests - 29 failed on amaura, 20 failed on michael, 28 failed on pepe xfstests - xfs generic/475 failed Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427) ubuntu_kvm_unit_tests - pmu on ms10-34-mcdivittB0-kernel (bug 1751000) gicv2-ipi and gicv2-active on starmie Issue to note in i386: ubuntu_kvm_unit_tests - failed to build (bug 1765366) xfstests - xfs generic/308 timed out, bug 1738152 Issue to note in s390x (Ubuntu on LPAR): aio_dio_bugs - event res -22 (bug 1730895) libhugetlbfs - failed 11 killed by signal 7 bad config 1 scrashme - Test failed to build (bug 1689240) ubuntu_bpf_jit - Unable to insert test_bpf module on Xenial (bug 1765698) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) Issue to note in s390x (zKVM): aio_dio_bugs - event res -22 (bug 1730895) libhugetlbfs - failed 11 killed by signal 7 bad config 1 scrashme - Test failed to build (bug 1689240) ubuntu_bpf_jit - Unable to insert test_bpf module on Xenial (bug 1765698) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - 11 failed (nested kvm is not supported) ubuntu_lxc - lxc-test-ubuntu (Failed to start networking in ubuntu-cloud container) ubuntu_qrt_apparmor - passed after re-test Issue to note in s390x (zVM): aio_dio_bugs - event res -22 (bug 1730895) libhugetlbfs - failed 11 killed by signal 7 bad config 1 scrashme - Test failed to build (bug 1689240) ubuntu_bpf_jit - Unable to insert test_bpf module on Xenial (bug 1765698) ubuntu_ecryptfs - passed after re-test ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - skey failed ubuntu_lxc - lxc-test-ubuntu (Failed to start networking in ubuntu-cloud container) MISSING RESULT FROM POWER8 - testing node out-of-order ** 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/1763687 Title: linux: 4.4.0-121.145 -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: Fix Released 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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1763688 (linux-lts-xenial) derivatives: bug 1763689 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to pr
[Group.of.nepali.translators] [Bug 1765698] Re: Unable to insert test_bpf module on Xenial
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) ** Description changed: With 4.4.0-119, the ubuntu_bpf_jit test will pass: - [ 127.177037] test_bpf: Summary: 291 PASSED, 0 FAILED, [0/283 JIT'ed] - PASSED: 291 - FAILED: 0 + [ 127.177037] test_bpf: Summary: 291 PASSED, 0 FAILED, [0/283 JIT'ed] + PASSED: 291 + FAILED: 0 But with 4.4.0-121, one test will fail - [ 221.361834] test_bpf: Summary: 290 PASSED, 1 FAILED, [282/282 JIT'ed] - PASSED: 290 - FAILED: 1 - stderr: - modprobe: ERROR: could not insert 'test_bpf': Invalid argument + [ 221.361834] test_bpf: Summary: 290 PASSED, 1 FAILED, [282/282 JIT'ed] + PASSED: 290 + FAILED: 1 + stderr: + modprobe: ERROR: could not insert 'test_bpf': Invalid argument $ sudo modprobe test_bpf modprobe: ERROR: could not insert 'test_bpf': Invalid argument + $ dmesg|grep test_bpf|grep FAIL + [ 45.286944] test_bpf: #248 BPF_MAXINSNS: Jump, gap, jump, ... FAIL to prog_create err=-524 len=4096 + [ 45.619293] test_bpf: Summary: 290 PASSED, 1 FAILED, [282/282 JIT'ed] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-121-generic 4.4.0-121.145 ProcVersionSignature: User Name 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Apr 20 12:29 seq - crw-rw 1 root audio 116, 33 Apr 20 12:29 timer + total 0 + crw-rw 1 root audio 116, 1 Apr 20 12:29 seq + crw-rw 1 root audio 116, 33 Apr 20 12:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: - + Date: Fri Apr 20 12:32:59 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: - + ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: - linux-restricted-modules-4.4.0-121-generic N/A - linux-backports-modules-4.4.0-121-generic N/A - linux-firmware 1.157.17 + linux-restricted-modules-4.4.0-121-generic N/A + linux-backports-modules-4.4.0-121-generic N/A + linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation -- 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/1765698 Title: Unable to insert test_bpf module on Xenial Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: In Progress Bug description: With 4.4.0-119, the ubuntu_bpf_jit test will pass: [ 127.177037] test_bpf: Summary: 291 PASSED, 0 FAILED, [0/283 JIT'ed] PASSED: 291 FAILED: 0 But with 4.4.0-121, one test will fail [ 221.361834] test_bpf: Summary: 290 PASSED, 1 FAILED, [282/282 JIT'ed] PASSED: 290 FAILED: 1 stderr: modprobe: ERROR: could not insert 'test_bpf': Invalid argument $ sudo modprobe test_bpf modprobe: ERROR: could not insert 'test_bpf': Invalid argument $ dmesg|grep test_bpf|grep FAIL [ 45.286944] test_bpf: #248 BPF_MAXINSNS: Jump, gap, jump, ... FAIL to prog_create err=-524 len=4096 [ 45.619293] test_bpf: Summary: 290 PASSED, 1 FAILED, [282/282 JI
[Group.of.nepali.translators] [Bug 1738259] Re: need to ensure microcode updates are available to all bare-metal installs of Ubuntu
linux-meta-lts-xenial should be nominated for trusty, not xenial
** Changed in: linux-meta (Ubuntu Artful)
Status: Triaged => Fix Committed
** Changed in: linux-meta (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-meta (Ubuntu Xenial)
Status: Triaged => Fix Committed
** Changed in: linux-meta (Ubuntu Artful)
Importance: Undecided => Medium
** Changed in: linux-meta-hwe (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-meta-hwe (Ubuntu Xenial)
Status: Triaged => Fix Committed
** Changed in: linux-meta-hwe-edge (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-meta-hwe-edge (Ubuntu Xenial)
Status: Triaged => Fix Committed
** Changed in: linux-meta-lts-xenial (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux-meta-lts-xenial (Ubuntu Xenial)
Status: New => Fix Committed
** Changed in: linux-meta-lts-xenial (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux-meta (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: linux-meta (Ubuntu Trusty)
Status: Triaged => 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/1738259
Title:
need to ensure microcode updates are available to all bare-metal
installs of Ubuntu
Status in linux-meta package in Ubuntu:
Triaged
Status in linux-meta-hwe package in Ubuntu:
New
Status in linux-meta-hwe-edge package in Ubuntu:
New
Status in linux-meta-lts-xenial package in Ubuntu:
Invalid
Status in linux-meta source package in Precise:
New
Status in linux-meta source package in Trusty:
Fix Committed
Status in linux-meta source package in Xenial:
Fix Committed
Status in linux-meta-hwe source package in Xenial:
Fix Committed
Status in linux-meta-hwe-edge source package in Xenial:
Fix Committed
Status in linux-meta-lts-xenial source package in Xenial:
Fix Committed
Status in linux-meta source package in Zesty:
Invalid
Status in linux-meta source package in Artful:
Fix Committed
Status in linux-meta source package in Bionic:
Triaged
Bug description:
From time to time, CPU vendors release updates to microcode that can
be loaded into the CPU from the OS. For x86, we have these updates
available in the archive as amd64-microcode and intel-microcode.
Sometimes, these microcode updates have addressed security issues with
the CPU. They almost certainly will again in the future.
We should ensure that all users of Ubuntu on baremetal x86 receive
these security updates, and have them applied to the CPU in early boot
where at all feasible.
Because these are hardware-dependent packages which we don't want to
install except on baremetal (so: not in VMs or containers), the
logical place to pull them into the system is via the kernel, so that
only the kernel baremetal flavors pull them in. This is analogous to
linux-firmware, which is already a dependency of the linux-
image-{lowlatency,generic} metapackages, and whose contents are
applied to the hardware by the kernel similar to microcode.
So, please update the linux-image-{lowlatency,generic} metapackages to
add a dependency on amd64-microcode [amd64], intel-microcode [amd64],
and the corresponding hwe metapackages also.
Please time this change to coincide with the next updates of the
microcode packages in the archive.
I believe we will also need to promote the *-microcode packages to
main from restricted as part of this (again, by analogy with linux-
firmware).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1738259/+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 1765563] Re: gegl: CVE-2018-10114 (ppm)
https://launchpad.net/ubuntu/+source/gegl/0.3.30-1ubuntu1 ** Changed in: gegl (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/1765563 Title: gegl: CVE-2018-10114 (ppm) Status in gegl package in Ubuntu: Fix Released Status in gegl source package in Trusty: New Status in gegl source package in Xenial: New Status in gegl source package in Artful: New Bug description: https://security-tracker.debian.org/tracker/CVE-2018-10114 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gegl/+bug/1765563/+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 1761462] Re: linux-hwe: 4.13.0-39.44~16.04.1 -proposed tracker
4.13.0-39.44~16.04.1 - lowlatency Regression test CMPL. Issue to note in amd64: monotonic_time - gtod tend to fail on onibi ubuntu_kvm_unit_tests - 25 failed on amaura, 8 failed on michael (apic, vmware_backdoors, vmx, vmx_interrupt, vmx_controls, vmx_eoi_bitmap_ioapic_scan, vmx_apic_passthrough, vmx_apic_passthrough_thread), 21 failed on pepe xfstests - test case issue, patch failed to apply Issue to note in i386: monotonic_time - gtod tend to fail on onibi ubuntu_kvm_unit_tests - failed to build (bug 1765366) xfstests - test case issue, patch failed to apply 4.13.0-39.44~16.04.1 - generic Regression test CMPL. Issue to note in amd64: monotonic_time - gtod tend to fail on onibi ubuntu_kvm_unit_tests - 25 failed on amaura, 8 failed on michael, 21 failed on pepe ubuntu_lxc - lxc-test-ubuntu failed (Failed to start networking in ubuntu-cloud container) xfstests - test case issue, patch failed to apply Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427) ubuntu_kvm_unit_tests - pmu on starmie (bug 1751000) gicv2-ipi and gicv2-active on starmie pmu on ms10-34-mcdivittB0-kernel (bug 1751000) ubuntu_unionmount_overlayfs_suite - timed out on starmie, passed on the rest ubuntu_zfs_xfs_generic - 192 failed on starmie, passed on the rest xfstests - xfs/438 timed out Issue to note in i386: ubuntu_kvm_unit_tests - failed to build (bug 1765366) xfstests - test case issue, patch failed to apply MISSING RESULT FROM POWER8 - testing node out-of-order ** 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/1761462 Title: linux-hwe: 4.13.0-39.44~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: Fix Released 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released 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: 1761456 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/1761462/+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 1765241] Re: virtio_scsi race can corrupt memory, panic kernel
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: 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/1765241 Title: virtio_scsi race can corrupt memory, panic kernel Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: In Progress Bug description: There's a race in the virtio_scsi driver (for all kernels) That race is inadvertently avoided on most kernels due to a synchronize_rcu call coincidentally placed in one of the racing code paths By happenstance, the set of patches backported to the Ubuntu 4.4 kernel ended up without a synchronize_rcu in the relevant place. The issue first manifests with commit be2a20802abbde04ae09846406d7b670731d97d2 Author: Jan Kara Date: Wed Feb 8 08:05:56 2017 +0100 block: Move bdi_unregister() to del_gendisk() BugLink: http://bugs.launchpad.net/bugs/1659111 The race can cause a kernel panic due to corruption of a freelist pointer in a slab cache. The panics occur in arbitrary places as the failure occurs at an allocation after the corruption of the pointer. However, the most common failure observed has been within virtio_scsi itself during probe processing, e.g.: [3.111628] [] kfree_const+0x22/0x30 [3.112340] [] kobject_release+0x94/0x190 [3.113126] [] kobject_put+0x27/0x50 [3.113838] [] put_device+0x17/0x20 [3.114568] [] __scsi_remove_device+0x92/0xe0 [3.115401] [] scsi_probe_and_add_lun+0x95b/0xe80 [3.116287] [] ? kmem_cache_alloc_trace+0x183/0x1f0 [3.117227] [] ? __pm_runtime_resume+0x5b/0x80 [3.118048] [] __scsi_scan_target+0x10a/0x690 [3.118879] [] scsi_scan_channel+0x7e/0xa0 [3.119653] [] scsi_scan_host_selected+0xf3/0x160 [3.120506] [] do_scsi_scan_host+0x8d/0x90 [3.121295] [] do_scan_async+0x1c/0x190 [3.122048] [] async_run_entry_fn+0x48/0x150 [3.122846] [] process_one_work+0x165/0x480 [3.123732] [] worker_thread+0x4b/0x4d0 [3.124508] [] ? process_one_work+0x480/0x480 Details on the race: CPU A: virtscsi_probe [...] __scsi_scan_target scsi_probe_and_add_lun [on return calls __scsi_remove_device, below] scsi_probe_lun [...] blk_execute_rq blk_execute_rq waits for the completion event, and then on wakeup returns up to scsi_probe_and_all_lun, which calls __scsi_remove_device. In order for the race to occur, the wakeup must occur on a CPU other than CPU B. After being woken up by the completion of the request, the call returns up the stack to scsi_probe_and_add_lun, which calls __scsi_remove_device: __scsi_remove_device blk_cleanup_queue [ no longer calls bdi_unregister ] scsi_target_reap(scsi_target(sdev)) scsi_target_reap_ref_put kref_put kref_sub scsi_target_reap_ref_release scsi_target_destroy ->target_destroy() = virtscsi_target_destroy kfree(tgt) <=== FREE TGT Note that the removal of the call to bdi_unregister in commit xenial be2a20802abbde block: Move bdi_unregister() to del_gendisk() and annotated above is the change that gates whether the issue manifests or not. The other code change from be2a20802abbde has no effect on the race. CPU B: vring_interrupt virtscsi_complete_cmd scsi_mq_done (via ->scsi_done()) scsi_mq_done blk_mq_complete_request __blk_mq_complete_request [...] blk_end_sync_rq complete [ wake up the task from CPU A ] After waking the CPU A task, execution returns up the stack, and then calls atomic_dec(&tgt->reqs) in virtscsi_complete_cmd immediately after returning from the call to ->scsi_done. If the activity on CPU A after it is woken up (starting at __scsi_remove_device) finishes before CPU B can call atomic_dec() in virtscsi_complete_cmd, then the atomic_dec() will modify a free list pointer in the freed slab object that contained tgt. This causes the system to panic on a subsequent allocation from the per-cpu slab cache. The call path on CPU B is significantly shorter than that on CPU A after wakeup, so it is likely that an external event delays CPU B. This could be either an interrupt within the VM or scheduling delays for the virtual cpu process on the hypervisor. Whatever the delay is, it is not the root cause but merely the triggering event. The virtscsi race window described above exists in all kernels that have been checked (4.4 upstream LTS, Ubuntu 4.13 and 4.15, and current mainline as of this writing). However, none
[Group.of.nepali.translators] [Bug 1763687] Re: linux: 4.4.0-121.145 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-121.145 /xenial-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing 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/1763687 Title: linux: 4.4.0-121.145 -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: Fix Released 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: Fix Released Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1763688 (linux-lts-xenial) derivatives: bug 1763689 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true 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/1763687/+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 1745081] Re: Add support for Realtek WiFi device [10ec:b822]
** Changed in: hwe-next 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/1745081 Title: Add support for Realtek WiFi device [10ec:b822] Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Fix Released Bug description: 05:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:b822] Subsystem: Lenovo Device [17aa:b023] Flags: fast devsel, IRQ 255 I/O ports at c000 [disabled] [size=256] Memory at f200 (64-bit, non-prefetchable) [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Device Serial Number 00-e0-4c-ff-fe-b8-22-01 Capabilities: [158] Latency Tolerance Reporting Capabilities: [160] L1 PM Substates To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1745081/+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
