[Kernel-packages] [Bug 1820075] Re: [Packaging] Improve config annotations check on custom kernels
** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- 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/1820075 Title: [Packaging] Improve config annotations check on custom kernels Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Xenial: Fix Released Status in linux-gcp source package in Xenial: New Status in linux-oracle source package in Xenial: New Status in linux-azure source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: New Status in linux-oracle source package in Bionic: New Status in linux-azure source package in Cosmic: Fix Released Status in linux-gcp source package in Cosmic: Fix Released Status in linux-oracle source package in Cosmic: New Status in linux-azure source package in Disco: Fix Released Status in linux-gcp source package in Disco: New Status in linux-oracle source package in Disco: New Bug description: [Impact] Currently for custom kernels, it's necessary to keep a separate annotations file that often gets out of sync with the corresponding file in debian.master/. The "debian/scripts/config-check" script can be changed to allow additional annotations files to act as overlays over the original annotations file, allowing custom kernels to override the policies just for the relevant configs. The proposal is to add support for an include directive in the annotations file so custom kernels can include the annotations file from its base kernel and override policies on a config basis. [Test Case] A kernel build should complete successfully after the change. [Regression Potential] Low regression potential since that's a change on the build process that doesn't affect the final kernel that is built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1820075/+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 1841132] Re: mpt3sas - storage controller resets under heavy disk io
attaching copy of syslog from moment of error ** Attachment added: "syslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841132/+attachment/5284119/+files/syslog.txt -- 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/1841132 Title: mpt3sas - storage controller resets under heavy disk io Status in linux package in Ubuntu: Incomplete Bug description: [summary] when a server running ubuntu 18.04 with an lsi sas controller experiences high disk io there is a chance the storage controller will reset this can take weeks or months, but once the controller resets it will keep resetting every few seconds or few minutes, dramatically degrading disk io the server must be rebooted to restore the controller to a normal state [hardware configuration] server: dell poweredge r7415, purchased 2019-02 cpu/chipset: amd epyc naples storage controller: "dell hba330 mini" with chipset "lsi sas3008" drives: 4x samsung 860 pro 2TB ssd [software configuration] ubuntu 18.04 server mdadm raid6 all firmware is fully updated (bios 1.9.3) (hba330 16.17.00.03) (ssd rvm01b6q) [what happened] server was operating as a vm host for months without issue one day the syslog was flooded with messages like "mpt3sas_cm0: sending diag reset !!" and "Power-on or device reset occurred", along with unusably-slow disk io the server was removed from production and I looked for a way to reproduce the issue [how to reproduce the issue] there are probably many ways to product this issue, the hackish way I found to reliably reproduce it was: have the four ssds in a mdadm raid6 with ext4 filesystem create three 500GB files containing random data open three terminals. one calculates md5sum of file1 in a loop, another does the same for file2, the third does a copy of file3 to file3-temp in a loop the number of files is arbitrary, the goal is just to generate a lot of disk io on files too large to be cached in memory then initiate an array check with "/usr/share/mdadm/checkarray -a" to cause even more drive thrashing within 1-15min the controller will enter the broken state. the longest I ever saw it take was 30min. I reproduced this several times rebooting the server restores the controller to a normal state if the server is not rebooted and the controller is left in this broken state eventually drives will fall out of the array, and sometimes array/filesystem corruption will occur [why this is being reported here] It's unlikely I am exceeding limits of the hardware since this server chassis can hold 24 drives and I am only using 4. The controller specs indicate I should not hit pcie bandwidth limits until at least 16 drives. My first thought was that the lsi controller firmware was at fault since they have been historically buggy, however I reproduced this with the newest firmware "16.17.00.03" and the previous version "15.17.09.06" (versions may be dell-specific). I then tried the most recent motherboard bios "1.9.3", and downgraded to "1.9.2", no change. I then wanted to eliminate the possibility of a bad drive. swapped out all 4 drives with different ones of the same model, no change. I then upgraded from the standard 18.04 kernel to the newer backported hwe kernel, which also came with a newer mpt3sas driver, no change. I then ran the same test on the same array but with rhel 8, to my surprise I could no longer reproduce the issue. - tl;dr version: ubuntu 18.04 (kernel 4.15.0) (mpt3sas driver 17.100.00.00) storage controller breaks in 1-10min ubuntu 18.04 hwe (kernel 5.0.0) (mpt3sas driver 27.101.00.00) storage controller breaks in 1-15min, max 30min rhel 8 (kernel 4.18.0) (mpt3sas driver 27.101.00.00) same stress test on same array for 19h, no errors [caveats] Server os misconfiguration is possible, however this is a rather basic vm host running kvm and no 3rd-party packages. I can't conclusively prove this isn't a hardware fault since I don't have a second unused identical server to test on right now, however the fact that the problem can be easily reproduced under ubuntu but not under rhel seems noteworthy. There is another bug (LP: #1810781) similar to this, I didn't post there because it's already marked as fixed. There is also a debian bug (Debian #926202) that encountered this on kernel 4.19.0, but I'm unable to tell if it's the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841132/+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 1841132] 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 1841132 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/1841132 Title: mpt3sas - storage controller resets under heavy disk io Status in linux package in Ubuntu: Incomplete Bug description: [summary] when a server running ubuntu 18.04 with an lsi sas controller experiences high disk io there is a chance the storage controller will reset this can take weeks or months, but once the controller resets it will keep resetting every few seconds or few minutes, dramatically degrading disk io the server must be rebooted to restore the controller to a normal state [hardware configuration] server: dell poweredge r7415, purchased 2019-02 cpu/chipset: amd epyc naples storage controller: "dell hba330 mini" with chipset "lsi sas3008" drives: 4x samsung 860 pro 2TB ssd [software configuration] ubuntu 18.04 server mdadm raid6 all firmware is fully updated (bios 1.9.3) (hba330 16.17.00.03) (ssd rvm01b6q) [what happened] server was operating as a vm host for months without issue one day the syslog was flooded with messages like "mpt3sas_cm0: sending diag reset !!" and "Power-on or device reset occurred", along with unusably-slow disk io the server was removed from production and I looked for a way to reproduce the issue [how to reproduce the issue] there are probably many ways to product this issue, the hackish way I found to reliably reproduce it was: have the four ssds in a mdadm raid6 with ext4 filesystem create three 500GB files containing random data open three terminals. one calculates md5sum of file1 in a loop, another does the same for file2, the third does a copy of file3 to file3-temp in a loop the number of files is arbitrary, the goal is just to generate a lot of disk io on files too large to be cached in memory then initiate an array check with "/usr/share/mdadm/checkarray -a" to cause even more drive thrashing within 1-15min the controller will enter the broken state. the longest I ever saw it take was 30min. I reproduced this several times rebooting the server restores the controller to a normal state if the server is not rebooted and the controller is left in this broken state eventually drives will fall out of the array, and sometimes array/filesystem corruption will occur [why this is being reported here] It's unlikely I am exceeding limits of the hardware since this server chassis can hold 24 drives and I am only using 4. The controller specs indicate I should not hit pcie bandwidth limits until at least 16 drives. My first thought was that the lsi controller firmware was at fault since they have been historically buggy, however I reproduced this with the newest firmware "16.17.00.03" and the previous version "15.17.09.06" (versions may be dell-specific). I then tried the most recent motherboard bios "1.9.3", and downgraded to "1.9.2", no change. I then wanted to eliminate the possibility of a bad drive. swapped out all 4 drives with different ones of the same model, no change. I then upgraded from the standard 18.04 kernel to the newer backported hwe kernel, which also came with a newer mpt3sas driver, no change. I then ran the same test on the same array but with rhel 8, to my surprise I could no longer reproduce the issue. - tl;dr version: ubuntu 18.04 (kernel 4.15.0) (mpt3sas driver 17.100.00.00) storage controller breaks in 1-10min ubuntu 18.04 hwe (kernel 5.0.0) (mpt3sas driver 27.101.00.00) storage controller breaks in 1-15min, max 30min rhel 8 (kernel 4.18.0) (mpt3sas driver 27.101.00.00) same stress test on same array for 19h, no errors [caveats] Server os misconfiguration is possible, however this is a rather basic vm host running kvm and no 3rd-party packages. I can't conclusively prove this isn't a hardware fault since I don't have a second unused identical server to test on right now, however the fact that the problem can be easily reproduced under ubuntu but not under rhel seems noteworthy. There is another bug (LP: #1810781) similar to this, I didn't post there because it's already marked as fixed. There is also a debian bug (Debian #926202) that encountered this on kernel 4.19.0, but I'm unable to tell if it's the same issue. To manage notifications about this bug go
[Kernel-packages] [Bug 1743908] Re: MODSIGN: Couldn't get UEFI db list
Error "Couldn't get size: 0x800e" has resurfaced despite of the released fix. I found this error in latest Ubuntu 18.04 install. Release fix needs to be re-evaluated. $ dmesg . [0.933031] Loading compiled-in X.509 certificates [0.934003] Loaded X.509 cert 'Build time autogenerated kernel key: x...' [0.936201] Loaded UEFI:db cert 'ASUSTeK MotherBoard SW Key Certificate: x...' linked to secondary sys keyring [0.936320] Loaded UEFI:db cert 'ASUSTeK Notebook SW Key Certificate: x...' linked to secondary sys keyring [0.936331] Loaded UEFI:db cert 'Microsoft Corporation UEFI CA 2011: x...' linked to secondary sys keyring [0.936340] Loaded UEFI:db cert 'Microsoft Windows Production PCA 2011: x...' linked to secondary sys keyring [0.936461] Loaded UEFI:db cert 'Canonical Ltd. Master Certificate Authority: x...' linked to secondary sys keyring [0.936838] Couldn't get size: 0x800e [0.936839] MODSIGN: Couldn't get UEFI MokListRT $ uname -a Linux Machine 5.0.0-25-generic #26~18.04.1-Ubuntu SMP Thu Aug 1 13:51:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l | grep linux-generic-hwe- ii linux-generic-hwe-18.04 5.0.0.25.82 amd64 Complete Generic Linux kernel and headers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic $ efibootmgr BootCurrent: Timeout: 1 seconds BootOrder: ,0001 Boot* ubuntu Boot0001* Hard Drive Fast Boot -- Disabled Secure Boot -- Disabled CSM -- Disabled -- 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/1743908 Title: MODSIGN: Couldn't get UEFI db list Status in linux package in Ubuntu: Fix Released Bug description: Kernel is having problem loading or validating certificates. Looking over the internet looks like this is a kernel issue. Patchs from other distro: https://bugzilla.redhat.com/show_bug.cgi?id=1497559 - 0001-Make-get_cert_list-not-complain-about-cert-lists-tha.patch - 0002-Add-efi_status_to_str-and-rework-efi_status_to_err.patch - 0003-Make-get_cert_list-use-efi_status_to_str-to-print-er.patch [1.203191] Loaded X.509 cert 'Build time autogenerated kernel key: ecdf0c3ef21a8b4ca325a4d1db7d45108ca78734' [1.203352] Couldn't get size: 0x800e [1.203354] MODSIGN: Couldn't get UEFI db list [1.205030] Loaded UEFI:MokListRT cert 'Canonical Ltd. Master Certificate Authority: ad91990bc22ab1f517048c23b6655a268e345a63' linked to secondary sys keyring [1.205102] Couldn't get size: 0x800e [1.205103] MODSIGN: Couldn't get UEFI dbx list ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wellington 1429 F pulseaudio /dev/snd/pcmC1D3p: wellington 1429 F...m pulseaudio /dev/snd/controlC1: wellington 1429 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 17 22:37:13 2018 HibernationDevice: RESUME=UUID=192fbe7e-0dbf-47fc-8277-75569f69f16e InstallationDate: Installed on 2018-01-16 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) IwConfig: lono wireless extensions. enp7s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic.efi.signed root=UUID=aa7179de-345d-4e48-8bbd-6397120a155a ro amd_iommu=fullflush iommu=pt RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.169.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD5 R5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn990FXA-UD5R5:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte
[Kernel-packages] [Bug 1841132] [NEW] mpt3sas - storage controller resets under heavy disk io
Public bug reported: [summary] when a server running ubuntu 18.04 with an lsi sas controller experiences high disk io there is a chance the storage controller will reset this can take weeks or months, but once the controller resets it will keep resetting every few seconds or few minutes, dramatically degrading disk io the server must be rebooted to restore the controller to a normal state [hardware configuration] server: dell poweredge r7415, purchased 2019-02 cpu/chipset: amd epyc naples storage controller: "dell hba330 mini" with chipset "lsi sas3008" drives: 4x samsung 860 pro 2TB ssd [software configuration] ubuntu 18.04 server mdadm raid6 all firmware is fully updated (bios 1.9.3) (hba330 16.17.00.03) (ssd rvm01b6q) [what happened] server was operating as a vm host for months without issue one day the syslog was flooded with messages like "mpt3sas_cm0: sending diag reset !!" and "Power-on or device reset occurred", along with unusably-slow disk io the server was removed from production and I looked for a way to reproduce the issue [how to reproduce the issue] there are probably many ways to product this issue, the hackish way I found to reliably reproduce it was: have the four ssds in a mdadm raid6 with ext4 filesystem create three 500GB files containing random data open three terminals. one calculates md5sum of file1 in a loop, another does the same for file2, the third does a copy of file3 to file3-temp in a loop the number of files is arbitrary, the goal is just to generate a lot of disk io on files too large to be cached in memory then initiate an array check with "/usr/share/mdadm/checkarray -a" to cause even more drive thrashing within 1-15min the controller will enter the broken state. the longest I ever saw it take was 30min. I reproduced this several times rebooting the server restores the controller to a normal state if the server is not rebooted and the controller is left in this broken state eventually drives will fall out of the array, and sometimes array/filesystem corruption will occur [why this is being reported here] It's unlikely I am exceeding limits of the hardware since this server chassis can hold 24 drives and I am only using 4. The controller specs indicate I should not hit pcie bandwidth limits until at least 16 drives. My first thought was that the lsi controller firmware was at fault since they have been historically buggy, however I reproduced this with the newest firmware "16.17.00.03" and the previous version "15.17.09.06" (versions may be dell-specific). I then tried the most recent motherboard bios "1.9.3", and downgraded to "1.9.2", no change. I then wanted to eliminate the possibility of a bad drive. swapped out all 4 drives with different ones of the same model, no change. I then upgraded from the standard 18.04 kernel to the newer backported hwe kernel, which also came with a newer mpt3sas driver, no change. I then ran the same test on the same array but with rhel 8, to my surprise I could no longer reproduce the issue. - tl;dr version: ubuntu 18.04 (kernel 4.15.0) (mpt3sas driver 17.100.00.00) storage controller breaks in 1-10min ubuntu 18.04 hwe (kernel 5.0.0) (mpt3sas driver 27.101.00.00) storage controller breaks in 1-15min, max 30min rhel 8 (kernel 4.18.0) (mpt3sas driver 27.101.00.00) same stress test on same array for 19h, no errors [caveats] Server os misconfiguration is possible, however this is a rather basic vm host running kvm and no 3rd-party packages. I can't conclusively prove this isn't a hardware fault since I don't have a second unused identical server to test on right now, however the fact that the problem can be easily reproduced under ubuntu but not under rhel seems noteworthy. There is another bug (LP: #1810781) similar to this, I didn't post there because it's already marked as fixed. There is also a debian bug (Debian #926202) that encountered this on kernel 4.19.0, but I'm unable to tell if it's the same issue. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bionic hba330 mpt3sas sas3008 -- 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/1841132 Title: mpt3sas - storage controller resets under heavy disk io Status in linux package in Ubuntu: New Bug description: [summary] when a server running ubuntu 18.04 with an lsi sas controller experiences high disk io there is a chance the storage controller will reset this can take weeks or months, but once the controller resets it will keep resetting every few seconds or few minutes, dramatically degrading disk io the server must be rebooted to restore the controller to a normal state [hardware configuration] server: dell poweredge r7415, purchased 2019-02 cpu/chipset: amd epyc naples storage controller: "dell hba330 mini" with chipset "lsi sas3008" drives: 4x samsung 860 pro 2TB ssd
[Kernel-packages] [Bug 1837136] Re: ideapad_laptop disables WiFi/BT radios on Lenovo Y540
How do I add the tag verification-done-disco ? ** Tags added: verification-done-disco ** Tags removed: verification-needed-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/1837136 Title: ideapad_laptop disables WiFi/BT radios on Lenovo Y540 Status in linux package in Ubuntu: Fix Released 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 Released Bug description: === SRU Justification === [Impact] WiFi on Ideapads are rfkill HW blocked by default. [Fix] Remove no_hw_rfkill_list as most Ideapads don't have hardware rfkill button. [Test] User reported the fix works. [Regression Potential] Low. If there's any actual device that has HW rfkill button, we can simply add it to whitelist. === Original Bug Report === I have a brand new LeNovo legion Y540 and the ideapad_laptop module results in a rfkill. If the module is removed/blacklisted, then wifi works, but some ACPI functionality is lost (the fans don't spin correctly and the laptop doesn't cool properly). I will try to compile ideapad_laptop adding the laptop info to no_hw_rfkill_list[]. I only tried in ubuntu 19.10 (although this is a kernel issue) rfkill output: sudo rfkill ID TYPE DEVICE SOFT HARD 2 bluetooth hci0blocked unblocked 3 wlan phy0 unblocked unblocked 4 wlan ideapad_wlan unblocked blocked 5 bluetooth ideapad_bluetooth blocked blocked 1) Ubuntu 5.0.0-20.21-generic 5.0.8 (rest of info in attachment) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jmamede2484 F pulseaudio /dev/snd/controlC0: jmamede2484 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-07-18 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81SX NonfreeKernelModules: nvidia_modeset nvidia 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/lvmmamede-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-20-generic N/A linux-backports-modules-5.0.0-20-generic N/A linux-firmware1.178.3 Tags: disco Uname: Linux 5.0.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/28/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.modalias: dmi:bvnLENOVO:bvrBHCN28WW:bd05/28/2019:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837136/+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 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
** Changed in: linux (Ubuntu Eoan) 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/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: New Status in linux source package in Eoan: Fix Committed Bug description: === SRU Justification === [Impact] Realtek Wifi stops working after the driver changed from rtlwifi to rtw88. [Fix] Sync rtw88 to upstream version, and use MSI on the device. [Test] User confirmed the backport fixes the issue. [Regression Potential] Low. Currently only 8822be uses rtw88. === Original Bug Report === On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that wifi was no longer working because at work I exclusively use a wired Ethernet connection. Today, however, when I tried to use my realtek r8822be wireless card, I discovered that it was totally unresponsive and did not work with wpa_supplicant / wpa_cli even when invoked manually from the command line (let alone with NetworkManager). When the problem occurred, I was using 19.04's latest kernel 5.0.0-21. I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname -a" shows that I am using the previous kernel version: Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux With this kernel version as well as linux-headers-5.0.0.20, linux- headers-5.0.0-20-generic, my realtek wireless card works fine. While booted into 5.0.0-20 kernel, here are the realtek kernel modules that are loaded: # lsmod | grep r8 r8822be 692224 0 mac80211 806912 1 r8822be cfg80211 671744 2 mac80211,r8822be r8169 81920 0 Hopefully this realtek wireless regression can get fixed in the next minor kernel version. Let me know if you need any more information. Best Regards, Jun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+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 1840882] Re: [SRU][B-OEM-OSP1/D/E] reduce s2idle power consumption when BIOS uses shared power resources
** 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/1840882 Title: [SRU][B-OEM-OSP1/D/E] reduce s2idle power consumption when BIOS uses shared power resources Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Committed Bug description: SRU justification: [Impact] When system goes to suspend-to idle, it's power consumption is around 4+ w. [Fix] Some TBT and other ACPI devices share the same power resource, when system goes to s2idle. PME polling thread continue bringing up devices to D0 mode. Use cached ACPI device power state will avoid this issue. [Test] Verified on 2 hardware. Tests result are good. [Regression Potential] Medium, upstream patches cherry-picked. Since these hareware is only supported by 5.0+ kernel, I set B-OEM- OSP1 and disco+ kernel tag. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1840882/+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 1812796] Re: TRACE_syscall.ptrace_syscall_dropped in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC
Hmm, how come this was marked as verification-needed-xenia? -- 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/1812796 Title: TRACE_syscall.ptrace_syscall_dropped in seccomp from ubuntu_kernel_selftests failed on B/C PowerPC Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: == SRU Justification == The TRACE_syscall.ptrace_syscall_dropped test in seccomp from ubuntu_kernel_selftests will fail on a Power8 node with B/C kernel. [ RUN ] TRACE_syscall.ptrace_syscall_dropped seccomp_bpf.c:1808:TRACE_syscall.ptrace_syscall_dropped:Expected 1 (1) == syscall(286) (18446744073709551615) TRACE_syscall.ptrace_syscall_dropped: Test failed at step #13 [ FAIL ] TRACE_syscall.ptrace_syscall_dropped == Fix == * ed5f1326 (selftests/seccomp: Enhance per-arch ptrace syscall skip tests) This patch can be cherry-picked into B/C, and it's already in Disco. The ptrace_syscall_dropped will be changed into ptrace_syscall_faked, and a new ptrace_syscall_errno test will be added. == Test == Patch tested with different arch (amd64 / power8 / arm64 / i386), the new test will pass on them except for PowerPC. Although the faked (bug 1829363) and errno (bug 1829359) test will fail on PowerPC, it's actually helping us to nail down a real issue in our kernel. == Regression Potential == Low, changes limited to the testing tool in the kernel. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 22 04:30 seq crw-rw 1 root audio 116, 33 Jan 22 04:30 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jan 22 06:09:34 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': '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.13 0.34 0.23 1/1487 35882 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #46-Ubuntu SMP Thu Dec 6 14:43:28 UTC 2018 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': '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 152) max: 3.694 GHz (cpu 1) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812796/+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 1824575] Re: Can't boot Thinkpad T540 it's on docking station
Yes, I am using Kubuntu 18.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824575 Title: Can't boot Thinkpad T540 it's on docking station Status in linux package in Ubuntu: Confirmed Bug description: The laptop boots without any issue when it is not connected to the docking station. However when it's connected to the docking and I try to boot it, I get a black screen shortly after the Kubuntu icon shows during the booting process. To boot the laptop, I have to disconnect it from the docking station, boot it up and log on, then I can connect it to the docking station. Similar bug has been reported for Fedora, here: https://bugzilla.redhat.com/show_bug.cgi?id=1527669 Rebasing Fedora 28 to Kernel 4.20.5-100 solved the problem for them. similar problem has also been reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1549169 The problem appears to exist for any version of Thinkpad laptop that is connected to a docking station. Any help to resolve this problem will be much appreciated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cadav 3479 F pulseaudio /dev/snd/controlC0: cadav 3479 F pulseaudio CurrentDesktop: KDE Date: Fri Apr 12 14:34:45 2019 HibernationDevice: RESUME=UUID=3d20fcf7-5e81-4968-899f-e10fdd62fd3e InstallationDate: Installed on 2016-08-12 (973 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 4239CTO ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=8281f38c-3259-4659-b75d-723fc8b5401b ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-21 (234 days ago) dmi.bios.date: 09/20/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 8AET66WW (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 4239CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8AET66WW(1.46):bd09/20/2016:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T520 dmi.product.name: 4239CTO dmi.product.version: ThinkPad T520 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824575/+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 1832138] Re: Login screen never appears on vmwgfx using bionic kernel 4.15
1. It appears nobody requested this fix for xenial so I wouldn't expect anyone interested in testing it. 2. I can't see the bug ID documented in any proposed xenial 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/1832138 Title: Login screen never appears on vmwgfx using bionic kernel 4.15 Status in linux package in Ubuntu: Invalid Status in linux-hwe package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-hwe source package in Bionic: Fix Released Status in mutter source package in Bionic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-hwe source package in Disco: Invalid Status in mutter source package in Disco: Invalid Status in linux source package in Eoan: Invalid Status in linux-hwe source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: [Impact] With most recent version of mutter installed. If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver) and if the login screen uses wayland, then the login prompt doesn't appears. All we see is the purple background with ubuntu in white at the bottom, nothing else. The vmwgfx driver in kernels prior to 4.17 reported bogus timestamps using the wrong clock. This would lead us to wait forever (or at least 49 years) before rendering the next frame. There's no decisive way to know this kernel bug is going to happen before it does so just detect timestamps which are obviously going to cause freezes and ignore them. [Test case] 1) Use Virtualbox or VMware ESxi (if you have the infra) 1.1) [virtualbox] Make sure in the VM setting that the display uses 'VMSVGA' which will force the OS to pick 'vmwgfx' video kernel driver. You can confirm with 'lspci -nnvv' command. 2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15) 4) apt-get dist-upgrade 5) Reboot with 4.15 it will fails with hwe kernel 4.18 it will work as expected. # workaround [Potential regression] Low, it should fix vmwgfx and stop using the wrong clock. A test kernel (pre-sru) has been made available to impact users for them to test and conclude it works. It does work as expected, and no regression has been found during the pre-sru testing phase. As per commit description: " This should be transparent to to user space, as long as it doesn't compare the time against the result of gettimeofday(). " [Other informations] upstream fix: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.2-rc5=37efe80ce85f [Original description] I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root
[Kernel-packages] [Bug 1839253] Re: Excessive screen tearing and flickering on Asus ZenBook S UX391UA
To test: intel_idle.max_cstate=4 1. Edit /etc/default/grub and add it to the line GRUB_CMDLINE_LINUX_DEFAULT=... 2. sudo update-grub 3. Reboot. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1839253 Title: Excessive screen tearing and flickering on Asus ZenBook S UX391UA Status in linux package in Ubuntu: Incomplete Bug description: I am experiencing a large amount of screen tearing flickering and artifacting. I've tried the common fix that is suggested on askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- graphics.conf and this has not changed anything. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 02:06:01 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1] InstallationDate: Installed on 2019-08-06 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 27c6:5201 Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:56b9 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839253/+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 1830587] Re: Reduce NAPI weight in hns driver from 256 to 64
This issue is not for xenial. Removing tag. ** Tags removed: verification-needed-xenial -- 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/1830587 Title: Reduce NAPI weight in hns driver from 256 to 64 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Incomplete Bug description: [Impact] We have a warning[1] in dmesg shows hns register napi as weight 256 but not recommended. According to this commit[2] we shall use weight 64 as suggested. [1] netif_napi_add() called with weight 256 [2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=82dc3c63c692b1e1d59378ecee948ac88e034aad [Test Case] dmesg | grep netif_napi_add [Fix] commit acb1ce15a61154aa501891d67ebf79bc9ea26818 Author: Yonglong Liu Date: Thu Apr 4 16:46:43 2019 +0800 net: hns: Use NAPI_POLL_WEIGHT for hns driver When the HNS driver loaded, always have an error print: "netif_napi_add() called with weight 256" This is because the kernel checks the NAPI polling weights requested by drivers and it prints an error message if a driver requests a weight bigger than 64. So use NAPI_POLL_WEIGHT to fix it. Signed-off-by: Yonglong Liu Signed-off-by: Peng Li Signed-off-by: David S. Miller [Regression Risk] Only weight for NAPI changed. Lowest regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830587/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
https://launchpad.net/ubuntu/+source/linux-hwe/4.15.0-59.66~16.04.1 ** Also affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe (Ubuntu) Status: New => Fix Released ** No longer affects: linux-hwe (Ubuntu Bionic) ** No longer affects: linux-hwe (Ubuntu Cosmic) ** No longer affects: linux-hwe (Ubuntu Disco) ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-hwe (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-hwe (Ubuntu Xenial) Status: New => Fix Committed ** No longer affects: linux (Ubuntu Xenial) -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in linux package in Ubuntu: Fix Released Status in linux-hwe package in Ubuntu: Fix Released Status in linux-hwe source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784485/+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 1841086] Re: bionic/linux: 4.15.0-60.67 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 22. August 2019 17:11 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-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 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/1841086 Title: bionic/linux: 4.15.0-60.67 -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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 22. August 2019 17:11 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:failed trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841086/+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 1841065] Re: Updated to 5.0.0-25 and headphone still inverted
You upgrade the BIOS on your machine? The DMI info is changed? From: Base Board Information Manufacturer: AMI Corporation Product Name: Cherry Trail CR Version: Default string to Base Board Information Manufacturer: AMI Corporation Product Name: Cherry Trail CR Version: NS_P11W7100 -- 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/1841065 Title: Updated to 5.0.0-25 and headphone still inverted Status in linux package in Ubuntu: Confirmed Bug description: I have this quirk file mentioned as work around and still not able to use headphones as before latest upgrade to 19.04. $ sudo cat /etc/modprobe.d/hacksound.conf [sudo] password for leetdavy: # Invert jack detection (1) and use detection mode 2 (2). options snd_soc_rt5645 quirk=0x21 # Failed test on 5.0.0-25 - Insignia Flex11 chtrt5645 headphone Ubuntu Studio begun as 18.04 using linuxium then maintaining upgrades in 19.04 $ ls -l /boot/vm* -rw-r--r-- 1 root root 8543992 Feb 9 2019 /boot/vmlinuz-4.18.0-15-generic -rw--- 1 root root 8711928 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-generic -rw--- 1 root root 8765176 Jul 29 10:52 /boot/vmlinuz-5.0.0-23-lowlatency -rw--- 1 root root 8711928 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-generic -rw--- 1 root root 8773368 Aug 1 07:36 /boot/vmlinuz-5.0.0-25-lowlatency apt-cache policy 500 http://us.archive.ubuntu.com/ubuntu disco/restricted i386 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=i386 origin us.archive.ubuntu.com 500 http://us.archive.ubuntu.com/ubuntu disco/restricted amd64 Packages release v=19.04,o=Ubuntu,a=disco,n=disco,l=Ubuntu,c=restricted,b=amd64 origin us.archive.ubuntu.com $ cat /etc/os-release NAME="Ubuntu" VERSION="19.04 (Disco Dingo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" VERSION_ID="19.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco $ dpkg -l | grep -i studio-install ii ubuntustudio-installer 0.04~19.04.1 all Software installer for Ubuntu Studio ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-25-generic 5.0.0-25.26 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leetdavy 1656 F pulseaudio CurrentDesktop: XFCE Date: Thu Aug 22 09:45:46 2019 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 004: ID 1017:1006 Speedy Industrial Supplies, Pte., Ltd 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: Insignia NS-P11W7100 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/bootsd/vmlinuz-5.0.0-25-generic root=UUID=7890991a-846c-4ad0-9a48-931d216cef5a quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-25-generic N/A linux-backports-modules-5.0.0-25-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-07-20 (32 days ago) dmi.bios.date: 05/19/2017 dmi.bios.version: BI-11.6-S116CJR100-CC34A-029-S dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrBI-11.6-S116CJR100-CC34A-029-S:bd05/19/2017:svnInsignia:pnNS-P11W7100:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: NS-P11W7100 dmi.product.sku: 5255800 dmi.product.version: Default string dmi.sys.vendor: Insignia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841065/+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
Re: [Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
@ Ryan we do not test Xenial or Disco On Thu, Aug 22, 2019 at 7:41 PM Ryan Harper <1784...@bugs.launchpad.net> wrote: > Finally, I did verify xenial proposed with our original test. I had > over 100 installs with no issue. > > @Jason > > Have you had any runs on Xenial or Disco? (or do you not test those)? > > -- > You received this bug notification because you are a member of Canonical > Field Critical, which is subscribed to a duplicate bug report (1796292). > 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: > New > 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
[Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
Finally, I did verify xenial proposed with our original test. I had over 100 installs with no issue. @Jason Have you had any runs on Xenial or Disco? (or do you not test those)? -- 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: New 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
[Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
Also, I had some confusion earlier about what kernel I was testing. apt-cache policy shows the package version 4.15.0.59.61, however that's the meta package, the actual kernel is the .66 one. # dpkg --list | grep linux-image ii linux-image-4.15.0-59-generic 4.15.0-59.66 amd64Signed kernel image generic ii linux-image-virtual 4.15.0.59.61 amd64Virtual Linux kernel image # cat /proc/version Linux version 4.15.0-59-generic (buildd@lgw01-amd64-035) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #66-Ubuntu SMP Wed Aug 14 10:56:44 UTC 2019 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: New 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
[Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
I've adjusted my bionic testing with the simpler configuration. I cannot reproduce the failure so far. I'll leave this running over night. I suspect there's something else going on baremetal that we can't reproduce in a VM. -- 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: New 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
[Kernel-packages] [Bug 1841121] [NEW] Disco update: upstream stable patchset 2019-08-22
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-22
Ported from the following upstream stable releases:
v4.19.63, v5.2.5
from git://git.kernel.org/
hvsock: fix epollout hang from race condition
drm/panel: simple: Fix panel_simple_dsi_probe
iio: adc: stm32-dfsdm: manage the get_irq error case
iio: adc: stm32-dfsdm: missing error case during probe
staging: vt6656: use meaningful error code during buffer allocation
usb: core: hub: Disable hub-initiated U1/U2
tty: max310x: Fix invalid baudrate divisors calculator
pinctrl: rockchip: fix leaked of_node references
tty: serial: cpm_uart - fix init when SMC is relocated
drm/amd/display: Fill prescale_params->scale for RGB565
drm/amdgpu/sriov: Need to initialize the HDP_NONSURFACE_BAStE
drm/amd/display: Disable ABM before destroy ABM struct
drm/amdkfd: Fix a potential memory leak
drm/amdkfd: Fix sdma queue map issue
drm/edid: Fix a missing-check bug in drm_load_edid_firmware()
PCI: Return error if cannot probe VF
drm/bridge: tc358767: read display_props in get_modes()
drm/bridge: sii902x: pixel clock unit is 10kHz instead of 1kHz
gpu: host1x: Increase maximum DMA segment size
drm/crc-debugfs: User irqsafe spinlock in drm_crtc_add_crc_entry
drm/crc-debugfs: Also sprinkle irqrestore over early exits
memstick: Fix error cleanup path of memstick_init
tty/serial: digicolor: Fix digicolor-usart already registered warning
tty: serial: msm_serial: avoid system lockup condition
serial: 8250: Fix TX interrupt handling condition
drm/amd/display: Always allocate initial connector state state
drm/virtio: Add memory barriers for capset cache.
phy: renesas: rcar-gen2: Fix memory leak at error paths
drm/amd/display: fix compilation error
powerpc/pseries/mobility: prevent cpu hotplug during DT update
drm/rockchip: Properly adjust to a true clock in adjusted_mode
serial: imx: fix locking in set_termios()
tty: serial_core: Set port active bit in uart_port_activate
usb: gadget: Zero ffs_io_data
mmc: sdhci: sdhci-pci-o2micro: Check if controller supports 8-bit width
powerpc/pci/of: Fix OF flags parsing for 64bit BARs
drm/msm: Depopulate platform on probe failure
serial: mctrl_gpio: Check if GPIO property exisits before requesting it
PCI: sysfs: Ignore lockdep for remove attribute
i2c: stm32f7: fix the get_irq error cases
kbuild: Add -Werror=unknown-warning-option to CLANG_FLAGS
genksyms: Teach parser about 128-bit built-in types
PCI: xilinx-nwl: Fix Multi MSI data programming
iio: iio-utils: Fix possible incorrect mask calculation
powerpc/cacheflush: fix variable set but not used
powerpc/xmon: Fix disabling tracing while in xmon
recordmcount: Fix spurious mcount entries on powerpc
mfd: madera: Add missing of table registration
mfd: core: Set fwnode for created devices
mfd: arizona: Fix undefined behavior
mfd: hi655x-pmic: Fix missing return value check for devm_regmap_init_mmio_clk
mm/swap: fix release_pages() when releasing devmap pages
um: Silence lockdep complaint about mmap_sem
powerpc/4xx/uic: clear pending interrupt after irq type/pol change
RDMA/i40iw: Set queue pair state when being queried
serial: sh-sci: Terminate TX DMA during buffer flushing
serial: sh-sci: Fix TX DMA buffer flushing and workqueue races
IB/mlx5: Fixed reporting counters on 2nd port for Dual port RoCE
powerpc/mm: Handle page table allocation failures
IB/ipoib: Add child to parent list only if device initialized
arm64: assembler: Switch ESB-instruction with a vanilla nop if !ARM64_HAS_RAS
PCI: mobiveil: Fix PCI base address in MEM/IO outbound windows
PCI: mobiveil: Fix the Class Code field
kallsyms: exclude kasan local symbols on s390
PCI: mobiveil: Initialize Primary/Secondary/Subordinate bus numbers
PCI: mobiveil: Use the 1st inbound window for MEM inbound transactions
perf test mmap-thread-lookup: Initialize variable to suppress memory sanitizer
warning
perf stat: Fix use-after-freed pointer detected by the smatch tool
perf top: Fix potential NULL pointer dereference detected by the smatch tool
perf session: Fix potential NULL pointer dereference found by the smatch tool
perf annotate: Fix dereferencing freed memory found by the smatch tool
perf hists browser: Fix potential NULL pointer dereference found by the smatch
tool
RDMA/rxe: Fill in wc byte_len with IB_WC_RECV_RDMA_WITH_IMM
PCI: dwc: pci-dra7xx: Fix compilation when !CONFIG_GPIOLIB
powerpc/boot: add {get, put}_unaligned_be32 to xz_config.h
block: init flush rq ref count to 1
f2fs: avoid out-of-range memory access
mailbox: handle failed named
Re: [Kernel-packages] [Bug 1839253] Re: Excessive screen tearing and flickering
I have found something that changes the state of the flickering. I tried to plug in a thunderbolt to hdmi display and while the machine didn't output to the display, the flickering stopped. I found that if I plugged in the display while flickering was occurring the flickering would stop and once I unplugged the device the flickering would begin again. On Tue, Aug 13, 2019 at 8:30 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > ** Changed in: linux (Ubuntu) >Status: Incomplete => Confirmed > > ** Summary changed: > > - Excessive screen tearing and flickering > + Excessive screen tearing and flickering on Asus ZenBook S UX391UA > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1839253 > > Title: > Excessive screen tearing and flickering on Asus ZenBook S UX391UA > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > I am experiencing a large amount of screen tearing flickering and > artifacting. I've tried the common fix that is suggested on > askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- > graphics.conf and this has not changed anything. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: xorg 1:7.7+19ubuntu12 > ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 > Uname: Linux 5.0.0-23-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27.1 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Aug 7 02:06:01 2019 > DistUpgraded: Fresh install > DistroCodename: disco > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 > [VGA controller]) > Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1] > InstallationDate: Installed on 2019-08-06 (1 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 27c6:5201 >Bus 001 Device 003: ID 8087:0a2b Intel Corp. >Bus 001 Device 002: ID 13d3:56b9 IMC Networks >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic > root=UUID=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/18/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX391UA.204 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX391UA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: ZenBook S > dmi.product.name: ZenBook S UX391UA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.97-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20180925-2 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839253/+subscriptions > -- 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/1839253 Title: Excessive screen tearing and flickering on Asus ZenBook S UX391UA Status in linux package in Ubuntu: Confirmed Bug description: I am experiencing a large amount of screen tearing flickering and artifacting. I've tried the common fix that is suggested on askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- graphics.conf and this has not changed anything. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1
Re: [Kernel-packages] [Bug 1839253] Re: Excessive screen tearing and flickering on Asus ZenBook S UX391UA
I'm not sure how to boot with this setting, could I get more information? On Wed, Aug 14, 2019 at 2:50 PM Timo Aaltonen wrote: > does booting with intel_idle.max_cstate=4 help? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1839253 > > Title: > Excessive screen tearing and flickering on Asus ZenBook S UX391UA > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > I am experiencing a large amount of screen tearing flickering and > artifacting. I've tried the common fix that is suggested on > askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- > graphics.conf and this has not changed anything. > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: xorg 1:7.7+19ubuntu12 > ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 > Uname: Linux 5.0.0-23-generic x86_64 > ApportVersion: 2.20.10-0ubuntu27.1 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Aug 7 02:06:01 2019 > DistUpgraded: Fresh install > DistroCodename: disco > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 > [VGA controller]) > Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1] > InstallationDate: Installed on 2019-08-06 (1 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 27c6:5201 >Bus 001 Device 003: ID 8087:0a2b Intel Corp. >Bus 001 Device 002: ID 13d3:56b9 IMC Networks >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ASUSTeK COMPUTER INC. ZenBook S UX391UA > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic > root=UUID=6c2ff7ef-a93b-47fe-ae85-a60f10a4201f ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/18/2018 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: UX391UA.204 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: UX391UA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.family: ZenBook S > dmi.product.name: ZenBook S UX391UA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.97-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20180925-2 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839253/+subscriptions > -- 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/1839253 Title: Excessive screen tearing and flickering on Asus ZenBook S UX391UA Status in linux package in Ubuntu: Confirmed Bug description: I am experiencing a large amount of screen tearing flickering and artifacting. I've tried the common fix that is suggested on askubuntu.com which is editing the file /etc/X11/xorg.conf.d/20-intel- graphics.conf and this has not changed anything. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 7 02:06:01 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:10a1] InstallationDate:
[Kernel-packages] [Bug 1840261] Re: eoan/linux: 5.2.0-13.14 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Confirmed ** Tags removed: block-proposed-eoan ** Tags removed: block-proposed ** 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 1840259 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Testing - phase-changed: Monday, 19. August 2019 11:56 UTC + phase: Ready for Promote to Release + phase-changed: Thursday, 22. August 2019 22:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + promote-to-release: Pending -- ready to copy trackers: bionic/linux-hwe-edge: bug 1840259 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/1840261 Title: eoan/linux: 5.2.0-13.14 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1840259 (bionic/linux-hwe-edge) -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Release phase-changed: Thursday, 22. August 2019 22:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy trackers: bionic/linux-hwe-edge: bug 1840259 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840261/+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 1840708] Re: HP Envy with AMD Ryzen 5 2500U processor hangs on boot
No, not similar. I get no messages on the screen. And the messages recorded by the other user seem different from messages which I can see in my syslog file. In my case the computer is not completely dead (there are messages in the syslog file which confirm that e.g. WiFi connection is activated), only the display is dead. -- 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/1840708 Title: HP Envy with AMD Ryzen 5 2500U processor hangs on boot Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.3, kernel 5.0.0-25-generic When grub menu disappears, the screen remains blank. I include a syslog file from a failed boot. The important part is at line 1175: irq 7: nobody cared (try booting with the "irqpoll" option) This laptop boots correctly with the 4.18 kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840708/+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 1841084] Re: bionic/linux-aws: 4.15.0-1047.49 -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: 1841086 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Ready for Packaging - phase-changed: Thursday, 22. August 2019 17:14 UTC + phase: Packaging + phase-changed: Thursday, 22. August 2019 21:57 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 trackers: bionic/linux-aws/aws-kernel: bug 1841081 xenial/linux-aws-hwe: bug 1841083 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/1841084 Title: bionic/linux-aws: 4.15.0-1047.49 -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 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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1841086 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Thursday, 22. August 2019 21:57 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 trackers: bionic/linux-aws/aws-kernel: bug 1841081 xenial/linux-aws-hwe: bug 1841083 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841084/+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 1841084] Re: bionic/linux-aws: 4.15.0-1047.49 -proposed tracker
** Summary changed: - bionic/linux-aws: -proposed tracker + bionic/linux-aws: 4.15.0-1047.49 -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) => Sultan Alsawaf (kerneltoast) ** 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) => Sultan Alsawaf (kerneltoast) ** 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) => Sultan Alsawaf (kerneltoast) -- 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/1841084 Title: bionic/linux-aws: 4.15.0-1047.49 -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 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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1841086 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Thursday, 22. August 2019 21:57 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 trackers: bionic/linux-aws/aws-kernel: bug 1841081 xenial/linux-aws-hwe: bug 1841083 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841084/+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 1841086] Re: bionic/linux: 4.15.0-60.67 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 22. August 2019 17:11 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed,signed:building + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 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/1841086 Title: bionic/linux: 4.15.0-60.67 -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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 22. August 2019 17:11 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841086/+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 1841110] Re: Eoan update: v5.2.9 upstream stable release
** Changed in: linux (Ubuntu Eoan) Status: Confirmed => 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/1841110 Title: Eoan update: v5.2.9 upstream stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Committed 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: v5.2.9 upstream stable release from git://git.kernel.org/ Linux 5.2.9 iwlwifi: mvm: fix version check for GEO_TX_POWER_LIMIT support iwlwifi: mvm: don't send GEO_TX_POWER_LIMIT on version < 41 iwlwifi: mvm: fix a use-after-free bug in iwl_mvm_tx_tso_segment iwlwifi: mvm: fix an out-of-bound access iwlwifi: don't unmap as page memory that was mapped as single mwifiex: fix 802.11n/WPA detection KVM: arm/arm64: Sync ICH_VMCR_EL2 back when about to block KVM: Fix leak vCPU's VMCS value into other pCPU NFSv4: Fix an Oops in nfs4_do_setattr NFSv4: Check the return value of update_open_stateid() NFSv4: Fix delegation state recovery smb3: send CAP_DFS capability during session setup SMB3: Fix deadlock in validate negotiate hits reconnect dax: dax_layout_busy_page() should not unmap cow pages mac80211: don't WARN on short WMM parameters from AP ALSA: hda - Workaround for crackled sound on AMD controller (1022:1457) ALSA: hda - Don't override global PCM hw info flag ALSA: hiface: fix multiple memory leak bugs ALSA: firewire: fix a memory leak bug drm/i915: Fix wrong escape clock divisor init for GLK hwmon: (lm75) Fixup tmp75b clr_mask hwmon: (nct7802) Fix wrong detection of in4 presence can: peak_usb: pcan_usb_fd: Fix info-leaks to USB devices can: peak_usb: pcan_usb_pro: Fix info-leaks to USB devices KVM/nSVM: properly map nested VMCB ALSA: usb-audio: fix a memory leak bug HID: sony: Fix race condition between rumble and device remove. gen_compile_commands: lower the entry count threshold s390/dma: provide proper ARCH_ZONE_DMA_BITS value perf/core: Fix creating kernel counters for PMUs that override event->cpu perf/x86: Apply more accurate check on hypervisor platform perf/x86/intel: Fix invalid Bit 13 for Icelake MSR_OFFCORE_RSP_x register perf/x86/intel: Fix SLOTS PEBS event constraint tty/ldsem, locking/rwsem: Add missing ACQUIRE to read_failed sleep loop test_firmware: fix a memory leak bug scsi: scsi_dh_alua: always use a 2 second delay before retrying RTPG scsi: ibmvfc: fix WARN_ON during event pool release scsi: megaraid_sas: fix panic on loading firmware crashdump ARM: dts: bcm: bcm47094: add missing #cells for mdio-bus-mux ARM: davinci: fix sleep.S build error on ARMv4 nvme: fix memory leak caused by incorrect subsystem free nvme: ignore subnqn for ADATA SX6000LNP ACPI/IORT: Fix off-by-one check in iort_dev_find_its_id() drbd: dynamically allocate shash descriptor perf probe: Avoid calling freeing routine multiple times for same pointer perf session: Fix loading of compressed data split across adjacent records perf stat: Fix segfault for event group in repeat mode perf tools: Fix proper buffer size for feature processing perf script: Fix off by one in brstackinsn IPC computation ALSA: compress: Be more restrictive about when a drain is allowed ALSA: compress: Don't allow paritial drain operations on capture streams ALSA: compress: Prevent bypasses of set_params ALSA: compress: Fix regression on compressed capture streams s390/qdio: add sanity checks to the fast-requeue path cpufreq/pasemi: fix use-after-free in pas_cpufreq_cpu_init() arm64: dts: imx8mq: fix SAI compatible arm64: dts: imx8mm: Correct SAI3 RXC/TXFS pin's mux option #1 drm: silence variable 'conn' set but not used drm/msm/dpu: Correct dpu encoder spinlock initialization iommu/vt-d: Check if domain->pgd was allocated arm64: entry: SP Alignment Fault doesn't write to FAR_EL1 arm64: Force SSBS on context switch powerpc/papr_scm: Force a scm-unbind if initial scm-bind fails ARM: dts: imx6ul: fix clock frequency property name of I2C buses hwmon: (nct6775) Fix register address and added missed tolerance for nct6106 hwmon: (occ) Fix division by zero issue allocate_flower_entry: should check for null deref mac80211: don't warn about CW params when not using them mac80211: fix possible memory leak in ieee80211_assign_beacon nl80211: fix NL80211_HE_MAX_CAPABILITY_LEN iscsi_ibft: make ISCSI_IBFT
[Kernel-packages] [Bug 1841086] Re: bionic/linux: 4.15.0-60.67 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 22. August 2019 17:11 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,main:building,meta:failed,signed:queued + promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed,signed:building trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 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/1841086 Title: bionic/linux: 4.15.0-60.67 -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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 22. August 2019 17:11 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed,signed:building trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841086/+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 1841109] [NEW] arm64: large modules fail to load
Public bug reported: [Impact] The 3rd party nvidia driver fails to load on arm64 systems. [Test Case] sudo modprobe nvidia On failure: [ 812.512205] nvidia: loading out-of-tree module taints kernel. [ 812.512216] nvidia: module license 'NVIDIA' taints kernel. [ 812.512218] Disabling lock debugging due to kernel taint [ 812.711108] nvidia: module verification failed: signature and/or required key missing - tainting kernel [ 812.711656] module nvidia: unsupported RELA relocation: 275 [Fix] a257e02579e42 arm64/kernel: don't ban ADRP to work around Cortex-A53 erratum #843419 [Regression Risk] Regressions would most likely impact the loading of modules. To mitigate this risk, I've tested on a couple different arm64 servers - including loading of some the largest available modules - and have not seen any issues. All code changes are restricted to arm64, except for a new macro & #include in the generic linux/sizes.h header. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Summary changed: - arm64: nvidia driver fails to load + arm64: large modules fail to load ** Description changed: [Impact] The 3rd party nvidia driver fails to load on arm64 systems. [Test Case] sudo modprobe nvidia On failure: [ 812.512205] nvidia: loading out-of-tree module taints kernel. [ 812.512216] nvidia: module license 'NVIDIA' taints kernel. [ 812.512218] Disabling lock debugging due to kernel taint [ 812.711108] nvidia: module verification failed: signature and/or required key missing - tainting kernel [ 812.711656] module nvidia: unsupported RELA relocation: 275 [Fix] a257e02579e42 arm64/kernel: don't ban ADRP to work around Cortex-A53 erratum #843419 [Regression Risk] - Regressions would most likely impact the loading of modules. To mitigate this risk, I've tested on a couple different arm64 servers - including loading of some the largest available modules - and have not seen any issues. + Regressions would most likely impact the loading of modules. To mitigate this risk, I've tested on a couple different arm64 servers - including loading of some the largest available modules - and have not seen any issues. All code changes are restricted to arm64, except for a new macro & #include in the generic linux/sizes.h header. -- 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/1841109 Title: arm64: large modules fail to load Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: [Impact] The 3rd party nvidia driver fails to load on arm64 systems. [Test Case] sudo modprobe nvidia On failure: [ 812.512205] nvidia: loading out-of-tree module taints kernel. [ 812.512216] nvidia: module license 'NVIDIA' taints kernel. [ 812.512218] Disabling lock debugging due to kernel taint [ 812.711108] nvidia: module verification failed: signature and/or required key missing - tainting kernel [ 812.711656] module nvidia: unsupported RELA relocation: 275 [Fix] a257e02579e42 arm64/kernel: don't ban ADRP to work around Cortex-A53 erratum #843419 [Regression Risk] Regressions would most likely impact the loading of modules. To mitigate this risk, I've tested on a couple different arm64 servers - including loading of some the largest available modules - and have not seen any issues. All code changes are restricted to arm64, except for a new macro & #include in the generic linux/sizes.h header. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841109/+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 1841110] [NEW] Eoan update: v5.2.9 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.2.9 upstream stable release from git://git.kernel.org/ Linux 5.2.9 iwlwifi: mvm: fix version check for GEO_TX_POWER_LIMIT support iwlwifi: mvm: don't send GEO_TX_POWER_LIMIT on version < 41 iwlwifi: mvm: fix a use-after-free bug in iwl_mvm_tx_tso_segment iwlwifi: mvm: fix an out-of-bound access iwlwifi: don't unmap as page memory that was mapped as single mwifiex: fix 802.11n/WPA detection KVM: arm/arm64: Sync ICH_VMCR_EL2 back when about to block KVM: Fix leak vCPU's VMCS value into other pCPU NFSv4: Fix an Oops in nfs4_do_setattr NFSv4: Check the return value of update_open_stateid() NFSv4: Fix delegation state recovery smb3: send CAP_DFS capability during session setup SMB3: Fix deadlock in validate negotiate hits reconnect dax: dax_layout_busy_page() should not unmap cow pages mac80211: don't WARN on short WMM parameters from AP ALSA: hda - Workaround for crackled sound on AMD controller (1022:1457) ALSA: hda - Don't override global PCM hw info flag ALSA: hiface: fix multiple memory leak bugs ALSA: firewire: fix a memory leak bug drm/i915: Fix wrong escape clock divisor init for GLK hwmon: (lm75) Fixup tmp75b clr_mask hwmon: (nct7802) Fix wrong detection of in4 presence can: peak_usb: pcan_usb_fd: Fix info-leaks to USB devices can: peak_usb: pcan_usb_pro: Fix info-leaks to USB devices KVM/nSVM: properly map nested VMCB ALSA: usb-audio: fix a memory leak bug HID: sony: Fix race condition between rumble and device remove. gen_compile_commands: lower the entry count threshold s390/dma: provide proper ARCH_ZONE_DMA_BITS value perf/core: Fix creating kernel counters for PMUs that override event->cpu perf/x86: Apply more accurate check on hypervisor platform perf/x86/intel: Fix invalid Bit 13 for Icelake MSR_OFFCORE_RSP_x register perf/x86/intel: Fix SLOTS PEBS event constraint tty/ldsem, locking/rwsem: Add missing ACQUIRE to read_failed sleep loop test_firmware: fix a memory leak bug scsi: scsi_dh_alua: always use a 2 second delay before retrying RTPG scsi: ibmvfc: fix WARN_ON during event pool release scsi: megaraid_sas: fix panic on loading firmware crashdump ARM: dts: bcm: bcm47094: add missing #cells for mdio-bus-mux ARM: davinci: fix sleep.S build error on ARMv4 nvme: fix memory leak caused by incorrect subsystem free nvme: ignore subnqn for ADATA SX6000LNP ACPI/IORT: Fix off-by-one check in iort_dev_find_its_id() drbd: dynamically allocate shash descriptor perf probe: Avoid calling freeing routine multiple times for same pointer perf session: Fix loading of compressed data split across adjacent records perf stat: Fix segfault for event group in repeat mode perf tools: Fix proper buffer size for feature processing perf script: Fix off by one in brstackinsn IPC computation ALSA: compress: Be more restrictive about when a drain is allowed ALSA: compress: Don't allow paritial drain operations on capture streams ALSA: compress: Prevent bypasses of set_params ALSA: compress: Fix regression on compressed capture streams s390/qdio: add sanity checks to the fast-requeue path cpufreq/pasemi: fix use-after-free in pas_cpufreq_cpu_init() arm64: dts: imx8mq: fix SAI compatible arm64: dts: imx8mm: Correct SAI3 RXC/TXFS pin's mux option #1 drm: silence variable 'conn' set but not used drm/msm/dpu: Correct dpu encoder spinlock initialization iommu/vt-d: Check if domain->pgd was allocated arm64: entry: SP Alignment Fault doesn't write to FAR_EL1 arm64: Force SSBS on context switch powerpc/papr_scm: Force a scm-unbind if initial scm-bind fails ARM: dts: imx6ul: fix clock frequency property name of I2C buses hwmon: (nct6775) Fix register address and added missed tolerance for nct6106 hwmon: (occ) Fix division by zero issue allocate_flower_entry: should check for null deref mac80211: don't warn about CW params when not using them mac80211: fix possible memory leak in ieee80211_assign_beacon nl80211: fix NL80211_HE_MAX_CAPABILITY_LEN iscsi_ibft: make ISCSI_IBFT dependson ACPI instead of ISCSI_IBFT_FIND drm/amd/display: Increase size of audios array drm/amd/display: Only enable audio if speaker allocation exists drm/amd/display: Fix dc_create failure handling and 666 color depths drm/amd/display: allocate 4 ddc engines for RV2 drm/amd/display: put back front end initialization sequence drm/amd/display: use encoder's engine id to find matched free audio device drm/amd/display: fix DMCU hang when going into Modern Standby drm/amd/display: Wait for backlight programming completion in set backlight level drm/amd/display: Clock
[Kernel-packages] [Bug 1841086] Re: bionic/linux: 4.15.0-60.67 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 22. August 2019 17:11 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:building,meta:failed,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,main:building,meta:failed,signed:queued trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 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/1841086 Title: bionic/linux: 4.15.0-60.67 -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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 22. August 2019 17:11 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,main:building,meta:failed,signed:queued trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841086/+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
** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => 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/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: New 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 creating an ext4
[Kernel-packages] [Bug 1838208] Re: Wifi stops responding sporadically on lenovo-yoga-720-15ikb
I will note that sometimes, restarting network-manager doesn't work, especially if I have put the machine to sleep prior to trying to access the network. Here's a dmesg where it did come back after network-manager restart. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1838208/+attachment/5284074/+files/dmesg.txt -- 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
[Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
** Attachment added: "spinda.maas-curtin_config.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5284072/+files/spinda.maas-curtin_config.txt -- 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
[Kernel-packages] [Bug 1784665] Re: bcache: bch_allocator_thread(): hung task timeout
We're still seeing a bcache timeout failure during curtin install 2019-08-22T10:16:40+00:00 spinda cloud-init[1604]: finish: cmd-install/stage-partitioning/builtin/cmd-block-meta/clear-holders: FAIL: removing previous storage devices 2019-08-22T10:16:40+00:00 spinda cloud-init[1604]: TIMED BLOCK_META: 1203.679 I attached the rsyslog from a unit that failed. Linux version 4.15.0-59-generic (buildd@lgw01-amd64-035) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #66-Ubuntu SMP Wed Aug 14 10:56:44 UTC 2019 (Ubuntu 4.15.0-59.66-generic 4.15.18) ** Attachment added: "messages" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784665/+attachment/5284071/+files/messages ** Tags removed: verification-done-bionic ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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,
[Kernel-packages] [Bug 1841070] Re: S3 sleep/suspend fails with Linux 4.15.0-58-generic
Further to my previous comment, I have now tested the following additional mainline kernels from https://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D 4.16.0-041600rc1-generic 4.15.18-041518-generic 4.15.17-041517-generic The bug does not occur when running these kernels. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Confirmed Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841098] [NEW] PCI-passthrough instance creation problem RTX2080Ti
Public bug reported: I am running Openstack Ansible Rocky 18.1.8 on Ubuntu 18.04 nodes. I use PCI-passthrough (IOMMU vfio) on GTX1080Tis and and RTX2080Tis. The 1080s work fine, but 2080 instances take anywhere from 3 minutes to over 3 hours to start with qemu/KVM and the amount of time varies randomly, with the averaging being around 1.5hrs. I tried upgrading the kernel to 5.0.0 and it did not fix the issue. Downgrading the GPU hosts to Ubuntu 16.04 fixed the issue, they now start in 30 seconds or less. Sorry, but I do not have any logs. I couldn't find any errors in any system logs including enabling debugging on libvirtd. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1841098 Title: PCI-passthrough instance creation problem RTX2080Ti Status in linux package in Ubuntu: Incomplete Bug description: I am running Openstack Ansible Rocky 18.1.8 on Ubuntu 18.04 nodes. I use PCI-passthrough (IOMMU vfio) on GTX1080Tis and and RTX2080Tis. The 1080s work fine, but 2080 instances take anywhere from 3 minutes to over 3 hours to start with qemu/KVM and the amount of time varies randomly, with the averaging being around 1.5hrs. I tried upgrading the kernel to 5.0.0 and it did not fix the issue. Downgrading the GPU hosts to Ubuntu 16.04 fixed the issue, they now start in 30 seconds or less. Sorry, but I do not have any logs. I couldn't find any errors in any system logs including enabling debugging on libvirtd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841098/+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 1841098] 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 1841098 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/1841098 Title: PCI-passthrough instance creation problem RTX2080Ti Status in linux package in Ubuntu: Incomplete Bug description: I am running Openstack Ansible Rocky 18.1.8 on Ubuntu 18.04 nodes. I use PCI-passthrough (IOMMU vfio) on GTX1080Tis and and RTX2080Tis. The 1080s work fine, but 2080 instances take anywhere from 3 minutes to over 3 hours to start with qemu/KVM and the amount of time varies randomly, with the averaging being around 1.5hrs. I tried upgrading the kernel to 5.0.0 and it did not fix the issue. Downgrading the GPU hosts to Ubuntu 16.04 fixed the issue, they now start in 30 seconds or less. Sorry, but I do not have any logs. I couldn't find any errors in any system logs including enabling debugging on libvirtd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841098/+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 1841070] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284069/+files/UdevDb.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1840674] Re: xenial/linux-gcp: 4.15.0-1041.43 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1841086 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Testing - phase-changed: Thursday, 22. August 2019 17:06 UTC + phase: Ready for Testing + phase-changed: Thursday, 22. August 2019 17:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1840672 xenial/linux-gcp/gke-kernel: bug 1840673 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/1840674 Title: xenial/linux-gcp: 4.15.0-1041.43 -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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug 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: 1841086 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Testing phase-changed: Thursday, 22. August 2019 17:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1840672 xenial/linux-gcp/gke-kernel: bug 1840673 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840674/+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 1841070] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284068/+files/RfKill.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841070] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284070/+files/WifiSyslog.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841070] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284067/+files/PulseList.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841070] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284058/+files/CurrentDmesg.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841070] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284060/+files/IwConfig.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841070] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284057/+files/CRDA.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841070] Re: S3 sleep/suspend fails with Linux 4.15.0-58-generic
apport information ** Tags added: apport-collected ** Description changed: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20.1-0ubuntu2.19 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: patrick1845 F pulseaudio + DistroRelease: Ubuntu 16.04 + EcryptfsInUse: Yes + HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 + InstallationDate: Installed on 2016-09-16 (1069 days ago) + InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) + MachineType: PC Specialist Limited N350DW + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 + Tags: xenial xenial + Uname: Linux 4.15.0-58-generic x86_64 + UnreportableReason: The report belongs to a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: False + dmi.bios.date: 05/26/2016 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 5.11 + dmi.board.asset.tag: Tag 12345 + dmi.board.name: N350DW + dmi.board.vendor: CLEVO + dmi.board.version: Not Applicable + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: No Enclosure + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: + dmi.product.family: Not Applicable + dmi.product.name: N350DW + dmi.product.version: Not Applicable + dmi.sys.vendor: PC Specialist Limited ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284056/+files/AlsaInfo.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
[Kernel-packages] [Bug 1841070] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284061/+files/Lspci.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841070] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284062/+files/Lsusb.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841070] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284066/+files/ProcModules.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841070] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284065/+files/ProcInterrupts.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841070] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284063/+files/ProcCpuinfoMinimal.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841070] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284064/+files/ProcEnviron.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841070] HookError_generic.txt
apport information ** Attachment added: "HookError_generic.txt" https://bugs.launchpad.net/bugs/1841070/+attachment/5284059/+files/HookError_generic.txt -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrick1845 F pulseaudio DistroRelease: Ubuntu 16.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=72e179a8-b27c-42d3-9523-8f1cceacaa64 InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: PC Specialist Limited N350DW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-58-generic root=UUID=deeef076-c1e1-47ec-8ee4-d3b56fa179f9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-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.157.22 Tags: xenial xenial Uname: Linux 4.15.0-58-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 05/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N350DW dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd05/26/2016:svnPCSpecialistLimited:pnN350DW:pvrNotApplicable:rvnCLEVO:rnN350DW:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N350DW dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841086] Re: bionic/linux: 4.15.0-60.67 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 22. August 2019 17:11 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:building,meta:failed,signed:depwait trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 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/1841086 Title: bionic/linux: 4.15.0-60.67 -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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 22. August 2019 17:11 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:building,meta:failed,signed:depwait trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841086/+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: 5.0.0-1014.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 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 + phase: Packaging + phase-changed: Thursday, 22. August 2019 17:22 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded 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: 5.0.0-1014.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-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: Packaging phase-changed: Thursday, 22. August 2019 17:22 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded 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 1841070] 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 1841070 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: Incomplete Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1841084] Re: bionic/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 -- swm properties -- kernel-stable-master-bug: 1841086 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Holding before Packaging - phase-changed: Thursday, 22. August 2019 16:32 UTC + phase: Ready for Packaging + phase-changed: Thursday, 22. August 2019 17:14 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified trackers: bionic/linux-aws/aws-kernel: bug 1841081 xenial/linux-aws-hwe: bug 1841083 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/1841084 Title: bionic/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-lrm 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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1841086 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Ready for Packaging phase-changed: Thursday, 22. August 2019 17:14 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-aws/aws-kernel: bug 1841081 xenial/linux-aws-hwe: bug 1841083 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841084/+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: 5.0.0-1014.16 -proposed tracker
** Summary changed: - disco/linux-aws: -proposed tracker + disco/linux-aws: 5.0.0-1014.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) => Sultan Alsawaf (kerneltoast) ** 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) => Sultan Alsawaf (kerneltoast) -- 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: 5.0.0-1014.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-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: Packaging phase-changed: Thursday, 22. August 2019 17:22 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded 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 1841086] Re: bionic/linux: 4.15.0-60.67 -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-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Packaging - phase-changed: Thursday, 22. August 2019 16:33 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 22. August 2019 17:11 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 + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 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/1841086 Title: bionic/linux: 4.15.0-60.67 -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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Thursday, 22. August 2019 17:11 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,meta:depwait,signed:depwait trackers: bionic/linux-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841086/+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 1841070] Re: S3 sleep/suspend fails with Linux 4.15.0-58-generic
** Description changed: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) - There are no external USB devices connected when the bug occurs. There - are USB devices integral to the laptop and always present, none of which - are new or changed. + The bug occurs both with and without external USB devices connected. + There are USB devices integral to the laptop, which are always present. + + Laptop model: CLEVO N350DW + Processor: 4x Intel(R) Core(TM) i5-6600T CPU + BIOS date: 05/26/2016 + BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: New Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) The bug occurs both with and without external USB devices connected. There are USB devices integral to the laptop, which are always present. Laptop model: CLEVO N350DW Processor: 4x Intel(R) Core(TM) i5-6600T CPU BIOS date: 05/26/2016 BIOS version: 5.11 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
$ reverse-depends -b -r xenial libseccomp-dev
Reverse-Build-Depends
=
* golang-github-seccomp-libseccomp-golang
* lxc
* ocserv
* qemu
* systemd
* tor
* ubuntu-core-launcher
none of these appear to reference pkey_mprotect, so none should need a
rebuild with the xenial-hwe kernel; marking verification-xenial-done
based on that.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
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/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
seccomp)
Status in libseccomp package in Ubuntu:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in libseccomp source package in Bionic:
Invalid
Status in linux source package in Bionic:
Fix Released
Status in systemd source package in Bionic:
Invalid
Bug description:
Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
failing on Bionic on ppc64el with the error messages:
Operating on architecture: ppc
Failed to add n/a() rule for architecture ppc, skipping: Bad address
Operating on architecture: ppc64
Failed to add n/a() rule for architecture ppc64, skipping: Bad address
Operating on architecture: ppc64-le
Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical
argument out of domain
Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413,
function test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function
test_memory_deny_write_execute_mmap(). Aborting.
Aborted (core dumped)
FAIL: test-seccomp (code: 134)
Full logs at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz
The testcase passed with systemd version 237-3ubuntu10.13 running on the same
4.15.0-45 kernel on ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+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 1841070] Re: S3 sleep/suspend fails with Linux 4.15.0-58-generic
I have tested the following mainline kernels from https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D 5.3.0-050300rc5-generic 4.15.1-041501-generic 4.15.0-041500-generic The bug does not occur when running these kernels. ** Package changed: linux-meta-hwe (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841070 Title: S3 sleep/suspend fails with Linux 4.15.0-58-generic Status in linux package in Ubuntu: New Bug description: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) There are no external USB devices connected when the bug occurs. There are USB devices integral to the laptop and always present, none of which are new or changed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841070/+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: 5.0.0-1015.15~18.04.1 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-restricted-modules-gcp 5.0.0-1015.15~18.04.1 - is in universe instead of restricted linux-modules-nvidia-390-5.0.0-1015-gcp 5.0.0-1015.15~18.04.1 - is in universe instead of restricted linux-modules-nvidia-390-gcp 5.0.0-1015.15~18.04.1 - is in universe instead of restricted linux-modules-nvidia-418-5.0.0-1015-gcp 5.0.0-1015.15~18.04.1 - is in universe instead of restricted linux-modules-nvidia-418-gcp 5.0.0-1015.15~18.04.1 - is in universe instead of restricted Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** 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 -- boot-testing-requested: true kernel-stable-master-bug: 1840808 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 22. August 2019 13:26 UTC reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + promote-to-proposed: Stalled -- packages are in the wrong component + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress 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: 5.0.0-1015.15~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete 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-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 -- boot-testing-requested: true kernel-stable-master-bug: 1840808 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 22. August 2019 13:26 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- packages are in the wrong component regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress 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 1840674] Re: xenial/linux-gcp: 4.15.0-1041.43 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1841086 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Promote to Proposed - phase-changed: Thursday, 22. August 2019 10:25 UTC + phase: Testing + phase-changed: Thursday, 22. August 2019 17:06 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1840672 xenial/linux-gcp/gke-kernel: bug 1840673 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/1840674 Title: xenial/linux-gcp: 4.15.0-1041.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug 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: 1841086 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 22. August 2019 17:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1840672 xenial/linux-gcp/gke-kernel: bug 1840673 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840674/+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 1841070] [NEW] S3 sleep/suspend fails with Linux 4.15.0-58-generic
You have been subscribed to a public bug: Regression: My laptop has become unable to enter S3 sleep/suspend. (A.K.A. Suspend to RAM) It seems to go through all the motions, including shutting down network interfaces and stopping the hard disk, but fails at the last moment and immediately starts back up again, showing the lock screen. 4.15.0-58-generic is affected. 4.15.0-55-generic is NOT affected. In /var/log/syslog, it seems that the cause might be that a USB device fails to suspend. (Log excerpt attached.) There are no external USB devices connected when the bug occurs. There are USB devices integral to the laptop and always present, none of which are new or changed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-generic-hwe-16.04 4.15.0.58.79 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 CurrentDesktop: KDE Date: Thu Aug 22 15:05:09 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-09-16 (1069 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-meta-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- S3 sleep/suspend fails with Linux 4.15.0-58-generic https://bugs.launchpad.net/bugs/1841070 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 1840932] Re: [Regression] failed to compile seccomp test from ubuntu_kernel_selftests
** Changed in: linux (Ubuntu Bionic) 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/1840932 Title: [Regression] failed to compile seccomp test from ubuntu_kernel_selftests Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Commit c33a23ff8ffc (selftests: skip seccomp get_metadata test if not real root) in Bionic tree Is causing compilation error for the seccomp test in ubuntu_kernel_selftests: $ sudo make -C tools/testing/selftests TARGETS=seccomp run_tests make: Entering directory '/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests' make[1]: Entering directory '/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/seccomp' gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf seccomp_bpf.c: In function ‘syscall_restart’: seccomp_bpf.c:2685:3: warning: implicit declaration of function ‘XFAIL’; did you mean ‘EFAULT’? [-Wimplicit-function-declaration] XFAIL(return, "get_metadata requires real root"); ^ EFAULT seccomp_bpf.c:2685:9: error: expected expression before ‘return’ XFAIL(return, "get_metadata requires real root"); ^~ Makefile:12: recipe for target 'seccomp_bpf' failed make[1]: *** [seccomp_bpf] Error 1 make[1]: Leaving directory '/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/seccomp' Makefile:73: recipe for target 'all' failed make: *** [all] Error 2 make: Leaving directory '/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests' [Fix] Commit upstream 3aa415dd2128 (selftests: skip seccomp get_metadata test if not real root) depends on d057dc4e35e1 (seccomp: add a selftest for get_metadata), but the latter has been reverted on bionic as part of bug #1837664. The get_metadata testcase doesn't exist anymore, the backport of the patch ended up changing syscall_restart instead. So the best solution is to revert c33a23ff8ffc, which is not needed and is causing trouble. [Test Case] Run the seccomp kernel selftests. [Regression potential] No regression potential. The commit introduced a regression by being wrongly backported, so reverting it will fix the issue and has no risk. --- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1040-gke 4.15.0-1040.42 ProcVersionSignature: Ubuntu 4.15.0-1040.42-gke 4.15.18 Uname: Linux 4.15.0-1040-gke x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Aug 21 14:33:19 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-gke-4.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1840932/+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 1840935] Re: [Regression] net test from ubuntu_kernel_selftests failed due to bpf test compilation issue
** Changed in: linux (Ubuntu Bionic) 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/1840935 Title: [Regression] net test from ubuntu_kernel_selftests failed due to bpf test compilation issue Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Commit a25d38b54163 (bpf: relax verifier restriction on BPF_MOV | BPF_ALU) in Bionic tree Is causing bpf test compilation failure: $ sudo make -C tools/testing/selftests TARGETS=bpf run_tests make: Entering directory '/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests' make[1]: Entering directory '/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf' make -C ../../../lib/bpf OUTPUT=/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf/ make[2]: Entering directory '/home/jenkins/ubuntu-gke-4.15-bionic/tools/lib/bpf' Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from latest version at 'include/uapi/linux/bpf.h' make[2]: Leaving directory '/home/jenkins/ubuntu-gke-4.15-bionic/tools/lib/bpf' make -C ../../../lib/bpf OUTPUT=/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf/ make[2]: Entering directory '/home/jenkins/ubuntu-gke-4.15-bionic/tools/lib/bpf' Warning: Kernel ABI header at 'tools/include/uapi/linux/bpf.h' differs from latest version at 'include/uapi/linux/bpf.h' make[2]: Leaving directory '/home/jenkins/ubuntu-gke-4.15-bionic/tools/lib/bpf' gcc -Wall -O2 -I../../../include/uapi -I../../../lib -I../../../../include/generated -I../../../includetest_verifier.c /home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf/libbpf.a /home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf/cgroup_helpers.c -lcap -lelf -lrt -o /home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf/test_verifier test_verifier.c:2173:4: error: ‘struct bpf_test’ has no member named ‘retval’ .retval = 0, ^~ ../lib.mk:121: recipe for target '/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf/test_verifier' failed make[1]: *** [/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf/test_verifier] Error 1 make[1]: Leaving directory '/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests/bpf' Makefile:73: recipe for target 'all' failed make: *** [all] Error 2 make: Leaving directory '/home/jenkins/ubuntu-gke-4.15-bionic/tools/testing/selftests' [Fix] Bionic misses 111e6b45315c (selftests/bpf: make test_verifier run most programs), which adds the 'retval' member to struct bpf_test. The fix is a SAUCE patch to remove setting '.retval = 0'. [Test Case] Run bpf kernel selftests. [Regression Potential] Low. There's a chance that not backporting 111e6b45315c (selftests/bpf: make test_verifier run most programs) will cause possible bugs on the changes added by a25d38b54163 (bpf: relax verifier restriction on BPF_MOV | BPF_ALU) to remain uncaught. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1040-gke 4.15.0-1040.42 ProcVersionSignature: Ubuntu 4.15.0-1040.42-gke 4.15.18 Uname: Linux 4.15.0-1040-gke x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Aug 21 15:09:32 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-gke-4.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1840935/+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 1839990] Re: bionic/linux-gcp: -proposed tracker
*** This bug is a duplicate of bug 1840806 *** https://bugs.launchpad.net/bugs/1840806 ** 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 1839989 (xenial/linux-gcp) - -- swm properties -- + kernel-stable-master-bug: 1841086 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Packaging phase-changed: Wednesday, 14. August 2019 11:15 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-gcp/gcp-kernel: bug 1839986 xenial/linux-gcp: bug 1839989 variant: debs ** Tags added: kernel-sru-derivative-of-1841086 -- 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/1839990 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 -- swm properties -- kernel-stable-master-bug: 1841086 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Packaging phase-changed: Wednesday, 14. August 2019 11:15 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-gcp/gcp-kernel: bug 1839986 xenial/linux-gcp: bug 1839989 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839990/+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 1839979] Re: bionic/linux-snapdragon: 4.15.0-1061.68 -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 1839978 (dragonboard-kernel) - -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1840006 + kernel-stable-master-bug: 1841086 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Signoff phase-changed: Wednesday, 21. August 2019 08:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839978 variant: debs ** Tags removed: kernel-sru-derivative-of-1840006 ** Tags added: kernel-sru-derivative-of-1841086 -- 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/1839979 Title: bionic/linux-snapdragon: 4.15.0-1061.68 -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-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1841086 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Signoff phase-changed: Wednesday, 21. August 2019 08:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839978 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839979/+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 1841086] [NEW] bionic/linux: 4.15.0-60.67 -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Thursday, 22. August 2019 16:33 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-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-lrm Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: Confirmed ** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-2019.08.12-6 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-lrm Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: bionic kernel-release-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned)
[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 + kernel-stable-master-bug: 1841086 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 ** Tags removed: kernel-sru-derivative-of-1840006 ** Tags added: kernel-sru-derivative-of-1841086 -- 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1841086 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
[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 + kernel-stable-master-bug: 1841086 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: 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 ** Tags removed: kernel-sru-backport-of-1840006 ** Tags added: kernel-sru-backport-of-1841086 -- 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: Fix Released 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1841086 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: 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 1839997] Re: bionic/linux-oracle: 4.15.0-1022.25 -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 1839996 (xenial/linux-oracle) + https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1840006 + kernel-stable-master-bug: 1841086 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Signoff phase-changed: Wednesday, 21. August 2019 08:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1839996 variant: debs ** Tags removed: kernel-sru-derivative-of-1840006 ** Tags added: kernel-sru-derivative-of-1841086 -- 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/1839997 Title: bionic/linux-oracle: 4.15.0-1022.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1841086 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Signoff phase-changed: Wednesday, 21. August 2019 08:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1839996 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839997/+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 1840674] Re: xenial/linux-gcp: 4.15.0-1041.43 -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 1840672 (gcp-kernel), bug 1840673 (gke-kernel) - -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1840006 + kernel-stable-master-bug: 1841086 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 22. August 2019 10:25 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-gcp/gcp-kernel: bug 1840672 xenial/linux-gcp/gke-kernel: bug 1840673 variant: debs ** Tags removed: kernel-sru-backport-of-1840006 ** Tags added: kernel-sru-backport-of-1841086 -- 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/1840674 Title: xenial/linux-gcp: 4.15.0-1041.43 -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: Fix Committed 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 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: 1841086 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Promote to Proposed phase-changed: Thursday, 22. August 2019 10:25 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-gcp/gcp-kernel: bug 1840672 xenial/linux-gcp/gke-kernel: bug 1840673 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840674/+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 1841084] Re: bionic/linux-aws: -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + bionic/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 -- swm properties -- kernel-stable-master-bug: 1841086 + packages: + lrm: linux-restricted-modules-aws + main: linux-aws + meta: linux-meta-aws + phase: Holding before Packaging + phase-changed: Thursday, 22. August 2019 16:32 UTC + reason: + prepare-package: Holding -- waiting for master bug + trackers: + bionic/linux-aws/aws-kernel: bug 1841081 + xenial/linux-aws-hwe: bug 1841083 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/1841084 Title: bionic/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-lrm 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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1841086 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Packaging phase-changed: Thursday, 22. August 2019 16:32 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-aws/aws-kernel: bug 1841081 xenial/linux-aws-hwe: bug 1841083 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841084/+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 1841084] Re: 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 -- swm properties -- + kernel-stable-master-bug: 1841086 variant: debs ** Tags added: kernel-sru-derivative-of-1841086 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium -- 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/1841084 Title: bionic/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-lrm 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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1841086 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Packaging phase-changed: Thursday, 22. August 2019 16:32 UTC reason: prepare-package: Holding -- waiting for master bug trackers: bionic/linux-aws/aws-kernel: bug 1841081 xenial/linux-aws-hwe: bug 1841083 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841084/+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 1841086] Re: bionic/linux: 4.15.0-60.67 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Ready for Packaging - phase-changed: Thursday, 22. August 2019 16:23 UTC + phase: Packaging + phase-changed: Thursday, 22. August 2019 16:33 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-aws: bug 1841084 + bionic/linux-fips: bug 1839998 + bionic/linux-gke-4.15: bug 1839992 + bionic/linux-ibm-gt: bug 1840974 + bionic/linux-kvm: bug 1839993 + bionic/linux-oem: bug 1839980 + bionic/linux-oracle: bug 1839997 + bionic/linux-raspi2: bug 1839977 + bionic/linux-snapdragon: bug 1839979 + bionic/linux/pc-kernel: bug 1841078 + bionic/linux/pc-lowlatency-kernel: bug 1841080 + xenial/linux-azure: bug 1840002 + xenial/linux-gcp: bug 1840674 + xenial/linux-hwe: bug 1841085 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/1841086 Title: bionic/linux: 4.15.0-60.67 -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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Thursday, 22. August 2019 16:33 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-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841086/+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 1839980] Re: bionic/linux-oem: 4.15.0-1051.60 -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 + https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: 1840006 + kernel-stable-master-bug: 1841086 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Monday, 19. August 2019 09:21 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 variant: debs ** Tags removed: kernel-sru-derivative-of-1840006 ** Tags added: kernel-sru-derivative-of-1841086 -- 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/1839980 Title: bionic/linux-oem: 4.15.0-1051.60 -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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1841086 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Monday, 19. August 2019 09:21 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 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839980/+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 1841086] Re: bionic/linux: -proposed tracker
** Summary changed: - linux: -proposed tracker + bionic/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 -- swm properties -- + packages: + lrm: linux-restricted-modules + main: linux + meta: linux-meta + signed: linux-signed + phase: Ready for Packaging + phase-changed: Thursday, 22. August 2019 16:23 UTC + reason: + 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 in Ubuntu. https://bugs.launchpad.net/bugs/1841086 Title: bionic/linux: 4.15.0-60.67 -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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Thursday, 22. August 2019 16:33 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-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841086/+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 1839998] Re: bionic/linux-fips: 4.15.0-1016.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 -- swm properties -- - kernel-stable-master-bug: 1840006 + kernel-stable-master-bug: 1841086 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Packaging phase-changed: Wednesday, 14. August 2019 21:20 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 variant: debs ** Tags removed: kernel-sru-derivative-of-1840006 ** Tags added: kernel-sru-derivative-of-1841086 -- 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/1839998 Title: bionic/linux-fips: 4.15.0-1016.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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New 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 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: 1841086 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Packaging phase-changed: Wednesday, 14. August 2019 21:20 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 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839998/+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 1840006] Re: bionic/linux: 4.15.0-59.66 -proposed tracker
*** This bug is a duplicate of bug 1841086 *** https://bugs.launchpad.net/bugs/1841086 ** This bug has been marked a duplicate of bug 1841086 linux: -proposed tracker -- 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/1840006 Title: bionic/linux: 4.15.0-59.66 -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: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: 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 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 backports: bug 1840002 (xenial/linux-azure), bug 1840005 (xenial/linux-hwe), bug 1840674 (xenial/linux-gcp) derivatives: bug 1839974 (pc-kernel), bug 1839975 (pc-lowlatency-kernel), bug 1839977 (linux-raspi2), bug 1839979 (linux-snapdragon), bug 1839980 (linux-oem), bug 1839985 (linux-aws), bug 1839992 (linux-gke-4.15), bug 1839993 (linux-kvm), bug 1839997 (linux-oracle), bug 1839998 (linux-fips), bug 1840974 (linux-ibm-gt) -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 15. August 2019 15:26 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: bionic/linux-aws: bug 1839985 bionic/linux-fips: bug 1839998 bionic/linux-gcp: bug 1839990 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1839974 bionic/linux/pc-lowlatency-kernel: bug 1839975 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1840005 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840006/+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 1840974] Re: bionic/linux-ibm-gt: 4.15.0-1033.35 -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: 1840006 + kernel-stable-master-bug: 1841086 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Ready for Testing phase-changed: Thursday, 22. August 2019 14:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs ** Tags removed: kernel-sru-derivative-of-1840006 ** Tags added: kernel-sru-derivative-of-1841086 -- 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/1840974 Title: bionic/linux-ibm-gt: 4.15.0-1033.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1841086 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Ready for Testing phase-changed: Thursday, 22. August 2019 14:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840974/+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 1839993] Re: bionic/linux-kvm: 4.15.0-1043.43 -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: 1840006 + kernel-stable-master-bug: 1841086 packages: main: linux-kvm meta: linux-meta-kvm phase: Signoff phase-changed: Monday, 19. August 2019 17:50 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 ** Tags removed: kernel-sru-derivative-of-1840006 ** Tags added: kernel-sru-derivative-of-1841086 -- 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/1839993 Title: bionic/linux-kvm: 4.15.0-1043.43 -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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1841086 packages: main: linux-kvm meta: linux-meta-kvm phase: Signoff phase-changed: Monday, 19. August 2019 17:50 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/1839993/+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 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
** Also affects: linux-aws-hwe (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws-hwe (Ubuntu Artful) Status: New => Invalid ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-aws-edge (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-aws-hwe (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-aws-edge (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-aws-hwe (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-aws-hwe (Ubuntu Xenial) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux-aws-hwe (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-aws-hwe (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux-aws-hwe (Ubuntu Disco) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux-aws-edge (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-aws-hwe (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux-aws (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux-aws-edge (Ubuntu) Status: In Progress => Fix Committed ** Changed in: linux-aws-hwe (Ubuntu) Status: New => Fix Committed ** Changed in: linux-aws-hwe (Ubuntu) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws-edge package in Ubuntu: Fix Committed Status in linux-aws-hwe package in Ubuntu: Fix Committed Status in linux source package in Xenial: Invalid Status in linux-aws source package in Xenial: Invalid Status in linux-aws-edge source package in Xenial: Invalid Status in linux-aws-hwe source package in Xenial: Fix Committed Status in linux source package in Artful: Won't Fix Status in linux-aws source package in Artful: Invalid Status in linux-aws-edge source package in Artful: Invalid Status in linux-aws-hwe source package in Artful: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Committed Status in linux-aws-edge source package in Bionic: Fix Committed Status in linux-aws-hwe source package in Bionic: Invalid Status in linux source package in Cosmic: Invalid Status in linux-aws source package in Cosmic: Invalid Status in linux-aws-edge source package in Cosmic: Invalid Status in linux-aws-hwe source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-aws source package in Disco: Fix Committed Status in linux-aws-edge source package in Disco: Invalid Status in linux-aws-hwe source package in Disco: Invalid Bug description: [Impact] File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods. [Test case] $ sudo perf record -k 1 -e instructions:u ./java -agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32 $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted $ sudo perf report -f -i ./perf.data.jitted [Fix] Include java build dependencies and install the library into linux-tools package. [Regression potential] Small regression potential, an extra file is distributed and is not automatically linked to anything. It could impact the build, which was tested. ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- linux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c
[Kernel-packages] [Bug 1841086] Re: bionic/linux: 4.15.0-60.67 -proposed tracker
** Summary changed: - bionic/linux: -proposed tracker + bionic/linux: 4.15.0-60.67 -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) => Stefan Bader (smb) ** 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) => Stefan Bader (smb) ** 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) => Stefan Bader (smb) ** 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) => Stefan Bader (smb) -- 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/1841086 Title: bionic/linux: 4.15.0-60.67 -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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Thursday, 22. August 2019 16:33 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-aws: bug 1841084 bionic/linux-fips: bug 1839998 bionic/linux-gke-4.15: bug 1839992 bionic/linux-ibm-gt: bug 1840974 bionic/linux-kvm: bug 1839993 bionic/linux-oem: bug 1839980 bionic/linux-oracle: bug 1839997 bionic/linux-raspi2: bug 1839977 bionic/linux-snapdragon: bug 1839979 bionic/linux/pc-kernel: bug 1841078 bionic/linux/pc-lowlatency-kernel: bug 1841080 xenial/linux-azure: bug 1840002 xenial/linux-gcp: bug 1840674 xenial/linux-hwe: bug 1841085 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841086/+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 1811254] Re: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1811254 Title: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LED's in the [f5] Speaker-mute, [f8] Micro-mute and [f11] Wireless on/off Buttons do not show the status. Disturbing is also the LED in [f11] permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 12 logs, unfortunately the upload did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log rfkill_list.txt udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt Previous attempts: My on-board search for other HP ProBook Hotkey LED-issues led me to this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586 but the solution to the file: /etc/modprobe.d/alsa-base.conf to supplement the entry: options snd-hda-intel mode = mute-led-gpio did not lead to the solution here. Presumably, the failure results from a different ubuntu-version and/or a another kernel. Information: This problem was previously discussed on linuxmintusers.de: https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+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 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1833716 Title: System crashes on hot adding a core with drmgr command (4.15.0-48-generic) Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] On Bionic GA kernel (4.15.0), hot add of cpu with drmgr causes the kernel to crash. The patches identified to fix these issues disables changing the NUMA associations for CPUs and Memory at runtime by default. [Test] # drmgr -c cpu -r -q 1 # drmgr -c cpu -a -q 1 Test kernel available in ppa:ubuntu-power-triage/lp1833716 Please see comment #2 for before and after results with the patches applied. [Fix] 558f86493df0 powerpc/numa: document topology_updates_enabled, disable by default 2d4d9b308f8f powerpc/numa: improve control of topology updates [Regression Potential] The two patches relate to powerpc/numa and does not impact other architectures or platform code. Regression potential is low. [Other Information] == Comment: #0 - Hari Krishna Bathini - 2019-05-07 13:18:35 == ---Problem Description--- On 4.15.0-48-generic kernel, hot adding a cpu with drmgr is crashing the kernel with below traces: --- root@ubuntu:~# drmgr -c cpu -r -q 1 Validating CPU DLPAR capability...yes. CPU 9 root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# root@ubuntu:~# drmgr -c cpu -a -q 1 Validating CPU DLPAR capability...yes. [ 218.555493] BUG: arch topology borken [ 218.03] the DIE domain not a subset of the NODE domain [ 218.12] BUG: arch topology borken [ 218.16] the DIE domain not a subset of the NODE domain [ 218.23] BUG: arch topology borken [ 218.28] the DIE domain not a subset of the NODE domain [ 218.35] BUG: arch topology borken [ 218.39] the DIE domain not a subset of the NODE domain [ 218.45] BUG: arch topology borken [ 218.50] the DIE domain not a subset of the NODE domain [ 218.56] BUG: arch topology borken [ 218.60] the DIE domain not a subset of the NODE domain [ 218.67] BUG: arch topology borken [ 218.71] the DIE domain not a subset of the NODE domain [ 218.77] BUG: arch topology borken [ 218.81] the DIE domain not a subset of the NODE domain [ 218.555672] Unable to handle kernel paging request for data at address 0x9332ae80f961139f [ 218.555679] Faulting instruction address: 0xc01768cc [ 218.555686] Oops: Kernel access of bad area, sig: 11 [#1] [ 218.555691] LE SMP NR_CPUS=2048 NUMA pSeries [ 218.555699] Modules linked in: vmx_crypto crct10dif_vpmsum sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ibmvscsi ibmveth crc32c_vpmsum [ 218.555745] CPU: 8 PID: 276 Comm: kworker/8:1 Not tainted 4.15.0-48-generic #51-Ubuntu [ 218.555757] Workqueue: events cpuset_hotplug_workfn [ 218.555763] NIP: c01768cc LR: c01769a8 CTR: [ 218.555770] REGS: c001f5f1f530 TRAP: 0380 Not tainted (4.15.0-48-generic) [ 218.555776] MSR: 80009033 CR: 22824228 XER: 0004 [ 218.555789] CFAR: c0176920 SOFTE: 1 [ 218.555789] GPR00: c01769a8 c001f5f1f7b0 c16eb400 c001f7bfd200 [ 218.555789] GPR04: 0001 0008 0010 [ 218.555789] GPR08: 0018 c001f7bfd408 [ 218.555789] GPR12: 8000 c7a35800 0007 c001f549d900 [ 218.555789] GPR16: 0040 c1722494 c001f0f29400 0001 [ 218.555789] GPR20: c001ffb68580 0008 c11d8580 c171dd78 [ 218.555789] GPR24: e830 ec30 12af [ 218.555789] GPR28: 102f c001f7bfd200
[Kernel-packages] [Bug 1819485] Re: x86: add support for AMD Rome
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1819485 Title: x86: add support for AMD Rome Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Bug description: [Impact] * Some upstream patches are missing to properly support the AMD Rome architecture, without them the affected systems cannot work correctly. [Test Case] * No test case provided (tests have been made by the bug reporter using the affected platform) [Fix] * The following commits are required to properly support this architecture: 818b7587b4d3 x86: irq_remapping: Move irq remapping mode enum e881dbd5d4a6 iommu/amd: Add support for higher 64-bit IOMMU Control Register 90fcffd9cf5e iommu/amd: Add support for IOMMU XT mode 210ba1201ff9 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef2 x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baff x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc28 x86/MCE/AMD: Fix the thresholding machinery initialization order [Regression Potential] * All the patches have been applied upstream and they have been tested on the newly supported platform with positive feedback. [Original bug report] The following patches will bring Rome support into 18.04. The patches are all localized to AMD source code. CCP/PSP: dcbc0c6e4aa1ef269179351ac615fd08ddefc849 crypto: ccp - Add support for new CCP/PSP device ID ad01a984f512c42c9f4fe79d36b9cddbc6156a3f crypto: ccp - Support register differences between PSP devices A few others: 210ba1201ff950b3d05bfd8fa5d47540cea393c0 hwmon/k10temp: Add support for AMD family 17h, model 30h CPUs be3518a16ef270e3b030a6ae96055f83f51bd3dd x86/amd_nb: Add PCI device IDs for family 17h, model 30h 556e4c62baffa71e2045a298379db7e57dd47f3d x86/amd_nb: Add support for newer PCI topologies dedf7dce4cec5c0abe69f4fa6938d5100398220b hwmon/k10temp, x86/amd_nb: Consolidate shared device IDs 60c8144afc287ef09ce8c1230c6aa972659ba1bb x86/MCE/AMD: Fix the thresholding machinery initialization order --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-02-28 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: enp33s0f0 no wireless extensions. lono wireless extensions. enp33s0f1 no wireless extensions. MachineType: AMD Corporation DAYTONA_X 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 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=6500165b-63c3-4a3e-bbee-ca9f43bb1784 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: RDY0071B dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DAYTONA_X dmi.board.vendor: AMD Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 2 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrRDY0071B:bd01/18/2019:svnAMDCorporation:pnDAYTONA_X:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rnDAYTONA_X:rvrTobefilledbyO.E.M.:cvnTobefilledbyO.E.M.:ct2:cvrTobefilledbyO.E.M.: dmi.product.family: Default string
[Kernel-packages] [Bug 1813118] Re: alignment test in powerpc from ubuntu_kernel_selftests failed on B/C Power9
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1813118 Title: alignment test in powerpc from ubuntu_kernel_selftests failed on B/C Power9 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: == Justification == The copy_unaligned / paste_unaligned / paste_last_unaligned test in powerpc/alignment will fail on a Power9 node as which implements ISA 3.0B, but the test was designed base on ISA 3.0. From the commit message: This is a test of the ISA 3.0 "copy" instruction. That instruction has an L field, which if set to 1 specifies that "the instruction identifies the beginning of a move group" (pp 858). That's also referred to as "copy first" vs "copy". In ISA 3.0B the copy instruction does not have an L field, and the corresponding bit in the instruction must be set to 1. This test is generating a "copy" instruction, not a "copy first", and so on Power9 (which implements 3.0B), this results in an illegal instruction. So just drop the test entirely. We still have copy_first_unaligned to test the "copy first" behaviour. == Fix == * 83039f22 (selftests/powerpc: Remove Power9 copy_unaligned test) Patch can be cherry-picked into C, for Bionic it needs patches for bug 1828935 to land first (8d191587) to make it a clean cherry-pick. It's already landed in D and onward. == Test == Tested on a Power9 server with Cosmic, the broken tests will be removed correctly. == Regression Potential == Low. Code change limited to testing tools and just removing broken tests. We still have copy_first_unaligned to test the "copy first" behaviour. == Original Bug Report == This issue was only spotted on Power9 system "balter", for Power8 system, it has passed (skipped, and marked as passed) with this test: TAP version 13 selftests: copy_unaligned test: test_copy_unaligned tags: git_version:unknown !! child died by signal 4 failure: test_copy_unaligned not ok 1..1 selftests: copy_unaligned [FAIL] selftests: copy_first_unaligned test: test_copy_first_unaligned tags: git_version:unknown success: test_copy_first_unaligned ok 1..2 selftests: copy_first_unaligned [PASS] selftests: paste_unaligned test: test_paste_unaligned tags: git_version:unknown !! child died by signal 4 failure: test_paste_unaligned not ok 1..3 selftests: paste_unaligned [FAIL] selftests: paste_last_unaligned test: test_paste_last_unaligned tags: git_version:unknown !! child died by signal 4 failure: test_paste_last_unaligned not ok 1..4 selftests: paste_last_unaligned [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 24 06:50 seq crw-rw 1 root audio 116, 33 Jan 24 06:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 24 07:05:20 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 1.24 0.89 0.66 3/1412 8319
[Kernel-packages] [Bug 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle 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 Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid 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: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1772412] Re: zfs 0.7.9 fixes a bug (https://github.com/zfsonlinux/zfs/pull/7343) that hangs the system completely
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verification-needed-xenial' to 'verification-failed-
xenial'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1772412
Title:
zfs 0.7.9 fixes a bug (https://github.com/zfsonlinux/zfs/pull/7343)
that hangs the system completely
Status in linux package in Ubuntu:
Invalid
Status in zfs-linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in zfs-linux source package in Bionic:
Fix Released
Bug description:
SRU Bionic
== SRU Justification ==
Intensive I/O such as performed by ZFS send/receive can cause hangs because
of monopolization of the global system_taskq. The outcome is that z_zvol hung
tasks occur and I/O gets blocked.
== Fix ==
Upstream ZFS commit 77d8a0f1a4d0b2f59cee63088f7987cb38e66538 ("Fix
hung z_zvol tasks during 'zfs receive'") fixes this issue, it adds a
dedicated per-pool prefetch taskq that prevents the traverse code from
monopolizing the global (and limited) system_taskq by inappropriately
scheduling long running tasks on it. This fixes the z_zvol hung tasks.
A trivial backport is required for Bionic ZFS.
== Testcase ==
Perform large send/receives. Occasionally they lock up. With the fix,
this issue is addressed and no more lockups occur. Also must pass the
full ZFS ubuntu autotest tests to prove no regressions occur.
== Regression Potential ==
This fix adds more per-pool prefetch taskq's so we have more kernel
resources being used. There is therefore a very small risk that this
may impact ZFS running on memory and CPU constrained systems.
However, the fix is small, has been upstream for a while and is in
Cosmic+ releases and has not caused any regressions, so I think this
is a relatively safe fix.
--
I have experienced the problems fixed by this commit
https://github.com/zfsonlinux/zfs/pull/7343 a few times on my NAS. The
system hangs completely when it occurs. It looks like 0.7.9 brings
other interesting bug fixes that potentially freeze the system.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772412/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784485/+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 1761379] Re: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: In Progress Status in linux-aws-edge package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in linux-aws source package in Artful: Invalid Status in linux-aws-edge source package in Artful: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: In Progress Status in linux-aws-edge source package in Bionic: In Progress Status in linux source package in Cosmic: Invalid Status in linux-aws source package in Cosmic: Invalid Status in linux-aws-edge source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-aws source package in Disco: In Progress Status in linux-aws-edge source package in Disco: Invalid Bug description: [Impact] File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods. [Test case] $ sudo perf record -k 1 -e instructions:u ./java -agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32 $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted $ sudo perf report -f -i ./perf.data.jitted [Fix] Include java build dependencies and install the library into linux-tools package. [Regression potential] Small regression potential, an extra file is distributed and is not automatically linked to anything. It could impact the build, which was tested. ---Problem Description--- File libperf-jvmti.so is missing in linux-tools-common deb making it impossible to use perf for the JVM JITed methods ---uname output--- linux-image-4.13.0-36-generic Machine Type = not relevant ---Debugger--- A debugger is not configured ---Steps to Reproduce--- File libperf-jvmti.so is missing in linux-tools-common deb provided for Ubuntu 17.10 making it impossible to use perf for the JVM JITed methods. I also checked if the file is available on launchpad (https://launchpad.net/ubuntu/+source/linux) for Bionic Beaver proposed (main) at it's also absent there: gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-common_4.15.0-13.14_all.deb | fgrep jvm gromero@ltc-wspoon3:~/download$ dpkg -c linux-tools-4.15.0-13-generic_4.15.0-13.14_ppc64el.deb | fgrep jvm I do see the file in tools/perf/jvmti dir in the source .tar.gz, but apparently it's no being packaged in any .deb file? Thanks. Userspace tool common name: perf The userspace tool has the following bit modes: 64-bit Userspace tool obtained from project website: na To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+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 1825942] Re: kernel crash : net_sched race condition in tcindex_destroy()
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1825942 Title: kernel crash : net_sched race condition in tcindex_destroy() Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Bug description: [Impact] It is possible to trigger a NULL pointer dereference in tcindex_delete() with a simple reproducer script, this is because in tcindex_set_parms() when old_r doesn't exist we set the new exts to cr.exts that can be uninitialized, triggering the NULL pointer dereference. In addition to that we may also hit a race condition in tcindex_destroy() (as pointed out in the original bug report and also here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542#10), that is also fixed upstream, but it requires 4b79817f7add "net_sched: switch to rcu_work". However adding these changes introduces three memory leak problems in cls_tcindex (that can be easily verified using the same test case). These leaks are also fixed upstream by 711ff09f3330 "net_sched: fix a memory leak in cls_tcindex" and 000d2aeda70c "net_sched: fix two more memory leaks in cls_tcindex", so we need to backport also these two additional fixes. After all these fixes are applied the test case doesn't seem to trigger any bug. [Test Case] #!/bin/sh -ex modprobe ifb while true; do tc qdisc add dev ifb0 root handle 2:0 prio bands 5 tc qdisc add dev ifb0 parent 2:5 sfq tc filter add dev ifb0 parent 2:0 protocol ip prio 5 handle 0 tcindex mask 0 classid 2:5 pass_on tc qdisc del dev ifb0 root || true done [Fix] * Fixes required to solve this problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2df8bee5654bb2b7312662ca6810d4dc16b0b67f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=8015d93ebd27484418d4952284fd02172fa4b0b2 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=033b228e7f26b29ae37f8bfa1bc6b209a5365e9f https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1db817e75f5b9387b8db11e37d5f0624eb9223e0 [Regression Potential] * All upstream fixes, tested on the affected platform, backport changes are minimal. [Original bug report] I am running into a kernel crash issue using latest Ubuntu 4.15 kernel. It does not appear to have been fixed in Ubuntu-4.15.0-48.51. This crash has also been reported for debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921542 The kernel crash issue was fixed in February in the Linux kernel: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=056a17982adbd52b2a6c5ec6266cee4521cd931b I did test one of the recent kernel-ppa/mainline kernels, more specifically: linux-image-unsigned-4.19.34-041934-generic_4.19.34-041934.201904051741_amd64.deb It seems to fix the problem, that is, no crashes experienced so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825942/+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 1833147] Re: hns: attempt to restart autoneg when disabled should report error
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1833147 Title: hns: attempt to restart autoneg when disabled should report error Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: [Impact] Asking the driver to restart autonegotiation silently fails when autonegotation has been disabled. It should report an error. [Test Case] sudo ethtool -s ethX autoneg off sudo ethtool -r ethX [Fix] ed29ca8b95925 net: hns: Restart autoneg need return failed when autoneg off [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833147/+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 1831103] Re: bionic: netlink: potential shift overflow in netlink_bind()
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1831103 Title: bionic: netlink: potential shift overflow in netlink_bind() Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Bug description: [Impact] The check for correctness of netlink_bind() userspace supplied parameter is done by applying a bitmask made from ngroups shift. However if we have more than 64 groups the shift results in an overflow causing an incorrect validation of the netlink_bind() parameters. This has been fixed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 And this fix has been applied to xenial, cosmic and disco (apparently only bionic is missing it). [Test Case] I've been able to reproduce this problem using a script with acpid to handle ACPI hibernate events. The script is the following: $ cat /etc/acpi/actions/sleep.sh #!/bin/sh echo "1=$1 2=$2" >> /home/ubuntu/acpi-event.log Any kernel that has the fix (xenial and cosmic for example) are logging two events (input and netlink) when the sleep button is fired: $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN 1=button/sleep 2=LNXSLPBN:00 The bionic kernel, instead, is logging only one event (input, netlink is lost): $ cat /home/ubuntu/acpi-event.log 1=button/sleep 2=SBTN [Fix] Fix that solves this problem: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91874ecf32e41b5d86a4cb9d60e0bee50d828058 [Regression Potential] Upsteram fix, tested on the affected platform, all other kernel releases have this fix applied already, so regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831103/+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 1833140] Re: hns: fix ICMP6 neighbor solicitation messages discard problem
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- xenial' to 'verification-done-xenial'. If the problem still exists, change the tag 'verification-needed-xenial' to 'verification-failed- xenial'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-xenial -- 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/1833140 Title: hns: fix ICMP6 neighbor solicitation messages discard problem Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: In Progress Bug description: [Impact] ICMP6 neighbor solicitation messages are discarded. [Test Case] Regression tested only [Fix] ea401685a20b5 net: hns: fix unsigned comparison to less than zero f058e46855dcb net: hns: fix ICMP6 neighbor solicitation messages discard problem [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833140/+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
