[Kernel-packages] [Bug 1853807] [NEW] clock_gettime and time are inconsistent with each other
Public bug reported: When I compile and run the attached program, the output shows an inconsistency between the time returned by clock_gettime() and time(). Even though the call to time() is after the call to clock_gettime(), it can return an earlier timestamp. This is particularly apparent after waiting until a particular time, as shown in the example code. Sample output is: Now (clock_gettime) time is 1574670740847614452 (timespec) =>1574670740(time_t) =>8:32:20 Now (time(nullptr)) time is 1574670740(time_t) =>8:32:20 Now (clock_gettime) time is 1574670742000185727 (timespec) =>1574670742(time_t) =>8:32:22 Now (time(nullptr)) time is 1574670741(time_t) =>8:32:21 Compiled with g++ v7 from the ubuntu repositories. Output of g++ version: g++ (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1064-oem 4.15.0-1064.73 ProcVersionSignature: Ubuntu 4.15.0-1064.73-oem 4.15.18 Uname: Linux 4.15.0-1064-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 08:28:21 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-turtlebay+X57 InstallationDate: Installed on 2019-08-12 (104 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "File showing inconsistency" https://bugs.launchpad.net/bugs/1853807/+attachment/5307635/+files/t2.cpp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1853807 Title: clock_gettime and time are inconsistent with each other Status in linux-signed-oem package in Ubuntu: New Bug description: When I compile and run the attached program, the output shows an inconsistency between the time returned by clock_gettime() and time(). Even though the call to time() is after the call to clock_gettime(), it can return an earlier timestamp. This is particularly apparent after waiting until a particular time, as shown in the example code. Sample output is: Now (clock_gettime) time is 1574670740847614452 (timespec) =>1574670740(time_t) =>8:32:20 Now (time(nullptr)) time is 1574670740(time_t) =>8:32:20 Now (clock_gettime) time is 1574670742000185727 (timespec) =>1574670742(time_t) =>8:32:22 Now (time(nullptr)) time is 1574670741(time_t) =>8:32:21 Compiled with g++ v7 from the ubuntu repositories. Output of g++ version: g++ (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1064-oem 4.15.0-1064.73 ProcVersionSignature: Ubuntu 4.15.0-1064.73-oem 4.15.18 Uname: Linux 4.15.0-1064-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 08:28:21 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-turtlebay+X57 InstallationDate: Installed on 2019-08-12 (104 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem/+bug/1853807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853807] Re: clock_gettime and time are inconsistent with each other
This bug also occurs on Fedora. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1853807 Title: clock_gettime and time are inconsistent with each other Status in linux-signed-oem package in Ubuntu: New Bug description: When I compile and run the attached program, the output shows an inconsistency between the time returned by clock_gettime() and time(). Even though the call to time() is after the call to clock_gettime(), it can return an earlier timestamp. This is particularly apparent after waiting until a particular time, as shown in the example code. Sample output is: Now (clock_gettime) time is 1574670740847614452 (timespec) =>1574670740(time_t) =>8:32:20 Now (time(nullptr)) time is 1574670740(time_t) =>8:32:20 Now (clock_gettime) time is 1574670742000185727 (timespec) =>1574670742(time_t) =>8:32:22 Now (time(nullptr)) time is 1574670741(time_t) =>8:32:21 Compiled with g++ v7 from the ubuntu repositories. Output of g++ version: g++ (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1064-oem 4.15.0-1064.73 ProcVersionSignature: Ubuntu 4.15.0-1064.73-oem 4.15.18 Uname: Linux 4.15.0-1064-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 25 08:28:21 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-turtlebay+X57 InstallationDate: Installed on 2019-08-12 (104 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem/+bug/1853807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852239] Re: disco/linux-azure: 5.0.0-1026.28 -proposed tracker
5.0.0-1026.28 - azure Regression test CMPL, RTB. Issue to note in x86_64 (azure): ubuntu_kernel_selftests - cpu-hotplug (bug 1814232) test_bpf in net (bug 1812189) msg_zerocopy in net (bug 1812620) trace_printk in ftrace (bug 1830084) ubuntu_kvm_unit_tests - ept (bug 1824228) vmx (bug 1821394) ubuntu_ltp - proc01 (bug 1829849) binfmt_misc02 (bug 1822246) cpuset_hotplug (bug 1834006) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_subgroup_charge (bug 1847982) memcg_usage_in_bytes (bug 1829984) memcg_use_hierarchy (bug 1829989) cpuhotplug02 (bug 1836166) cpuhotplug03 (bug 1836167) cpuhotplug04 (bug 1836169) cpuhotplug06 (bug 1836170) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ubuntu_ltp_syscalls - move_pages12 (bug 1831043) ubuntu_lttng_smoke_test - module build issue on Standard_B1ms (bug 1847989) ubuntu_lxc - lxc-test-no-new-privs (failed to fetch package) on Standard_B1ms, Standard_DC2s, Standard_F1s, Standard_F2s (bug 1821152), passed on the rest ubuntu_qrt_apparmor - timed out on Standard-B1ms only Skipped / blacklisted: * libhugetlbfs ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => 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 Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1852239 Title: disco/linux-azure: 5.0.0-1026.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: 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: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 14. November 2019 22:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1852238 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852239] Re: disco/linux-azure: 5.0.0-1026.28 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 14. November 2019 22:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1852238 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1852239 Title: disco/linux-azure: 5.0.0-1026.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: 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: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Thursday, 14. November 2019 22:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1852238 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853326] Re: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
** Description changed: [Impact] 4.15.0-71-generic can not boot on ThunderX Here are console logs - https://pastebin.ubuntu.com/p/vN2c3CFVXR/ + https://pastebin.ubuntu.com/p/xcRk7VRrzF/ https://pastebin.ubuntu.com/p/DkdBqbBqqD/ [Test Case] Boot kernel with earlycon. See if kernel oops while booting. [Regression Risk] TBD -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853326 Title: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [Impact] 4.15.0-71-generic can not boot on ThunderX Here are console logs https://pastebin.ubuntu.com/p/xcRk7VRrzF/ https://pastebin.ubuntu.com/p/DkdBqbBqqD/ [Test Case] Boot kernel with earlycon. See if kernel oops while booting. [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853762] Re: Headphones stop working until pairing again
Thank you for your bug report. Once it refuses to work, can you try to connect to the headphones using bluetoothctl, what error does it give? (assuming that you normally try from the Desktop UI?) Could you also add your journal log after a failed connect try and indicate the time where you tried? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1853762 Title: Headphones stop working until pairing again Status in bluez package in Ubuntu: New Bug description: I'm using Marshall MID ANC headphones with Ubuntu 19.10. Every now and then, I won't be able to use them without re-pairing first (like today - see logs). After re-pairing, everything works again for a while : I can switch off and on the headphones, reboot... Until it breaks again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 24 19:13:40 2019 InstallationDate: Installed on 2018-07-28 (483 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:AB:C5:7E:41:26 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:319948 acl:71 sco:0 events:45583 errors:0 TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853647] [NEW] wireless is hard blocked after suspend, hardware switch has no effect
You have been subscribed to a public bug: When my laptop suspends automatically or through closing the lid, upon resuming, the wireless (wifi + bluetooth) device is reported as hard blocked. My laptops hardware switch has no effect on the reported status. the hardware is an 'Intel Wireless-AC 9560' module. The network- manager GUI options also have no effect. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 22 14:09:48 2019 InstallationDate: Installed on 2019-10-26 (27 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.25 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- wireless is hard blocked after suspend, hardware switch has no effect https://bugs.launchpad.net/bugs/1853647 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853647] Re: wireless is hard blocked after suspend, hardware switch has no effect
** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853647 Title: wireless is hard blocked after suspend, hardware switch has no effect Status in linux package in Ubuntu: New Bug description: When my laptop suspends automatically or through closing the lid, upon resuming, the wireless (wifi + bluetooth) device is reported as hard blocked. My laptops hardware switch has no effect on the reported status. the hardware is an 'Intel Wireless-AC 9560' module. The network-manager GUI options also have no effect. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 22 14:09:48 2019 InstallationDate: Installed on 2019-10-26 (27 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.25 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852244] Re: disco/linux-gcp: 5.0.0-1026.27 -proposed tracker
5.0.0-1026.27 - gcp Regression test CMPL, RTB. Issue to note in gcp: ubuntu_k8s_unit_tests - scheduler and spdy (bug 1824136) ubuntu_kernel_selftests - test_bpf in net (bug 1812189) msg_zerocopy in net (bug 1812620) trace_printk in ftrace (bug 1830084) ubuntu_ltp - test timeouted with 4 hours threshold on jenkins (bug 1837206) ubuntu_ltp_syscalls - clock_settime01 (bug 1850741) msgstress03 (bug 1797341) pivot_root01 (bug 1852966) settimeofday01 (bug 1833905) stime01 (bug 1845620) Skipped / blacklisted: * libhugetlbfs ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => 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 Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1852244 Title: disco/linux-gcp: 5.0.0-1026.27 -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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852253 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1852241 bionic/linux-gke-5.0: bug 1852243 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853721] Re: Possible cause for 19.10 invisible cursor with Matrox graphics
I can confirm that this issue is resolved in 5.4.0. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853721 Title: Possible cause for 19.10 invisible cursor with Matrox graphics Status in linux package in Ubuntu: Confirmed Bug description: BUG: Invisible Cursor with Ubuntu 19.10 Desktop Upgrade and Install CD Boot This bug was reported here: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1851340 WHAT OCCURRED: Upgrade from Ubuntu 19.04 to 19.10 results in having invisible cursor on main Gnome Desktop Subsequent testing revealed that issues is able to be demonstrated by just booting from Live iso image B) Attempt Fresh 19.10 Desktop Install B.1) Boot - Ubuntu 19.10 Desktop CD-ROM image via USB - Mouse / Cursor not visible So I have unable to proceed with clean 19.10 install as there was no mouse cursor visible. WHAT WAS EXPECTD: Gnome Desktop with working cursor POSSIBLE ROOT CAUSE: Investigation has identified pull request for 5.3 Kernel that includes fix for cursor issue with MatroX Graphics: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=574cc4539762561d96b456dbc0544d8898bd4c6e See: mgag200: - cursor support fix So issue possibly resolved with kernel update, as have two cases reported with Matrox G200 embedd graphics controllers. Raising here so that can be verified and tested by Ubuntu Kernel team. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 MachineType: LENOVO System x3650 M5 -[8871AC1]- NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=622f4924-1ed5-41a8-8a55-8ca455583434 ro ipv6.disable=1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (21 days ago) UserGroups: adm cdrom dip libvirt lxd plugdev sudo _MarkForUpload: True dmi.bios.date: 06/03/2019 dmi.bios.vendor: LENOVO dmi.bios.version: -[TCE140H-2.91]- dmi.board.asset.tag: (none) dmi.board.name: 01KN179 dmi.board.vendor: LENOVO dmi.board.version: NULL dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: LENOVO dmi.chassis.version: none dmi.modalias: dmi:bvnLENOVO:bvr-[TCE140H-2.91]-:bd06/03/2019:svnLENOVO:pnSystemx3650M5-[8871AC1]-:pvr13:rvnLENOVO:rn01KN179:rvrNULL:cvnLENOVO:ct23:cvrnone: dmi.product.family: System X dmi.product.name: System x3650 M5 -[8871AC1]- dmi.product.sku: (none) dmi.product.version: 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852244] Re: disco/linux-gcp: 5.0.0-1026.27 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852253 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1852241 bionic/linux-gke-5.0: bug 1852243 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1852244 Title: disco/linux-gcp: 5.0.0-1026.27 -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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852253 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp: bug 1852241 bionic/linux-gke-5.0: bug 1852243 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767568] Re: Console DPMS is not enabled by default in Ubuntu Server 18.04
> I understand that the original reporter said that he got it working with setterm, but as by convention these bug reports often require verification from others in order to get any attention, it seems only reasonable that after many have said that the DPMS power saving is what is not working, while simple blanking and leaving the monitor on is what is currently happening, that this bug should not have been marked invalid. I disagree. The reporter accidentally conflated DPMS with the intentional screen blanking change we made. This muddles every subsequent comment. As the reporter said that the problem was resolved, clearly it is the bug subject that was mistaken. The bug status is correct for the original problem the reporter had intended to report. If instead you think the reporter thought they were reporting was actually something else, and the bug subject was correct, then I guess that's self-consistent and you're entitled to think that, but this is only going to lead to further confusion. I suggest you file a separate bug if you think that there is a bug in DPMS. Please make sure to use an appropriate bug subject and a clear explanation in the bug description (steps to reproduce, expected behaviour, actual behaviour, etc) and then hopefully there will be clarity on exactly what you are reporting and then the community can determine the correct status of your issue as any outcome emerges. ** Summary changed: - Console DPMS is not enabled by default in Ubuntu Server 18.04 + Console blanking is not enabled by default in Ubuntu Server 18.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767568 Title: Console blanking is not enabled by default in Ubuntu Server 18.04 Status in linux package in Ubuntu: Invalid Bug description: My console display is DPMS capable, i.e., power management functions worked before upgrading from Ubuntu Server 16.0.4.4. Currently the display stays on 24x7 with idle keyboard input. 1) My release information is as follows: Description:Ubuntu 18.04 LTS Release:18.04 2) I am not sure what package this issue is tied to. The current kernel appears to have DPMS support enabled, per the configuration file in /boot. If the kernel is responsible, below is the version I am running. linux-generic: Installed: 4.15.0.20.23 3) I expected to have DPMS support for my console as in the previous release of Ubuntu Server. 4) What happened instead is my monitor stays on all the time, without DPMS controlling it. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-20-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D3', '/dev/snd/hwC1D2', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ab9de6b4-cca0-4e5c-89d7-e706214c8f11 InstallationDate: Installed on 2014-07-23 (1378 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Gigabyte Technology Co., Ltd. X58A-UD5 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=5631d3aa-8dce-4306-a08d-4ab3753256ab ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic apport-hook-error Uname: Linux 4.15.0-20-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to bionic on 2018-04-26 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 03/11/2010 dmi.bios.vendor: A
[Kernel-packages] [Bug 1853647] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1853647 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853647 Title: wireless is hard blocked after suspend, hardware switch has no effect Status in linux package in Ubuntu: Incomplete Bug description: When my laptop suspends automatically or through closing the lid, upon resuming, the wireless (wifi + bluetooth) device is reported as hard blocked. My laptops hardware switch has no effect on the reported status. the hardware is an 'Intel Wireless-AC 9560' module. The network-manager GUI options also have no effect. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-lowlatency 5.3.10 Uname: Linux 5.3.0-24-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 22 14:09:48 2019 InstallationDate: Installed on 2019-10-26 (27 days ago) InstallationMedia: Ubuntu-Studio 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.25 metric 600 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
Here's the change that was made: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/zesty/commit/?id=a87ae50beda8c46c543b39e19070549cf355eb65 It's just the default of the consoleblank= kernel parameter. You can override it by specifying that parameter to the kernel at boot time (eg. via /etc/default/grub) If someone could test and document exact steps to do this override in this bug please, that'd be useful to users and I'd appreciate it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kbd source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Status in kbd package in Debian: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853701] Re: thermald not works on intel GeminiLake
just verified this case on intel glk , platform pci subsystem ID = 08AF with 2 ways to heating CPU: - $ stress -c 20 - $ sudo stress-ng --ignite-cpu --cpu 4 with thermald 1.7.0-5ubuntu5 + kernel 4.15.0-1065-oem , the thermald looks work well and the system was not shut down by overheating. refer to the attached log from thermald with `--loglevel=debug`. by monitoring sensors in /sys/class/thermal/, the temperature is keep closing to critical (95 degree), but thermald will always cool it on time. So, I will mark this issue as invalid. ** Attachment added: "thermal.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853701/+attachment/5307654/+files/thermal.log ** Changed in: oem-priority Status: New => Invalid ** Changed in: oem-priority/bionic Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853701 Title: thermald not works on intel GeminiLake Status in OEM Priority Project: Invalid Status in OEM Priority Project bionic series: Invalid Status in linux package in Ubuntu: Incomplete Bug description: After the patch landed by "LP: #1851506 Add GeminiLake support on Intel int340x thermal device" The thermal zone "TCPU" is corretly created, but thermald still not work as expected on bionic so system will shutdown by cpu stress test. But thermald 1.9 works well with patched kernel, so it might some patches needed for thermald 1.7 on bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1853701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853592] Re: hw-tc-offload not reliable with VXLAN
This may be related to bug 1851819 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853592 Title: hw-tc-offload not reliable with VXLAN Status in linux package in Ubuntu: Confirmed Bug description: OpenStack Train OVS 2.12 Linux 5.3 from hwe edge Connect-X 5 running latest firmware from Mellanox. Overlay networking configured with VXLAN for project networking. Some instances successfully DHCP, some don't. For those that don't: compute: 11:51:24.926581 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 gateway: 11:50:44.010864 IP bond1.2925.node-laveran.maas.58901 > bond1.2925.node-lepaute.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from fa:16:3e:e8:59:f3 (oui Unknown), length 300 11:50:44.011196 IP bond1.2925.node-lepaute.maas.55067 > bond1.2925.node-laveran.maas.4789: VXLAN, flags [I] (0x08), vni 1233 IP 172.16.0.2.bootps > 172.16.2.236.bootpc: BOOTP/DHCP, Reply, length 328 The response is send from the gateway unit to the compute unit, but is never seen in the tcpdump. If hardware encap is disabled on the two underlying ports/the card, traffic flow is seen and all instances correctly DHCP configure on boot. sudo ethtool -K enp3s0f0 hw-tc-offload off sudo ethtool -K enp3s0f1 hw-tc-offload off ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-23-generic 5.3.0-23.25~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Fri Nov 22 12:29:20 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 19 16:45 seq crw-rw 1 root audio 116, 33 Nov 19 16:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R630 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=2ff5e234-ee62-4bce-8266-cd9aa78c532f ro intel_iommu=on iommu=pt probe_vf=0 ProcVersionSignature: Ubuntu 5.3.0-23.25~18.04.1-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.173.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/08/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.3.4 dmi.board.name: 02C2CP dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.3.4:bd11/08/2016:svnDellInc.:pnPowerEdgeR630:pvr:rvnDellInc.:rn02C2CP:rvrA03:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R630 dmi.product.sku: SKU=NotProvided;ModelName=PowerEdge R630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853050] Re: Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci)
Hmm, it was too early to celebrate, it seems. On subsequent reboots 5.4-rc8 still does not work. As a workaround, I have use an usb-tethered phone :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853050 Title: Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci) Status in linux package in Ubuntu: Confirmed Bug description: Wifi just fails to connect to an access point after upgrading from Ubuntu 19.04 to 19.10. Some outputs: uname -a Linux mothership 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lspci -nnk | grep 0280 -A3 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] Subsystem: AzureWave RTL8822BE 802.11a/b/g/n/ac WiFi adapter [1a3b:2950] Kernel driver in use: rtw_pci Kernel modules: rtwpci The typical failure looks like this in journalctl: Nov 18 23:04:13 mothership kernel: wlp3s0: send auth to d4:60:e3:15:4d:71 (try 3/3) Nov 18 23:04:13 mothership kernel: [ cut here ] Nov 18 23:04:13 mothership kernel: purge skb(s) not reported by firmware Nov 18 23:04:13 mothership kernel: WARNING: CPU: 5 PID: 0 at drivers/net/wireless/realtek/rtw88/tx.c:156 rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Nov 18 23:04:13 mothership kernel: Modules linked in: nf_conntrack_netlink xt_owner xt_conntrack xt_MASQUERADE nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_addrtype bpfilter aufs overlay binfmt_misc nvidia_uvm(O Nov 18 23:04:13 mothership kernel: spi_pxa2xx_platform videobuf2_memops asus_wmi videobuf2_v4l2 i915 mxm_wmi wmi_bmof sparse_keymap serio_raw videobuf2_common cfg80211 dw_dmac soundcore dw_dmac_core videodev input_leds drm_kms_helper joydev ipmi_devintf libarc4 mc ipmi_ Nov 18 23:04:13 mothership kernel: CPU: 5 PID: 0 Comm: swapper/5 Tainted: P W OE 5.3.0-23-generic #25-Ubuntu Nov 18 23:04:13 mothership kernel: Hardware name: ASUSTeK COMPUTER INC. X705UDR/X705UDR, BIOS X705UDR.300 08/29/2017 Nov 18 23:04:13 mothership kernel: RIP: 0010:rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Nov 18 23:04:13 mothership kernel: Code: 00 00 00 00 00 0f 1f 44 00 00 8b 47 f0 85 c0 75 01 c3 55 48 89 e5 41 55 41 54 53 48 89 fb 48 c7 c7 f0 cd b3 c0 e8 f6 fa 7b f6 <0f> 0b 4c 8d 6b d8 4c 89 ef e8 dd 3f 1c f7 48 8d 7b e0 49 89 c4 e8 Nov 18 23:04:13 mothership kernel: RSP: 0018:a25b4020ce48 EFLAGS: 00010286 Nov 18 23:04:13 mothership kernel: RAX: RBX: 913317bed848 RCX: 0006 Nov 18 23:04:13 mothership kernel: RDX: 0007 RSI: 0082 RDI: 91331eb57440 Nov 18 23:04:13 mothership kernel: RBP: a25b4020ce60 R08: 1754 R09: 0004 Nov 18 23:04:13 mothership kernel: R10: R11: 0001 R12: 91331eb5b600 Nov 18 23:04:13 mothership kernel: R13: 913317bed848 R14: c0adb7d0 R15: 913317bed848 Nov 18 23:04:13 mothership kernel: FS: () GS:91331eb4() knlGS: Nov 18 23:04:13 mothership kernel: CS: 0010 DS: ES: CR0: 80050033 Nov 18 23:04:13 mothership kernel: CR2: 7fb4eee0b000 CR3: 0003818bc005 CR4: 003606e0 Nov 18 23:04:13 mothership kernel: Call Trace: Nov 18 23:04:13 mothership kernel: Nov 18 23:04:13 mothership kernel: call_timer_fn+0x32/0x130 Nov 18 23:04:13 mothership kernel: __run_timers.part.0+0x177/0x270 Nov 18 23:04:13 mothership kernel: ? enqueue_hrtimer+0x3d/0x90 Nov 18 23:04:13 mothership kernel: ? recalibrate_cpu_khz+0x10/0x10 Nov 18 23:04:13 mothership kernel: ? ktime_get+0x42/0xa0 Nov 18 23:04:13 mothership kernel: run_timer_softirq+0x2a/0x50 Nov 18 23:04:13 mothership kernel: __do_softirq+0xe1/0x2d6 Nov 18 23:04:13 mothership kernel: ? hrtimer_interrupt+0x13b/0x220 Nov 18 23:04:13 mothership kernel: irq_exit+0xae/0xb0 Nov 18 23:04:13 mothership kernel: smp_apic_timer_interrupt+0x7b/0x140 Nov 18 23:04:13 mothership kernel: apic_timer_interrupt+0xf/0x20 Nov 18 23:04:13 mothership kernel: Nov 18 23:04:13 mothership kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x420 Nov 18 23:04:13 mothership kernel: Code: ff e8 5f 73 83 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 3d 03 00 00 31 ff e8 c2 ce 89 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 89 d1 01 00 00 41 c7 44 24 10 00 00 00 00 48 83 c4 18 Nov 18 23:04:13 mothership kernel: RSP: 0018:a25b400f3e38 EFLAGS: 0246 ORIG_RAX: ff13 Nov 18 23:04:13 mothership kernel: RAX: 91331eb6a740 RBX: b895a740 RCX: 001f Nov 18 23:04:13 mothership kernel: RDX: RSI: 4041ceb5 RDI: Nov 18 23:04:13 mothership kernel: RBP: fff
[Kernel-packages] [Bug 1852216] Re: Disable unreliable HPET on CFL-H system
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1852216 Title: Disable unreliable HPET on CFL-H system Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-oem source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Incomplete Status in linux-oem-osp1 source package in Disco: Invalid Status in linux source package in Eoan: Incomplete Status in linux-oem-osp1 source package in Eoan: Invalid Bug description: [Impact] TSC marked unstable by skewed HPET after Intel CFL-H SoC reached PC10 state. [Fix] Disable HPET on CFL-H SoC. [Test] I can confirm disabling HPET can workaround this issue. [Regression Potential] Low. TSC on recent Intel SoC is now an invariant clocksource, so it's harmless to disable HPET on these platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1852216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852386] Re: no HDMI video output since GDM greeter after linux-oem-osp1 version 5.0.0-1026
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852386 Title: no HDMI video output since GDM greeter after linux-oem-osp1 version 5.0.0-1026 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: In Progress Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: In Progress Status in linux-oem-osp1 source package in Focal: New Bug description: [SRU Justification: oem-osp1-bionic] [Impact] Bug 1849278 introduced a regression on some Comet Lake platforms that device may have no video output on HDMI port. [Fix] A currently in-review patch https://patchwork.freedesktop.org/patch/340416 should be applied to correct PCH's identity and restore HDMI output. [Test Case] 1. Apply the patches to oem-osp1 kernel >= 1026 or Eoan/Focal generic kernels. 2. Boot affected platforms with HDMI cable connected to an external monitor. 3. Check if the monitor lights up when GDM service is started. This was verified in to victim platforms. [Regression Risk] Low. This should affects only systems with matching PCH hw that is currently affected by the regression to be fixed. == [SRU Justification: E/F/U] [Impact] Some Comet Lake platforms got i915 call trace dump due to the lake of support to its PCH id: [2.999233] [ cut here ] [2.999238] eDP powered off while attempting aux channel communication. [2.999338] WARNING: CPU: 2 PID: 296 at drivers/gpu/drm/i915/display/intel_dp.c:1148 intel_dp_aux_xfer+0x767/0x900 [i915] [2.999341] Modules linked in: i915(+) i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm r8169 ahci realtek libahci wmi video [2.999350] CPU: 2 PID: 296 Comm: systemd-udevd Not tainted 5.3.0-997-generic #201910072204 [2.999352] Hardware name: Dell Inc. OptiPlex 3280 AIO/, BIOS 99.00.08 10/01/2019 [2.999391] RIP: 0010:intel_dp_aux_xfer+0x767/0x900 [i915] [2.999394] Code: e8 ee b5 ff ff 84 c0 0f 85 ec f9 ff ff 48 8b 7d 80 e8 5d b6 ff ff 84 c0 0f 85 db f9 ff ff 48 c7 c7 50 22 5d c0 e8 84 ea b5 d1 <0f> 0b 48 8b 7d 80 48 8d 75 90 4c 8d ab a8 07 00 00 e8 63 b4 ff ff [2.999398] RSP: 0018:b740b5b8 EFLAGS: 00010286 [2.999400] RAX: RBX: 9bfa9dc2 RCX: 0396 [2.999402] RDX: 0001 RSI: 0082 RDI: 0246 [2.999404] RBP: b740b698 R08: 0396 R09: 0019 [2.999406] R10: 072e R11: b740b420 R12: 0004 [2.999408] R13: 9bfa9fbca120 R14: 9bfa9dc2 R15: 9bfa9dc207a8 [2.999410] FS: 7f0d8613a680() GS:9bfaaec8() knlGS: [2.999412] CS: 0010 DS: ES: CR0: 80050033 [2.999414] CR2: 7ffca955ae58 CR3: 00041e67e002 CR4: 003606e0 [2.999416] DR0: DR1: DR2: [2.999418] DR3: DR6: fffe0ff0 DR7: 0400 [2.999420] Call Trace: [2.999425] ? vprintk_default+0x29/0x50 [2.999464] intel_dp_aux_transfer+0x15e/0x220 [i915] [2.999472] drm_dp_dpcd_access+0x72/0x110 [drm_kms_helper] [2.999478] drm_dp_dpcd_read+0x33/0xc0 [drm_kms_helper] [2.999515] intel_dp_read_dpcd+0x41/0x130 [i915] [2.999551] intel_edp_init_connector+0x136/0x540 [i915] [2.999587] intel_dp_init_connector+0x47f/0x870 [i915] [2.999623] intel_ddi_init+0x425/0x590 [i915] [2.999660] intel_setup_outputs+0x8e4/0xc60 [i915] [Fix] Two patches to be backported to have correct support: * commit 37c92dc303dd "drm/i915: Add new CNL PCH ID seen on a CML platform" from drm-tip tree. * patch "https://patchwork.freedesktop.org/patc
[Kernel-packages] [Bug 1813877] Re: Can't adjust brightness on DELL UHD dGPU AIO
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1813877 Title: Can't adjust brightness on DELL UHD dGPU AIO Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [Impact] The dell-uart-backlight driver has been loaded, but the backlight is controller by graphics driver instead of scalar IC. The old way to determinate weather the driver should be loaded is not working anymore, since the behavior of scalar command, show firmware version, is not the same as old platforms. [Fix] Using more a reliable command, get_scalar_status, to check if scalar is in charge of the AIO backlight. For the old platforms which don't have the new command, I add a list to list them all and use the old way to determinate the scalar IC. [Test] Verified on old and new Dell AIO platforms. [Regression Potential] Low. The quirk lists all old platforms which use the old way to check if scalar IC is in use. So, it won't change the behavior on old platforms, and apply the new method on new platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1813877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846335] Re: [CML] New device id's for CMP-H
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846335 Title: [CML] New device id's for CMP-H Status in HWE Next: New Status in intel: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: In Progress Status in linux-oem-osp1 source package in Disco: New Status in linux source package in Eoan: In Progress Status in linux-oem-osp1 source package in Eoan: New Status in linux source package in Focal: In Progress Status in linux-oem-osp1 source package in Focal: New Bug description: split from bug 1843774 Description This task is to identify what new device IDs are required for CML PCH-H. Controller Kernel Version Commit Approved to be published Comments USB device/xDCI 0x02ee v5.2 7ae622c978db6b2 I²C (CMP-H)|0x06c5 0x06c6 0x06e8 0x06e9 0x06ea 0x06eb https://lore.kernel.org/lkml/20191029094409.43741-1-andriy.shevche...@linux.intel.com/ HS-UART (CMP-H) 0x06a8 0x06a9 0x06c7 https://lore.kernel.org/lkml/20191029094409.43741-1-andriy.shevche...@linux.intel.com/ SPI (CMP-H) 0x06aa 0x06ab 0x06fb f0cf17ed76cf from spi.git https://lore.kernel.org/lkml/20191029094409.43741-1-andriy.shevche...@linux.intel.com/ SPI Flash Controller (CMP-H) 0x06a4 https://lore.kernel.org/linux- mtd/20191023145140.51427-1-mika.westerb...@linux.intel.com/ GPIO(CMP-H) INT3450 "It seems the same as for CNL, nothing needs to be done here. SD Card (CMP-H) 0x06f5 v5.4-rc1 8f05eee67c1404a SMBus (CMP-H) 0x06a3 v5.5 07f047e3fe33 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1846335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852070] Re: The alsa hda driver is not loaded due to the missing of PCIID for Comet Lake-S [8086:a3f0]
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852070 Title: The alsa hda driver is not loaded due to the missing of PCIID for Comet Lake-S [8086:a3f0] Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: New Status in linux-oem-osp1 source package in Disco: Invalid Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Invalid Bug description: [Impact] Intel Comet Lake-S platform has the sound controller with PCIID 0x8086:a3f0, the ID is not in the alsa hda driver yet. When we run the linux on the Comet Lake-S platform, the alsa hda driver will not be loaded. [Fix] Adding the PCIID into the alsa hda driver. [Test Case] We already tested this driver on a Dell Comet Lake-S machine with the codec RT274, all audio devices worked well. [Regression Risk] Low, adding a new PCIID, will not introduce regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1852070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852303] Re: xenial/linux-fips: 4.4.0-1026.31 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852303 Title: xenial/linux-fips: 4.4.0-1026.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852306 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Monday, 25. November 2019 12:31 UTC reason: promote-signing-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852216] Re: Disable unreliable HPET on CFL-H system
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1852216 Title: Disable unreliable HPET on CFL-H system Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-oem source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Incomplete Status in linux-oem-osp1 source package in Disco: Invalid Status in linux source package in Eoan: Incomplete Status in linux-oem-osp1 source package in Eoan: Invalid Bug description: [Impact] TSC marked unstable by skewed HPET after Intel CFL-H SoC reached PC10 state. [Fix] Disable HPET on CFL-H SoC. [Test] I can confirm disabling HPET can workaround this issue. [Regression Potential] Low. TSC on recent Intel SoC is now an invariant clocksource, so it's harmless to disable HPET on these platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1852216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852581] Re: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852581 Title: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO Status in linux package in Ubuntu: In Progress Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe-edge source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-hwe-edge source package in Eoan: Invalid Bug description: SRU Justification Impact: The fix for bug 1850234 does not function as intended in bionic, as a result of modinfo not knowing about module signatures. This results in no modules being signed in hwe kernels based on 5.3, rendering systems with secure boot enabled unbootable. Fix: Check for the module signature at the end of modules instead of relying on modinfo. This can be done without any external tools needing to be aware of module signatures. Test Case: Check that all built modules contain signatures, except for those in staging which have not been whitelisted. Regression Potential: I can think of two possible regression situations. We could regress to the behavior prior to the fix for bug 1850234, or the eoan 5.3 kernel could also end up with all modules unsigned. I've done test builds of both the eoan 5.3 kernel and the bionic 5.3 hwe-edge kernel with this patch and checked that the results are as intended. We should also check this again once new kernels have been built, before copying them out to -proposed. --- The latest hwe-edge kernel 5.3.0-23.25 fails to boot with the message that it cannot find the UUID associated with the root partition. The user gets dropped to a busybox shell with an initramfs prompt. The standard hwe kernel does not have this issue and the last hwe-edge kernel that does work is 5.3.0-19.20. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04-edge 5.3.0.23.90 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 14 08:19:57 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-09-01 (73 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847948] Re: Improve NVMe guest performance on Bionic QEMU
I found no obvious regressions with this build in a run of our usual set of tests. @IBM - for SRu verification - can you give the actual testcase it was intended for a shot in your environment as you had that set up int he past? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847948 Title: Improve NVMe guest performance on Bionic QEMU Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in qemu source package in Bionic: Fix Committed Bug description: [Impact] * In the past qemu has generally not allowd MSI-X BAR mapping on VFIO. But there can be platforms (like ppc64 spapr) that can and want to do exactly that. * Backport two patches from upstream (in since qemu 2.12 / Disco). * Due to that there is a tremendous speedup, especially useful with page size bigger than 4k. This avoids that being split into chunks and makes direct MMIO access possible for the guest. [Test Case] * On ppc64 pass through an NVME device to the guest and run I/O benchmarks, see below for Details how to set that up. Note: this needs the HWE kernel or another kernel fixup for [1]. Note: the test should also be done with the non-HWE kernel, the expectation there is that it would not show the perf benefits, but still work fine [Regression Potential] * Changes: a) if the host driver allows mapping of MSI-X data the entire BAR is mapped. This is only done if the kernel reports that capability [1]. This ensures that only on kernels able to do so qemu does expose the new behavior (safe against regression in that regard) b) on ppc64 MSI-X emulation is disabled for VFIO devices this is local to just this HW and will not affect other HW. Generally the regressions that come to mind are slight changes in behavior (real HW vs the former emulation) that on some weird/old guests could cause trouble. But then it is limited to only PPC where only a small set of certified HW is really allowed. The mapping that might be added even on other platforms should not consume too much extra memory as long as it isn't used. Further since it depends on the kernel capability it isn't randomly issues on kernels where we expect it to fail. So while it is quite a change, it seems safe to me. [Other Info] * I know, one could as well call that a "feature", but it really is a performance bug fix more than anything else. Also the SRU policy allows exploitation/toleration of new HW especially for LTS releases. Therefore I think this is fine as SRU. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a32295c612c57990d17fb0f41e7134394b2f35f6 == Comment: #0 - Murilo Opsfelder Araujo - 2019-10-11 14:16:14 == ---Problem Description--- Back-port the following patches to Bionic QEMU to improve NVMe guest performance by more than 200%: ?vfio-pci: Allow mmap of MSIX BAR? https://git.qemu.org/?p=qemu.git;a=commit;h=ae0215b2bb56a9d5321a185dde133bfdd306a4c0 ?ppc/spapr, vfio: Turn off MSIX emulation for VFIO devices? https://git.qemu.org/?p=qemu.git;a=commit;h=fcad0d2121976df4b422b4007a5eb7fcaac01134 ---uname output--- na ---Additional Hardware Info--- 0030:01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 172Xa/172Xb (rev 01) Machine Type = AC922 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install or setup a guest image and boot it. Once guest is running, passthrough the NVMe disk to the guest using the XML: host$ cat nvme-disk.xml host$ virsh attach-device nvme-disk.xml --live On the guest, run fio benchmarks: guest$ fio --direct=1 --rw=randrw --refill_buffers --norandommap --randrepeat=0 --ioengine=libaio --bs=4k --rwmixread=100 --iodepth=16 --runtime=60 --name=job1 --filename=/dev/nvme0n1 --numjobs=4 Results are similar with numjobs=4 and numjobs=64, respectively: READ: bw=385MiB/s (404MB/s), 78.0MiB/s-115MiB/s (81.8MB/s-120MB/s), io=11.3GiB (12.1GB), run=30001-30001msec READ: bw=382MiB/s (400MB/s), 2684KiB/s-12.6MiB/s (2749kB/s-13.2MB/s), io=11.2GiB (12.0GB), run=30001-30009msec With the two patches applied, performance improved significantly for numjobs=4 and numjobs=64 cases, respectively: READ: bw=1191MiB/s (1249MB/s), 285MiB/s-309MiB/s (299MB/s-324MB/s), io=34.9GiB (37.5GB), run=30001-30001msec READ: bw=4273MiB/s (4481MB/s), 49.7MiB/s-113MiB/s (52.1MB/s-119MB/s), io=125GiB (134GB), run=30001-30005msec Userspace tool common name: qemu Userspace rpm: qemu The userspace t
[Kernel-packages] [Bug 1852303] Re: xenial/linux-fips: 4.4.0-1026.31 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852306 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Ready for Promote to Proposed - phase-changed: Friday, 22. November 2019 19:02 UTC + phase: Promote to Proposed + phase-changed: Monday, 25. November 2019 12:31 UTC reason: - promote-signing-to-proposed: Stalled -- ready for review + promote-signing-to-proposed: Stalled -- review in progress variant: debs ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852306 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Promote to Proposed - phase-changed: Monday, 25. November 2019 12:31 UTC + phase: Testing + phase-changed: Monday, 25. November 2019 12:37 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Stalled -- review in progress + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852303 Title: xenial/linux-fips: 4.4.0-1026.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852306 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Monday, 25. November 2019 12:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852303/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1852282 Title: xenial/linux-azure: 4.15.0-1064.69 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852289 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 25. November 2019 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852281] Re: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 20. November 2019 18:24 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 25. November 2019 12:38 UTC reason: - promote-signing-to-proposed: Holding -- master bug not ready for proposed + promote-signing-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1852281 Title: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Monday, 25. November 2019 12:38 UTC reason: promote-signing-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852289 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Promote to Proposed - phase-changed: Wednesday, 20. November 2019 08:01 UTC + phase: Testing + phase-changed: Monday, 25. November 2019 12:36 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Stalled -- copy FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1852282 Title: xenial/linux-azure: 4.15.0-1064.69 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852289 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 25. November 2019 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852406] Re: Double-escape in initramfs DECRYPT_CMD
@Witold, is it possible for you to sanity check this, if it's not
verified it won't be fixed.
thanks
Colin
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852406
Title:
Double-escape in initramfs DECRYPT_CMD
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Eoan:
Fix Committed
Status in zfs-linux source package in Focal:
Fix Released
Bug description:
== SRU Justification, Eoan ==
initramfs/scripts/zfs.in incorrectly quotes ${ENCRYPTIONROOT} on line
414:
DECRYPT_CMD="${ZFS} load-key '${ENCRYPTIONROOT}'"
This is OK when the line is executed by shell, such as in line 430 or
436, but when plymouth is used it results in plymouth executing "zfs
load-key 'rpool'" - and zfs is unable to find pool called "'rpool'".
If I understand
https://docs.oracle.com/cd/E23824_01/html/821-1448/gbcpt.html
correctly zfs pool name is always 'shell-friendly', so removing the
quotation marks would be a proper fix for that.
== Fix ==
One line fix as attached in https://bugs.launchpad.net/ubuntu/+source
/zfs-linux/+bug/1852406/comments/1
== Test ==
Boot with encrypted data set with plymouth. Without the fix zfs is
unable to find the root encrypted pool. With the fix this works.
== Regression Potential ==
This just affects the encrypted dataset that holds key for root
dataset; currently this is causing issues because of the bug, so the
risk of the fix outweighs the current situation where this is
currently broken.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1852406/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852281] Re: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1852281 Title: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 25. November 2019 12:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852281] Re: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/regression-testing 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/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Promote to Proposed - phase-changed: Monday, 25. November 2019 12:38 UTC + phase: Testing + phase-changed: Monday, 25. November 2019 12:51 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Pending -- ready for review + regression-testing: Ongoing -- testing in progress + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1852281 Title: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 25. November 2019 12:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847389] Re: Prevent bpool (or pools with /BOOT/) to be upgraded
How exactly does it break booting? I did a zpool upgrade bpool on two machines (one VM and one laptop) before reading this warning. Both seems to boot just fine after the upgrade. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847389 Title: Prevent bpool (or pools with /BOOT/) to be upgraded Status in zfs-linux package in Ubuntu: New Bug description: The bpool status is confusing. Should I upgrade the pool or is it on purpose that the bpool is like this. I do no like to see this warning after installing the system on ZFS from scratch. See screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852581] Re: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO
** Tags removed: verification-needed-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852581 Title: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO Status in linux package in Ubuntu: In Progress Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe-edge source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-hwe-edge source package in Eoan: Invalid Bug description: SRU Justification Impact: The fix for bug 1850234 does not function as intended in bionic, as a result of modinfo not knowing about module signatures. This results in no modules being signed in hwe kernels based on 5.3, rendering systems with secure boot enabled unbootable. Fix: Check for the module signature at the end of modules instead of relying on modinfo. This can be done without any external tools needing to be aware of module signatures. Test Case: Check that all built modules contain signatures, except for those in staging which have not been whitelisted. Regression Potential: I can think of two possible regression situations. We could regress to the behavior prior to the fix for bug 1850234, or the eoan 5.3 kernel could also end up with all modules unsigned. I've done test builds of both the eoan 5.3 kernel and the bionic 5.3 hwe-edge kernel with this patch and checked that the results are as intended. We should also check this again once new kernels have been built, before copying them out to -proposed. --- The latest hwe-edge kernel 5.3.0-23.25 fails to boot with the message that it cannot find the UUID associated with the root partition. The user gets dropped to a busybox shell with an initramfs prompt. The standard hwe kernel does not have this issue and the last hwe-edge kernel that does work is 5.3.0-19.20. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04-edge 5.3.0.23.90 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 14 08:19:57 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-09-01 (73 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853843] [NEW] Kerne build log filled with "/bin/bash: line 5: warning: command substitution: ignored null byte in input"
You have been subscribed to a public bug: SRU Justification Impact: The fix for bug 1852581 causes the build log to be spammed with "/bin/bash: line 5: warning: command substitution: ignored null byte in input" each time an unsigned module is processed. Fix: Replace the fix with a different one which does not result in the message. Test Case: Build with debug package build enabled, and check for the message in the logs. Also confirm that the resulting modules are signed, aside from those in staging and not whitelisted in drivers/staging /signature-inclusion. Regression Potential: I've tested the patch for the above criteria, and all is working as expected, so this should not result in any regressions. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress -- Kerne build log filled with "/bin/bash: line 5: warning: command substitution: ignored null byte in input" https://bugs.launchpad.net/bugs/1853843 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853842] [NEW] Make Goodix I2C touchpads work
Public bug reported: [Impact] Goodix touchpads in general don't work well. Sometimes not working at all. [Fix] Remove runtime pm from HID over I2C driver. The power saving is little to none and causes many problems. [Test] After applying the fix, which removes runtime pm, the Goodix touchpad works like a charm. [Regression Potential] Low. This actually mimics behavior on Windows. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Affects: linux-oem-osp1 (Ubuntu Disco) Importance: Undecided Status: Won't Fix ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Affects: linux-oem-osp1 (Ubuntu Eoan) Importance: Undecided Status: Won't Fix ** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: linux-oem-osp1 (Ubuntu Disco) Status: New => Won't Fix ** Changed in: linux-oem-osp1 (Ubuntu Eoan) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853842 Title: Make Goodix I2C touchpads work Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: New Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Bug description: [Impact] Goodix touchpads in general don't work well. Sometimes not working at all. [Fix] Remove runtime pm from HID over I2C driver. The power saving is little to none and causes many problems. [Test] After applying the fix, which removes runtime pm, the Goodix touchpad works like a charm. [Regression Potential] Low. This actually mimics behavior on Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853843] [NEW] Kerne build log filled with "/bin/bash: line 5: warning: command substitution: ignored null byte in input"
Public bug reported: SRU Justification Impact: The fix for bug 1852581 causes the build log to be spammed with "/bin/bash: line 5: warning: command substitution: ignored null byte in input" each time an unsigned module is processed. Fix: Replace the fix with a different one which does not result in the message. Test Case: Build with debug package build enabled, and check for the message in the logs. Also confirm that the resulting modules are signed, aside from those in staging and not whitelisted in drivers/staging /signature-inclusion. Regression Potential: I've tested the patch for the above criteria, and all is working as expected, so this should not result in any regressions. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Package changed: linux-hwe-edge (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853843 Title: Kerne build log filled with "/bin/bash: line 5: warning: command substitution: ignored null byte in input" Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Bug description: SRU Justification Impact: The fix for bug 1852581 causes the build log to be spammed with "/bin/bash: line 5: warning: command substitution: ignored null byte in input" each time an unsigned module is processed. Fix: Replace the fix with a different one which does not result in the message. Test Case: Build with debug package build enabled, and check for the message in the logs. Also confirm that the resulting modules are signed, aside from those in staging and not whitelisted in drivers/staging/signature-inclusion. Regression Potential: I've tested the patch for the above criteria, and all is working as expected, so this should not result in any regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852070] Re: The alsa hda driver is not loaded due to the missing of PCIID for Comet Lake-S [8086:a3f0]
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852070 Title: The alsa hda driver is not loaded due to the missing of PCIID for Comet Lake-S [8086:a3f0] Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: New Status in linux-oem-osp1 source package in Disco: Invalid Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Invalid Bug description: [Impact] Intel Comet Lake-S platform has the sound controller with PCIID 0x8086:a3f0, the ID is not in the alsa hda driver yet. When we run the linux on the Comet Lake-S platform, the alsa hda driver will not be loaded. [Fix] Adding the PCIID into the alsa hda driver. [Test Case] We already tested this driver on a Dell Comet Lake-S machine with the codec RT274, all audio devices worked well. [Regression Risk] Low, adding a new PCIID, will not introduce regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1852070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847948] Comment bridged from LTC Bugzilla
--- Comment From mu...@br.ibm.com 2019-11-25 08:42 EDT--- (In reply to comment #24) > I found no obvious regressions with this build in a run of our usual set of > tests. > > @IBM - for SRu verification - can you give the actual testcase it was > intended for a shot in your environment as you had that set up int he past? Yeah, sure, I don't own the setup to do so, but I am trying to schedule some time in it to run the testcase. I'll get back with the results as soon as possible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847948 Title: Improve NVMe guest performance on Bionic QEMU Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in qemu source package in Bionic: Fix Committed Bug description: [Impact] * In the past qemu has generally not allowd MSI-X BAR mapping on VFIO. But there can be platforms (like ppc64 spapr) that can and want to do exactly that. * Backport two patches from upstream (in since qemu 2.12 / Disco). * Due to that there is a tremendous speedup, especially useful with page size bigger than 4k. This avoids that being split into chunks and makes direct MMIO access possible for the guest. [Test Case] * On ppc64 pass through an NVME device to the guest and run I/O benchmarks, see below for Details how to set that up. Note: this needs the HWE kernel or another kernel fixup for [1]. Note: the test should also be done with the non-HWE kernel, the expectation there is that it would not show the perf benefits, but still work fine [Regression Potential] * Changes: a) if the host driver allows mapping of MSI-X data the entire BAR is mapped. This is only done if the kernel reports that capability [1]. This ensures that only on kernels able to do so qemu does expose the new behavior (safe against regression in that regard) b) on ppc64 MSI-X emulation is disabled for VFIO devices this is local to just this HW and will not affect other HW. Generally the regressions that come to mind are slight changes in behavior (real HW vs the former emulation) that on some weird/old guests could cause trouble. But then it is limited to only PPC where only a small set of certified HW is really allowed. The mapping that might be added even on other platforms should not consume too much extra memory as long as it isn't used. Further since it depends on the kernel capability it isn't randomly issues on kernels where we expect it to fail. So while it is quite a change, it seems safe to me. [Other Info] * I know, one could as well call that a "feature", but it really is a performance bug fix more than anything else. Also the SRU policy allows exploitation/toleration of new HW especially for LTS releases. Therefore I think this is fine as SRU. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a32295c612c57990d17fb0f41e7134394b2f35f6 == Comment: #0 - Murilo Opsfelder Araujo - 2019-10-11 14:16:14 == ---Problem Description--- Back-port the following patches to Bionic QEMU to improve NVMe guest performance by more than 200%: ?vfio-pci: Allow mmap of MSIX BAR? https://git.qemu.org/?p=qemu.git;a=commit;h=ae0215b2bb56a9d5321a185dde133bfdd306a4c0 ?ppc/spapr, vfio: Turn off MSIX emulation for VFIO devices? https://git.qemu.org/?p=qemu.git;a=commit;h=fcad0d2121976df4b422b4007a5eb7fcaac01134 ---uname output--- na ---Additional Hardware Info--- 0030:01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller 172Xa/172Xb (rev 01) Machine Type = AC922 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install or setup a guest image and boot it. Once guest is running, passthrough the NVMe disk to the guest using the XML: host$ cat nvme-disk.xml host$ virsh attach-device nvme-disk.xml --live On the guest, run fio benchmarks: guest$ fio --direct=1 --rw=randrw --refill_buffers --norandommap --randrepeat=0 --ioengine=libaio --bs=4k --rwmixread=100 --iodepth=16 --runtime=60 --name=job1 --filename=/dev/nvme0n1 --numjobs=4 Results are similar with numjobs=4 and numjobs=64, respectively: READ: bw=385MiB/s (404MB/s), 78.0MiB/s-115MiB/s (81.8MB/s-120MB/s), io=11.3GiB (12.1GB), run=30001-30001msec READ: bw=382MiB/s (400MB/s), 2684KiB/s-12.6MiB/s (2749kB/s-13.2MB/s), io=11.2GiB (12.0GB), run=30001-30009msec With the two patches applied, performance improved significantly for numjobs=4 and numjobs=64 cases, respectively: READ: bw=1191MiB/s (1249MB/s), 285MiB/s
[Kernel-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) Status in linux package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Bug description: The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 60 and 50 GHz, if you switch to any other than 75, the flickering will disappear until the display turns off. After switching on, flicker returns. At the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is not visible. More in the video https://www.youtube.com/watch?v=d_LXHqWKTbk ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:13:19 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1043:0519] InstallationDate: Installed on 2019-01-22 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: MSI MS-7693 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-G43 (MS-7693) dmi.board.vendor: MSI dmi.board.version: 3.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7693 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853694] [NEW] Ubuntu causing eye strain on Intel Integrated Graphics
You have been subscribed to a public bug: I find when running Ubuntu after 5-10 minutes get heavy eyes and after a few hours develop dizziness/headaches. After research online and talking with a community at LED Strain (https://ledstrain.org) it is believed the issue is caused by dithering being enabled on Ubuntu. There is no known way turn off all dithering by default and would like an option to turn off all dithering to avoid discomfort. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-36-generic 5.0.0-36.39~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 23 12:56:12 2019 InstallationDate: Installed on 2019-11-22 (1 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic -- Ubuntu causing eye strain on Intel Integrated Graphics https://bugs.launchpad.net/bugs/1853694 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847389] Re: Prevent bpool (or pools with /BOOT/) to be upgraded
Well the people involved in the design and maintenance Richard Laager and Didier Roche warned me NOT to upgrade, so I did not upgrade the pool. My bug was about the confusions caused by that message. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847389 Title: Prevent bpool (or pools with /BOOT/) to be upgraded Status in zfs-linux package in Ubuntu: New Bug description: The bpool status is confusing. Should I upgrade the pool or is it on purpose that the bpool is like this. I do no like to see this warning after installing the system on ZFS from scratch. See screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853694] Re: Ubuntu causing eye strain on Intel Integrated Graphics
Ubuntu uses 24bit color palette by default, so I bet it's not dithering you see.. Maybe you mean the screen is flickering? ** Package changed: linux-signed-hwe (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853694 Title: Ubuntu causing eye strain on Intel Integrated Graphics Status in linux package in Ubuntu: Incomplete Bug description: I find when running Ubuntu after 5-10 minutes get heavy eyes and after a few hours develop dizziness/headaches. After research online and talking with a community at LED Strain (https://ledstrain.org) it is believed the issue is caused by dithering being enabled on Ubuntu. There is no known way turn off all dithering by default and would like an option to turn off all dithering to avoid discomfort. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-36-generic 5.0.0-36.39~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 23 12:56:12 2019 InstallationDate: Installed on 2019-11-22 (1 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853842] Re: Make Goodix I2C touchpads work
** Tags added: oem-priority originate-from-1853404 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853842 Title: Make Goodix I2C touchpads work Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Disco: New Status in linux-oem-osp1 source package in Disco: Won't Fix Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Bug description: [Impact] Goodix touchpads in general don't work well. Sometimes not working at all. [Fix] Remove runtime pm from HID over I2C driver. The power saving is little to none and causes many problems. [Test] After applying the fix, which removes runtime pm, the Goodix touchpad works like a charm. [Regression Potential] Low. This actually mimics behavior on Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1853842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1572132] Re: SMBv2+ does not show all files when mounting a windows share
same problem: ls -al 516.p*- > file or dir not found
BUT ls -al 516.pdf->then file is shown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1572132
Title:
SMBv2+ does not show all files when mounting a windows share
Status in Linux:
Unknown
Status in Release Notes for Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux package in Debian:
Confirmed
Bug description:
When using the SMBv2 Protocol to mount a top level windows share (such
as C:\) not all files (or directories) are shown that exist on the
server side. Exactly 2 files are always missing...
Steps to reproduce:
On a windows7 PC (or Server) e.g. C:\ must be published as Share (must be top
level share - a subfolder like C:\data\ seems to work)
sudo mount -t cifs //SERVER/SHARE_NAME /mnt -o
domain=DOMAIN_NAME,username=${USER},uid=1000,gid=1000,nounix,vers=2.0
As a result always 2 Files (or directories) are missing in the mounted
directory of the ubuntu installation.
Seems to be a kernel bug (source tree: linux/fs/cifs).
The ubuntu versions I have checked:
Ubuntu 14.04LTS amd64
Ubuntu 15.10 amd64
Ubuntu 16.04 amd64
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.12
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Tue Apr 19 14:50:02 2016
InstallationDate: Installed on 2016-04-19 (0 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160417.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1572132/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852581] Re: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO
Hi Harm van Bakel, Can you please try the same version of the linux-hwe-edge (5.3.0-23.25~18.04.2) but installing it from the -proposed pocket? The build in the canonical-kernel-team ppa doesn't have the complete signing bits, so the binaries are not the same. Thank you. ** Tags removed: verification-failed-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852581 Title: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO Status in linux package in Ubuntu: In Progress Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe-edge source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-hwe-edge source package in Eoan: Invalid Bug description: SRU Justification Impact: The fix for bug 1850234 does not function as intended in bionic, as a result of modinfo not knowing about module signatures. This results in no modules being signed in hwe kernels based on 5.3, rendering systems with secure boot enabled unbootable. Fix: Check for the module signature at the end of modules instead of relying on modinfo. This can be done without any external tools needing to be aware of module signatures. Test Case: Check that all built modules contain signatures, except for those in staging which have not been whitelisted. Regression Potential: I can think of two possible regression situations. We could regress to the behavior prior to the fix for bug 1850234, or the eoan 5.3 kernel could also end up with all modules unsigned. I've done test builds of both the eoan 5.3 kernel and the bionic 5.3 hwe-edge kernel with this patch and checked that the results are as intended. We should also check this again once new kernels have been built, before copying them out to -proposed. --- The latest hwe-edge kernel 5.3.0-23.25 fails to boot with the message that it cannot find the UUID associated with the root partition. The user gets dropped to a busybox shell with an initramfs prompt. The standard hwe kernel does not have this issue and the last hwe-edge kernel that does work is 5.3.0-19.20. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04-edge 5.3.0.23.90 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 14 08:19:57 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-09-01 (73 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844493] Re: ubuntu_sysdig_smoke_test failed on Eoan
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Tags added: sru-2019 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1844493 Title: ubuntu_sysdig_smoke_test failed on Eoan Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux source package in Eoan: Incomplete Status in linux-aws source package in Eoan: New Status in linux-azure source package in Eoan: New Status in linux-gcp source package in Eoan: New Bug description: Test failed with: FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Steps: sudo apt-get install git python-minimal python-yaml gdb -y git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_sysdig_smoke_test/control Test output: == sysdig smoke test to trace dd, cat, read and writes == Limiting raw capture file to 16384 blocks Try 1 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 18 Mbytes Try 2 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 22 Mbytes Try 3 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 4 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 5 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 6 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 7 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 8 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 9 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Try 10 of 10 Sysdig capture started after 1 seconds wait Raw capture file is 16 Mbytes Converted events file is 21 Mbytes Found: 279845 sysdig events 29882 context switches 0 reads from /dev/zero by dd 0 writes to /dev/null by dd PASSED (trace at least 25 context switches) FAILED (trace at least 25 reads of /dev/zero by dd) FAILED (trace at least 25 writes to /dev/null by dd) Summary: 1 passed, 2 failed ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-10-generic 5.3.0-10.11 ProcVersionSignature: User Name 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 18 08:10 seq crw-rw 1 root audio 116, 33 Sep 18 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed Sep 18 08:18:54 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': '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:
[Kernel-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
** Changed in: ubuntu-kernel-tests Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Cosmic: Incomplete Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853485] Re: Bionic kernel panic on Cavium ThunderX CN88XX
** Tags added: lippmann ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853485 Title: Bionic kernel panic on Cavium ThunderX CN88XX Status in linux package in Ubuntu: Confirmed Bug description: Description: kernel panic while trying to deploy Bionic 18.04.3 Linux version 4.15.0-70-generic on Cavium ThunderX CN88XX (arm64) System: Board Model: gbt-mt30 Board name: MT30-GS0 System name:MT30-GS0 SKU: CN8890-2000BG2601-AAP-Y22-G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
The kernel issue pointed at the github was solved by:
commit cbaee3aa0e23
Author: Dan Williams
Date: Thu Feb 7 20:56:50 2019
acpi/nfit: Fix bus command validation
BugLink: https://bugs.launchpad.net/bugs/1821607
in kernel: Ubuntu-5.0.0-9.10 (Disco)
AND
commit 3b8d3410b3d8
Author: Dan Williams
Date: Thu Feb 7 20:56:50 2019
acpi/nfit: Fix bus command validation
BugLink: https://bugs.launchpad.net/bugs/1837952
commit ebe9f6f19d80d8978d16078dff3d5bd93ad8d102 upstream.
in kernel: Ubuntu-4.15.0-59.66 (Bionic)
So kernel part is good (or kind of.. actually it is missing 2 fixes
on top of that):
TODO: KERNEL TEAM SHOULD BACKPORT THIS TO BIONIC AND DISCO:
commit ebe9f6f19d80
Author: Dan Williams
Date: Thu Feb 7 20:56:50 2019
acpi/nfit: Fix bus command validation
Fixes: 11189c1089da ("acpi/nfit: Fix command-supported detection")
commit 0171b6b78131
Author: Dan Williams
Date: Sun Feb 3 17:17:27 2019
acpi/nfit: Require opt-in for read-only label configurations
Fixes: 11189c1089da ("acpi/nfit: Fix command-supported detection")
TO FIX THE ISSUE'S FIX
-
TODO: FEEDBACK ABOUT PROPOSED USERLAND FIX
and the userland fix was, indeed, the ndctl patch I did a SRU for.
UNFORTUNATELY I can't reproduce the issue with QEMU. I have tried
different label sizes in multiple attempts and wasn't able to cause the
labeling error (making sure it was fixed). With that it is hard for me
to guarantee the fix is good and I'll depend on a feedback from
reporter.
There is a PPA in comment #19 containing the fix. I'll flag this case as
incomplete while I have no feedback, as we wouldn't be able to verify
the fix in order for it to land -updates archive.
Nevertheless, documentation here might be important to others, in order
to understand the errors.
** Changed in: linux (Ubuntu)
Status: Invalid => Fix Released
** Changed in: ndctl (Ubuntu Bionic)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: ndctl (Ubuntu Disco)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
** Changed in: ndctl (Ubuntu Bionic)
Status: In Progress => Incomplete
** Changed in: ndctl (Ubuntu Disco)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Status in ndctl:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in ndctl package in Ubuntu:
Fix Released
Status in ndctl source package in Bionic:
Incomplete
Status in ndctl source package in Disco:
Incomplete
Status in ndctl source package in Eoan:
Fix Released
Bug description:
On ubuntu 18.04.1 :
1°) With 4.15.0-43 two default namespaces in raw mode are visible
while there shouldn't be any but no settings change could be applied.
root@server:~# ndctl list -R
[
{
"dev":"region1",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":1,
"persistence_domain":"unknown"
},
{
"dev":"region0",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":0,
"persistence_domain":"unknown"
}
]
root@server:~# ndctl list
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
]
root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem
--mode=sector -f
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
lib
[Kernel-packages] [Bug 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
TODOs in this bug:
- End user must confirm the issue is still reproducible and test PPA package
- Mark the case as Confirmed again (instead of Incomplete)
- From that point, the SRU would continue (merge requests already present in
this bug)
- Patches would be sent out to kernel team for inclusion in the next SRU
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Status in ndctl:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in ndctl package in Ubuntu:
Fix Released
Status in ndctl source package in Bionic:
Incomplete
Status in ndctl source package in Disco:
Incomplete
Status in ndctl source package in Eoan:
Fix Released
Bug description:
On ubuntu 18.04.1 :
1°) With 4.15.0-43 two default namespaces in raw mode are visible
while there shouldn't be any but no settings change could be applied.
root@server:~# ndctl list -R
[
{
"dev":"region1",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":1,
"persistence_domain":"unknown"
},
{
"dev":"region0",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":0,
"persistence_domain":"unknown"
}
]
root@server:~# ndctl list
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
]
root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem
--mode=sector -f
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
[Kernel-packages] [Bug 1852227] Re: eoan/linux-gcp: 5.3.0-1009.10 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1852227 Title: eoan/linux-gcp: 5.3.0-1009.10 -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-lrm 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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852232 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-5.3: bug 1852226 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852581] Re: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO
Ah, my apologies. After reinstalling from the -proposed pocket the 5.3.0-23.25~18.04.2 kernel is indeed booting properly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852581 Title: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO Status in linux package in Ubuntu: In Progress Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe-edge source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-hwe-edge source package in Eoan: Invalid Bug description: SRU Justification Impact: The fix for bug 1850234 does not function as intended in bionic, as a result of modinfo not knowing about module signatures. This results in no modules being signed in hwe kernels based on 5.3, rendering systems with secure boot enabled unbootable. Fix: Check for the module signature at the end of modules instead of relying on modinfo. This can be done without any external tools needing to be aware of module signatures. Test Case: Check that all built modules contain signatures, except for those in staging which have not been whitelisted. Regression Potential: I can think of two possible regression situations. We could regress to the behavior prior to the fix for bug 1850234, or the eoan 5.3 kernel could also end up with all modules unsigned. I've done test builds of both the eoan 5.3 kernel and the bionic 5.3 hwe-edge kernel with this patch and checked that the results are as intended. We should also check this again once new kernels have been built, before copying them out to -proposed. --- The latest hwe-edge kernel 5.3.0-23.25 fails to boot with the message that it cannot find the UUID associated with the root partition. The user gets dropped to a busybox shell with an initramfs prompt. The standard hwe kernel does not have this issue and the last hwe-edge kernel that does work is 5.3.0-19.20. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04-edge 5.3.0.23.90 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 14 08:19:57 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-09-01 (73 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852227] Re: eoan/linux-gcp: 5.3.0-1009.10 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852232 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-5.3: bug 1852226 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1852227 Title: eoan/linux-gcp: 5.3.0-1009.10 -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-lrm 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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852232 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp-5.3: bug 1852226 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852406] Re: Double-escape in initramfs DECRYPT_CMD
@colin-king I just checked and, with the plymouth fix also applied, the
issue is fixed in 0.8.1-1ubuntu14.2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852406
Title:
Double-escape in initramfs DECRYPT_CMD
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Eoan:
Fix Committed
Status in zfs-linux source package in Focal:
Fix Released
Bug description:
== SRU Justification, Eoan ==
initramfs/scripts/zfs.in incorrectly quotes ${ENCRYPTIONROOT} on line
414:
DECRYPT_CMD="${ZFS} load-key '${ENCRYPTIONROOT}'"
This is OK when the line is executed by shell, such as in line 430 or
436, but when plymouth is used it results in plymouth executing "zfs
load-key 'rpool'" - and zfs is unable to find pool called "'rpool'".
If I understand
https://docs.oracle.com/cd/E23824_01/html/821-1448/gbcpt.html
correctly zfs pool name is always 'shell-friendly', so removing the
quotation marks would be a proper fix for that.
== Fix ==
One line fix as attached in https://bugs.launchpad.net/ubuntu/+source
/zfs-linux/+bug/1852406/comments/1
== Test ==
Boot with encrypted data set with plymouth. Without the fix zfs is
unable to find the root encrypted pool. With the fix this works.
== Regression Potential ==
This just affects the encrypted dataset that holds key for root
dataset; currently this is causing issues because of the bug, so the
risk of the fix outweighs the current situation where this is
currently broken.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1852406/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853882] [NEW] Eoan update: 5.3.13 upstream stable release
Public bug reported: 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 following upstream stable patches should be included in the Ubuntu kernel: 5.3.13 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Eoan) Importance: Medium Assignee: Connor Kuehl (connork) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853882 Title: Eoan update: 5.3.13 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: In Progress 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 following upstream stable patches should be included in the Ubuntu kernel: 5.3.13 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790825] Re: gicv3-ipi and gicv3-active failed on Bionic Moonshot ARM64 server
So after running into bug# 1828165 I now stumbled across this one, This test is invalid, as gicv3 is only supported on arm64 hardware Thunderx and newer. the HP Moonshot cartridges are NOT to be used for this test. This needs to be blacklisted somehow, will touch base with SAM on doing so. ** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Sean Feole (sfeole) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Bionic) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790825 Title: gicv3-ipi and gicv3-active failed on Bionic Moonshot ARM64 server Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: These two test will fail on a Moonshot node, with Bionic installed. $ sudo ./run_tests.sh -v SKIP selftest-setup (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP selftest-vectors-kernel (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP selftest-vectors-user (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP selftest-smp (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP pci-test (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP pmu (qemu-system-aarch64: Unable to determine GIC version supported by host) TESTNAME=gicv2-ipi TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'ipi' PASS gicv2-ipi (3 tests) TESTNAME=gicv3-ipi TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP -machine gic-version=3 -append 'ipi' FAIL gicv3-ipi TESTNAME=gicv2-active TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'active' PASS gicv2-active (1 tests) TESTNAME=gicv3-active TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP -machine gic-version=3 -append 'active' FAIL gicv3-active SKIP psci (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP timer (qemu-system-aarch64: Unable to determine GIC version supported by host) Further check with these two failed test case, they are complaining the same issue: root@ms10-35-mcdivittB0-kernel:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=gicv3-ipi TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP -machine gic-version=3 -append 'ipi' timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults -machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel arm/gic.flat -smp -machine gic-version=3 -append ipi # -initrd /tmp/tmp.oWkFeTiIeQ qemu-system-aarch64: -smp -machine: Parameter 'cpus' expects a number root@ms10-35-mcdivittB0-kernel:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=gicv3-active TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP -machine gic-version=3 -append 'active' timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults -machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel arm/gic.flat -smp -machine gic-version=3 -append active # -initrd /tmp/tmp.1X2ud5gyAh qemu-system-aarch64: -smp -machine: Parameter 'cpus' expects a number ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: User Name 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 5 08:09 seq crw-rw 1 root audio 116, 33 Sep 5 08:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed Sep 5 08:56:52 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or dir
[Kernel-packages] [Bug 1790825] Re: gicv3-ipi and gicv3-active failed on Bionic Moonshot ARM64 server
Marking the linux bug invalid as this test is not properly targeted to run on the correct hardware ** Changed in: ubuntu-kernel-tests Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790825 Title: gicv3-ipi and gicv3-active failed on Bionic Moonshot ARM64 server Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: These two test will fail on a Moonshot node, with Bionic installed. $ sudo ./run_tests.sh -v SKIP selftest-setup (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP selftest-vectors-kernel (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP selftest-vectors-user (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP selftest-smp (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP pci-test (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP pmu (qemu-system-aarch64: Unable to determine GIC version supported by host) TESTNAME=gicv2-ipi TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'ipi' PASS gicv2-ipi (3 tests) TESTNAME=gicv3-ipi TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP -machine gic-version=3 -append 'ipi' FAIL gicv3-ipi TESTNAME=gicv2-active TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'active' PASS gicv2-active (1 tests) TESTNAME=gicv3-active TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP -machine gic-version=3 -append 'active' FAIL gicv3-active SKIP psci (qemu-system-aarch64: Unable to determine GIC version supported by host) SKIP timer (qemu-system-aarch64: Unable to determine GIC version supported by host) Further check with these two failed test case, they are complaining the same issue: root@ms10-35-mcdivittB0-kernel:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=gicv3-ipi TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP -machine gic-version=3 -append 'ipi' timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults -machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel arm/gic.flat -smp -machine gic-version=3 -append ipi # -initrd /tmp/tmp.oWkFeTiIeQ qemu-system-aarch64: -smp -machine: Parameter 'cpus' expects a number root@ms10-35-mcdivittB0-kernel:/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests# TESTNAME=gicv3-active TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $MAX_SMP -machine gic-version=3 -append 'active' timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults -machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel arm/gic.flat -smp -machine gic-version=3 -append active # -initrd /tmp/tmp.1X2ud5gyAh qemu-system-aarch64: -smp -machine: Parameter 'cpus' expects a number ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: User Name 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 5 08:09 seq crw-rw 1 root audio 116, 33 Sep 5 08:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed Sep 5 08:56:52 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': '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/1790825/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1853881] [NEW] Xenial update: 4.4.203 upstream stable release
Public bug reported: 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 following upstream stable patches should be included in the Ubuntu kernel: 4.4.203 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Connor Kuehl (connork) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853881 Title: Xenial update: 4.4.203 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress 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 following upstream stable patches should be included in the Ubuntu kernel: 4.4.203 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828165] Re: gicv2-mmio in ubuntu_kvm_unit_tests failed on X ARM64 Moonshot
** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Tags added: sru-2019 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828165 Title: gicv2-mmio in ubuntu_kvm_unit_tests failed on X ARM64 Moonshot Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Bug description: This test passed with X-HWE on ARM64 Moonshot: TESTNAME=gicv2-mmio TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'mmio' PASS gicv2-mmio (17 tests, 1 skipped) So this feels like a kernel issue to me. # MAX_SMP=8 # TESTNAME=gicv2-mmio TIMEOUT=90s ACCEL= ./arm/run arm/gic.flat -smp $((($MAX_SMP < 8)?$MAX_SMP:8)) -machine gic-version=2 -append 'mmio' timeout -k 1s --foreground 90s /usr/bin/qemu-system-aarch64 -nodefaults -machine virt,gic-version=host,accel=kvm -cpu host -device virtio-serial-device -device virtconsole,chardev=ctd -chardev testdev,id=ctd -device pci-testdev -display none -serial stdio -kernel arm/gic.flat -smp 8 -machine gic-version=2 -append mmio # -initrd /tmp/tmp.OlzPYOZSZn INFO: gicv2: mmio: number of implemented SPIs: 256 PASS: gicv2: mmio: all 8 CPUs have interrupts INFO: gicv2: mmio: IIDR: 0x4b00043b PASS: gicv2: mmio: GICD_TYPER is read-only PASS: gicv2: mmio: GICD_IIDR is read-only PASS: gicv2: mmio: ICPIDR2 is read-only (0x) PASS: gicv2: mmio: IPRIORITYR: consistent priority masking (0x) PASS: gicv2: mmio: IPRIORITYR: implements at least 4 priority bits (8) PASS: gicv2: mmio: IPRIORITYR: clearing priorities PASS: gicv2: mmio: IPRIORITYR: accesses beyond limit RAZ/WI PASS: gicv2: mmio: IPRIORITYR: accessing last SPIs PASS: gicv2: mmio: IPRIORITYR: priorities are preserved PASS: gicv2: mmio: IPRIORITYR: byte reads successful (0xff7fbf3f => 0xbf) PASS: gicv2: mmio: IPRIORITYR: byte writes successful (0x1f => 0xff1fbf3f) SKIP: gicv2: mmio: ITARGETSR: CPU masking (all CPUs implemented) PASS: gicv2: mmio: ITARGETSR: accesses beyond limit RAZ/WI FAIL: gicv2: mmio: ITARGETSR: register content preserved (0103020f => 01010201) PASS: gicv2: mmio: ITARGETSR: byte reads successful (0x0103020f => 0x02) FAIL: gicv2: mmio: ITARGETSR: byte writes successful (0x1f => 0x01010201) SUMMARY: 17 tests, 2 unexpected failures, 1 skipped ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-146-generic 4.4.0-146.172 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 8 02:17 seq crw-rw 1 root audio 116, 33 May 8 02:17 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 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: CRDA: N/A Date: Wed May 8 06:36:49 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.4.0-146-generic N/A linux-backports-modules-4.4.0-146-generic N/A linux-firmware 1.157.21 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/1828165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed with B/E
** Tags added: arm64 ** Tags added: amd64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829849 Title: proc01 in fs from ubuntu_ltp failed with B/E Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Bug description: proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens6/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable proc01 0 TINFO : /proc/sysrq-trigger: is write-only. proc01 0 TINFO : /proc/self/task/8782/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/task/8782/clear_refs: is write-only. proc01 0 TINFO : /proc/self/task/8782/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/task/8782/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 1 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 2 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 3 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 4 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 5 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 6 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 7 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 8 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 9 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/clear_refs: is write-only. proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 10 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 11 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 12 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 13 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 14 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 15 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 16 TFAIL : proc01.c:397: read failed: /proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 17 TFAIL : proc01.c:397: read failed: /proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 18 TFAIL : proc01.c:397: read failed: /proc/self/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 19 TFAIL :
[Kernel-packages] [Bug 1852406] Re: Double-escape in initramfs DECRYPT_CMD
I was hoping you could test the version in -proposed. Without it being
verified as fixed then the fix won't be released for Eoan.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852406
Title:
Double-escape in initramfs DECRYPT_CMD
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Eoan:
Fix Committed
Status in zfs-linux source package in Focal:
Fix Released
Bug description:
== SRU Justification, Eoan ==
initramfs/scripts/zfs.in incorrectly quotes ${ENCRYPTIONROOT} on line
414:
DECRYPT_CMD="${ZFS} load-key '${ENCRYPTIONROOT}'"
This is OK when the line is executed by shell, such as in line 430 or
436, but when plymouth is used it results in plymouth executing "zfs
load-key 'rpool'" - and zfs is unable to find pool called "'rpool'".
If I understand
https://docs.oracle.com/cd/E23824_01/html/821-1448/gbcpt.html
correctly zfs pool name is always 'shell-friendly', so removing the
quotation marks would be a proper fix for that.
== Fix ==
One line fix as attached in https://bugs.launchpad.net/ubuntu/+source
/zfs-linux/+bug/1852406/comments/1
== Test ==
Boot with encrypted data set with plymouth. Without the fix zfs is
unable to find the root encrypted pool. With the fix this works.
== Regression Potential ==
This just affects the encrypted dataset that holds key for root
dataset; currently this is causing issues because of the bug, so the
risk of the fix outweighs the current situation where this is
currently broken.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1852406/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836169] Re: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on ARM64
Again, similar to bug#1790825 I would like to see this test run on newer hardware, not the HP Moonshots. will speak with sam ** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Sean Feole (sfeole) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836169 Title: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on ARM64 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: New Bug description: This issue can be found on both ThunderX and Moonshot ARM64 <<>> incrementing stop Name: cpuhotplug04 Date: Thu Jul 11 08:34:50 UTC 2019 Desc: Does it prevent us from offlining the last CPU? sh: echo: I/O error cpuhotplug04 1 TFAIL: Could not offline cpu0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=9 cstime=4 <<>> Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "cpuhotplug04 cpuhotplug04.sh -l 1" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 11 06:57 seq crw-rw 1 root audio 116, 33 Jul 11 06:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.4 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jul 11 08:28:42 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.175.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': '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/1836169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853365] Re: bionic/linux-ibm-gt: 4.15.0-1043.46 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849855 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt - phase: Testing - phase-changed: Friday, 22. November 2019 09:52 UTC + phase: Holding before Promote to Updates + phase-changed: Monday, 25. November 2019 18:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853365 Title: bionic/linux-ibm-gt: 4.15.0-1043.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849855 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Holding before Promote to Updates phase-changed: Monday, 25. November 2019 18:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853365] Re: bionic/linux-ibm-gt: 4.15.0-1043.46 -proposed tracker
Smoke/Boot test passed across amd64/ppc/s390x ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853365 Title: bionic/linux-ibm-gt: 4.15.0-1043.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1849855 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Holding before Promote to Updates phase-changed: Monday, 25. November 2019 18:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853365/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852232 Title: eoan/linux: 5.3.0-24.26 -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-lrm 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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1852231 eoan/linux-aws: bug 1852223 eoan/linux-azure: bug 1852225 eoan/linux-gcp: bug 1852227 eoan/linux-kvm: bug 1852228 eoan/linux-oracle: bug 1852230 eoan/linux-raspi2: bug 1852220 eoan/linux/pc-kernel: bug 1852217 eoan/linux/pc-lowlatency-kernel: bug 1852218 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed
** Tags added: arm64
** Tags added: arm64-aws
** Changed in: ubuntu-kernel-tests
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1829995
Title:
getaddrinfo_01 from ipv6_lib test suite in LTP failed
Status in ubuntu-kernel-tests:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in linux-aws package in Ubuntu:
New
Status in linux source package in Bionic:
Incomplete
Status in linux-aws source package in Bionic:
New
Status in linux source package in Disco:
New
Status in linux-aws source package in Disco:
New
Status in linux source package in Eoan:
New
Status in linux-aws source package in Eoan:
New
Bug description:
startup='Wed May 22 08:02:52 2019'
getaddrinfo_011 TPASS : getaddrinfo IPv4 basic lookup
getaddrinfo_012 TFAIL : getaddrinfo_01.c:140: getaddrinfo IPv4
canonical name ("curly.maas") doesn't match hostname ("curly")
getaddrinfo_013 TFAIL : getaddrinfo_01.c:578: getaddrinfo IPv6 basic
lookup ("curly") returns -5 ("No address associated with hostname")
tag=getaddrinfo_01 stime=1558512172 dur=1 exit=exited stat=1 core=no cu=0 cs=0
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-50-generic 4.15.0-50.54
ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 22 02:57 seq
crw-rw 1 root audio 116, 33 May 22 02:57 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Wed May 22 08:04:30 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
RelatedPackageVersions:
linux-restricted-modules-4.15.0-50-generic N/A
linux-backports-modules-4.15.0-50-generic N/A
linux-firmware 1.173.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias:
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829995/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829849] Re: proc01 in fs from ubuntu_ltp failed with B/E
** Tags added: s390x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829849 Title: proc01 in fs from ubuntu_ltp failed with B/E Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Bug description: proc01 0 TINFO : /proc/sys/fs/binfmt_misc/register: is write-only. proc01 0 TINFO : /proc/sys/net/ipv6/conf/all/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/default/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/ens6/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/sys/net/ipv6/conf/lo/stable_secret: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/kmsg: known issue: errno=EAGAIN/EWOULDBLOCK(11): Resource temporarily unavailable proc01 0 TINFO : /proc/sysrq-trigger: is write-only. proc01 0 TINFO : /proc/self/task/8782/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/task/8782/clear_refs: is write-only. proc01 0 TINFO : /proc/self/task/8782/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/task/8782/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/task/8782/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 1 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 2 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 3 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 4 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 5 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 6 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 7 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 8 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 9 TFAIL : proc01.c:397: read failed: /proc/self/task/8782/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/mem: known issue: errno=EIO(5): Input/output error proc01 0 TINFO : /proc/self/clear_refs: is write-only. proc01 0 TINFO : /proc/self/pagemap: reached maxmbytes (-m) proc01 0 TINFO : /proc/self/attr/prev: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/exec: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/fscreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/keycreate: known issue: errno=EINVAL(22): Invalid argument proc01 0 TINFO : /proc/self/attr/sockcreate: known issue: errno=EINVAL(22): Invalid argument proc01 10 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/current: errno=EINVAL(22): Invalid argument proc01 11 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/prev: errno=EINVAL(22): Invalid argument proc01 12 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/exec: errno=EINVAL(22): Invalid argument proc01 13 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/fscreate: errno=EINVAL(22): Invalid argument proc01 14 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/keycreate: errno=EINVAL(22): Invalid argument proc01 15 TFAIL : proc01.c:397: read failed: /proc/self/attr/selinux/sockcreate: errno=EINVAL(22): Invalid argument proc01 16 TFAIL : proc01.c:397: read failed: /proc/self/attr/smack/current: errno=EINVAL(22): Invalid argument proc01 17 TFAIL : proc01.c:397: read failed: /proc/self/attr/apparmor/prev: errno=EINVAL(22): Invalid argument proc01 18 TFAIL : proc01.c:397: read failed: /proc/self/attr/apparmor/exec: errno=EINVAL(22): Invalid argument proc01 19 TFAIL : proc01.c:466: readpro
[Kernel-packages] [Bug 1852232] Re: eoan/linux: 5.3.0-24.26 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1852231 eoan/linux-aws: bug 1852223 eoan/linux-azure: bug 1852225 eoan/linux-gcp: bug 1852227 eoan/linux-kvm: bug 1852228 eoan/linux-oracle: bug 1852230 eoan/linux-raspi2: bug 1852220 eoan/linux/pc-kernel: bug 1852217 eoan/linux/pc-lowlatency-kernel: bug 1852218 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852232 Title: eoan/linux: 5.3.0-24.26 -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-lrm 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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1852231 eoan/linux-aws: bug 1852223 eoan/linux-azure: bug 1852225 eoan/linux-gcp: bug 1852227 eoan/linux-kvm: bug 1852228 eoan/linux-oracle: bug 1852230 eoan/linux-raspi2: bug 1852220 eoan/linux/pc-kernel: bug 1852217 eoan/linux/pc-lowlatency-kernel: bug 1852218 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852223] Re: eoan/linux-aws: 5.3.0-1008.9 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1852223 Title: eoan/linux-aws: 5.3.0-1008.9 -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-lrm 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 verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852232 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Friday, 15. November 2019 15:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 185 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851619] Re: test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3
looks to be more related with the 5.3 kernel, also affects Eoan ** Tags added: eoan ** Tags added: aws ** Tags added: sru-2019 ** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Eoan) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1851619 Title: test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3 Status in ubuntu-kernel-tests: Triaged Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-aws source package in Bionic: New Status in linux-gcp source package in Bionic: New Status in linux-aws source package in Eoan: New Status in linux-gcp source package in Eoan: New Bug description: The test_blackhole_dev from net in ubuntu_kernel_selftests failed on B-GCP 5.3 (5.3.0-1007.7~18.04.1-gcp) # selftests: net: test_blackhole_dev.sh # test_blackhole_dev: [FAIL] not ok 13 selftests: net: test_blackhole_dev.sh Need to run this manually to see what's going on there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829992] Re: zram02 from kernel_misc test suite in LTP failed
** Tags added: arm64 ** Tags removed: cosmic ** Tags added: eoan ** Tags added: arm64-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829992 Title: zram02 from kernel_misc test suite in LTP failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Bug description: startup='Wed May 22 07:02:20 2019' zram02 1 TINFO: create '1' zram device(s) zram02 1 TFAIL: unexpected num of devices: 4 zram02 2 TINFO: zram cleanup tag=zram02 stime=1558508540 dur=0 exit=exited stat=1 core=no cu=1 cs=0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-20-generic 4.18.0-20.21 ProcVersionSignature: User Name 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 06:28 seq crw-rw 1 root audio 116, 33 May 22 06:28 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed May 22 07:52:48 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-20-generic N/A linux-backports-modules-4.18.0-20-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852225] Re: eoan/linux-azure: 5.3.0-1008.9 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1852225 Title: eoan/linux-azure: 5.3.0-1008.9 -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-lrm 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: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852232 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 15. November 2019 16:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1852224 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852223] Re: eoan/linux-aws: 5.3.0-1008.9 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852232 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Friday, 15. November 2019 15:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 185 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1852223 Title: eoan/linux-aws: 5.3.0-1008.9 -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-lrm 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 verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852232 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Friday, 15. November 2019 15:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 185 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852225] Re: eoan/linux-azure: 5.3.0-1008.9 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852232 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 15. November 2019 16:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1852224 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1852225 Title: eoan/linux-azure: 5.3.0-1008.9 -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-lrm 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: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852232 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 15. November 2019 16:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-5.3: bug 1852224 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852225/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853882] Re: Eoan update: 5.3.13 upstream stable release
** Description changed: + SRU Justification - 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 following upstream + stable patches should be included in the Ubuntu kernel: - 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 following upstream -stable patches should be included in the Ubuntu kernel: + * net: cdc_ncm: Signedness bug in cdc_ncm_set_dgram_size() + * block, bfq: deschedule empty bfq_queues not referred by any process + * mm/memory_hotplug: don't access uninitialized memmaps in shrink_pgdat_span() + * mm/memory_hotplug: fix updating the node span + * arm64: uaccess: Ensure PAN is re-enabled after unhandled uaccess fault + * fbdev: Ditch fb_edid_add_monspecs + * Linux 5.3.13 + * UBUNTU: upstream stable to v5.3.13 -5.3.13 upstream stable release -from git://git.kernel.org/ + 5.3.13 upstream stable release + from git://git.kernel.org/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853882 Title: Eoan update: 5.3.13 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: In Progress 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 following upstream stable patches should be included in the Ubuntu kernel: * net: cdc_ncm: Signedness bug in cdc_ncm_set_dgram_size() * block, bfq: deschedule empty bfq_queues not referred by any process * mm/memory_hotplug: don't access uninitialized memmaps in shrink_pgdat_span() * mm/memory_hotplug: fix updating the node span * arm64: uaccess: Ensure PAN is re-enabled after unhandled uaccess fault * fbdev: Ditch fb_edid_add_monspecs * Linux 5.3.13 * UBUNTU: upstream stable to v5.3.13 5.3.13 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853694] Re: Ubuntu causing eye strain on Intel Integrated Graphics
The screen is flickering in so much as there is a very faint shimmering effect. This is usually the effect of dithering which adjusts the pixel color values rapidly to give the impression of colors that are not normally present. This effect is welcomed if using a low quality display however for certain indivduals causes significant discomfort. Can it be confirmed that any form of dithering is enabled by default in Ubuntu and is there an option to turn it off? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853694 Title: Ubuntu causing eye strain on Intel Integrated Graphics Status in linux package in Ubuntu: Incomplete Bug description: I find when running Ubuntu after 5-10 minutes get heavy eyes and after a few hours develop dizziness/headaches. After research online and talking with a community at LED Strain (https://ledstrain.org) it is believed the issue is caused by dithering being enabled on Ubuntu. There is no known way turn off all dithering by default and would like an option to turn off all dithering to avoid discomfort. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-36-generic 5.0.0-36.39~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 23 12:56:12 2019 InstallationDate: Installed on 2019-11-22 (1 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853900] [NEW] bionic/linux-azure: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Monday, 25. November 2019 20:01 UTC reason: prepare-package: Holding -- waiting for master bug replaces: bug 1852238 trackers: bionic/linux-azure/azure-kernel: bug 1853899 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: linux-azure stakeholder signoff (linux-azure-signoff) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1853901 kernel-sru-cycle-2019.11.11-4 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided =>
[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + disco/linux-azure: -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852253 + packages: + main: linux-azure + meta: linux-meta-azure + signed: linux-signed-azure + phase: Ready for Packaging + phase-changed: Monday, 25. November 2019 20:02 UTC + reason: + prepare-package: Pending -- version not specified replaces: bug 1852239 + trackers: + bionic/linux-azure: bug 1852238, bug 1853900 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1853901 Title: disco/linux-azure: 5.0.0-1027.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Monday, 25. November 2019 20:05 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1852239 trackers: bionic/linux-azure: bug 1852238, bug 1853900 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853901] [NEW] disco/linux-azure: 5.0.0-1027.29 -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Monday, 25. November 2019 20:05 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1852239 trackers: bionic/linux-azure: bug 1852238, bug 1853900 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Marcelo Cerri (mhcerri) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: linux-azure stakeholder signoff (linux-azure-signoff) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Disco) Importance: Medium Status: Confirmed ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.11.11-4 kernel-sru-derivative-of-1852253 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: disco kernel-release-tracking-bug ** Also affects: linux-azure (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Disco) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Inva
[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Packaging - phase-changed: Monday, 25. November 2019 20:02 UTC + phase: Packaging + phase-changed: Monday, 25. November 2019 20:05 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1852239 trackers: bionic/linux-azure: bug 1852238, bug 1853900 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1853901 Title: disco/linux-azure: 5.0.0-1027.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Monday, 25. November 2019 20:05 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1852239 trackers: bionic/linux-azure: bug 1853900, bug 1852238 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker
** Summary changed: - disco/linux-azure: -proposed tracker + disco/linux-azure: 5.0.0-1027.29 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1853901 Title: disco/linux-azure: 5.0.0-1027.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Monday, 25. November 2019 20:05 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1852239 trackers: bionic/linux-azure: bug 1852238, bug 1853900 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852238] Re: bionic/linux-azure: 5.0.0-1026.28~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1852239 + kernel-stable-master-bug: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 15. November 2019 02:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1852237 variant: debs ** Tags removed: kernel-sru-backport-of-1852239 ** Tags added: kernel-sru-backport-of-1853901 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1852238 Title: bionic/linux-azure: 5.0.0-1026.28~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-lrm 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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 15. November 2019 02:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1852237 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853900] Re: bionic/linux-azure: -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + bionic/linux-azure: -proposed tracker ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1853901 + packages: + lrm: linux-restricted-modules-azure + main: linux-azure + meta: linux-meta-azure + signed: linux-signed-azure + phase: Holding before Packaging + phase-changed: Monday, 25. November 2019 20:01 UTC + reason: + prepare-package: Holding -- waiting for master bug replaces: bug 1852238 + trackers: + bionic/linux-azure/azure-kernel: bug 1853899 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1853900 Title: bionic/linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Monday, 25. November 2019 20:01 UTC reason: prepare-package: Holding -- waiting for master bug replaces: bug 1852238 trackers: bionic/linux-azure/azure-kernel: bug 1853899 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852253] Re: disco/linux: 5.0.0-37.40 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1853116 disco/linux-aws: bug 1852236 - disco/linux-azure: bug 1852239 + disco/linux-azure: bug 1852239, bug 1853901 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 unknown/unknown: bug 1852245 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852253 Title: disco/linux: 5.0.0-37.40 -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: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1853116 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1852239, bug 1853901 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 unknown/unknown: bug 1852245 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Monday, 25. November 2019 20:05 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1852239 trackers: - bionic/linux-azure: bug 1852238, bug 1853900 + bionic/linux-azure: bug 1853900, bug 1852238 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1853901 Title: disco/linux-azure: 5.0.0-1027.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Monday, 25. November 2019 20:05 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1852239 trackers: bionic/linux-azure: bug 1853900, bug 1852238 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852581] Re: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO
Hello, I have HP x360 The same situation that laptop does not boot with kernel 5.3.0-23 with error -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852581 Title: hwe-edge kernel 5.3.0-23.25 kernel does not boot on Precision 5720 AIO Status in linux package in Ubuntu: In Progress Status in linux-hwe-edge package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-hwe-edge source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-hwe-edge source package in Eoan: Invalid Bug description: SRU Justification Impact: The fix for bug 1850234 does not function as intended in bionic, as a result of modinfo not knowing about module signatures. This results in no modules being signed in hwe kernels based on 5.3, rendering systems with secure boot enabled unbootable. Fix: Check for the module signature at the end of modules instead of relying on modinfo. This can be done without any external tools needing to be aware of module signatures. Test Case: Check that all built modules contain signatures, except for those in staging which have not been whitelisted. Regression Potential: I can think of two possible regression situations. We could regress to the behavior prior to the fix for bug 1850234, or the eoan 5.3 kernel could also end up with all modules unsigned. I've done test builds of both the eoan 5.3 kernel and the bionic 5.3 hwe-edge kernel with this patch and checked that the results are as intended. We should also check this again once new kernels have been built, before copying them out to -proposed. --- The latest hwe-edge kernel 5.3.0-23.25 fails to boot with the message that it cannot find the UUID associated with the root partition. The user gets dropped to a busybox shell with an initramfs prompt. The standard hwe kernel does not have this issue and the last hwe-edge kernel that does work is 5.3.0-19.20. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04-edge 5.3.0.23.90 ProcVersionSignature: Ubuntu 5.3.0-19.20~18.04.2-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 14 08:19:57 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-09-01 (73 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852581/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777586] Re: Ubuntu Server 18.04 LTS aacraid error
I also have this issue triggered on my system. Is there a fix in the ubuntu-provided kernel yet? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777586 Title: Ubuntu Server 18.04 LTS aacraid error Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: I upgraded from a previous version of Ubuntu 14.04LTS to 18.04LTS and am now running into these raid adapter driver errors. The server ran fine in older version. My apologies as I lost the exact version, but it never had any errors like this version. Now when ever I try to copy files to the RAID 5 drive, or untar a file, I get these errors now after a few MB's of written data. Linux batboat 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux batboat:/var/log$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 I have tried the IRQ debugging tips to no avail. I loaded in Debian9.4.0 and it only briefly showed this error once. But appears to be much more resilient and appears to work fine. Jun 19 00:02:21 batboat kernel: [ 498.770839] aacraid: Host adapter reset request. SCSI hang ? Jun 19 00:02:37 batboat kernel: [ 514.139167] aacraid: Host adapter reset request. SCSI hang ? Jun 19 00:02:37 batboat kernel: [ 514.795083] aacraid :03:09.0: Adapter health - 199 Jun 19 00:02:37 batboat kernel: [ 514.800376] aacraid :03:09.0: outstanding cmd: midlevel-0 Jun 19 00:02:37 batboat kernel: [ 514.800378] aacraid :03:09.0: outstanding cmd: lowlevel-0 Jun 19 00:02:37 batboat kernel: [ 514.800381] aacraid :03:09.0: outstanding cmd: error handler-0 Jun 19 00:02:37 batboat kernel: [ 514.800383] aacraid :03:09.0: outstanding cmd: firmware-5 Jun 19 00:02:37 batboat kernel: [ 514.800385] aacraid :03:09.0: outstanding cmd: kernel-0 Jun 19 00:02:37 batboat kernel: [ 514.800391] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800394] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800396] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800399] sd 4:0:0:0: Device offlined - not ready after error recovery Jun 19 00:02:37 batboat kernel: [ 514.800401] sd 4:0:0:0: Device offlined - not ready after error recovery To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker
** Summary changed: - bionic/linux-azure: -proposed tracker + bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri (mhcerri) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1853900 Title: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Monday, 25. November 2019 20:51 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1852238 trackers: bionic/linux-azure/azure-kernel: bug 1853899 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Packaging - phase-changed: Monday, 25. November 2019 20:01 UTC + phase: Packaging + phase-changed: Monday, 25. November 2019 20:51 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- package not yet uploaded + prepare-package-lrm: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1852238 trackers: bionic/linux-azure/azure-kernel: bug 1853899 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1853900 Title: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Monday, 25. November 2019 20:51 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1852238 trackers: bionic/linux-azure/azure-kernel: bug 1853899 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852406] Re: Double-escape in initramfs DECRYPT_CMD
@colin-king I got it (0.8.1-1ubuntu14.2) from eoan-proposed, and yes -
this version fixes the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852406
Title:
Double-escape in initramfs DECRYPT_CMD
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Eoan:
Fix Committed
Status in zfs-linux source package in Focal:
Fix Released
Bug description:
== SRU Justification, Eoan ==
initramfs/scripts/zfs.in incorrectly quotes ${ENCRYPTIONROOT} on line
414:
DECRYPT_CMD="${ZFS} load-key '${ENCRYPTIONROOT}'"
This is OK when the line is executed by shell, such as in line 430 or
436, but when plymouth is used it results in plymouth executing "zfs
load-key 'rpool'" - and zfs is unable to find pool called "'rpool'".
If I understand
https://docs.oracle.com/cd/E23824_01/html/821-1448/gbcpt.html
correctly zfs pool name is always 'shell-friendly', so removing the
quotation marks would be a proper fix for that.
== Fix ==
One line fix as attached in https://bugs.launchpad.net/ubuntu/+source
/zfs-linux/+bug/1852406/comments/1
== Test ==
Boot with encrypted data set with plymouth. Without the fix zfs is
unable to find the root encrypted pool. With the fix this works.
== Regression Potential ==
This just affects the encrypted dataset that holds key for root
dataset; currently this is causing issues because of the bug, so the
risk of the fix outweighs the current situation where this is
currently broken.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1852406/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847948] Comment bridged from LTC Bugzilla
--- Comment From mu...@br.ibm.com 2019-11-25 16:06 EDT--- Apologies for the delay, just tested with the 1:2.11+dfsg-1ubuntu7.21 release and the performance numbers are good in it: # fio --direct=1 --rw=randrw --refill_buffers --norandommap --randrepeat=0 --ioengine=libaio --bs=4k --rwmixread=100 --iodepth=16 --runtime=60 --name=job1 --filename=/dev/nvme0n1 --numjobs=4 READ: bw=1216MiB/s (1275MB/s), 300MiB/s-315MiB/s (314MB/s-330MB/s), io=71.3GiB (76.5GB), run=60001-60002msec # fio --direct=1 --rw=randrw --refill_buffers --norandommap --randrepeat=0 --ioengine=libaio --bs=4k --rwmixread=100 --iodepth=16 --runtime=60 --name=job1 --filename=/dev/nvme0n1 --numjobs=64 READ: bw=4081MiB/s (4280MB/s), 58.3MiB/s-69.8MiB/s (61.1MB/s-73.1MB/s), io=239GiB (257GB), run=60001-60011msec The same note as before applies that I am using the patched custom kernel mentioned in previous comments. $ dpkg -l | grep 1:2.11+dfsg-1ubuntu7.21 ii qemu 1:2.11+dfsg-1ubuntu7.21 ppc64el fast processor emulator ii qemu-block-extra:ppc64el 1:2.11+dfsg-1ubuntu7.21 ppc64el extra block backend modules for qemu-system and qemu-utils ii qemu-kvm 1:2.11+dfsg-1ubuntu7.21 ppc64el QEMU Full virtualization on x86 hardware ii qemu-system1:2.11+dfsg-1ubuntu7.21 ppc64el QEMU full system emulation binaries ii qemu-system-arm1:2.11+dfsg-1ubuntu7.21 ppc64el QEMU full system emulation binaries (arm) ii qemu-system-common 1:2.11+dfsg-1ubuntu7.21 ppc64el QEMU full system emulation binaries (common files) ii qemu-system-mips 1:2.11+dfsg-1ubuntu7.21 ppc64el QEMU full system emulation binaries (mips) ii qemu-system-misc 1:2.11+dfsg-1ubuntu7.21 ppc64el QEMU full system emulation binaries (miscellaneous) ii qemu-system-ppc1:2.11+dfsg-1ubuntu7.21 ppc64el QEMU full system emulation binaries (ppc) ii qemu-system-s390x 1:2.11+dfsg-1ubuntu7.21 ppc64el QEMU full system emulation binaries (s390x) ii qemu-system-sparc 1:2.11+dfsg-1ubuntu7.21 ppc64el QEMU full system emulation binaries (sparc) ii qemu-system-x861:2.11+dfsg-1ubuntu7.21 ppc64el QEMU full system emulation binaries (x86) ii qemu-user 1:2.11+dfsg-1ubuntu7.21 ppc64el QEMU user mode emulation binaries ii qemu-user-binfmt 1:2.11+dfsg-1ubuntu7.21 ppc64el QEMU user mode binfmt registration for qemu-user ii qemu-utils 1:2.11+dfsg-1ubuntu7.21 ppc64el QEMU utilities -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847948 Title: Improve NVMe guest performance on Bionic QEMU Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in qemu source package in Bionic: Fix Committed Bug description: [Impact] * In the past qemu has generally not allowd MSI-X BAR mapping on VFIO. But there can be platforms (like ppc64 spapr) that can and want to do exactly that. * Backport two patches from upstream (in since qemu 2.12 / Disco). * Due to that there is a tremendous speedup, especially useful with page size bigger than 4k. This avoids that being split into chunks and makes direct MMIO access possible for the guest. [Test Case] * On ppc64 pass through an NVME device to the guest and run I/O benchmarks, see below for Details how to set that up. Note: this needs the HWE kernel or another kernel fixup for [1]. Note: the test should also be done with the non-HWE kernel, the expectation there is that it would not show the perf benefits, but still work fine [Regression Potential] * Changes: a) if the host driver allows mapping of MSI-X data the entire BAR is mapped. This is only done if the kernel reports that capability [1]. This ensures that only on kernels able to do so qemu does expose the new behavior (safe against regression in that regard) b) on ppc64 MSI-X emulation is disabled for VFIO devices this is local to just this HW and will not affect other HW. Generally
[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Packaging - phase-changed: Monday, 25. November 2019 20:05 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 25. November 2019 21:12 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait replaces: bug 1852239 trackers: - bionic/linux-azure: bug 1853900, bug 1852238 + bionic/linux-azure: bug 1852238, bug 1853900 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1853901 Title: disco/linux-azure: 5.0.0-1027.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Monday, 25. November 2019 21:12 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait replaces: bug 1852239 trackers: bionic/linux-azure: bug 1852238, bug 1853900 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852406] Re: Double-escape in initramfs DECRYPT_CMD
Thanks Witold! Much appreciated.
** Tags added: verification-done verification-done-eoan
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852406
Title:
Double-escape in initramfs DECRYPT_CMD
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Eoan:
Fix Committed
Status in zfs-linux source package in Focal:
Fix Released
Bug description:
== SRU Justification, Eoan ==
initramfs/scripts/zfs.in incorrectly quotes ${ENCRYPTIONROOT} on line
414:
DECRYPT_CMD="${ZFS} load-key '${ENCRYPTIONROOT}'"
This is OK when the line is executed by shell, such as in line 430 or
436, but when plymouth is used it results in plymouth executing "zfs
load-key 'rpool'" - and zfs is unable to find pool called "'rpool'".
If I understand
https://docs.oracle.com/cd/E23824_01/html/821-1448/gbcpt.html
correctly zfs pool name is always 'shell-friendly', so removing the
quotation marks would be a proper fix for that.
== Fix ==
One line fix as attached in https://bugs.launchpad.net/ubuntu/+source
/zfs-linux/+bug/1852406/comments/1
== Test ==
Boot with encrypted data set with plymouth. Without the fix zfs is
unable to find the root encrypted pool. With the fix this works.
== Regression Potential ==
This just affects the encrypted dataset that holds key for root
dataset; currently this is causing issues because of the bug, so the
risk of the fix outweighs the current situation where this is
currently broken.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1852406/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Monday, 25. November 2019 20:51 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + prepare-package: Stalled -- package tag not yet published + prepare-package-lrm: Stalled -- package tag not yet published + prepare-package-meta: Stalled -- package tag not yet published + prepare-package-signed: Stalled -- package tag not yet published + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,signed:depwait replaces: bug 1852238 trackers: bionic/linux-azure/azure-kernel: bug 1853899 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1853900 Title: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Committed Status in Kernel SRU Workflow prepare-package-lrm series: Fix Committed Status in Kernel SRU Workflow prepare-package-meta series: Fix Committed Status in Kernel SRU Workflow prepare-package-signed series: Fix Committed Status in Kernel SRU Workflow promote-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Monday, 25. November 2019 20:51 UTC reason: prepare-package: Stalled -- package tag not yet published prepare-package-lrm: Stalled -- package tag not yet published prepare-package-meta: Stalled -- package tag not yet published prepare-package-signed: Stalled -- package tag not yet published promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,signed:depwait replaces: bug 1852238 trackers: bionic/linux-azure/azure-kernel: bug 1853899 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853762] Re: Headphones stop working until pairing again
** Attachment added: "user-1000.journal" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+attachment/5307828/+files/user-1000.journal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1853762 Title: Headphones stop working until pairing again Status in bluez package in Ubuntu: New Bug description: I'm using Marshall MID ANC headphones with Ubuntu 19.10. Every now and then, I won't be able to use them without re-pairing first (like today - see logs). After re-pairing, everything works again for a while : I can switch off and on the headphones, reboot... Until it breaks again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 24 19:13:40 2019 InstallationDate: Installed on 2018-07-28 (483 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:AB:C5:7E:41:26 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:319948 acl:71 sco:0 events:45583 errors:0 TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853762] Re: Headphones stop working until pairing again
** Attachment added: "system.journal" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+attachment/5307827/+files/system.journal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1853762 Title: Headphones stop working until pairing again Status in bluez package in Ubuntu: New Bug description: I'm using Marshall MID ANC headphones with Ubuntu 19.10. Every now and then, I won't be able to use them without re-pairing first (like today - see logs). After re-pairing, everything works again for a while : I can switch off and on the headphones, reboot... Until it breaks again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 24 19:13:40 2019 InstallationDate: Installed on 2018-07-28 (483 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:AB:C5:7E:41:26 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:319948 acl:71 sco:0 events:45583 errors:0 TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853762] Re: Headphones stop working until pairing again
I'm adding system.journal and user-1000.journal to this bug report. Today (November 25th) at : - 20:47 : I switched the headphones on... which didn't connect - 20:48 : I tried to connect manually using UI (but the switch/toggle immediately came back to "off") - 20:49-50 : I used bluetoothctl, which worked - 20:51 : I used bluetootctl to disconnect the headphones, and tried to connect them back with UI (which didn't work) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1853762 Title: Headphones stop working until pairing again Status in bluez package in Ubuntu: New Bug description: I'm using Marshall MID ANC headphones with Ubuntu 19.10. Every now and then, I won't be able to use them without re-pairing first (like today - see logs). After re-pairing, everything works again for a while : I can switch off and on the headphones, reboot... Until it breaks again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 24 19:13:40 2019 InstallationDate: Installed on 2018-07-28 (483 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:AB:C5:7E:41:26 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:319948 acl:71 sco:0 events:45583 errors:0 TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Monday, 25. November 2019 21:12 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait replaces: bug 1852239 trackers: bionic/linux-azure: bug 1852238, bug 1853900 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1853901 Title: disco/linux-azure: 5.0.0-1027.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Monday, 25. November 2019 21:12 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait replaces: bug 1852239 trackers: bionic/linux-azure: bug 1852238, bug 1853900 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
