[Kernel-packages] [Bug 1836308] Re: Unhide Nvidia HDA audio controller
** Changed in: hwe-next Status: New => Fix Released -- 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/1836308 Title: Unhide Nvidia HDA audio controller Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [Impact] Nvidia HDA audio controller comes with Nvidia graphics cannot be found by PCI subsystem. [Fix] Write bit 25 at graphics' config space offset 0x488 to enable the HDA controller. [Test] Nvidia HDA controller is not listed under lspci. After applying the fix lspci can find Nvidia HDA controller. [Regression Potential] Low. This fix doesn't bring any functional change other then exposing HDA controller at hardware level. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836308/+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 1840802] Re: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -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-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm 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-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 derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Wednesday, 21. August 2019 04:26 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-meta: Stalled -- package tag not yet published + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,signed:depwait trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 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/1840802 Title: bionic/linux-azure: 5.0.0-1018.19~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 Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Committed 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 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 derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure- edge) -- swm properties -- kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Wednesday, 21. August 2019 04:26 UTC reason: prepare-package-meta: Stalled -- package tag not yet published promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,signed:depwait trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840802/+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 1581711] Re: 024C:B723 Need support for Realtek Wifi card rtl8723bs
Mainline kernel has rtl8723bs support for a while. -- 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/1581711 Title: 024C:B723 Need support for Realtek Wifi card rtl8723bs Status in HWE Next: Won't Fix Status in HWE Next xenial series: Won't Fix Status in linux package in Ubuntu: Fix Released Bug description: This device is appearing in some OEM machines. WORKAROUND: sudo apt-get install build-essential linux-headers-generic git git clone https://github.com/hadess/rtl8723as.git cd rtl8723as make sudo make install sudo depmod -a sudo modprobe r8723bs cat /sys/bus/sdio/devices/mmc1:0001:1/* 0x07 0xb723 cat: '/sys/bus/sdio/devices/mmc1:0001:1/firmware_node': Is a directory sdio:c07v024CdB723 cat: '/sys/bus/sdio/devices/mmc1:0001:1/power': Is a directory cat: '/sys/bus/sdio/devices/mmc1:0001:1/subsystem': Is a directory SDIO_CLASS=07 SDIO_ID=024C:B723 MODALIAS=sdio:c07v024CdB723 0x024c WORKAROUND 2: Install this DKMS driver package: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581711/+attachment/4732838/+files /rtl8723bs-dkms_4.4.1+17245.20160325.2_all.deb --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e59c3a84-25cb-4931-887e-13ab29829963 InstallationDate: Installed on 2016-05-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:73f4 Synaptics, Inc. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer One S1002 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mmcblk0p2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10 dmi.board.name: Popcorn dmi.board.vendor: Acer dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd10/20/2015:svnAcer:pnOneS1002:pvr1.10:rvnAcer:rnPopcorn:rvrTobefilledbyO.E.M.:cvnAcer:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: One S1002 dmi.product.version: 1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1581711/+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 1838208] Re: Wifi stops responding sporadically on lenovo-yoga-720-15ikb
If restarting network-manager can fix the issue then it's less likely to be a kernel bug. ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version:
[Kernel-packages] [Bug 1838208] Re: Wifi stops responding sporadically on lenovo-yoga-720-15ikb
Can you please still attach dmesg with latest kernel/firmware when the issue happens? -- 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/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias:
[Kernel-packages] [Bug 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
** Description changed: From bug: https://bugs.launchpad.net/bugs/1840511 - clockhouse builds test started failing because of the presence of stderr + clickhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). FOR THE KERNEL TEAM: Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? -- 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/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) Status in cpuinfo package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Bug description: From bug: https://bugs.launchpad.net/bugs/1840511 clickhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). FOR THE KERNEL TEAM: Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+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 1840816] Re: disco/linux: 5.0.0-27.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 backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:31 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed + promote-to-proposed: Pending -- builds not complete in ppa meta:failed trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 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/1840816 Title: disco/linux: 5.0.0-27.28 -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: New 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: 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 verification-testing series: New 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 backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:31 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:failed trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840816/+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 1840803] Re: disco/linux-azure: 5.0.0-1018.19 -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 backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:41 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 trackers: bionic/linux-azure: bug 1840802 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/1840803 Title: disco/linux-azure: 5.0.0-1018.19 -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 backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:41 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait trackers: bionic/linux-azure: bug 1840802 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840803/+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 1840802] Re: bionic/linux-azure: 5.0.0-1018.19~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 derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Packaging - phase-changed: Wednesday, 21. August 2019 03:43 UTC + phase: Packaging + phase-changed: Wednesday, 21. August 2019 04:26 UTC reason: - prepare-package: Pending -- version not specified + 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 trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 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/1840802 Title: bionic/linux-azure: 5.0.0-1018.19~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 derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure- edge) -- swm properties -- kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Wednesday, 21. August 2019 04:26 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 trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840802/+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 1840796] Re: sound not working in 4.15.0-58, but does in 4.15.0-55
Speakers in the laptop don't work. -- 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/1840796 Title: sound not working in 4.15.0-58, but does in 4.15.0-55 Status in linux package in Ubuntu: Confirmed Bug description: First excuse me, this is my very first bug report, if anything is missing, notify me on email. -- I find it rather hard to believe, but since I installed kernel: > 4.15.0-**58** several days ago, my sound on Linux Mint 19.2 Cinnamon stopped working, and no matter what I tried like: sudo apt reinstall alsa-base pulseaudio sudo alsa force-reload + reboot(-s) + alsamixer nothing brought me sound back, so I just installed an older kernel, namely the littlest bit older one: > 4.15.0-**55** now everything works like a charm. --- How can I debug this and figure out if the problem is a bug in the kernel itself or in some other audio-related package? I don't know what exact information you could require for this. --- I have just reproduced the problem by upgrading back to 4.15.0-**58** from 4.15.0-**55**. Sound not working again. Plus, by switching to an older kernel proves sound is functional. --- Hardware: laptop Dell HG6D142: [direct link to product page][1] -- $ lsb_release -rd Description: Linux Mint 19.2 Tina Release: 19.2 --- expectation: sound working --- happened: sound does not work at all, neither with Intel GPU, nor Nvidia GPU online, tried all I could mentioned above I attach a simple diff between 55 and 58 loaded. --- Thank you! [1]: https://www.dell.com/support/home/us/en/04/product-support/servicetag/0-dVRqMHhSVXVMa3ZPOVFNUUEzSk1mQT090/overview --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vlastimil 2458 F pulseaudio /dev/snd/controlC1: vlastimil 2458 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2018-06-16 (430 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180531 MachineType: Dell Inc. Inspiron 7577 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=f1fc7345-be7a-4c6b-9559-fc6e2d445bfa ro ipv6.disable=1 quiet splash fsck.mode=force fsck.repair=yes vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 Tags: tina Uname: Linux 4.15.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0J8HMF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd04/19/2019:svnDellInc.:pnInspiron7577:pvr:rvnDellInc.:rn0J8HMF:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7577 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840796/+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 1840810] Re: disco/linux-kvm: 5.0.0-1015.16 -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: 1840816 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:42 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building + promote-to-proposed: Holding -- master bug not ready for proposed variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1840810 Title: disco/linux-kvm: 5.0.0-1015.16 -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 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 verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1840816 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:42 UTC reason: promote-to-proposed: Holding -- master bug not ready for proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840810/+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 1840802] Re: bionic/linux-azure: 5.0.0-1018.19~18.04.1 -proposed tracker
** Summary changed: - bionic/linux-azure: -proposed tracker + bionic/linux-azure: 5.0.0-1018.19~18.04.1 -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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) -- 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/1840802 Title: bionic/linux-azure: 5.0.0-1018.19~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 derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure- edge) -- swm properties -- kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Wednesday, 21. August 2019 04:26 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 trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840802/+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 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
The attachment "cpuinfo_0.0~git20190201.d5e37ad-1ubuntu1.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) Status in cpuinfo package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Bug description: From bug: https://bugs.launchpad.net/bugs/1840511 clockhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). FOR THE KERNEL TEAM: Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+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 1840808] Re: disco/linux-gcp: 5.0.0-1015.15 -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 backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:42 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait trackers: bionic/linux-gcp: bug 1840806 bionic/linux-gke-5.0: bug 1840823 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/1840808 Title: disco/linux-gcp: 5.0.0-1015.15 -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 verification-testing series: New 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 backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:42 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait trackers: bionic/linux-gcp: bug 1840806 bionic/linux-gke-5.0: bug 1840823 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840808/+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 1840810] Re: disco/linux-kvm: 5.0.0-1015.16 -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: 1840816 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:42 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued + promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1840810 Title: disco/linux-kvm: 5.0.0-1015.16 -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 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 verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1840816 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:42 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840810/+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 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
PPA containing clickhouse build (LP: #1840511) and cpuinfo with this fix: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1840511 Debdiff with proposed changes are attached to this bug. -- 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/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) Status in cpuinfo package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Bug description: From bug: https://bugs.launchpad.net/bugs/1840511 clockhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). FOR THE KERNEL TEAM: Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+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 1840803] Re: disco/linux-azure: 5.0.0-1018.19 -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 backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:41 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait trackers: bionic/linux-azure: bug 1840802 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/1840803 Title: disco/linux-azure: 5.0.0-1018.19 -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 backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:41 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait trackers: bionic/linux-azure: bug 1840802 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840803/+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 1840816] Re: disco/linux: 5.0.0-27.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 backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:31 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 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/1840816 Title: disco/linux: 5.0.0-27.28 -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: New 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: 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 verification-testing series: New 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 backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:31 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840816/+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 1840806] Re: bionic/linux-gcp: -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 derivatives: bug 1840805 (gcp-kernel), bug 1840824 (linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1840808 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Packaging - phase-changed: Tuesday, 20. August 2019 18:19 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 21. August 2019 03:43 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: bionic/linux-gcp-edge: bug 1840824 bionic/linux-gcp/gcp-kernel: bug 1840805 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/1840806 Title: bionic/linux-gcp: -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: Confirmed 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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 derivatives: bug 1840805 (gcp-kernel), bug 1840824 (linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1840808 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Packaging phase-changed: Wednesday, 21. August 2019 03:43 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-gcp-edge: bug 1840824 bionic/linux-gcp/gcp-kernel: bug 1840805 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840806/+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 1840803] Re: disco/linux-azure: 5.0.0-1018.19 -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 backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Packaging - phase-changed: Tuesday, 20. August 2019 21:05 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 21. August 2019 03:41 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: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait trackers: bionic/linux-azure: bug 1840802 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/1840803 Title: disco/linux-azure: 5.0.0-1018.19 -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 backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:41 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait trackers: bionic/linux-azure: bug 1840802 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840803/+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 1840808] Re: disco/linux-gcp: 5.0.0-1015.15 -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 backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Packaging - phase-changed: Tuesday, 20. August 2019 20:50 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 21. August 2019 03:42 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: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait trackers: bionic/linux-gcp: bug 1840806 bionic/linux-gke-5.0: bug 1840823 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/1840808 Title: disco/linux-gcp: 5.0.0-1015.15 -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 verification-testing series: New 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 backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:42 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait trackers: bionic/linux-gcp: bug 1840806 bionic/linux-gke-5.0: bug 1840823 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840808/+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 1840810] Re: disco/linux-kvm: 5.0.0-1015.16 -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 ** 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: 1840816 packages: main: linux-kvm meta: linux-meta-kvm - phase: Packaging - phase-changed: Tuesday, 20. August 2019 21:15 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 21. August 2019 03:42 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1840810 Title: disco/linux-kvm: 5.0.0-1015.16 -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 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 verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1840816 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:42 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840810/+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 1840802] Re: bionic/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 derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Packaging - phase-changed: Tuesday, 20. August 2019 18:18 UTC + phase: Ready for Packaging + phase-changed: Wednesday, 21. August 2019 03:43 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 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/1840802 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: Confirmed 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 derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure- edge) -- swm properties -- kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Packaging phase-changed: Wednesday, 21. August 2019 03:43 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840802/+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 1840816] Re: disco/linux: 5.0.0-27.28 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm 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 backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Packaging - phase-changed: Tuesday, 20. August 2019 19:06 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 21. August 2019 03:31 UTC reason: - prepare-package-lrm: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 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/1840816 Title: disco/linux: 5.0.0-27.28 -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: New 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: 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 verification-testing series: New 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 backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 21. August 2019 03:31 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840816/+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 1840619] Re: skb_warn_bad_offload kernel splat due to CHECKSUM target not compatible with GSO skbs
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1840619 [Impact] In environments which have CHECKSUM iptables rules set, the following kernel call trace will be created when a GSO skb is processed by the CHECKSUM target: WARNING: CPU: 34 PID: 806048 at /build/linux-zdslHp/linux-4.4.0/net/core/dev.c:2456 skb_warn_bad_offload+0xcf/0x110() qr-f78bfdf7-fe: caps=(0x0fdb58e9, 0x0fdb58e9) len=1955 data_len=479 gso_size=1448 gso_type=1 ip_summed=3 CPU: 34 PID: 806048 Comm: haproxy Tainted: GW OE 4.4.0-138-generic #164-Ubuntu Call Trace: dump_stack+0x63/0x90 warn_slowpath_common+0x82/0xc0 warn_slowpath_fmt+0x5c/0x80 ? ___ratelimit+0xa2/0xe0 skb_warn_bad_offload+0xcf/0x110 skb_checksum_help+0x185/0x1a0 checksum_tg+0x22/0x29 [xt_CHECKSUM] ipt_do_table+0x301/0x730 [ip_tables] ? ipt_do_table+0x349/0x730 [ip_tables] iptable_mangle_hook+0x39/0x107 [iptable_mangle] nf_iterate+0x68/0x80 nf_hook_slow+0x73/0xd0 ip_output+0xcf/0xe0 ? __ip_flush_pending_frames.isra.43+0x90/0x90 ip_local_out+0x3b/0x50 ip_queue_xmit+0x154/0x390 __tcp_transmit_skb+0x52b/0x9b0 tcp_write_xmit+0x1dd/0xf50 __tcp_push_pending_frames+0x31/0xd0 tcp_push+0xec/0x110 tcp_sendmsg+0x749/0xba0 inet_sendmsg+0x6b/0xa0 sock_sendmsg+0x3e/0x50 SYSC_sendto+0x101/0x190 ? __sys_sendmsg+0x51/0x90 SyS_sendto+0xe/0x10 entry_SYSCALL_64_fastpath+0x22/0xc1 The CHECKSUM target does not support GSO skbs, and when a GSO skb is passed to skb_checksum_help(), it errors out and skb_warn_bad_offload() is called. The above call trace was found in a customer environment which has an Openstack deployment, with the following sorts of iptables rules set: -A neutron-l3-agent-POSTROUTING -o qr-+ -p tcp -m tcp --sport 9697 -j CHECKSUM --checksum-fill -A neutron-dhcp-age-POSTROUTING -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill This was causing haproxy running on the node to crash and restart every time a GSO skb was processed by the CHECKSUM target. I recommend reading the netdev mailing list thread for more details: https://www.spinics.net/lists/netdev/msg517366.html [Fix] This was fixed in 4.19 upstream with the below commit: commit 10568f6c5761db24249c610c94d6e44d5505a0ba Author: Florian Westphal Date: Wed Aug 22 11:33:27 2018 +0200 Subject: netfilter: xt_checksum: ignore gso skbs This commit adds a check to see if the current skb is a gso skb, and if it is, skips skb_checksum_help(). It then continues on to check if the packet uses udp, and if it does, exits early. Otherwise it prints a single warning that CHECKSUM should be avoided, and if really needed, only for use with outbound udp. Note, 10568f6c5761db24249c610c94d6e44d5505a0ba was included in upstream stable version 4.18.13, and was backported to bionic in 4.15.0-58.64 by LP #1836426. This patch required minor backporting for 4.4, by slightly adjusting the context in the final patch hunk. [Testcase] You can reproduce this by adding the following iptables rule to the mangle table: -A POSTROUTING -p tcp -m tcp --sport 80 -j CHECKSUM --checksum-fill and running traffic over port 80 with incorrect checksums in the ip header. I built a test kernel, which is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf216537-test For unpatched kernels, this causes the process which was handeling the socket to crash, as seen by haproxy crashing on a node in production which hits this issue. - On patched kernels you see the warning printed to dmesg and no crashes - occur. + On patched kernels you see the below warning printed to dmesg and no + crashes occur. + + xt_CHECKSUM: CHECKSUM should be avoided. If really needed, restrict + with "-p udp" and only use in OUTPUT [Regression Potential] The changes are limited only to users which have CHECKSUM rules enabled in their iptables configs. Openstack commonly configures such rules on deployment, even though they are not necessary, as almost all packets have their checksum calculated by NICs these days, and CHECKSUM is only around to service old dhcp clients which would discard UDP packets with empty checksums. This commit was selected for upstream -stable 4.18.13, and has made its way into bionic 4.15.0-58.64 by LP #1836426. There have been no reported problems and those kernels would have had sufficient testing with Openstack and its configured iptables rules. If any users are affected by regression, then they can simply delete any CHECKSUM entries in their iptables configs. ** Description changed: BugLink: https://bugs.launchpad.net/bugs/1840619 [Impact] In environments which have CHECKSUM iptables rules set, the following kernel call trace will be created when a GSO skb is processed by the CHECKSUM target: WARNING: CPU: 34
[Kernel-packages] [Bug 1840867] 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 1840867 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/1840867 Title: pthread test from ubuntu_stress_smoke_test hang with X Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on the following nodes: Power8 "modoc" 2 failures out of 2 attempts i386 "pepe" 2 failures out of 2 attempts ARM64 "wright" 1 failure out of 1 attempt Syslog from node pepe: Aug 19 05:51:55 pepe stress-ng: invoked with './stress-n' by user 0 Aug 19 05:51:55 pepe stress-ng: system: 'pepe' Linux 4.4.0-160-generic #188-Ubuntu SMP Wed Aug 14 04:17:20 UTC 2019 i686 Aug 19 05:51:55 pepe stress-ng: memory (MB): total 3991.91, free 3669.34, shared 2.11, buffer 132.39, swap 1023.99, free swap 970.16 Aug 19 05:51:55 pepe stress-ng: info: [25162] dispatching hogs: 4 pthread Aug 19 05:52:00 pepe stress-ng: info: [25164] stress-ng-pthread: 99.75% of iterations could not reach requested 1024 threads (instance 1) Aug 19 05:54:49 pepe systemd[1]: Starting Cleanup of Temporary Directories... Aug 19 05:54:49 pepe systemd-tmpfiles[28049]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Aug 19 05:54:49 pepe systemd[1]: Started Cleanup of Temporary Directories. Aug 19 06:03:16 pepe systemd[1]: Time has been changed Aug 19 06:03:16 pepe systemd[2037]: Time has been changed Aug 19 06:16:05 pepe systemd[2037]: Time has been changed Syslog from node wright: Aug 19 21:36:28 wright-kernel stress-ng: invoked with './stress-n' by user 0 Aug 19 21:36:28 wright-kernel stress-ng: system: 'wright-kernel' Linux 4.15.0-59-generic #66~16.04.1-Ubuntu SMP Wed Aug 14 15:43:01 UTC 2019 aarch64 Aug 19 21:36:28 wright-kernel stress-ng: memory (MB): total 128876.61, free 126748.83, shared 9.28, buffer 63.37, swap 9215.99, free swap 9215.99 Aug 19 21:36:28 wright-kernel stress-ng: info: [16352] dispatching hogs: 4 pthread Aug 19 21:36:28 wright-kernel stress-ng: info: [16352] cache allocate: using defaults, can't determine cache details from sysfs Aug 19 21:39:19 wright-kernel systemd[3731]: Time has been changed Aug 19 21:39:19 wright-kernel rsyslogd-2007: action 'action 11' suspended, next retry is Mon Aug 19 21:40:19 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Aug 19 21:39:19 wright-kernel systemd[1]: Time has been changed Aug 19 22:00:55 wright-kernel systemd[3731]: Time has been changed Aug 19 22:00:55 wright-kernel rsyslogd-2007: action 'action 11' suspended, next retry is Mon Aug 19 22:01:55 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Aug 19 22:00:55 wright-kernel systemd[1]: Time has been changed Aug 19 22:13:47 wright-kernel systemd[1]: Time has been changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-160-generic 4.4.0-160.188 ProcVersionSignature: Ubuntu 4.4.0-160.188-generic 4.4.186 Uname: Linux 4.4.0-160-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 19 05:45 seq crw-rw 1 root audio 116, 33 Aug 19 05:45 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-160-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.19 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed Aug 21 02:27:28 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0 ProcLoadAvg: 0.00 0.00 0.00 1/1313 25458 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 /home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng/swap.img file1048512 0
[Kernel-packages] [Bug 1840867] [NEW] pthread test from ubuntu_stress_smoke_test hang with X
Public bug reported: Issue found on the following nodes: Power8 "modoc" 2 failures out of 2 attempts i386 "pepe" 2 failures out of 2 attempts ARM64 "wright" 1 failure out of 1 attempt Syslog from node pepe: Aug 19 05:51:55 pepe stress-ng: invoked with './stress-n' by user 0 Aug 19 05:51:55 pepe stress-ng: system: 'pepe' Linux 4.4.0-160-generic #188-Ubuntu SMP Wed Aug 14 04:17:20 UTC 2019 i686 Aug 19 05:51:55 pepe stress-ng: memory (MB): total 3991.91, free 3669.34, shared 2.11, buffer 132.39, swap 1023.99, free swap 970.16 Aug 19 05:51:55 pepe stress-ng: info: [25162] dispatching hogs: 4 pthread Aug 19 05:52:00 pepe stress-ng: info: [25164] stress-ng-pthread: 99.75% of iterations could not reach requested 1024 threads (instance 1) Aug 19 05:54:49 pepe systemd[1]: Starting Cleanup of Temporary Directories... Aug 19 05:54:49 pepe systemd-tmpfiles[28049]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Aug 19 05:54:49 pepe systemd[1]: Started Cleanup of Temporary Directories. Aug 19 06:03:16 pepe systemd[1]: Time has been changed Aug 19 06:03:16 pepe systemd[2037]: Time has been changed Aug 19 06:16:05 pepe systemd[2037]: Time has been changed Syslog from node wright: Aug 19 21:36:28 wright-kernel stress-ng: invoked with './stress-n' by user 0 Aug 19 21:36:28 wright-kernel stress-ng: system: 'wright-kernel' Linux 4.15.0-59-generic #66~16.04.1-Ubuntu SMP Wed Aug 14 15:43:01 UTC 2019 aarch64 Aug 19 21:36:28 wright-kernel stress-ng: memory (MB): total 128876.61, free 126748.83, shared 9.28, buffer 63.37, swap 9215.99, free swap 9215.99 Aug 19 21:36:28 wright-kernel stress-ng: info: [16352] dispatching hogs: 4 pthread Aug 19 21:36:28 wright-kernel stress-ng: info: [16352] cache allocate: using defaults, can't determine cache details from sysfs Aug 19 21:39:19 wright-kernel systemd[3731]: Time has been changed Aug 19 21:39:19 wright-kernel rsyslogd-2007: action 'action 11' suspended, next retry is Mon Aug 19 21:40:19 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Aug 19 21:39:19 wright-kernel systemd[1]: Time has been changed Aug 19 22:00:55 wright-kernel systemd[3731]: Time has been changed Aug 19 22:00:55 wright-kernel rsyslogd-2007: action 'action 11' suspended, next retry is Mon Aug 19 22:01:55 2019 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Aug 19 22:00:55 wright-kernel systemd[1]: Time has been changed Aug 19 22:13:47 wright-kernel systemd[1]: Time has been changed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-160-generic 4.4.0-160.188 ProcVersionSignature: Ubuntu 4.4.0-160.188-generic 4.4.186 Uname: Linux 4.4.0-160-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Aug 19 05:45 seq crw-rw 1 root audio 116, 33 Aug 19 05:45 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-160-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.19 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Wed Aug 21 02:27:28 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: ProcKernelCmdLine: root=/dev/mapper/mpath0-part2 ro console=hvc0 ProcLoadAvg: 0.00 0.00 0.00 1/1313 25458 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 /home/ubuntu/autotest/client/tmp/ubuntu_stress_smoke_test/src/stress-ng/swap.img file 1048512 0 -2 ProcVersion: Linux version 4.4.0-160-generic (buildd@bos02-ppc64el-002) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.10) ) #188-Ubuntu SMP Wed Aug 14 04:17:46 UTC 2019 RelatedPackageVersions: linux-restricted-modules-4.4.0-160-generic N/A linux-backports-modules-4.4.0-160-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 159) max: 3.694 GHz (cpu 2) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Colin Ian King (colin-king) Status: New ** Tags:
[Kernel-packages] [Bug 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
** Patch added: "cpuinfo_0.0~git20190201.d5e37ad-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840847/+attachment/5283577/+files/cpuinfo_0.0~git20190201.d5e37ad-1ubuntu1.debdiff ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Description changed: From bug: https://bugs.launchpad.net/bugs/1840511 clockhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). + FOR THE KERNEL TEAM: + Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? -- 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/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) Status in cpuinfo package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Bug description: From bug: https://bugs.launchpad.net/bugs/1840511 clockhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). FOR THE KERNEL TEAM: Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+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 1840847] Re: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
I'm changing CPUINFO_LOG_LEVEL from warning to error only to mitigate this issue. Unfortunately this is the best way to address: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1840511 Right now, allowing clickhouse build to succeed and unblocking MySQL 8 upgrade. ** Changed in: cpuinfo (Ubuntu) Status: New => In Progress ** Changed in: cpuinfo (Ubuntu) Importance: Undecided => Medium ** Changed in: cpuinfo (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- 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/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) Status in cpuinfo package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Bug description: From bug: https://bugs.launchpad.net/bugs/1840511 clockhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+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 1840796] Re: sound not working in 4.15.0-58, but does in 4.15.0-55
Which audio device deosn't work under -58 kernel? Intel hdmi audio, NV hdmi audio, speaker or headphone? -- 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/1840796 Title: sound not working in 4.15.0-58, but does in 4.15.0-55 Status in linux package in Ubuntu: Confirmed Bug description: First excuse me, this is my very first bug report, if anything is missing, notify me on email. -- I find it rather hard to believe, but since I installed kernel: > 4.15.0-**58** several days ago, my sound on Linux Mint 19.2 Cinnamon stopped working, and no matter what I tried like: sudo apt reinstall alsa-base pulseaudio sudo alsa force-reload + reboot(-s) + alsamixer nothing brought me sound back, so I just installed an older kernel, namely the littlest bit older one: > 4.15.0-**55** now everything works like a charm. --- How can I debug this and figure out if the problem is a bug in the kernel itself or in some other audio-related package? I don't know what exact information you could require for this. --- I have just reproduced the problem by upgrading back to 4.15.0-**58** from 4.15.0-**55**. Sound not working again. Plus, by switching to an older kernel proves sound is functional. --- Hardware: laptop Dell HG6D142: [direct link to product page][1] -- $ lsb_release -rd Description: Linux Mint 19.2 Tina Release: 19.2 --- expectation: sound working --- happened: sound does not work at all, neither with Intel GPU, nor Nvidia GPU online, tried all I could mentioned above I attach a simple diff between 55 and 58 loaded. --- Thank you! [1]: https://www.dell.com/support/home/us/en/04/product-support/servicetag/0-dVRqMHhSVXVMa3ZPOVFNUUEzSk1mQT090/overview --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vlastimil 2458 F pulseaudio /dev/snd/controlC1: vlastimil 2458 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.2 InstallationDate: Installed on 2018-06-16 (430 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180531 MachineType: Dell Inc. Inspiron 7577 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=f1fc7345-be7a-4c6b-9559-fc6e2d445bfa ro ipv6.disable=1 quiet splash fsck.mode=force fsck.repair=yes vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-58-generic N/A linux-backports-modules-4.15.0-58-generic N/A linux-firmware 1.173.9 Tags: tina Uname: Linux 4.15.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/19/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.0 dmi.board.name: 0J8HMF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.0:bd04/19/2019:svnDellInc.:pnInspiron7577:pvr:rvnDellInc.:rn0J8HMF:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7577 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840796/+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 1836916] Re: alsa/hdmi: add icelake hdmi audio support for a Dell machine
** 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/1836916 Title: alsa/hdmi: add icelake hdmi audio support for a Dell machine Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [Impact] On a Dell icelake platform, the hdmi audio doesn't work at all, when users plug hdmi cable, they can't find hdmi audio from gnome-sound-setting. [Fix] add icl hdmi audio id and related support patch to alsa driver. [Test Case] after applying the patchset, we plug hdmi cable and the hdmi audio shows up in the sound-setting and works well, after unplugging the cable, the hdmi audio disappears as expected. [Regression Risk] Low. this patchset is specific to a icl hdmi audio codec. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836916/+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 1840619] Re: skb_warn_bad_offload kernel splat due to CHECKSUM target not compatible with GSO skbs
** Description changed: BugLink: https://bugs.launchpad.net/bugs/1840619 [Impact] In environments which have CHECKSUM iptables rules set, the following kernel call trace will be created when a GSO skb is processed by the CHECKSUM target: WARNING: CPU: 34 PID: 806048 at /build/linux-zdslHp/linux-4.4.0/net/core/dev.c:2456 skb_warn_bad_offload+0xcf/0x110() qr-f78bfdf7-fe: caps=(0x0fdb58e9, 0x0fdb58e9) len=1955 data_len=479 gso_size=1448 gso_type=1 ip_summed=3 CPU: 34 PID: 806048 Comm: haproxy Tainted: GW OE 4.4.0-138-generic #164-Ubuntu Call Trace: dump_stack+0x63/0x90 warn_slowpath_common+0x82/0xc0 warn_slowpath_fmt+0x5c/0x80 ? ___ratelimit+0xa2/0xe0 skb_warn_bad_offload+0xcf/0x110 skb_checksum_help+0x185/0x1a0 checksum_tg+0x22/0x29 [xt_CHECKSUM] ipt_do_table+0x301/0x730 [ip_tables] ? ipt_do_table+0x349/0x730 [ip_tables] iptable_mangle_hook+0x39/0x107 [iptable_mangle] nf_iterate+0x68/0x80 nf_hook_slow+0x73/0xd0 ip_output+0xcf/0xe0 ? __ip_flush_pending_frames.isra.43+0x90/0x90 ip_local_out+0x3b/0x50 ip_queue_xmit+0x154/0x390 __tcp_transmit_skb+0x52b/0x9b0 tcp_write_xmit+0x1dd/0xf50 __tcp_push_pending_frames+0x31/0xd0 tcp_push+0xec/0x110 tcp_sendmsg+0x749/0xba0 inet_sendmsg+0x6b/0xa0 sock_sendmsg+0x3e/0x50 SYSC_sendto+0x101/0x190 ? __sys_sendmsg+0x51/0x90 SyS_sendto+0xe/0x10 entry_SYSCALL_64_fastpath+0x22/0xc1 The CHECKSUM target does not support GSO skbs, and when a GSO skb is passed to skb_checksum_help(), it errors out and skb_warn_bad_offload() is called. The above call trace was found in a customer environment which has an Openstack deployment, with the following sorts of iptables rules set: -A neutron-l3-agent-POSTROUTING -o qr-+ -p tcp -m tcp --sport 9697 -j CHECKSUM --checksum-fill -A neutron-dhcp-age-POSTROUTING -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill This was causing haproxy running on the node to crash and restart every time a GSO skb was processed by the CHECKSUM target. I recommend reading the netdev mailing list thread for more details: https://www.spinics.net/lists/netdev/msg517366.html [Fix] This was fixed in 4.19 upstream with the below commit: commit 10568f6c5761db24249c610c94d6e44d5505a0ba Author: Florian Westphal Date: Wed Aug 22 11:33:27 2018 +0200 Subject: netfilter: xt_checksum: ignore gso skbs This commit adds a check to see if the current skb is a gso skb, and if it is, skips skb_checksum_help(). It then continues on to check if the packet uses udp, and if it does, exits early. Otherwise it prints a single warning that CHECKSUM should be avoided, and if really needed, only for use with outbound udp. Note, 10568f6c5761db24249c610c94d6e44d5505a0ba was included in upstream stable version 4.18.13, and was backported to bionic in 4.15.0-58.64 by LP #1836426. This patch required minor backporting for 4.4, by slightly adjusting the context in the final patch hunk. [Testcase] - You can reproduce this by adding the following iptables rule: + You can reproduce this by adding the following iptables rule to the + mangle table: -A POSTROUTING -p tcp -m tcp --sport 80 -j CHECKSUM --checksum-fill - and running traffic over port 80. + and running traffic over port 80 with incorrect checksums in the ip + header. I built a test kernel, which is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf216537-test For unpatched kernels, this causes the process which was handeling the socket to crash, as seen by haproxy crashing on a node in production which hits this issue. On patched kernels you see the warning printed to dmesg and no crashes occur. [Regression Potential] The changes are limited only to users which have CHECKSUM rules enabled in their iptables configs. Openstack commonly configures such rules on deployment, even though they are not necessary, as almost all packets have their checksum calculated by NICs these days, and CHECKSUM is only around to service old dhcp clients which would discard UDP packets with empty checksums. This commit was selected for upstream -stable 4.18.13, and has made its way into bionic 4.15.0-58.64 by LP #1836426. There have been no reported problems and those kernels would have had sufficient testing with Openstack and its configured iptables rules. If any users are affected by regression, then they can simply delete any CHECKSUM entries in their iptables configs. -- 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/1840619 Title: skb_warn_bad_offload kernel splat due to CHECKSUM target not compatible with GSO skbs Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: In Progress Bug
[Kernel-packages] [Bug 1840854] 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 1840854 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 ** Tags added: 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/1840854 Title: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1840854 [Impact] On machines equipped with Mellanox NIC's, in this particular case, Mellanox 5 series NICs using the mlx5_core driver, after installing 4.15.0-56 or later there is the following kernel splat: bond0: hw csum failure CPU: 63 PID: 2473 Comm: in:imklog Tainted: P OE 4.15.0-58-generic #64~16.04.1-Ubuntu Call Trace: dump_stack+0x63/0x8b netdev_rx_csum_fault+0x38/0x40 __skb_checksum_complete+0xc0/0xd0 nf_ip_checksum+0xca/0xf0 tcp_error+0xe0/0x1a0 [nf_conntrack] ? tcp_v4_rcv+0x7c6/0xa70 nf_conntrack_in+0xde/0x520 [nf_conntrack] ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4] nf_hook_slow+0x48/0xd0 ? skb_send_sock+0x50/0x50 ip_rcv+0x30f/0x370 ? inet_del_offload+0x40/0x40 __netif_receive_skb_core+0x879/0xba0 ? tcp4_gro_receive+0x117/0x1b0 __netif_receive_skb+0x18/0x60 ? __netif_receive_skb+0x18/0x60 netif_receive_skb_internal+0x45/0xf0 napi_gro_receive+0xd0/0xf0 mlx5e_handle_rx_cqe_mpwrq+0x4a1/0x8a0 [mlx5_core] mlx5e_poll_rx_cq+0xc3/0x880 [mlx5_core] mlx5e_napi_poll+0x9b/0x280 [mlx5_core] net_rx_action+0x265/0x3b0 __do_softirq+0xf5/0x2a8 irq_exit+0xca/0xd0 do_IRQ+0x57/0xe0 common_interrupt+0x8c/0x8c In 4.15.0-56, a commit was added from upstream -stable that introduced an optimisation for checksumming packets which have had zero bytes padded to the end of the packet. commit 88078d98d1bb085d72af8437707279e203524fa5 Author: Eric Dumazet Date: Wed Apr 18 11:43:15 2018 -0700 subject: net: pskb_trim_rcsum() and CHECKSUM_COMPLETE are friends You can read it here: https://github.com/torvalds/linux/commit/88078d98d1bb085d72af8437707279e203524fa5 It was discussed in this bugzilla link: https://bugzilla.kernel.org/show_bug.cgi?id=201849 This commit causes problems with a number of NIC devices, including Mellanox. This is best described by the maintainer, Dimitris Michailidis: > > > MLNX devices have an issue with packets that are padded past the end of > > > the L3 payload with bytes that aren't all 0s. They use a mode of checksum > > > reporting which should be including the padding bytes but MLNX devices > > > leave those out. When the padding bytes aren't all 0 this omission causes > > > a checksum error. This device behavior has existed for a long time but it > > > has begun causing errors only this year. Before a padded packet had its > HW > > > checksum ignored so it wasn't material what HW had reported. More > recently > > > padded packet checksums started using the HW value and now it is > > > noticeable when that value isn't right. Now, some routers stick additional information in the zero padding section on occasion, which will change the hardware checksum. Since the hardware checksum was ignored until 4.15.0-56 with 88078d98d1bb085d72af8437707279e203524fa5, this wasn't an issue. But with the optimisation, we start running into trouble since the hardware checksums no longer match what the kernel is expecting. [Fix] This was fixed for Mellanox 4 and 5 series drivers recently. Mellanox 4: 74abc07dee613086f9c0ded9e263ddc959a6de04 https://github.com/torvalds/linux/commit/74abc07dee613086f9c0ded9e263ddc959a6de04 Mellanox 5: e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a https://github.com/torvalds/linux/commit/e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a This customer hit the issue with mlx5_core driver, so the fix is: commit e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a Author: Cong Wang Date: Mon Dec 3 22:14:04 2018 -0800 subject: net/mlx5e: Force CHECKSUM_UNNECESSARY for short ethernet frames This is actually present in 4.15.0-59, which is currently sitting in -proposed. The commits are a part of 4.9.156, 4.14.99, 4.19.21 upstream -stable releases, and have been pulled into bionic as a part of LP #1837664 [Testcase] Simply try and bring an interface up on a machine with Mellanox series 5
[Kernel-packages] [Bug 1840854] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs
The customer installed 4.15.0-59 from -proposed to a machine with Mellanox Ethernet CX4LX cards, using the mlx5_core kernel module. Checksums are now calculated correctly and the kernel spat does not occur when the devices are brought up. Marking this as verified. ** 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/1840854 Title: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs Status in linux package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1840854 [Impact] On machines equipped with Mellanox NIC's, in this particular case, Mellanox 5 series NICs using the mlx5_core driver, after installing 4.15.0-56 or later there is the following kernel splat: bond0: hw csum failure CPU: 63 PID: 2473 Comm: in:imklog Tainted: P OE 4.15.0-58-generic #64~16.04.1-Ubuntu Call Trace: dump_stack+0x63/0x8b netdev_rx_csum_fault+0x38/0x40 __skb_checksum_complete+0xc0/0xd0 nf_ip_checksum+0xca/0xf0 tcp_error+0xe0/0x1a0 [nf_conntrack] ? tcp_v4_rcv+0x7c6/0xa70 nf_conntrack_in+0xde/0x520 [nf_conntrack] ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4] nf_hook_slow+0x48/0xd0 ? skb_send_sock+0x50/0x50 ip_rcv+0x30f/0x370 ? inet_del_offload+0x40/0x40 __netif_receive_skb_core+0x879/0xba0 ? tcp4_gro_receive+0x117/0x1b0 __netif_receive_skb+0x18/0x60 ? __netif_receive_skb+0x18/0x60 netif_receive_skb_internal+0x45/0xf0 napi_gro_receive+0xd0/0xf0 mlx5e_handle_rx_cqe_mpwrq+0x4a1/0x8a0 [mlx5_core] mlx5e_poll_rx_cq+0xc3/0x880 [mlx5_core] mlx5e_napi_poll+0x9b/0x280 [mlx5_core] net_rx_action+0x265/0x3b0 __do_softirq+0xf5/0x2a8 irq_exit+0xca/0xd0 do_IRQ+0x57/0xe0 common_interrupt+0x8c/0x8c In 4.15.0-56, a commit was added from upstream -stable that introduced an optimisation for checksumming packets which have had zero bytes padded to the end of the packet. commit 88078d98d1bb085d72af8437707279e203524fa5 Author: Eric Dumazet Date: Wed Apr 18 11:43:15 2018 -0700 subject: net: pskb_trim_rcsum() and CHECKSUM_COMPLETE are friends You can read it here: https://github.com/torvalds/linux/commit/88078d98d1bb085d72af8437707279e203524fa5 It was discussed in this bugzilla link: https://bugzilla.kernel.org/show_bug.cgi?id=201849 This commit causes problems with a number of NIC devices, including Mellanox. This is best described by the maintainer, Dimitris Michailidis: > > > MLNX devices have an issue with packets that are padded past the end of > > > the L3 payload with bytes that aren't all 0s. They use a mode of checksum > > > reporting which should be including the padding bytes but MLNX devices > > > leave those out. When the padding bytes aren't all 0 this omission causes > > > a checksum error. This device behavior has existed for a long time but it > > > has begun causing errors only this year. Before a padded packet had its > HW > > > checksum ignored so it wasn't material what HW had reported. More > recently > > > padded packet checksums started using the HW value and now it is > > > noticeable when that value isn't right. Now, some routers stick additional information in the zero padding section on occasion, which will change the hardware checksum. Since the hardware checksum was ignored until 4.15.0-56 with 88078d98d1bb085d72af8437707279e203524fa5, this wasn't an issue. But with the optimisation, we start running into trouble since the hardware checksums no longer match what the kernel is expecting. [Fix] This was fixed for Mellanox 4 and 5 series drivers recently. Mellanox 4: 74abc07dee613086f9c0ded9e263ddc959a6de04 https://github.com/torvalds/linux/commit/74abc07dee613086f9c0ded9e263ddc959a6de04 Mellanox 5: e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a https://github.com/torvalds/linux/commit/e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a This customer hit the issue with mlx5_core driver, so the fix is: commit e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a Author: Cong Wang Date: Mon Dec 3 22:14:04 2018 -0800 subject: net/mlx5e: Force CHECKSUM_UNNECESSARY for short ethernet frames This is actually present in 4.15.0-59, which is currently sitting in -proposed. The commits are a part of 4.9.156, 4.14.99, 4.19.21 upstream -stable releases, and have been pulled into bionic as a part of LP #1837664 [Testcase] Simply try and bring an interface up on a machine with Mellanox series 5 NICs. When a packet comes through which is smaller than required and padding is added, the problem will be triggered. The 4.15.0-59 from -proposed has been tested by the customer, and resolves the issue. [Regression Potential] This patch has a low chance of regression since it fixes a regression introduced by
[Kernel-packages] [Bug 1840854] [NEW] mlx5_core reports hardware checksum error for padded packets on Mellanox NICs
Public bug reported: BugLink: https://bugs.launchpad.net/bugs/1840854 [Impact] On machines equipped with Mellanox NIC's, in this particular case, Mellanox 5 series NICs using the mlx5_core driver, after installing 4.15.0-56 or later there is the following kernel splat: bond0: hw csum failure CPU: 63 PID: 2473 Comm: in:imklog Tainted: P OE 4.15.0-58-generic #64~16.04.1-Ubuntu Call Trace: dump_stack+0x63/0x8b netdev_rx_csum_fault+0x38/0x40 __skb_checksum_complete+0xc0/0xd0 nf_ip_checksum+0xca/0xf0 tcp_error+0xe0/0x1a0 [nf_conntrack] ? tcp_v4_rcv+0x7c6/0xa70 nf_conntrack_in+0xde/0x520 [nf_conntrack] ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4] nf_hook_slow+0x48/0xd0 ? skb_send_sock+0x50/0x50 ip_rcv+0x30f/0x370 ? inet_del_offload+0x40/0x40 __netif_receive_skb_core+0x879/0xba0 ? tcp4_gro_receive+0x117/0x1b0 __netif_receive_skb+0x18/0x60 ? __netif_receive_skb+0x18/0x60 netif_receive_skb_internal+0x45/0xf0 napi_gro_receive+0xd0/0xf0 mlx5e_handle_rx_cqe_mpwrq+0x4a1/0x8a0 [mlx5_core] mlx5e_poll_rx_cq+0xc3/0x880 [mlx5_core] mlx5e_napi_poll+0x9b/0x280 [mlx5_core] net_rx_action+0x265/0x3b0 __do_softirq+0xf5/0x2a8 irq_exit+0xca/0xd0 do_IRQ+0x57/0xe0 common_interrupt+0x8c/0x8c In 4.15.0-56, a commit was added from upstream -stable that introduced an optimisation for checksumming packets which have had zero bytes padded to the end of the packet. commit 88078d98d1bb085d72af8437707279e203524fa5 Author: Eric Dumazet Date: Wed Apr 18 11:43:15 2018 -0700 subject: net: pskb_trim_rcsum() and CHECKSUM_COMPLETE are friends You can read it here: https://github.com/torvalds/linux/commit/88078d98d1bb085d72af8437707279e203524fa5 It was discussed in this bugzilla link: https://bugzilla.kernel.org/show_bug.cgi?id=201849 This commit causes problems with a number of NIC devices, including Mellanox. This is best described by the maintainer, Dimitris Michailidis: > > > MLNX devices have an issue with packets that are padded past the end of > > > the L3 payload with bytes that aren't all 0s. They use a mode of checksum > > > reporting which should be including the padding bytes but MLNX devices > > > leave those out. When the padding bytes aren't all 0 this omission causes > > > a checksum error. This device behavior has existed for a long time but it > > > has begun causing errors only this year. Before a padded packet had its > HW > > > checksum ignored so it wasn't material what HW had reported. More > recently > > > padded packet checksums started using the HW value and now it is > > > noticeable when that value isn't right. Now, some routers stick additional information in the zero padding section on occasion, which will change the hardware checksum. Since the hardware checksum was ignored until 4.15.0-56 with 88078d98d1bb085d72af8437707279e203524fa5, this wasn't an issue. But with the optimisation, we start running into trouble since the hardware checksums no longer match what the kernel is expecting. [Fix] This was fixed for Mellanox 4 and 5 series drivers recently. Mellanox 4: 74abc07dee613086f9c0ded9e263ddc959a6de04 https://github.com/torvalds/linux/commit/74abc07dee613086f9c0ded9e263ddc959a6de04 Mellanox 5: e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a https://github.com/torvalds/linux/commit/e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a This customer hit the issue with mlx5_core driver, so the fix is: commit e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a Author: Cong Wang Date: Mon Dec 3 22:14:04 2018 -0800 subject: net/mlx5e: Force CHECKSUM_UNNECESSARY for short ethernet frames This is actually present in 4.15.0-59, which is currently sitting in -proposed. The commits are a part of 4.9.156, 4.14.99, 4.19.21 upstream -stable releases, and have been pulled into bionic as a part of LP #1837664 [Testcase] Simply try and bring an interface up on a machine with Mellanox series 5 NICs. When a packet comes through which is smaller than required and padding is added, the problem will be triggered. The 4.15.0-59 from -proposed has been tested by the customer, and resolves the issue. [Regression Potential] This patch has a low chance of regression since it fixes a regression introduced by 88078d98d1bb085d72af8437707279e203524fa5 in 4.15.0-56. The changes are limited to mlx5_core driver, and have been well tested and accepted by the community due to their selection for upstream -stable. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Matthew Ruffell (mruffell) Status: Fix Committed ** Tags: sts verification-done-bionic ** Description changed: - BugLink: https://bugs.launchpad.net/bugs/ + BugLink: https://bugs.launchpad.net/bugs/1840854 [Impact] On machines equipped with Mellanox NIC's, in this particular case, Mellanox 5 series NICs using the mlx5_core driver, after installing 4.15.0-56 or later there is the following kernel splat: bond0: hw csum failure CPU: 63 PID: 2473 Comm: in:imklog
[Kernel-packages] [Bug 1840004] Re: xenial/linux-deeplens: 4.15.0-1006.6 -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: 1840005 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Promote to Proposed phase-changed: Tuesday, 20. August 2019 10:40 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review 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/1840004 Title: xenial/linux-deeplens: 4.15.0-1006.6 -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: Confirmed 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: 1840005 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Ready for Promote to Proposed phase-changed: Tuesday, 20. August 2019 10:40 UTC reason: promote-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840004/+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 1581711] Re: 024C:B723 Need support for Realtek Wifi card rtl8723bs
With 19 more months of support for 16.04 (and the 4.4 kernel), consider the 8723bs drivers in the trusty-chestersmill repository ( http://oem.archive.canonical.com/updates/ trusty-chestersmill public) These drivers worked fine through the Ubuntu 4.4.0-142 release (when the API change broke many drivers). The fix for that problem may be much simpler than changing the lwfinger or hadess drivers. Note, bug 1755309 for the header fix necessary for the audio packages from that repo. -- 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/1581711 Title: 024C:B723 Need support for Realtek Wifi card rtl8723bs Status in HWE Next: Won't Fix Status in HWE Next xenial series: Won't Fix Status in linux package in Ubuntu: Fix Released Bug description: This device is appearing in some OEM machines. WORKAROUND: sudo apt-get install build-essential linux-headers-generic git git clone https://github.com/hadess/rtl8723as.git cd rtl8723as make sudo make install sudo depmod -a sudo modprobe r8723bs cat /sys/bus/sdio/devices/mmc1:0001:1/* 0x07 0xb723 cat: '/sys/bus/sdio/devices/mmc1:0001:1/firmware_node': Is a directory sdio:c07v024CdB723 cat: '/sys/bus/sdio/devices/mmc1:0001:1/power': Is a directory cat: '/sys/bus/sdio/devices/mmc1:0001:1/subsystem': Is a directory SDIO_CLASS=07 SDIO_ID=024C:B723 MODALIAS=sdio:c07v024CdB723 0x024c WORKAROUND 2: Install this DKMS driver package: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581711/+attachment/4732838/+files /rtl8723bs-dkms_4.4.1+17245.20160325.2_all.deb --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e59c3a84-25cb-4931-887e-13ab29829963 InstallationDate: Installed on 2016-05-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:73f4 Synaptics, Inc. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer One S1002 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mmcblk0p2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10 dmi.board.name: Popcorn dmi.board.vendor: Acer dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd10/20/2015:svnAcer:pnOneS1002:pvr1.10:rvnAcer:rnPopcorn:rvrTobefilledbyO.E.M.:cvnAcer:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: One S1002 dmi.product.version: 1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1581711/+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 1581711] Re: 024C:B723 Need support for Realtek Wifi card rtl8723bs
With 19 more months of support for 16.04 (and the 4.4 kernel), consider the 8723bs drivers in the trusty-chestersmill repository ( http://oem.archive.canonical.com/updates/ trusty-chestersmill public) These drivers worked fine through the Ubuntu 4.4.0-142 release (when the API change broke many drivers). The fix for that problem may be much simpler than changing the lwfinger or hadess drivers. Note, bug 175309 for the header fix necessary for the audio packages from that repo. -- 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/1581711 Title: 024C:B723 Need support for Realtek Wifi card rtl8723bs Status in HWE Next: Won't Fix Status in HWE Next xenial series: Won't Fix Status in linux package in Ubuntu: Fix Released Bug description: This device is appearing in some OEM machines. WORKAROUND: sudo apt-get install build-essential linux-headers-generic git git clone https://github.com/hadess/rtl8723as.git cd rtl8723as make sudo make install sudo depmod -a sudo modprobe r8723bs cat /sys/bus/sdio/devices/mmc1:0001:1/* 0x07 0xb723 cat: '/sys/bus/sdio/devices/mmc1:0001:1/firmware_node': Is a directory sdio:c07v024CdB723 cat: '/sys/bus/sdio/devices/mmc1:0001:1/power': Is a directory cat: '/sys/bus/sdio/devices/mmc1:0001:1/subsystem': Is a directory SDIO_CLASS=07 SDIO_ID=024C:B723 MODALIAS=sdio:c07v024CdB723 0x024c WORKAROUND 2: Install this DKMS driver package: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581711/+attachment/4732838/+files /rtl8723bs-dkms_4.4.1+17245.20160325.2_all.deb --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=e59c3a84-25cb-4931-887e-13ab29829963 InstallationDate: Installed on 2016-05-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:73f4 Synaptics, Inc. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer One S1002 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mmcblk0p2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 RelatedPackageVersions: linux-restricted-modules-4.4.0-22-generic N/A linux-backports-modules-4.4.0-22-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.4.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.10 dmi.board.name: Popcorn dmi.board.vendor: Acer dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.10:bd10/20/2015:svnAcer:pnOneS1002:pvr1.10:rvnAcer:rnPopcorn:rvrTobefilledbyO.E.M.:cvnAcer:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: One S1002 dmi.product.version: 1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1581711/+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 1840846] Re: Disco update: upstream stable patchset 2019-08-20
** 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: + upstream stable patchset 2019-08-20 -upstream stable patchset 2019-08-20 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.19.60, v5.1.19, + v4.19.61, v5.1.20 + + from git://git.kernel.org/ ** Description changed: 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: upstream stable patchset 2019-08-20 - Ported from the following upstream stable releases: - v4.19.60, v5.1.19, - v4.19.61, v5.1.20 + Ported from the following upstream stable releases: + v4.19.60, v5.1.19, + v4.19.61, v5.1.20 from git://git.kernel.org/ + + Revert "e1000e: fix cyclic resets at link up with active tx" + e1000e: start network tx queue only when link is up + Input: synaptics - enable SMBUS on T480 thinkpad trackpad + nilfs2: do not use unexported cpu_to_le32()/le32_to_cpu() in uapi header + drivers: base: cacheinfo: Ensure cpu hotplug work is done before Intel RDT + firmware: improve LSM/IMA security behaviour + irqchip/gic-v3-its: Fix command queue pointer comparison bug + clk: ti: clkctrl: Fix returning uninitialized data + efi/bgrt: Drop BGRT status field reserved bits check + perf/core: Fix perf_sample_regs_user() mm check + ARM: dts: gemini Fix up DNS-313 compatible string + ARM: omap2: remove incorrect __init annotation + afs: Fix uninitialised spinlock afs_volume::cb_break_lock + x86/apic: Fix integer overflow on 10 bit left shift of cpu_khz + be2net: fix link failure after ethtool offline test + ppp: mppe: Add softdep to arc4 + sis900: fix TX completion + ARM: dts: imx6ul: fix PWM[1-4] interrupts + pinctrl: mcp23s08: Fix add_data and irqchip_add_nested call order + dm table: don't copy from a NULL pointer in realloc_argv() + dm verity: use message limit for data block corruption message + x86/boot/64: Fix crash if kernel image crosses page table boundary + x86/boot/64: Add missing fixup_pointer() for next_early_pgt access + HID: chicony: add another quirk for PixArt mouse + pinctrl: mediatek: Ignore interrupts that are wake only during resume + cpu/hotplug: Fix out-of-bounds read when setting fail state + pinctrl: mediatek: Update cur_mask in mask/mask ops + linux/kernel.h: fix overflow for DIV_ROUND_UP_ULL + genirq: Delay deactivation in free_irq() + genirq: Fix misleading synchronize_irq() documentation + genirq: Add optional hardware synchronization for shutdown + x86/ioapic: Implement irq_get_irqchip_state() callback + x86/irq: Handle spurious interrupt after shutdown gracefully + x86/irq: Seperate unused system vectors from spurious entry again + ARC: hide unused function unw_hdr_alloc + s390: fix stfle zero padding + s390/qdio: (re-)initialize tiqdio list entries + s390/qdio: don't touch the dsci in tiqdio_add_input_queues() + crypto: talitos - move struct talitos_edesc into talitos.h + crypto: talitos - fix hash on SEC1. + crypto/NX: Set receive window credits to max number of CRBs in RxFIFO + drm/udl: introduce a macro to convert dev to udl. + drm/udl: move to embedding drm device inside udl device. + x86/entry/32: Fix ENDPROC of common_spurious + irqchip/irq-csky-mpintc: Support auto irq deliver to all cpus + arm64: dts: ls1028a: Fix CPU idle fail. + selftests/powerpc: Add test of fork with mapping above 512TB + x86/efi: fix a -Wtype-limits compilation warning + pinctrl: ocelot: fix gpio direction for pins after 31 + pinctrl: ocelot: fix pinmuxing for pins after 31 + mm/oom_kill.c:
[Kernel-packages] [Bug 1840847] 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 1840847 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/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) Status in cpuinfo package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: From bug: https://bugs.launchpad.net/bugs/1840511 clockhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpuinfo/+bug/1840847/+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 1840847] [NEW] cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr)
Public bug reported: >From bug: https://bugs.launchpad.net/bugs/1840511 clockhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) >From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32; #endif #else static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) /* * sched.h is only used for CPU_SETSIZE constant. * Android NDK headers before platform 21 do have this constant in sched.h */ #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? ** Affects: cpuinfo (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: From bug: https://bugs.launchpad.net/bugs/1840511 - clockhouse test started failing because of the presence of stderr + clockhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) - /* - * Android NDK headers before platform 21 do not define CPU_SETSIZE, - * so we hard-code its value, as defined in platform 21 headers - */ - #if defined(__LP64__) - static const uint32_t default_max_processors_count = 1024; - #else - static const uint32_t default_max_processors_count = 32; - #endif + /* + * Android NDK headers before platform 21 do not define CPU_SETSIZE, + * so we hard-code its value, as defined in platform 21 headers + */ + #if defined(__LP64__) + static const uint32_t default_max_processors_count = 1024; + #else + static const uint32_t default_max_processors_count = 32; + #endif #else - static const uint32_t default_max_processors_count = CPU_SETSIZE; + static const uint32_t default_max_processors_count = CPU_SETSIZE; #endif #if !defined(__ANDROID__) - /* - * sched.h is only used for CPU_SETSIZE constant. - * Android NDK headers before platform 21 do have this constant in sched.h - */ - #include + /* + * sched.h is only used for CPU_SETSIZE constant. + * Android NDK headers before platform 21 do have this constant in sched.h + */ + #include #endif and resolving includes: x86_64-linux-gnu/bits/cpu-set.h: /* Size definition for CPU sets. */ #define __CPU_SETSIZE 1024 And the warning: Warning in cpuinfo: kernel_max value of 8191 parsed from /sys/devices/system/cpu/kernel_max exceeds platform-default limit 1023 Will always be displayed in Ubuntu OS, when it should NOT (does not make any sense to trigger a warning for something that can't be changed). Should ubuntu update sched.h and/or cpu-set.h to reflect its decision in using 8192 max CPUs ? -- 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/1840847 Title: cpuinfo_linux_get_max_processors_count always warns Ubuntu default MAX cpu values (stderr) Status in cpuinfo package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: From bug: https://bugs.launchpad.net/bugs/1840511 clockhouse builds test started failing because of the presence of stderr whenever using the function: cpuinfo_linux_get_max_processors_count(void) From cpuid library. This happens because: #if defined(__ANDROID__) && !defined(CPU_SETSIZE) /* * Android NDK headers before platform 21 do not define CPU_SETSIZE, * so we hard-code its value, as defined in platform 21 headers */ #if defined(__LP64__) static const uint32_t default_max_processors_count = 1024; #else static const uint32_t default_max_processors_count = 32;
[Kernel-packages] [Bug 1840810] Re: disco/linux-kvm: 5.0.0-1015.16 -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: 1840816 packages: main: linux-kvm meta: linux-meta-kvm - phase: Ready for Packaging - phase-changed: Tuesday, 20. August 2019 20:12 UTC + phase: Packaging + phase-changed: Tuesday, 20. August 2019 21:15 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1840810 Title: disco/linux-kvm: 5.0.0-1015.16 -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 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 verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1840816 packages: main: linux-kvm meta: linux-meta-kvm phase: Packaging phase-changed: Tuesday, 20. August 2019 21:15 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840810/+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 1840846] Re: Disco update: upstream stable patchset 2019-08-20
** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1840846 Title: Disco update: upstream stable patchset 2019-08-20 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: 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: upstream stable patchset 2019-08-20 Ported from the following upstream stable releases: v4.19.60, v5.1.19, v4.19.61, v5.1.20 from git://git.kernel.org/ Revert "e1000e: fix cyclic resets at link up with active tx" e1000e: start network tx queue only when link is up Input: synaptics - enable SMBUS on T480 thinkpad trackpad nilfs2: do not use unexported cpu_to_le32()/le32_to_cpu() in uapi header drivers: base: cacheinfo: Ensure cpu hotplug work is done before Intel RDT firmware: improve LSM/IMA security behaviour irqchip/gic-v3-its: Fix command queue pointer comparison bug clk: ti: clkctrl: Fix returning uninitialized data efi/bgrt: Drop BGRT status field reserved bits check perf/core: Fix perf_sample_regs_user() mm check ARM: dts: gemini Fix up DNS-313 compatible string ARM: omap2: remove incorrect __init annotation afs: Fix uninitialised spinlock afs_volume::cb_break_lock x86/apic: Fix integer overflow on 10 bit left shift of cpu_khz be2net: fix link failure after ethtool offline test ppp: mppe: Add softdep to arc4 sis900: fix TX completion ARM: dts: imx6ul: fix PWM[1-4] interrupts pinctrl: mcp23s08: Fix add_data and irqchip_add_nested call order dm table: don't copy from a NULL pointer in realloc_argv() dm verity: use message limit for data block corruption message x86/boot/64: Fix crash if kernel image crosses page table boundary x86/boot/64: Add missing fixup_pointer() for next_early_pgt access HID: chicony: add another quirk for PixArt mouse pinctrl: mediatek: Ignore interrupts that are wake only during resume cpu/hotplug: Fix out-of-bounds read when setting fail state pinctrl: mediatek: Update cur_mask in mask/mask ops linux/kernel.h: fix overflow for DIV_ROUND_UP_ULL genirq: Delay deactivation in free_irq() genirq: Fix misleading synchronize_irq() documentation genirq: Add optional hardware synchronization for shutdown x86/ioapic: Implement irq_get_irqchip_state() callback x86/irq: Handle spurious interrupt after shutdown gracefully x86/irq: Seperate unused system vectors from spurious entry again ARC: hide unused function unw_hdr_alloc s390: fix stfle zero padding s390/qdio: (re-)initialize tiqdio list entries s390/qdio: don't touch the dsci in tiqdio_add_input_queues() crypto: talitos - move struct talitos_edesc into talitos.h crypto: talitos - fix hash on SEC1. crypto/NX: Set receive window credits to max number of CRBs in RxFIFO drm/udl: introduce a macro to convert dev to udl. drm/udl: move to embedding drm device inside udl device. x86/entry/32: Fix ENDPROC of common_spurious irqchip/irq-csky-mpintc: Support auto irq deliver to all cpus arm64: dts: ls1028a: Fix CPU idle fail. selftests/powerpc: Add test of fork with mapping above 512TB x86/efi: fix a -Wtype-limits compilation warning pinctrl: ocelot: fix gpio direction for pins after 31 pinctrl: ocelot: fix pinmuxing for pins after 31 mm/oom_kill.c: fix uninitialized oc->constraint fork,memcg: alloc_thread_stack_node needs to set tsk->stack UBUNTU: upstream stable to v4.19.60, v5.1.19 MIPS: ath79: fix ar933x uart parity mode MIPS: fix build on non-linux hosts arm64/efi: Mark __efistub_stext_offset as an absolute symbol explicitly scsi: iscsi: set auth_protocol back to NULL if CHAP_A value is not supported dmaengine: imx-sdma: fix use-after-free on probe error path wil6210: fix potential out-of-bounds read ath10k: Do not send probe response template for mesh ath9k: Check for errors when reading SREV register ath6kl: add some bounds checking ath10k: add peer id check in ath10k_peer_find_by_id wil6210: fix spurious interrupts in 3-msi ath: DFS JP domain W56 fixed pulse type 3 RADAR detection regmap: debugfs: Fix memory leak in regmap_debugfs_init batman-adv: fix for leaked TVLV handler. media: dvb: usb: fix use after free in dvb_usb_device_exit media: spi: IR LED:
[Kernel-packages] [Bug 1840810] Re: disco/linux-kvm: 5.0.0-1015.16 -proposed tracker
** Summary changed: - disco/linux-kvm: -proposed tracker + disco/linux-kvm: 5.0.0-1015.16 -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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1840810 Title: disco/linux-kvm: 5.0.0-1015.16 -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 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 verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1840816 packages: main: linux-kvm meta: linux-meta-kvm phase: Packaging phase-changed: Tuesday, 20. August 2019 21:15 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840810/+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 1829749] Re: [MIR] Please add support for SIPL
** Changed in: linux-signed (Ubuntu)
Status: New => Fix Committed
--
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/1829749
Title:
[MIR] Please add support for SIPL
Status in Launchpad itself:
Fix Released
Status in linux package in Ubuntu:
Fix Committed
Status in linux-signed package in Ubuntu:
Fix Committed
Status in s390-tools package in Ubuntu:
Fix Released
Status in s390-tools-signed package in Ubuntu:
Fix Released
Bug description:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1829749/+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 1840803] Re: disco/linux-azure: 5.0.0-1018.19 -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 backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Packaging - phase-changed: Tuesday, 20. August 2019 20:12 UTC + phase: Packaging + phase-changed: Tuesday, 20. August 2019 21: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 trackers: bionic/linux-azure: bug 1840802 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/1840803 Title: disco/linux-azure: 5.0.0-1018.19 -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 backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Tuesday, 20. August 2019 21: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 trackers: bionic/linux-azure: bug 1840802 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840803/+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 1840846] [NEW] Disco update: upstream stable patchset 2019-08-20
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: upstream stable patchset 2019-08-20 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Disco) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) 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 Disco) Importance: Undecided Status: New -- 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/1840846 Title: Disco update: upstream stable patchset 2019-08-20 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: 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: upstream stable patchset 2019-08-20 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840846/+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 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
I've verified that disco-proposed linux-virtual kernel succeeds our test-case (curtin-nvme). I've 50 installs with no issue. root@ubuntu:~# apt-cache policy linux-virtual linux-virtual: Installed: 5.0.0.26.27 Candidate: 5.0.0.26.27 Version table: *** 5.0.0.26.27 500 500 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.0.0.25.26 500 500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 5.0.0.13.14 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages root@ubuntu:~# uname -r 5.0.0-26-generic root@ubuntu:~# lsb_release -rd Description:Ubuntu 19.04 Release:19.04 ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- 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/1784665 Title: bcache: bch_allocator_thread(): hung task timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] bcache_allocator() can call the following: bch_allocator_thread() -> bch_prio_write() -> bch_bucket_alloc() -> wait on >set->bucket_wait But the wake up event on bucket_wait is supposed to come from bch_allocator_thread() itself causing a deadlock. [Test Case] This is a simple script that can easily trigger the deadlock condition: https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh A better test case has been also provided in bug 1796292 (duplicate of this bug): https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh [Fix] Fix by making the call to bch_prio_write() non-blocking, so that bch_allocator_thread() never waits on itself. Moreover, make sure to wake up the garbage collector thread when bch_prio_write() is failing to allocate buckets to increase the chance of freeing up more buckets. In addition to that it would be safe to also import other upstream bcache fixes (all clean cherry picks): 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock in cached_def_free() 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire bch_register_lock later in cached_dev_free() ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace bch_read_string_list() by __sysfs_match_string() ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of functions to sysfs.c 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string arrays to sysfs.c 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning in bcache_device_init() 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of sparse complaints about lock imbalances 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings about set-but-not-used variables f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused variable 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch fall-through 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation to __bch_check_keys() fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop variable in memory shrink f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value in memory shrink 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs output value of strip size 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform duplicated CACHE_SET_IO_DISABLE set c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy during journal a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target calc on large devices 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot() 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a discard operation [Regression Potential] The upstream fixes are all clean cherry picks from stable (most of them are small cleanups), so regression potential is minimal. The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in bcache_allocator()" that is addressing the main deadlock bug (that seems to be a mainline bug - not fixed yet). We should spend more time trying to reproduce this deadlock with a mainline
[Kernel-packages] [Bug 1840395] Re: reboot will introduce an alarm 'beep ...' during BIOS phase
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed -- 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/1840395 Title: reboot will introduce an alarm 'beep ...' during BIOS phase Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Committed Bug description: Since this fix is still in the maintainer's tree, I add the UBUNTU: SAUCE: prefix in the patch title. And this patchset is fixing a bug in the oem project, so please merge the patchset to OEM-B asap. [Impact] We often hear the Beep noise when a couple of LENOVO laptops reboot, the reproduce rate is about 3/10. [Fix] make the codec enter D3 before rebooting or poweroff, this can fix the issue. [Test Case] Tested on those LENOVO latpops, reboot 50 times, didn't reproduce the noise issue. [Regression Risk] Low. We tested this patch on different lenovo and dell laptops, they all worked well as bfore. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1840395/+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 1840075] Re: Goodix touchpad may drop first input event
** Changed in: linux (Ubuntu Eoan) Status: Incomplete => Fix Committed -- 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/1840075 Title: Goodix touchpad may drop first input event Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Incomplete Status in linux source package in Disco: Incomplete Status in linux source package in Eoan: Fix Committed Bug description: [Impact] If a touchpad is connected to Intel LPSS PCI device, sometimes the first tap event can be dropped. Goodix touchpad has a rather small buffer so the time its parent devices spend in resuming need to be small. [Fix] Remove Intel LPSS D3cold delay, which is the bottleneck of the situation. [Test] Intel had tested the patch and the result is positive. [Regression Potential] Low. Intel internally tested this so it should be rather safe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840075/+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 1826716] Re: Include Sunix serial/parallel driver
** Changed in: linux (Ubuntu Eoan) Status: Incomplete => Fix Committed -- 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/1826716 Title: Include Sunix serial/parallel driver Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid 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 source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Bug description: [Impact] We shipped several platform with sunix device, which is enabled by sunix DKMS driver. We should use in-tree driver instead. [Fix] Backport in-tree Sunix driver. [Test] Sunix test it on all their devices and they confirmed it works. [Regression Potential] Low. It's a new driver so the regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1826716/+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 1837223] Re: shiftfs: add O_DIRECT support
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- 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/1837223 Title: shiftfs: add O_DIRECT support Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: Currently shiftfs does not handle O_DIRECT if the underlay supports it. This is blocking dqlite - an essential part of LXD - from profiting from the performance benefits of O_DIRECT on suitable filesystems when used with async io such as aio or io_uring. Regression Potential: Limited to shiftfs and virtually none since we have not supported this feature before. Test Case: Run LXD with dqlite on a kernel that has support for shiftfs with O_DIRECT. Target Kernels: All LTS kernels with shiftfs support. Patches: https://github.com/brauner/ubuntu-disco/tree/shiftfs_direct_io To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837223/+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 1831482] Re: VIMC module not available (CONFIG_VIDEO_VIMC not set)
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- 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/1831482 Title: VIMC module not available (CONFIG_VIDEO_VIMC not set) Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: Fix Committed Bug description: == SRU Justification == VIMC is a virtual media controller that can emulate a real media device. This is useful for automated tests, and development of multimedia frameworks. == Fix == Enable VIMC as a module in B/D/E kernel configs. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1831482-cfg-vimc/ User has reported that the Eoan kernel works as expected. I have also smoke tested the B/D kernel to make sure the VIMC modules can be loaded properly. == Regression Potential == Low, this patchset enables the VIMC module support, we might see some bug reports against this module in the future. However the acutal impact for a non-vimc user should be minimum. There is a null pointer deference issue was found while inserting the vimc module on some system (lp:1840028), it will be handled in that bug. == Original Bug report == The Multimedia VIMC module provides a test interface for the linux-media media controller framework. This is useful for automated tests, and development of multimedia frameworks. Other components similar to this such as VIVID (CONFIG_VIDEO_VIVID=m) are enabled, but VIMC is missing from the linux-modules packages: $ grep VIMC /boot/config-* /boot/config-4.15.0-32-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.17.9-041709-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.4-041804-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.7-041807-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-13-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-15-generic:# CONFIG_VIDEO_VIMC is not set Could this be enabled in future releases as a module please? I'm running Ubuntu 19.04, with Ubuntu 5.0.0-13.14-generic 5.0.6, however I believe this issue affects all current Ubuntu kernel releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831482/+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 1837231] Re: UBUNTU: SAUCE: shiftfs: pass correct point down
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- 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/1837231 Title: UBUNTU: SAUCE: shiftfs: pass correct point down Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: In Progress Bug description: SRU Justification Impact: shiftfs is currently passing down an unsigned long to copy_from_user() which expects a void __user * pointer. This will cause the compiler to complain because of mismatching types and in general is rather ugly. Regression Potential: Limited to shiftfs. Test Case: Compile kernel with patch and see that compiler does not complain anymore. Target Kernels: All LTS kernels with shiftfs support. Patches: https://github.com/brauner/ubuntu-disco/tree/shiftfs_direct_io To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837231/+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 1829749] Re: [MIR] Please add support for SIPL
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
--
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/1829749
Title:
[MIR] Please add support for SIPL
Status in Launchpad itself:
Fix Released
Status in linux package in Ubuntu:
Fix Committed
Status in linux-signed package in Ubuntu:
Fix Committed
Status in s390-tools package in Ubuntu:
Fix Released
Status in s390-tools-signed package in Ubuntu:
Fix Released
Bug description:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2+
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1829749/+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 1839622] Re: enable lockdown on s390x when Secure IPL is performed
** Changed in: linux (Ubuntu) Status: Triaged => Fix Committed -- 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/1839622 Title: enable lockdown on s390x when Secure IPL is performed Status in linux package in Ubuntu: Fix Committed Bug description: s390x support secureboot via secure IPL mechanism. When booted with Secure IPL, lock-down should be enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839622/+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 1840803] Re: disco/linux-azure: 5.0.0-1018.19 -proposed tracker
** Summary changed: - disco/linux-azure: -proposed tracker + disco/linux-azure: 5.0.0-1018.19 -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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) -- 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/1840803 Title: disco/linux-azure: 5.0.0-1018.19 -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 backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Tuesday, 20. August 2019 21: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 trackers: bionic/linux-azure: bug 1840802 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840803/+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 1840808] Re: disco/linux-gcp: 5.0.0-1015.15 -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 backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Ready for Packaging - phase-changed: Tuesday, 20. August 2019 20:12 UTC + phase: Packaging + phase-changed: Tuesday, 20. August 2019 20:50 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 trackers: bionic/linux-gcp: bug 1840806 bionic/linux-gke-5.0: bug 1840823 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/1840808 Title: disco/linux-gcp: 5.0.0-1015.15 -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 verification-testing series: New 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 backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Tuesday, 20. August 2019 20:50 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 trackers: bionic/linux-gcp: bug 1840806 bionic/linux-gke-5.0: bug 1840823 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840808/+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 1840808] Re: disco/linux-gcp: 5.0.0-1015.15 -proposed tracker
** Summary changed: - disco/linux-gcp: -proposed tracker + disco/linux-gcp: 5.0.0-1015.15 -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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) -- 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/1840808 Title: disco/linux-gcp: 5.0.0-1015.15 -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 verification-testing series: New 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 backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Tuesday, 20. August 2019 20:50 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 trackers: bionic/linux-gcp: bug 1840806 bionic/linux-gke-5.0: bug 1840823 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840808/+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 1332764] Re: [Dell Studio 1458] Black (off) screen after waking from suspend
This problemes persist in Ubuntu 18.02 LTS in my notebook Dell Studio 1458 I dont have a solution -- 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/1332764 Title: [Dell Studio 1458] Black (off) screen after waking from suspend Status in linux package in Ubuntu: Expired Bug description: The laptop wakes up from suspend with a black screen i.e. screen not turned ON. The keyboard and mouse seems to be responsive as backlit turns ON if I click any key or touch track pad. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: atul 2085 F pulseaudio /dev/snd/controlC0: atul 2085 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 20 22:55:37 2014 HibernationDevice: RESUME=UUID=15f965f3-ae06-4b09-a249-61c32e50481e InstallationDate: Installed on 2014-04-19 (62 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Studio 1458 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=12be9505-0800-40e5-8928-e60118a8f0c2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0VF0FR dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A06 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/27/2010:svnDellInc.:pnStudio1458:pvrA06:rvnDellInc.:rn0VF0FR:rvrA06:cvnDellInc.:ct8:cvrA06: dmi.product.name: Studio 1458 dmi.product.version: A06 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1332764/+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 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
> Is there a BIOS update for your Dell? At the time I was running the latest BIOS, but a few days later an update appeared on Dell Support software (on Windows). I updated the BIOS and then I let Ubuntu update the microcode normally. It seems to work fine now with the latest microcode and no dis_ucode_ldr option at boot time. -- 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/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 WORKAROUND 3: upgrade BIOS Asus has released updated BIOSes, which probably include the newest microcode. After upgrading workarounds 1,2 are not needed. Please NOTE, unlike workarounds 1,2, BIOS upgrade is permanent and cannot be (easily) reverted. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage
[Kernel-packages] [Bug 1840800] Re: disco/linux-aws: -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 backports: bug 1840820 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-aws meta: linux-meta-aws - phase: Holding before Packaging - phase-changed: Tuesday, 20. August 2019 18:18 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 20. August 2019 20:12 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: bionic/linux-aws-edge: bug 1840820 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/1840800 Title: disco/linux-aws: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta 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 verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 backports: bug 1840820 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-aws meta: linux-meta-aws phase: Ready for Packaging phase-changed: Tuesday, 20. August 2019 20:12 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-aws-edge: bug 1840820 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840800/+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 1840808] Re: disco/linux-gcp: -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 backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Packaging - phase-changed: Tuesday, 20. August 2019 18:19 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 20. August 2019 20:12 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: bionic/linux-gcp: bug 1840806 bionic/linux-gke-5.0: bug 1840823 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/1840808 Title: disco/linux-gcp: -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: Confirmed 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 verification-testing series: New 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 backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Packaging phase-changed: Tuesday, 20. August 2019 20:12 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-gcp: bug 1840806 bionic/linux-gke-5.0: bug 1840823 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840808/+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 1840810] Re: disco/linux-kvm: -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: 1840816 packages: main: linux-kvm meta: linux-meta-kvm - phase: Holding before Packaging - phase-changed: Tuesday, 20. August 2019 18:19 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 20. August 2019 20:12 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1840810 Title: disco/linux-kvm: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta 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 verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1840816 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Packaging phase-changed: Tuesday, 20. August 2019 20:12 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840810/+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 1840811] Re: disco/linux-oracle: -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 backports: bug 1840826 (bionic/linux-oracle-edge) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Holding before Packaging - phase-changed: Tuesday, 20. August 2019 18:20 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 20. August 2019 20:13 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: bionic/linux-oracle-edge: bug 1840826 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1840811 Title: disco/linux-oracle: -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: Confirmed 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 verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 backports: bug 1840826 (bionic/linux-oracle-edge) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Ready for Packaging phase-changed: Tuesday, 20. August 2019 20:13 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-oracle-edge: bug 1840826 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840811/+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 1840816] Re: disco/linux: 5.0.0-27.28 -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 backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Tuesday, 20. August 2019 19:06 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 trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 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/1840816 Title: disco/linux: 5.0.0-27.28 -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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: In Progress 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 verification-testing series: New 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 backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Tuesday, 20. August 2019 19:06 UTC reason: prepare-package-lrm: Pending -- package not yet uploaded trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840816/+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 1840803] Re: 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 backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Packaging - phase-changed: Tuesday, 20. August 2019 18:19 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 20. August 2019 20:12 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: bionic/linux-azure: bug 1840802 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/1840803 Title: disco/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: Confirmed 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 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 backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Packaging phase-changed: Tuesday, 20. August 2019 20:12 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-azure: bug 1840802 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840803/+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 1840012] Re: xenial/linux-kvm: 4.4.0-1055.62 -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: 1840021 packages: main: linux-kvm meta: linux-meta-kvm phase: Signoff phase-changed: Friday, 16. August 2019 07:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- 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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1840012 Title: xenial/linux-kvm: 4.4.0-1055.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1840021 packages: main: linux-kvm meta: linux-meta-kvm phase: Signoff phase-changed: Friday, 16. August 2019 07: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 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840012/+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 1840016] Re: xenial/linux-snapdragon: 4.4.0-1123.129 -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 derivatives: bug 1840015 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840021 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 15. August 2019 18:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1840015 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1840016 Title: xenial/linux-snapdragon: 4.4.0-1123.129 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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 derivatives: bug 1840015 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840021 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 15. August 2019 18:16 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: xenial/linux-snapdragon/dragonboard-kernel: bug 1840015 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840016/+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 1840010] Re: xenial/linux-aws: 4.4.0-1091.102 -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 derivatives: bug 1840009 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840021 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 15. August 2019 17:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1840009 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/1840010 Title: xenial/linux-aws: 4.4.0-1091.102 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 derivatives: bug 1840009 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840021 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 15. August 2019 17:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-aws/aws-kernel: bug 1840009 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840010/+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 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display
systemctl list-units --no-pager |grep "systemd-backlight" systemd-backlight@backlight:acpi_video0.service loaded active exitedLoad/Save Screen Backlight Brightness of backlight:acpi_video0 systemd-backlight@backlight:nvidia_0.service loaded active exitedLoad/Save Screen Backlight Brightness of backlight:nvidia_0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1840592 Title: systemd-backlight does not save and restore brightness for nvidia display Status in nvidia-graphics-drivers package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5% steps. However, after a reboot or after a shutdown, brightness level reverts to 100%. Please fix to is "remembers" the current brightness value at shutdown time, like in does Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592/+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 1840014] Re: xenial/linux-raspi2: 4.4.0-1119.128 -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 derivatives: bug 1840013 (pi2-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840021 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Signoff phase-changed: Friday, 16. August 2019 07:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1840013 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1840014 Title: xenial/linux-raspi2: 4.4.0-1119.128 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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 derivatives: bug 1840013 (pi2-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840021 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Signoff phase-changed: Friday, 16. August 2019 07:51 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: xenial/linux-raspi2/pi2-kernel: bug 1840013 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840014/+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 1840592] Re: systemd-backlight does not save and restore brightness for nvidia display
The notebook has 2 gpus, one is from the intel cpu and another is nvidia which can be enabled or disable on bios on section "MSI VGA MODE" and choose "MSI IGPU MODE" or "MSI DGPU MODE" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1840592 Title: systemd-backlight does not save and restore brightness for nvidia display Status in nvidia-graphics-drivers package in Ubuntu: New Status in nvidia-graphics-drivers-418 package in Ubuntu: New Status in nvidia-settings package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Running nvidia gtx 1080 graphics card, with proprietary nvidia drivers on ubuntu 19.04. I can change screen brightness from 0% to 100% in 5% steps. However, after a reboot or after a shutdown, brightness level reverts to 100%. Please fix to is "remembers" the current brightness value at shutdown time, like in does Windows. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1840592/+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 1840021] Re: xenial/linux: 4.4.0-160.188 -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 backports: bug 1840018 (trusty/linux-aws), bug 1840020 (trusty/linux-lts-xenial) derivatives: bug 1840008 (pc-kernel), bug 1840010 (linux-aws), bug 1840012 (linux-kvm), bug 1840014 (linux-raspi2), bug 1840016 (linux-snapdragon), bug 1840017 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 15. August 2019 20:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1840018 trusty/linux-lts-xenial: bug 1840020 xenial/linux-aws: bug 1840010 xenial/linux-fips: bug 1840017 xenial/linux-kvm: bug 1840012 xenial/linux-raspi2: bug 1840014 xenial/linux-snapdragon: bug 1840016 xenial/linux/pc-kernel: bug 1840008 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/1840021 Title: xenial/linux: 4.4.0-160.188 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux 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 backports: bug 1840018 (trusty/linux-aws), bug 1840020 (trusty/linux-lts-xenial) derivatives: bug 1840008 (pc-kernel), bug 1840010 (linux-aws), bug 1840012 (linux-kvm), bug 1840014 (linux-raspi2), bug 1840016 (linux-snapdragon), bug 1840017 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 15. August 2019 20:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED 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: trusty/linux-aws: bug 1840018 trusty/linux-lts-xenial: bug 1840020 xenial/linux-aws: bug 1840010 xenial/linux-fips: bug 1840017 xenial/linux-kvm: bug 1840012 xenial/linux-raspi2: bug 1840014 xenial/linux-snapdragon: bug 1840016 xenial/linux/pc-kernel: bug 1840008 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840021/+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 1840626] Re: [nvidia] Slowness and sometimes the computer freezes
Hi, After some test, I try this and now my system seems to be more stable : xx@XXX:~$ ubuntu-drivers devices == /sys/devices/pci:00/:00:1c.4/:04:00.0 == modalias : pci:v10DEd1299sv1025sd0974bc03sc02i00 vendor : NVIDIA Corporation model: GK208BM [GeForce 920M] driver : nvidia-driver-410 - third-party free driver : nvidia-driver-415 - third-party free recommended driver : nvidia-driver-390 - third-party free driver : xserver-xorg-video-nouveau - distro free builtin xx@XXX:~$ sudo apt install nvidia-driver-415 If I have another problem I will try on Terminal your command: journalctl -b0 > journal.txt Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1840626 Title: [nvidia] Slowness and sometimes the computer freezes Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Since maybe two months, my computer deosn't work correctly. There is slowness and sometime the computer freeze. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Aug 19 00:42:31 2019 DistUpgraded: 2019-02-23 11:53:16,014 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0974] Subsystem: Acer Incorporated [ALI] GK208BM [GeForce 920M] [1025:0974] InstallationDate: Installed on 2019-02-21 (178 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Acer Aspire E5-772G ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=377aa352-9018-46e8-bfee-2799a1be51e6 ro persistent quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-02-23 (176 days ago) dmi.bios.date: 07/28/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.09 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire E5-772G dmi.board.vendor: Acer dmi.board.version: V1.09 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.09:bd07/28/2015:svnAcer:pnAspireE5-772G:pvrV1.09:rvnAcer:rnAspireE5-772G:rvrV1.09:cvnAcer:ct10:cvrV1.09: dmi.product.family: BDW dmi.product.name: Aspire E5-772G dmi.product.version: V1.09 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Aug 19 00:38:49 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1840626/+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 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
I've also verified Solutions QA tests succeed with the proposed Bionic kernel. -- 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/1784665 Title: bcache: bch_allocator_thread(): hung task timeout Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] bcache_allocator() can call the following: bch_allocator_thread() -> bch_prio_write() -> bch_bucket_alloc() -> wait on >set->bucket_wait But the wake up event on bucket_wait is supposed to come from bch_allocator_thread() itself causing a deadlock. [Test Case] This is a simple script that can easily trigger the deadlock condition: https://launchpadlibrarian.net/381282009/bcache-basic-repro.sh A better test case has been also provided in bug 1796292 (duplicate of this bug): https://bugs.launchpad.net/curtin/+bug/1796292/+attachment/5280353/+files/curtin-nvme.sh [Fix] Fix by making the call to bch_prio_write() non-blocking, so that bch_allocator_thread() never waits on itself. Moreover, make sure to wake up the garbage collector thread when bch_prio_write() is failing to allocate buckets to increase the chance of freeing up more buckets. In addition to that it would be safe to also import other upstream bcache fixes (all clean cherry picks): 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e bcache: fix potential deadlock in cached_def_free() 80265d8dfd77792e133793cef44a21323aac2908 bcache: acquire bch_register_lock later in cached_dev_free() ce4c3e19e5201424357a0c82176633b32a98d2ec bcache: Replace bch_read_string_list() by __sysfs_match_string() ecb37ce9baac653cc09e2b631393dde3df82979f bcache: Move couple of functions to sysfs.c 04cbc21137bfa4d7b8771a5b14f3d6c9b2aee671 bcache: Move couple of string arrays to sysfs.c 5f2b18ec8e1643410a2369f06888951cdedea0bf bcache: Fix a compiler warning in bcache_device_init() 20d3a518713e394efa5a899c84574b4b79ec5098 bcache: Reduce the number of sparse complaints about lock imbalances 42361469ae84c851e40cb1f94c8c9a14cdd94039 bcache: Suppress more warnings about set-but-not-used variables f0d3814090ac77de94c42b7124c37ece23629197 bcache: Remove an unused variable 47344e330eabc1515cbe6061eb337100a3ab6d37 bcache: Fix kernel-doc warnings 9dfbdec7b7fea1ff1b7b5d5d12980dbc7dca46c7 bcache: Annotate switch fall-through 4a4e443835a43a79113cc237c472c0d268eb1e1c bcache: Add __printf annotation to __bch_check_keys() fd01991d5c20098c5c1ffc4dca6c821cc60a2f74 bcache: Fix indentation ca71df31661a0518ed58a1a59cf1993962153ebb bcache: fix using of loop variable in memory shrink f3641c3abd1da978ee969b0203b71b86ec1bfa93 bcache: fix error return value in memory shrink 688892b3bc05e25da94866e32210e5f503f16f69 bcache: fix incorrect sysfs output value of strip size 09a44ca2114737e0932257619c16a2b50c7807f1 bcache: use pr_info() to inform duplicated CACHE_SET_IO_DISABLE set c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0 bcache: fix high CPU occupancy during journal a728eacbbdd229d1d903e46261c57d5206f87a4a bcache: add journal statistic 616486ab52ab7f9739b066d958bdd20e65aefd74 bcache: fix writeback target calc on large devices 1f0ffa67349c56ea54c03ccfd1e073c990e7411e bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached eb8cbb6df38f6e5124a3d5f1f8a3dbf519537c60 bcache: improve bcache_reboot() 9951379b0ca88c95876ad9778b9099e19a95d566 bcache: never writeback a discard operation [Regression Potential] The upstream fixes are all clean cherry picks from stable (most of them are small cleanups), so regression potential is minimal. The only special patch is "UBUNTU: SAUCE: bcache: fix deadlock in bcache_allocator()" that is addressing the main deadlock bug (that seems to be a mainline bug - not fixed yet). We should spend more time trying to reproduce this deadlock with a mainline kernel and post the patch to the LKML for review / feedback. However, considering that this patch seems to fix/prevent the specific deadlock problem reported in this bug (tested on the affected platform) it can be considered safe to apply it. [Original Bug Report] $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful
[Kernel-packages] [Bug 1840750] Re: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1840750 Title: [Potential Regression] System crashes when running ftrace test in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Fix Committed Bug description: [Impact] ftrace test in ubuntu_kernel_selftests causes a system crash + reboot when testing "Register/unregister many kprobe events". [Fix] The issue has been discussed in the following LKML thread: https://lkml.org/lkml/2019/6/5/274 and the following 3 upstream commits have been identified to resolve this issue: d2a68c4effd8 x86/ftrace: Do not call function graph from dynamic trampolines 3c0dab44e227 x86/ftrace: Set trampoline pages as executable 7298e24f9042 x86/kprobes: Set instruction page as executable From these commits, the Disco kernel currently in -proposed (5.0.0-26.27) is missing only the following commit, which has been already committed as part of LP: #1839887 (Disco update: upstream stable patchset 2019-08-12) but not yet released: 7298e24f9042 x86/kprobes: Set instruction page as executable [Regression potential] The commit touches the x86/kprobes code so there's a chance of regression there which I would flag as medium. However, it has been applied upstream for v5.2-rc1 and there is no follow-up commits marked as fix for it. -- This issue is 100% reproducible. It looks like this has something to do with the Disco kernel in proposed (5.0.0-1014.14). Test combinations: kernel in updates + source code master branch = OK kernel in proposed + source code master-next branch = NOT OK kernel in proposed + source code master branch = NOT OK The system will crash and reboot itself when testing: "Register/unregister many kprobe events" [33] Kprobe event with comm arguments [PASS] [34] Kprobe event string type argument[PASS] [35] Kprobe event symbol argument [PASS] [36] Kprobe event argument syntax [PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer[PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events packet_write_wait: Connection to 35.233.208.253 port 22: Broken pipe Tried with use "tail -f /var/log/syslog" and "dmesg -w" to see what happened, but it will just disconnected and reboot itself. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1014-gcp 5.0.0-1014.14 ProcVersionSignature: Ubuntu 5.0.0-1014.14-gcp 5.0.21 Uname: Linux 5.0.0-1014-gcp x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Aug 20 08:13:13 2019 SourcePackage: linux-signed-gcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1840750/+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 1840835] Re: High power consumption using 5.0.0-25-generic
apport-collect has this issue: $ apport-collect 1840835 dpkg-query: no packages found matching linux -- 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/1840835 Title: High power consumption using 5.0.0-25-generic Status in linux package in Ubuntu: Incomplete Bug description: After updating to 5.0.0-25-generic kernel, battery life is considerably less and power consumption is about 10 watts more idle, using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and a possible cause is not powering off the dedicated GPU completely while using the integrated. nvidia-driver-430 GP107M [GeForce GTX 1050 Mobile] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+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 1840816] Re: disco/linux: 5.0.0-27.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 backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Ready for Packaging - phase-changed: Tuesday, 20. August 2019 18:20 UTC + phase: Packaging + phase-changed: Tuesday, 20. August 2019 19:06 UTC reason: - prepare-package: Pending -- version not specified + 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 trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 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/1840816 Title: disco/linux: 5.0.0-27.28 -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: New 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 verification-testing series: New 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 backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Tuesday, 20. August 2019 19:06 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 trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840816/+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 1840835] [NEW] High power consumption using 5.0.0-25-generic
You have been subscribed to a public bug: After updating to 5.0.0-25-generic kernel, battery life is considerably less and power consumption is about 10 watts more idle, using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and a possible cause is not powering off the dedicated GPU completely while using the integrated. nvidia-driver-430 GP107M [GeForce GTX 1050 Mobile] ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: disco -- High power consumption using 5.0.0-25-generic https://bugs.launchpad.net/bugs/1840835 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 1840816] Re: disco/linux: 5.0.0-27.28 -proposed tracker
** Summary changed: - disco/linux: -proposed tracker + disco/linux: 5.0.0-27.28 -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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) ** 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) => Khaled El Mously (kmously) -- 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/1840816 Title: disco/linux: 5.0.0-27.28 -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: New 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 verification-testing series: New 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 backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Tuesday, 20. August 2019 19:06 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 trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840816/+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 1840835] Re: High power consumption using 5.0.0-25-generic
This has only occurred on 5.0.0-25-generic. nvidia-driver-430 GP107M [GeForce GTX 1050 Mobile] ** Description changed: After updating to 5.0.0-25-generic kernel, battery life is considerably less and power consumption is about 10 watts more idle, using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and a possible cause is not powering off the dedicated GPU completely while using the integrated. + + nvidia-driver-430 + GP107M [GeForce GTX 1050 Mobile] -- 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/1840835 Title: High power consumption using 5.0.0-25-generic Status in linux package in Ubuntu: Incomplete Bug description: After updating to 5.0.0-25-generic kernel, battery life is considerably less and power consumption is about 10 watts more idle, using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and a possible cause is not powering off the dedicated GPU completely while using the integrated. nvidia-driver-430 GP107M [GeForce GTX 1050 Mobile] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+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 1840835] 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 1840835 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 ** Tags added: disco -- 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/1840835 Title: High power consumption using 5.0.0-25-generic Status in linux package in Ubuntu: Incomplete Bug description: After updating to 5.0.0-25-generic kernel, battery life is considerably less and power consumption is about 10 watts more idle, using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and a possible cause is not powering off the dedicated GPU completely while using the integrated. nvidia-driver-430 GP107M [GeForce GTX 1050 Mobile] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+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 1840835] Re: High power consumption using 5.0.0-25-generic
** Attachment added: "FILENAME.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+attachment/5283548/+files/FILENAME.apport -- 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/1840835 Title: High power consumption using 5.0.0-25-generic Status in linux package in Ubuntu: Incomplete Bug description: After updating to 5.0.0-25-generic kernel, battery life is considerably less and power consumption is about 10 watts more idle, using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and a possible cause is not powering off the dedicated GPU completely while using the integrated. nvidia-driver-430 GP107M [GeForce GTX 1050 Mobile] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+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 1650337] Re: unknown filesystem efivarfs
This bug prevents from using fwupdmgr to update bios because it needs access to EFI variables. Manually trying to mount this mount -t efivarfs none /sys/firmware/efi does not work because mount does not recognize the efivarfs filesystem type. Running 19.04 ubuntu mate on Thinkpad460s. -- 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/1650337 Title: unknown filesystem efivarfs Status in linux package in Ubuntu: Triaged Status in linux source package in Disco: Triaged Bug description: Please add file system efivarfs to 32-bit Linux kernel, so on EFI machine following command could be executed: sudo mount -t efivarfs efivarfs /sys/firmware/efi/efivars See also: bug 1648278 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650337/+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 1840835] Re: High power consumption using 5.0.0-25-generic
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+attachment/5283547/+files/lspci-vnvn.log -- 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/1840835 Title: High power consumption using 5.0.0-25-generic Status in linux package in Ubuntu: Incomplete Bug description: After updating to 5.0.0-25-generic kernel, battery life is considerably less and power consumption is about 10 watts more idle, using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and a possible cause is not powering off the dedicated GPU completely while using the integrated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+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 1840835] Re: High power consumption using 5.0.0-25-generic
Thank you for filing the bug and make ubuntu better! To file bugs in the future please use: ubuntu-bug packagename so relevant system info gets pulled into your bug and the developers can help/debug you a betetr way. You can still use: apport-collect bugID in this stage to add your info afterwards. is it also possible you add your nvidia driver version your card/chipset uses? (nvidia-smi and/or ubuntu-drivers list) Does this occur on other kernel versions too? -- 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/1840835 Title: High power consumption using 5.0.0-25-generic Status in linux package in Ubuntu: Incomplete Bug description: After updating to 5.0.0-25-generic kernel, battery life is considerably less and power consumption is about 10 watts more idle, using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and a possible cause is not powering off the dedicated GPU completely while using the integrated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+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 1840835] [NEW] High power consumption using 5.0.0-25-generic
Public bug reported: After updating to 5.0.0-25-generic kernel, battery life is considerably less and power consumption is about 10 watts more idle, using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and a possible cause is not powering off the dedicated GPU completely while using the integrated. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: disco ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1840835/+attachment/5283546/+files/version.log -- 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/1840835 Title: High power consumption using 5.0.0-25-generic Status in linux package in Ubuntu: Incomplete Bug description: After updating to 5.0.0-25-generic kernel, battery life is considerably less and power consumption is about 10 watts more idle, using integrated graphics. This is a hybrid GPU laptop Intel HD 630/GP107M, and a possible cause is not powering off the dedicated GPU completely while using the integrated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840835/+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 1840800] Re: disco/linux-aws: -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + disco/linux-aws: -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 backports: bug 1840820 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1840816 + packages: + main: linux-aws + meta: linux-meta-aws + phase: Holding before Packaging + phase-changed: Tuesday, 20. August 2019 18:18 UTC + reason: + prepare-package: Holding -- waiting for master bug variant: debs ** 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 backports: bug 1840820 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-aws meta: linux-meta-aws phase: Holding before Packaging phase-changed: Tuesday, 20. August 2019 18:18 UTC reason: prepare-package: Holding -- waiting for master bug + trackers: + bionic/linux-aws-edge: bug 1840820 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/1840800 Title: disco/linux-aws: -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-meta 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 verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 backports: bug 1840820 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-aws meta: linux-meta-aws phase: Holding before Packaging phase-changed: Tuesday, 20. August 2019 18:18 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-aws-edge: bug 1840820 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840800/+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 1840001] Re: trusty/linux-azure: 4.15.0-1056.61~14.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: 1840002 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Monday, 19. August 2019 23:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- 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/1840001 Title: trusty/linux-azure: 4.15.0-1056.61~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: Confirmed 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: Confirmed 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: 1840002 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Monday, 19. August 2019 23:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- 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/1840001/+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 1840811] Re: disco/linux-oracle: -proposed tracker
** Summary changed: - linux-oracle: -proposed tracker + disco/linux-oracle: -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 backports: bug 1840826 (bionic/linux-oracle-edge) -- swm properties -- kernel-stable-master-bug: 1840816 + packages: + main: linux-oracle + meta: linux-meta-oracle + signed: linux-signed-oracle + phase: Holding before Packaging + phase-changed: Tuesday, 20. August 2019 18:20 UTC + reason: + prepare-package: Holding -- waiting for master bug variant: debs ** 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 backports: bug 1840826 (bionic/linux-oracle-edge) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Packaging phase-changed: Tuesday, 20. August 2019 18:20 UTC reason: prepare-package: Holding -- waiting for master bug + trackers: + bionic/linux-oracle-edge: bug 1840826 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1840811 Title: disco/linux-oracle: -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-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 verification-testing series: New Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 backports: bug 1840826 (bionic/linux-oracle-edge) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Packaging phase-changed: Tuesday, 20. August 2019 18:20 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-oracle-edge: bug 1840826 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840811/+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 1840802] 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 derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1840803 + packages: + lrm: linux-restricted-modules-azure + main: linux-azure + meta: linux-meta-azure + signed: linux-signed-azure + phase: Holding before Packaging + phase-changed: Tuesday, 20. August 2019 18:18 UTC + reason: + prepare-package: Holding -- waiting for master bug + trackers: + bionic/linux-azure/azure-kernel: bug 1840801 variant: debs ** 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 derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Tuesday, 20. August 2019 18:18 UTC reason: prepare-package: Holding -- waiting for master bug trackers: + bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 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/1840802 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 derivatives: bug 1840801 (azure-kernel), bug 1840821 (linux-azure- edge) -- swm properties -- kernel-stable-master-bug: 1840803 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Tuesday, 20. August 2019 18:18 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-azure-edge: bug 1840821 bionic/linux-azure/azure-kernel: bug 1840801 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840802/+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 1840810] Re: disco/linux-kvm: -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + disco/linux-kvm: -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: 1840816 + packages: + main: linux-kvm + meta: linux-meta-kvm + phase: Holding before Packaging + phase-changed: Tuesday, 20. August 2019 18:19 UTC + reason: + prepare-package: Holding -- waiting for master bug variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1840810 Title: disco/linux-kvm: -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-meta 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 verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1840816 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Packaging phase-changed: Tuesday, 20. August 2019 18:19 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840810/+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 1840806] Re: bionic/linux-gcp: -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + bionic/linux-gcp: -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 derivatives: bug 1840805 (gcp-kernel), bug 1840824 (linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1840808 + packages: + lrm: linux-restricted-modules-gcp + main: linux-gcp + meta: linux-meta-gcp + signed: linux-signed-gcp + phase: Holding before Packaging + phase-changed: Tuesday, 20. August 2019 18:19 UTC + reason: + prepare-package: Holding -- waiting for master bug + trackers: + bionic/linux-gcp/gcp-kernel: bug 1840805 variant: debs ** 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 derivatives: bug 1840805 (gcp-kernel), bug 1840824 (linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1840808 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Tuesday, 20. August 2019 18:19 UTC reason: prepare-package: Holding -- waiting for master bug trackers: + bionic/linux-gcp-edge: bug 1840824 bionic/linux-gcp/gcp-kernel: bug 1840805 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/1840806 Title: bionic/linux-gcp: -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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 derivatives: bug 1840805 (gcp-kernel), bug 1840824 (linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1840808 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Tuesday, 20. August 2019 18:19 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-gcp-edge: bug 1840824 bionic/linux-gcp/gcp-kernel: bug 1840805 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840806/+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 1840803] Re: disco/linux-azure: -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + disco/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 backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 + packages: + main: linux-azure + meta: linux-meta-azure + signed: linux-signed-azure + phase: Holding before Packaging + phase-changed: Tuesday, 20. August 2019 18:19 UTC + reason: + prepare-package: Holding -- waiting for master bug + trackers: + bionic/linux-azure: bug 1840802 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/1840803 Title: disco/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-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 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 backports: bug 1840802 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Tuesday, 20. August 2019 18:19 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-azure: bug 1840802 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840803/+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 1840808] Re: disco/linux-gcp: -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + disco/linux-gcp: -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 backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- kernel-stable-master-bug: 1840816 + packages: + main: linux-gcp + meta: linux-meta-gcp + signed: linux-signed-gcp + phase: Holding before Packaging + phase-changed: Tuesday, 20. August 2019 18:19 UTC + reason: + prepare-package: Holding -- waiting for master bug + trackers: + bionic/linux-gcp: bug 1840806 variant: debs ** 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 backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Tuesday, 20. August 2019 18:19 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-gcp: bug 1840806 + bionic/linux-gke-5.0: bug 1840823 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/1840808 Title: disco/linux-gcp: -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-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 verification-testing series: New 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 backports: bug 1840806 (bionic/linux-gcp), bug 1840823 (bionic/linux- gke-5.0) -- swm properties -- kernel-stable-master-bug: 1840816 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Tuesday, 20. August 2019 18:19 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-gcp: bug 1840806 bionic/linux-gke-5.0: bug 1840823 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840808/+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 1840826] Re: bionic/linux-oracle-edge: -proposed tracker
** Summary changed: - linux-oracle-edge: -proposed tracker + bionic/linux-oracle-edge: -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: 1840811 + packages: + main: linux-oracle-edge + meta: linux-meta-oracle-edge + signed: linux-signed-oracle-edge + phase: Holding before Packaging + phase-changed: Tuesday, 20. August 2019 18:21 UTC + reason: + prepare-package: Holding -- waiting for master bug 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/1840826 Title: bionic/linux-oracle-edge: -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-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 verification-testing series: New 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 -- kernel-stable-master-bug: 1840811 packages: main: linux-oracle-edge meta: linux-meta-oracle-edge signed: linux-signed-oracle-edge phase: Holding before Packaging phase-changed: Tuesday, 20. August 2019 18:21 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840826/+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 1840816] Re: disco/linux: -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 backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- + packages: + lrm: linux-restricted-modules + main: linux + meta: linux-meta + signed: linux-signed + phase: Ready for Packaging + phase-changed: Tuesday, 20. August 2019 18:20 UTC + reason: + prepare-package: Pending -- version not specified + trackers: + bionic/linux-hwe: bug 1840812 + bionic/linux-oem-osp1: bug 1840815 + disco/linux-aws: bug 1840800 + disco/linux-azure: bug 1840803 + disco/linux-gcp: bug 1840808 + disco/linux-kvm: bug 1840810 + disco/linux-oracle: bug 1840811 + disco/linux-raspi2: bug 1839949 + disco/linux-snapdragon: bug 1839968 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/1840816 Title: disco/linux: -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: New Status in Kernel SRU Workflow prepare-package series: Confirmed 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 verification-testing series: New 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 backports: bug 1840812 (bionic/linux-hwe), bug 1840815 (bionic/linux-oem-osp1) derivatives: bug 1839949 (linux-raspi2), bug 1839968 (linux-snapdragon), bug 1840800 (linux-aws), bug 1840803 (linux-azure), bug 1840808 (linux-gcp), bug 1840810 (linux-kvm), bug 1840811 (linux-oracle) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Packaging phase-changed: Tuesday, 20. August 2019 18:20 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-hwe: bug 1840812 bionic/linux-oem-osp1: bug 1840815 disco/linux-aws: bug 1840800 disco/linux-azure: bug 1840803 disco/linux-gcp: bug 1840808 disco/linux-kvm: bug 1840810 disco/linux-oracle: bug 1840811 disco/linux-raspi2: bug 1839949 disco/linux-snapdragon: bug 1839968 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840816/+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 1840002] Re: xenial/linux-azure: 4.15.0-1056.61 -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 backports: bug 1840001 (trusty/linux-azure) derivatives: bug 183 (azure-kernel), bug 184 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Signoff phase-changed: Monday, 19. August 2019 15:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1840001 xenial/linux-azure-edge: bug 184 xenial/linux-azure/azure-kernel: bug 183 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/1840002 Title: xenial/linux-azure: 4.15.0-1056.61 -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: Confirmed 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: Confirmed 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 backports: bug 1840001 (trusty/linux-azure) derivatives: bug 183 (azure-kernel), bug 184 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Signoff phase-changed: Monday, 19. August 2019 15:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1840001 xenial/linux-azure-edge: bug 184 xenial/linux-azure/azure-kernel: bug 183 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840002/+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 1839977] Re: bionic/linux-raspi2: 4.15.0-1044.47 -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 derivatives: bug 1839976 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Saturday, 17. August 2019 00:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1839976 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1839977 Title: bionic/linux-raspi2: 4.15.0-1044.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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 derivatives: bug 1839976 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840006 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Saturday, 17. August 2019 00:20 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-raspi2/pi-kernel: bug 1839976 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839977/+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
