[Kernel-packages] [Bug 1847192] [NEW] drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL platforms
Public bug reported: [Reproduce Steps] 1. Enter s2idle 2. Press power button to wake up the system 3. The Select Audio Device dialog show up [Results] Expected: There is no dialog show up Actual: The Select Audio Device dialog show up ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: Incomplete ** Tags: originate-from-1842025 somerville ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Tags added: originate-from-1842025 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847192 Title: drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL platforms Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Reproduce Steps] 1. Enter s2idle 2. Press power button to wake up the system 3. The Select Audio Device dialog show up [Results] Expected: There is no dialog show up Actual: The Select Audio Device dialog show up To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847192/+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 1847192] 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 1847192 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/1847192 Title: drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL platforms Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Reproduce Steps] 1. Enter s2idle 2. Press power button to wake up the system 3. The Select Audio Device dialog show up [Results] Expected: There is no dialog show up Actual: The Select Audio Device dialog show up To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847192/+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 1847193] [NEW] ath10k_pci 0000:02:00.0: firmware crashed!
Public bug reported: the wifi failed randomly, and it seems always happens with error message: " ath10k_pci :02:00.0: firmware crashed!" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 14:52:39 2019 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux-firmware 1.173.9 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1057-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True ** Affects: oem-priority Importance: Critical Assignee: Alex Tu (alextu) Status: New ** Affects: linux-signed-oem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-collected bionic ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Tags added: apport-collected ** Description changed: the wifi failed randomly, and it seems always happens with error message: " ath10k_pci :02:00.0: firmware crashed!" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 14:52:39 2019 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.7 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + Dependencies: + + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-08-11 (57 days ago) + InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + Package: linux-firmware 1.173.9 + PackageArchitecture: all + ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-1057-oem x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1847193 Title: ath10k_pci :02:00.0: firmware crashed! Status in OEM Priority Project: New Status in linux-signed-oem package in Ubuntu: New Bug description: the wifi failed randomly, and it seems always happens with error message: " ath10k_pci :02:00.0: firmware crashed!" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 14:52:39 2019 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux-firmware 1.173.9 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1057-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchp
[Kernel-packages] [Bug 1847193] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1847193/+attachment/5295313/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1847193 Title: ath10k_pci :02:00.0: firmware crashed! Status in OEM Priority Project: New Status in linux-signed-oem package in Ubuntu: New Bug description: the wifi failed randomly, and it seems always happens with error message: " ath10k_pci :02:00.0: firmware crashed!" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 14:52:39 2019 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux-firmware 1.173.9 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1057-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847193/+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 1847193] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1847193/+attachment/5295312/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1847193 Title: ath10k_pci :02:00.0: firmware crashed! Status in OEM Priority Project: New Status in linux-signed-oem package in Ubuntu: New Bug description: the wifi failed randomly, and it seems always happens with error message: " ath10k_pci :02:00.0: firmware crashed!" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 14:52:39 2019 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux-firmware 1.173.9 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1057-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847193/+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 1841193] Re: s390x load + decompress time of kernel image with lz4 is 2x slower than lzo
Just checked Eoan's master tree and this config patch is in and tagged with Ubuntu-5.3.0-11.12 (and newer) and since there is already 5.3.0.13.14 in Eoan's release pocket: "linux-generic | 5.3.0.13.14 | eoan| s390x" I'm closing this ticket as Fix Released. ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released ** Information type changed from Private to Public -- 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/1841193 Title: s390x load + decompress time of kernel image with lz4 is 2x slower than lzo Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Canonical Kernel Performance Team has been doing benchmarks on loading & decompressing time of the kernel images to select the fastest compression. On x86_64 lz4 came out as the best one. On our s390x load + decompress time of kernel image with lz4 appeared to be 2x slower than lzo. Tested on z13 mainframde, whilst kernel is compiled targetingging -march=zEC12. Which is a bit surprising. Are there any performance improvements that can be done to kernel lz4? You can see assessment details over at the public bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840934 I wonder if IBM teams can try different kernel compression algorithms to doublecheck that indeed load+decompress time of lzo kernel image is the fastest, and faster than lz4 or gzip. Also, would that change with z14 and the hw accelerated decompression there? Is that implemented for the kernel decompressors? We will be switching kernel image compression to lzo with the v5.3 kernel on s390x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1841193/+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 1841193] Comment bridged from LTC Bugzilla
--- Comment From h.carst...@de.ibm.com 2019-08-30 07:12 EDT--- --- Comment From h.carst...@de.ibm.com 2019-08-30 07:52 EDT--- --- Comment From h.carst...@de.ibm.com 2019-08-30 16:25 EDT--- -- 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/1841193 Title: s390x load + decompress time of kernel image with lz4 is 2x slower than lzo Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Canonical Kernel Performance Team has been doing benchmarks on loading & decompressing time of the kernel images to select the fastest compression. On x86_64 lz4 came out as the best one. On our s390x load + decompress time of kernel image with lz4 appeared to be 2x slower than lzo. Tested on z13 mainframde, whilst kernel is compiled targetingging -march=zEC12. Which is a bit surprising. Are there any performance improvements that can be done to kernel lz4? You can see assessment details over at the public bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840934 I wonder if IBM teams can try different kernel compression algorithms to doublecheck that indeed load+decompress time of lzo kernel image is the fastest, and faster than lz4 or gzip. Also, would that change with z14 and the hw accelerated decompression there? Is that implemented for the kernel decompressors? We will be switching kernel image compression to lzo with the v5.3 kernel on s390x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1841193/+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 1846424] Re: 19.10 ZFS Update failed on 2019-10-02
Sorry, but this is ridiculous. After the upgrade to 19.10, the system worked fine for a week. I should export/import ~700 GB of data to get an standard update working? Why should your advice help this time? If I'm stupid enough to move 700GB of data around, I will probably have the same problem again with the next zfs update. With my 40 years of ICT experience as OS designer, department manager and chief architect of Eurocontrol (the European FAA), I would say that your upgrade process should be so robust, that it can at least handle a normal datapool, like hp-data with normal datasets. I do not remember having these problems with 18.04 on my laptop or 19.04 on my desktop. If Canonical can't solve this problem, I can't use 19.10 and I will stay on 19.04 for my Ryzen/VEGA desktop. For my laptop I consider; - ignore the error messages after updates and run ZFS without those bugfixes. - install 18.04 again - re-installing 19.10 in e.g November/December by copying it from ext4 or from an official ZFS install on an USB disk, since ZFS itself is working fine, only the ZFS update process fucks up. - Install Pop! OS, that would be the first non-Ubuntu distro I use since 2008. -- 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/1846424 Title: 19.10 ZFS Update failed on 2019-10-02 Status in zfs-linux package in Ubuntu: Invalid Bug description: On all my systems the update from zfs-initrams_0.8.1-1ubuntu12_amd64.deb failed the same is true for zfs-zed and zfsutils-linux. The system still runs on 0.8.1-1ubuntu11_amd64. The first error message was about a failing mount and at the end it announced that all 3 modules were not updated. I have the error on Xubuntu 19.10, Ubuntu Mate 19.10 on my laptop i5-2520M and in a VBox VM on a Ryzen 3 2200G with Ubuntu 19.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+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 1841193] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2019-10-08 03:28 EDT--- IBM bugzilla status -> closed, Fix Released with Eoan -- 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/1841193 Title: s390x load + decompress time of kernel image with lz4 is 2x slower than lzo Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Canonical Kernel Performance Team has been doing benchmarks on loading & decompressing time of the kernel images to select the fastest compression. On x86_64 lz4 came out as the best one. On our s390x load + decompress time of kernel image with lz4 appeared to be 2x slower than lzo. Tested on z13 mainframde, whilst kernel is compiled targetingging -march=zEC12. Which is a bit surprising. Are there any performance improvements that can be done to kernel lz4? You can see assessment details over at the public bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840934 I wonder if IBM teams can try different kernel compression algorithms to doublecheck that indeed load+decompress time of lzo kernel image is the fastest, and faster than lz4 or gzip. Also, would that change with z14 and the hw accelerated decompression there? Is that implemented for the kernel decompressors? We will be switching kernel image compression to lzo with the v5.3 kernel on s390x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1841193/+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 1831587] Re: brightness control not work with OLED panel
Same issue for me on an ThinkPad X1 extreme (gen 2), EDID info: # edid-decode /sys/class/drm/card0-eDP-1/edid [09:29:37] Extracted contents: header: 00 ff ff ff ff ff ff 00 serial number: 4c 83 41 41 00 00 00 00 13 1d version: 01 04 basic params:b5 22 13 78 02 chroma info: 94 91 ae 51 3e b7 24 0b 50 54 established: 00 00 00 standard:01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 descriptor 1:f0 d4 00 40 f1 70 18 80 30 20 44 00 58 c2 10 00 00 1b descriptor 2:f0 d4 00 40 f1 70 18 80 30 20 44 00 58 c2 10 00 00 1b descriptor 3:00 00 00 0f 00 ff 09 3c ff 09 3c 2c 80 00 00 00 00 00 descriptor 4:00 00 00 fe 00 41 54 4e 41 35 36 57 52 30 38 2d 30 20 extensions: 01 checksum:15 Manufacturer: SDC Model 4141 Serial Number 0 Made week 19 of 2019 EDID version: 1.4 Digital display 10 bits per primary color channel DisplayPort interface Maximum image size: 34 cm x 19 cm Gamma: 2.20 Supported color formats: RGB 4:4:4 First detailed timing is preferred timing Established timings supported: Standard timings supported: Detailed mode: Clock 545.120 MHz, 344 mm x 194 mm 3840 3888 3920 4160 hborder 0 2160 2164 2168 2184 vborder 0 +hsync -vsync Detailed mode: Clock 545.120 MHz, 344 mm x 194 mm 3840 3888 3920 4160 hborder 0 2160 2164 2168 2184 vborder 0 +hsync -vsync Manufacturer-specified data, tag 15 ASCII string: ATNA56WR08-0 Has 1 extension blocks Checksum: 0x15 (valid) CEA extension block Extension version: 3 11 bytes of CEA data Extended tag: Colorimetry data block xvYCC601 xvYCC709 sYCC601 AdobeYCC601 AdobeRGB BT2020cYCC BT2020YCC BT2020RGB Extended tag: HDR static metadata data block Electro optical transfer functions: Traditional gamma - SDR luminance range Traditional gamma - HDR luminance range SMPTE ST2084 Supported static metadata descriptors: Static metadata type 1 Desired content max luminance: 115 Desired content max frame-average luminance: 109 Desired content min luminance: 7 0 native detailed modes Checksum: 0xab (valid) EDID block does NOT conform to EDID 1.3! Missing name descriptor Missing monitor ranges Detailed block string not properly terminated -- 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/1831587 Title: brightness control not work with OLED panel Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Triaged Bug description: image: disco 19.04 kernel: 5.0.0-15-generic also verified failed on linux-image-unsigned-5.2.0-050200rc2-generic also refer to : - https://askubuntu.com/questions/824949/lenovo-thinkpad-x1-yoga-oled-brightness - https://bugs.freedesktop.org/show_bug.cgi?id=97883 Linux can not control the brightness on the OLED panel in the traditional way [1]. Although there's a workaround from the community [2] that to execute script while brightness hotkey event is triggered. But if we want to upstream it, it's still a problem to recognize the OLED panel so that the system knows when to go workaround. - EDID of my laptop which has OLED: https://paste.ubuntu.com/p/w7rVqJTYDy/ - EDID of the same model without OLED: https://paste.ubuntu.com/p/P3ChhX9yBJ/ there's a kernel patch related OLED for reference: - https://patchwork.kernel.org/patch/6133471/ [1] https://wiki.ubuntu.com/Kernel/Debugging/Backlight [2] https://askubuntu.com/questions/824949/lenovo-thinkpad-x1-yoga-oled-brightness To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831587/+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 1847198] Re: amdgpu kernel module should be used instead of radeon on amd graphic
** Package changed: linux-meta-oem (Ubuntu) => linux-oem (Ubuntu) ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1847198 Title: amdgpu kernel module should be used instead of radeon on amd graphic Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in linux-oem package in Ubuntu: New Status in linux-oem source package in Bionic: New Bug description: there're some graphic be supported both on amdgpu and radeon. But somehow kernel might pick radeon instead of amdgpu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Oct 8 03:33:43 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847198/+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 1847198] [NEW] amdgpu kernel module should be used instead of radeon on amd graphic
Public bug reported: there're some graphic be supported both on amdgpu and radeon. But somehow kernel might pick radeon instead of amdgpu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Oct 8 03:33:43 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: oem-priority Importance: High Assignee: Alex Tu (alextu) Status: New ** Affects: oem-priority/bionic Importance: Undecided Assignee: AceLan Kao (acelankao) Status: New ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Importance: Critical => High ** Also affects: oem-priority/bionic Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1847198 Title: amdgpu kernel module should be used instead of radeon on amd graphic Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in linux-oem package in Ubuntu: New Status in linux-oem source package in Bionic: New Bug description: there're some graphic be supported both on amdgpu and radeon. But somehow kernel might pick radeon instead of amdgpu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Oct 8 03:33:43 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847198/+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 1847198] Re: amdgpu kernel module should be used instead of radeon on amd graphic
** Changed in: oem-priority/bionic Assignee: (unassigned) => AceLan Kao (acelankao) -- 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/1847198 Title: amdgpu kernel module should be used instead of radeon on amd graphic Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in linux-oem package in Ubuntu: New Status in linux-oem source package in Bionic: New Bug description: there're some graphic be supported both on amdgpu and radeon. But somehow kernel might pick radeon instead of amdgpu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Oct 8 03:33:43 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847198/+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 1847201] Re: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1847201 Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: made upgrade using update-manager ProblemType: Package DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Oct 8 09:52:47 2019 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-05-18 (142 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1.1 apt 1.8.3 SourcePackage: bluez Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A1IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-14A1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: GS40 6QE Phantom dmi.product.sku: Default string dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:0A:FA:40 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:775 acl:0 sco:0 events:59 errors:0 TX bytes:3668 acl:0 sco:0 commands:59 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1847201/+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 1844021] Re: Suspend stopped working from 4.4.0-157 onwards
Please try again. -- 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/1844021 Title: Suspend stopped working from 4.4.0-157 onwards Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading the kernel above 4.4.0-154, starting with 4.4.0-157, suspend does not work for me anymore. Never had such an issue in the last 6 years. This is the relevant output when suspend fails: [ 328.25] PM: Suspending system (mem) [ 328.288902] Suspending console(s) (use no_console_suspend to debug) [ 328.289118] wlp1s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) [ 328.289209] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [ 328.289570] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 328.289600] sd 0:0:0:0: [sda] Stopping disk [ 328.291700] sd 1:0:0:0: [sdb] Stopping disk [ 328.312413] xhci_hcd :03:00.0: WARN: xHC save state timeout [ 328.312456] suspend_common(): xhci_pci_suspend+0x0/0x70 returns -110 [ 328.312461] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110 [ 328.312465] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110 [ 328.312483] PM: Device :03:00.0 failed to suspend async: error -110 [ 328.848109] PM: Some devices failed to suspend, or early wake event detected This is my relevant lspci -v output: 03:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller (prog-if 30 [XHCI]) Subsystem: Samsung Electronics Co Ltd ASM1042 SuperSpeed USB Host Controller Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f050 (64-bit, non-prefetchable) [size=32K] Capabilities: Kernel driver in use: xhci_hcd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844021/+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 1847201] [NEW] package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1
Public bug reported: made upgrade using update-manager ProblemType: Package DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Oct 8 09:52:47 2019 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-05-18 (142 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1.1 apt 1.8.3 SourcePackage: bluez Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A1IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-14A1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: GS40 6QE Phantom dmi.product.sku: Default string dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. hciconfig: hci0: Type: Primary Bus: USB BD Address: 9C:B6:D0:0A:FA:40 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:775 acl:0 sco:0 events:59 errors:0 TX bytes:3668 acl:0 sco:0 commands:59 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1847201 Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: made upgrade using update-manager ProblemType: Package DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Oct 8 09:52:47 2019 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-05-18 (142 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1.1 apt 1.8.3 SourcePackage: bluez Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStat
[Kernel-packages] [Bug 1846424] Re: 19.10 ZFS Update failed on 2019-10-02
The size of the pool is not particularly relevant. It sounds like you think I'm asking you to backup and restore your pool, which I definitely am not. A pool "import" is somewhat like "mounting" a pool (though it's not literally mounting, because mounting is something that happens with filesystems). An "export" is similarly like unmounting. As I said, those instructions were intended to be a _safe_ way for you to return your system to working order. It's likely not necessary to boot into recovery mode, or export the pool to resolve this. The key thing is that /vms and /hp-data are non-empty. Fix that and your mounting issue will be resolved. I was suggesting you go into recovery mode and export the data pool to avoid the potential for accidents. But really, if you only use `rmdir` rather than `rm -rf`, you should be safe. Root-on-ZFS installs are not supported by Ubuntu or Canonical. Canonical is working on providing experimental support for Root-on-ZFS in the installer for 19.10, which should be out this month. I do not work for Canonical. I provide the upstream ZFS-on-Linux Root- on-ZFS HOWTOs for Debian and Ubuntu as a volunteer project. I have never guaranteed any in-place upgrade path. And you likely didn't follow my HOWTO anyway, as your dataset naming and mount properties don't match those from the HOWTO. I certainly agree that this is fragile. But it's an unofficial, experimental setup. That comes with the territory. Important progress is being made, and this will hopefully be more robust in the future. -- 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/1846424 Title: 19.10 ZFS Update failed on 2019-10-02 Status in zfs-linux package in Ubuntu: Invalid Bug description: On all my systems the update from zfs-initrams_0.8.1-1ubuntu12_amd64.deb failed the same is true for zfs-zed and zfsutils-linux. The system still runs on 0.8.1-1ubuntu11_amd64. The first error message was about a failing mount and at the end it announced that all 3 modules were not updated. I have the error on Xubuntu 19.10, Ubuntu Mate 19.10 on my laptop i5-2520M and in a VBox VM on a Ryzen 3 2200G with Ubuntu 19.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+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 1847201] Re: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to restart
** Summary changed: - package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 + package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to restart bluetooth.service: Unit -.mount is masked.] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1847201 Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to restart bluetooth.service: Unit -.mount is masked.] Status in bluez package in Ubuntu: New Bug description: made upgrade using update-manager ProblemType: Package DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Tue Oct 8 09:52:47 2019 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-05-18 (142 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.6ubuntu1.1 apt 1.8.3 SourcePackage: bluez Title: package bluez 5.50-0ubuntu2.1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A1IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-14A1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: GS40 6QE Phantom dmi.product.sku: Default string dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:0A:FA:40 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:775 acl:0 sco:0 events:59 errors:0 TX bytes:3668 acl:0 sco:0 commands:59 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1847201/+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 1824559] Re: Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling frequency)
** 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/1824559 Title: Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling frequency) Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have an issue with a lenovo yoga mouse. This mouse has 2 working mode either bluetooth or with a provided usb dongle. USB dongle works fine, but bluetooth don't. Cursor is slow and laggy. "evhz" (https://gitlab.com/iankelling/evhz) reports 22Hz in bluetooth mouse while USB mode and other mouse reports 125Hz. Polling speed is too slow. I tried different howto suggesting to change usbhid mousepoll value => does not help. The mouse seems handled by btusb module, not usbhid (modprobe -r usbhid killed my other mouse, but not the lenovo, while modprobe -r btusb killed the lenovo). I tried 2 laptops (XPS9370 with 18.04, kernel 4.18 and kernek 5.07 and an older dell Precision M6400 16.04 kernel 4.15). Bluetooth pairing works well, either with gnome bluetooth interface or with "bluetoothctl" Both laptops reports ~20-22Hz polling speed with evhz (and same laggy behavior) I also tried 2 bluetooth interface on the XPS13 9370 : the integrated bluetooth and a Sabrent USB Bluetooth 4.0 (to connect with the Sabrent, I have switched off integrated bluetooth with rfkill). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) Uname: Linux 5.0.7-050007-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 12 18:05:16 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-10 (337 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.7-050007-generic root=UUID=d36c5071-0243-427d-8fe1-7416c3b775f1 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2019-03-02 (40 days ago) dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.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.8.1:bd02/14/2019: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. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:8B:33:C6 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:12041 acl:294 sco:0 events:363 errors:0 TX bytes:8633 acl:76 sco:0 commands:171 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824559/+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 1847109] Re: [Ubuntu 18.04] Wrong cpu-mf counter number
** Summary changed: - [Ubuntu 18.04] Ubuntu 18.04.3 - wrong cpu-mf counter number + [Ubuntu 18.04] Wrong cpu-mf counter number ** Summary changed: - [Ubuntu 18.04] Wrong cpu-mf counter number + Ubuntu 18.04 - wrong cpu-mf counter number -- 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/1847109 Title: Ubuntu 18.04 - wrong cpu-mf counter number Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: New Bug description: Kernel: Linux t35lp11 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:15:19 UTC 2019 s390x s390x s390x GNU/Linux Description/Reproduction: The cpu-mf counter LAST_HOST_TRANSLATIONS has the wrong number. # cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS event=0x00e9 should be event=0x00e8 Fix already available: commit 81507f38d427ebed3291a3c153a798937c998140 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1847109/+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 1847198] Re: amdgpu kernel module should be used instead of radeon on amd graphic
** Attachment added: "udevadm.log" https://bugs.launchpad.net/oem-priority/+bug/1847198/+attachment/5295339/+files/udevadm.log -- 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/1847198 Title: amdgpu kernel module should be used instead of radeon on amd graphic Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in linux-oem package in Ubuntu: New Status in linux-oem source package in Bionic: New Bug description: there're some graphic be supported both on amdgpu and radeon. But somehow kernel might pick radeon instead of amdgpu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Oct 8 03:33:43 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847198/+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 1847198] Re: amdgpu kernel module should be used instead of radeon on amd graphic
When will upstream migrate CI/SI to use amdgpu? We need to think of upgrades, and if upstream (AMD) doesn't know when or if that will happen, then we'd need to keep the change "forever". -- 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/1847198 Title: amdgpu kernel module should be used instead of radeon on amd graphic Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in linux-oem package in Ubuntu: New Status in linux-oem source package in Bionic: New Bug description: there're some graphic be supported both on amdgpu and radeon. But somehow kernel might pick radeon instead of amdgpu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Oct 8 03:33:43 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847198/+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 1847198] Re: amdgpu kernel module should be used instead of radeon on amd graphic
** Attachment added: "modinfo-radeon.log" https://bugs.launchpad.net/oem-priority/+bug/1847198/+attachment/5295341/+files/modinfo-radeon.log -- 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/1847198 Title: amdgpu kernel module should be used instead of radeon on amd graphic Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in linux-oem package in Ubuntu: New Status in linux-oem source package in Bionic: New Bug description: there're some graphic be supported both on amdgpu and radeon. But somehow kernel might pick radeon instead of amdgpu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Oct 8 03:33:43 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847198/+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 1834578] Re: Mouse stop working
Can you check if: 1. This mouse works fine with other machine 2. It looks like you have been using Bionic for over 280 days, can you boot with older 4.15 kernel to see if your mouse works with older 4.15 kernel (prior to 4.15.0-53.57-generic)? 3. This mouse works fine with other version of Ubuntu Thanks ** 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/1834578 Title: Mouse stop working Status in linux package in Ubuntu: Incomplete Bug description: USB mouse stop working randomly ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-53.57-generic 4.15.18 Uname: Linux 4.15.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 28 10:24:54 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-52-generic, x86_64: installed nvidia, 390.116, 4.15.0-53-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-52-generic, x86_64: installed virtualbox, 5.2.18, 4.15.0-53-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d3] InstallationDate: Installed on 2018-09-21 (280 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 009: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 0518:5111 EzKEY Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-53-generic root=UUID=8e5738ba-3515-4603-abfb-a837482ef7ba ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0809 dmi.board.asset.tag: Default string dmi.board.name: PRIME B250M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0809:bd07/07/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834578/+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 1847198] Re: amdgpu kernel module should be used instead of radeon on amd graphic
** Attachment added: "modinfo-amdgpu.log" https://bugs.launchpad.net/oem-priority/+bug/1847198/+attachment/5295340/+files/modinfo-amdgpu.log -- 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/1847198 Title: amdgpu kernel module should be used instead of radeon on amd graphic Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in linux-oem package in Ubuntu: New Status in linux-oem source package in Bionic: New Bug description: there're some graphic be supported both on amdgpu and radeon. But somehow kernel might pick radeon instead of amdgpu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Oct 8 03:33:43 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847198/+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 1846122] Re: trusty/linux-azure: 4.15.0-1061.66~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846123 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Monday, 07. October 2019 20:33 UTC reason: - promote-signing-to-proposed: Pending -- ready for review + promote-signing-to-proposed: Stalled -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1846122 Title: trusty/linux-azure: 4.15.0-1061.66~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846123 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Monday, 07. October 2019 20:33 UTC reason: promote-signing-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846122/+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 1847212] [NEW] touchpad not working after upgrade to 5.0.0-31 kernel
Public bug reported: touchpad is not avaliable after upgrade to linux-image-5.0.0-31-generic It works on 5.0.0-29 kernel. Laptop model: MSI GS40 6QE-091RU ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-31-generic 5.0.0-31.33 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vkovalen 1900 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Oct 8 10:37:31 2019 InstallationDate: Installed on 2019-05-18 (142 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 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A1IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-14A1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: GS40 6QE Phantom dmi.product.sku: Default string dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco regression-update -- 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/1847212 Title: touchpad not working after upgrade to 5.0.0-31 kernel Status in linux package in Ubuntu: New Bug description: touchpad is not avaliable after upgrade to linux-image-5.0.0-31-generic It works on 5.0.0-29 kernel. Laptop model: MSI GS40 6QE-091RU ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-31-generic 5.0.0-31.33 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vkovalen 1900 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Oct 8 10:37:31 2019 InstallationDate: Installed on 2019-05-18 (142 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 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A1IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-14A1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalia
[Kernel-packages] [Bug 1847215] [NEW] test
Public bug reported: test ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 04:45:58 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1847215 Title: test Status in linux-signed-oem package in Ubuntu: New Bug description: test ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 04:45:58 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem/+bug/1847215/+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 1847215] Re: test
** Changed in: linux-signed-oem (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1847215 Title: test Status in linux-signed-oem package in Ubuntu: Invalid Bug description: test ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 04:45:58 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem/+bug/1847215/+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 1847212] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1847212 Title: touchpad not working after upgrade to 5.0.0-31 kernel Status in linux package in Ubuntu: Confirmed Bug description: touchpad is not avaliable after upgrade to linux-image-5.0.0-31-generic It works on 5.0.0-29 kernel. Laptop model: MSI GS40 6QE-091RU ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-31-generic 5.0.0-31.33 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vkovalen 1900 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Oct 8 10:37:31 2019 InstallationDate: Installed on 2019-05-18 (142 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 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A1IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-14A1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: GS40 6QE Phantom dmi.product.sku: Default string dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847212/+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 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances
on the new HWE kernel from ubuntu 18.04, which is linux 5.0, the modules are not present anymore nf_conntrack_ipv4 and nf_conntrack_ipv6 i think it was merged into nf_conntrack but i'm not sure. -- 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/1834213 Title: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances Status in OpenStack neutron-openvswitch charm: Fix Committed Status in neutron: New Status in linux package in Ubuntu: Confirmed Bug description: With an environment running Xenial-Queens, and having just upgraded the linux-image-generic kernel for MDS patching, a few of our hypervisor hosts that were rebooted (3 out of 100) ended up dropping IP (tcp/udp) ingress traffic. It turns out that nf_conntrack module was loaded, but nf_conntrack_ipv4 was not loading, and the traffic was being dropped by this rule: table=72, n_packets=214989, priority=50,ct_state=+inv+trk actions=resubmit(,93) The ct_state "inv" means invalid conntrack state, which the manpage describes as: The state is invalid, meaning that the connection tracker couldn’t identify the connection. This flag is a catch- all for problems in the connection or the connection tracker, such as: • L3/L4 protocol handler is not loaded/unavailable. With the Linux kernel datapath, this may mean that the nf_conntrack_ipv4 or nf_conntrack_ipv6 modules are not loaded. • L3/L4 protocol handler determines that the packet is malformed. • Packets are unexpected length for protocol. It appears that there may be an issue when patching the OS of a hypervisor not running instances may fail to update initrd to load nf_conntrack_ipv4 (and/or _ipv6). I couldn't find anywhere in the charm code that this would be loaded unless the charm's "harden" option is used on nova-compute charm (see charmhelpers contrib/host templates). It is unset in our environment, so we are not using any special module probing. Did nf_conntrack_ipv4 get split out from nf_conntrack in recent kernel upgrades or is it possible that the charm should define a modprobe file if we have the OVS firewall driver configured? To manage notifications about this bug go to: https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+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 1847193] Re: ath10k_pci 0000:02:00.0: firmware crashed!
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem/+bug/1847193/+attachment/5295372/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1847193 Title: ath10k_pci: firmware crashed randomly (Qualcomm Atheros QCA6174 ) Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: New Bug description: the wifi failed randomly, and it seems always happens with error message: " ath10k_pci :02:00.0: firmware crashed!" 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:143a] Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 14:52:39 2019 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux-firmware 1.173.9 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1057-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847193/+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 1847193] Re: ath10k_pci 0000:02:00.0: firmware crashed!
** Attachment added: "lspci-nnk.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem/+bug/1847193/+attachment/5295373/+files/lspci-nnk.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1847193 Title: ath10k_pci: firmware crashed randomly (Qualcomm Atheros QCA6174 ) Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: New Bug description: the wifi failed randomly, and it seems always happens with error message: " ath10k_pci :02:00.0: firmware crashed!" 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:143a] Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 14:52:39 2019 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux-firmware 1.173.9 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1057-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847193/+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 1847193] Re: ath10k_pci 0000:02:00.0: firmware crashed!
** Attachment added: "dpkg-l.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem/+bug/1847193/+attachment/5295375/+files/dpkg-l.log ** Summary changed: - ath10k_pci :02:00.0: firmware crashed! + ath10k_pci :02:00.0: firmware crashed randomly ** Description changed: the wifi failed randomly, and it seems always happens with error message: " ath10k_pci :02:00.0: firmware crashed!" + + 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) + Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:143a] + Kernel driver in use: ath10k_pci + Kernel modules: ath10k_pci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 14:52:39 2019 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: - + DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux-firmware 1.173.9 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1057-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True ** Summary changed: - ath10k_pci :02:00.0: firmware crashed randomly + ath10k_pci: firmware crashed randomly (Qualcomm Atheros QCA6174 ) ** Package changed: linux-signed-oem (Ubuntu) => linux-oem (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1847193 Title: ath10k_pci: firmware crashed randomly (Qualcomm Atheros QCA6174 ) Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: New Bug description: the wifi failed randomly, and it seems always happens with error message: " ath10k_pci :02:00.0: firmware crashed!" 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:143a] Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 14:52:39 2019 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux-firmware 1.173.9 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1057-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847193/+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 1847193] Re: ath10k_pci 0000:02:00.0: firmware crashed!
** Attachment added: "udevadmin.log" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem/+bug/1847193/+attachment/5295374/+files/udevadmin.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem in Ubuntu. https://bugs.launchpad.net/bugs/1847193 Title: ath10k_pci: firmware crashed randomly (Qualcomm Atheros QCA6174 ) Status in OEM Priority Project: New Status in linux-oem package in Ubuntu: New Bug description: the wifi failed randomly, and it seems always happens with error message: " ath10k_pci :02:00.0: firmware crashed!" 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:143a] Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1057-oem 4.15.0-1057.66 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 8 14:52:39 2019 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed-oem UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-08-11 (57 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux-firmware 1.173.9 PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Tags: bionic Uname: Linux 4.15.0-1057-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847193/+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 1846024] Re: bionic/linux-bluefield: 5.0.0-1002.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846024 Title: bionic/linux-bluefield: 5.0.0-1002.11 -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: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1846026 packages: main: linux-bluefield meta: linux-meta-bluefield phase: Holding before Promote to Security phase-changed: Tuesday, 08. October 2019 09:50 UTC proposed-announcement-sent: true proposed-testing-requested: true replaces: bug 1844385 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846024/+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 1846078] Re: bionic/linux-azure: 5.0.0-1023.24~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846079 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 07. October 2019 21:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1846077 bionic/linux-azure/azure-kernel: bug 1846076 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1846078 Title: bionic/linux-azure: 5.0.0-1023.24~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in 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: 1846079 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 07. October 2019 21:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure-edge: bug 1846077 bionic/linux-azure/azure-kernel: bug 1846076 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846078/+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 1846096] Re: bionic/linux-bluefield: 5.0.0-1003.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846097 packages: main: linux-bluefield meta: linux-meta-bluefield - phase: Holding before Promote to Proposed - phase-changed: Friday, 04. October 2019 05:51 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 08. October 2019 09:51 UTC reason: - promote-to-proposed: Stalled -- another kernel is currently pending in Proposed + promote-to-proposed: Pending -- ready for review variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846096 Title: bionic/linux-bluefield: 5.0.0-1003.12 -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-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1846097 packages: main: linux-bluefield meta: linux-meta-bluefield phase: Ready for Promote to Proposed phase-changed: Tuesday, 08. October 2019 09:51 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846096/+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 1846024] Re: bionic/linux-bluefield: 5.0.0-1002.11 -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: 1846026 packages: main: linux-bluefield meta: linux-meta-bluefield - phase: Ready for Promote to Updates - phase-changed: Tuesday, 08. October 2019 02:50 UTC + phase: Promote to Updates + phase-changed: Tuesday, 08. October 2019 09:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- ready to copy + promote-to-updates: Ongoing -- packages not yet published replaces: bug 1844385 variant: debs ** Changed in: kernel-sru-workflow/promote-to-updates 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: 1846026 packages: main: linux-bluefield meta: linux-meta-bluefield - phase: Promote to Updates - phase-changed: Tuesday, 08. October 2019 09:45 UTC + phase: Holding before Promote to Security + phase-changed: Tuesday, 08. October 2019 09:50 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published replaces: bug 1844385 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/1846024 Title: bionic/linux-bluefield: 5.0.0-1002.11 -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: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1846026 packages: main: linux-bluefield meta: linux-meta-bluefield phase: Holding before Promote to Security phase-changed: Tuesday, 08. October 2019 09:50 UTC proposed-announcement-sent: true proposed-testing-requested: true replaces: bug 1844385 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846024/+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 1845296] Re: package nvidia-dkms-435 (not installed) failed to install/upgrade: installed nvidia-dkms-435 package post-installation script subprocess returned error exit status
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1845296 Title: package nvidia-dkms-435 (not installed) failed to install/upgrade: installed nvidia-dkms-435 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Had a new Ubuntu 18.04 installation with nvidia-dkms-435 package installed. Updated to 19.04 with no issues for the nvidia driver, but updating to 19.10 resulted in the error. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-435 (not installed) ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Wed Sep 25 05:52:04 2019 ErrorMessage: installed nvidia-dkms-435 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2019-09-24 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-435 Title: package nvidia-dkms-435 (not installed) failed to install/upgrade: installed nvidia-dkms-435 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-09-25 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1845296/+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 1845714] Re: Drop i386 build for 19.10
** Also affects: debian-installer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845714 Title: Drop i386 build for 19.10 Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: i386 will not be a supported architecture in 19.10, so we should drop it from our packaging. However we will still need to support i386 in hwe kernels. Fix: Stop building i386 packages, but keep the configs and other bits for supporting i386 in place. Test Case: Verify that i386 kernels are no longer produced, but that configs can still be updated. Regression Potential: The changes are straightforward, and any regressions are likely to be build-time issues, so regressions impacting users are unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1845714/+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 1845714] Re: Drop i386 build for 19.10
** Branch linked: lp:~ubuntu-core-dev/debian-installer/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/1845714 Title: Drop i386 build for 19.10 Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: i386 will not be a supported architecture in 19.10, so we should drop it from our packaging. However we will still need to support i386 in hwe kernels. Fix: Stop building i386 packages, but keep the configs and other bits for supporting i386 in place. Test Case: Verify that i386 kernels are no longer produced, but that configs can still be updated. Regression Potential: The changes are straightforward, and any regressions are likely to be build-time issues, so regressions impacting users are unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1845714/+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 1845714] Re: Drop i386 build for 19.10
** Changed in: debian-installer (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845714 Title: Drop i386 build for 19.10 Status in debian-installer package in Ubuntu: In Progress Status in linux package in Ubuntu: Fix Committed Bug description: SRU Justification Impact: i386 will not be a supported architecture in 19.10, so we should drop it from our packaging. However we will still need to support i386 in hwe kernels. Fix: Stop building i386 packages, but keep the configs and other bits for supporting i386 in place. Test Case: Verify that i386 kernels are no longer produced, but that configs can still be updated. Regression Potential: The changes are straightforward, and any regressions are likely to be build-time issues, so regressions impacting users are unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1845714/+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 1847042] Re: Kernel 5.3.0-13-generic crashes at boot in tpm_read_log_efi(), HP EliteBook 840 G5
This seems to be a duplicate of bug 1845454. Could you please try the test kernel build in bug 1845454 comment 11 and tell if that resolves the problem? Thanks! -- 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/1847042 Title: Kernel 5.3.0-13-generic crashes at boot in tpm_read_log_efi(), HP EliteBook 840 G5 Status in linux package in Ubuntu: Confirmed Bug description: Upgraded to Ubuntu 19.10 from 19.04. On first boot of 19.10, Kernel 5.3.0.13-generic crashed with an error in tpm_read_log_efi(), see screenshot. Disabling TPM in BIOS allowed successful boot of kernel 5.3.0.13-generic. Kernel 5.0.0-31-generic will boot 19.10 successfully, with or without TPM enabled in the BIOS. Hardware is HP EliteBook 840 G5. BIOS not most recent, cannot upgrade without installing Windows. --- $ lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 $ apt-cache policy linux-generic linux-generic: Installed: 5.3.0.13.14 Candidate: 5.3.0.13.14 Version table: *** 5.3.0.13.14 500 500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847042/+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 1845454] Re: Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10 (but 5.2 works)
Similarly for bug 1847042.
--
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/1845454
Title:
Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10
(but 5.2 works)
Status in linux package in Ubuntu:
In Progress
Bug description:
SRU Justification
Impact: Some systems are getting kernel panics during boot while
parsing tpm event logs from the firmware. This happens only when the
tpm and secure boot are both enabled in the firmware.
Fix: 3 patches which are currently applied to the upstream EFI
maintainer tree.
Test Case: On an affected system, booting a 5.3-based kernel will
panic during boot when the tpm and secure boot are enabled. A patched
kernel will boot successfully. The patches have been verified to fix
the issue on a gen 6 Lenovo X1 Carbon.
Regression Potential: If the patches have bugs they could cause
regressions on systems not currently experiencing issues. The patches
are pretty straightforward though, so I believe the risk is minimal
and (given the severity of the issue on affected hardware) acceptable.
---
Image: http://cdimage.ubuntu.com/daily-live/20190926/eoan-desktop-amd64.iso
Device: Dell XPS 13 7390 (201908-27305)
When trying to start the live session ("try Ubuntu") or trying to
install the ISO ("install Ubuntu"), the boot process stops within 1
second with a kernel panic (see attached screenshot).
The system could boot with a previous version of Eoan image:
2019-09-09 09:11 (kernel 5.3.0-10)
Workaround: disable TPM2 in the BIOS.
/!\ Please note: the information below (and the attached file
ProcCpuinfoMinimal.txt) come from a 18.04 live session, since I cannot boot
anything with 19.10 beta image.
==
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: syslinux 3:6.03+dfsg1-2
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 26 07:41:16 2019
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
mtools 4.0.18-2ubuntu1
syslinux-common 3:6.03+dfsg1-2
LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: syslinux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845454/+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 1847198] Re: amdgpu kernel module should be used instead of radeon on amd graphic
DC does not support VGA yet https://bugs.freedesktop.org/show_bug.cgi?id=105880 ** Bug watch added: freedesktop.org Bugzilla #105880 https://bugs.freedesktop.org/show_bug.cgi?id=105880 -- 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/1847198 Title: amdgpu kernel module should be used instead of radeon on amd graphic Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in linux-oem package in Ubuntu: New Status in linux-oem source package in Bionic: New Bug description: there're some graphic be supported both on amdgpu and radeon. But somehow kernel might pick radeon instead of amdgpu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem 4.15.0.1057.61 ProcVersionSignature: Ubuntu 4.15.0-1057.66-oem 4.15.18 Uname: Linux 4.15.0-1057-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Oct 8 03:33:43 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-lancel+X97 InstallationDate: Installed on 2019-10-04 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847198/+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 1847192] Re: drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL platforms
** Description changed: - [Reproduce Steps] - 1. Enter s2idle - 2. Press power button to wake up the system - 3. The Select Audio Device dialog show up + Since Bionic kernel doesn't support ICL platforms (i915), so these two + patches will not be sent to Bionic kernel. - [Results] - Expected: There is no dialog show up - Actual: The Select Audio Device dialog show up + [Impact] + On the ICL platforms, the hdmi can't work well, the audio driver + will print "azx_get_response timeout" randomly, then the whole + audio doesn't work anymore. + + [Fix] + Intel provide these two fixes to us, and we tested these two + patches, it really fixed the issue. + + [Test Case] + Boot and check the hdmi audio, then suspend and resume, check + the hdmi audio, all work well. + + [Regression Risk] + Low, Only enable the audio PIN and enable the clock for ICL. we + tested on both ICL and non-ICL, all worked well as before. -- 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/1847192 Title: drm/i915: Fix the issue of "azx_get_response timeout" for hdmi audio on ICL platforms Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: Since Bionic kernel doesn't support ICL platforms (i915), so these two patches will not be sent to Bionic kernel. [Impact] On the ICL platforms, the hdmi can't work well, the audio driver will print "azx_get_response timeout" randomly, then the whole audio doesn't work anymore. [Fix] Intel provide these two fixes to us, and we tested these two patches, it really fixed the issue. [Test Case] Boot and check the hdmi audio, then suspend and resume, check the hdmi audio, all work well. [Regression Risk] Low, Only enable the audio PIN and enable the clock for ICL. we tested on both ICL and non-ICL, all worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847192/+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 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez
there's a lot of people subscribed to this bug, and presumably interested in seeing it fixed on Bionic; can any of you please test with the package from bionic-proposed and report the results? Until you do, it's unlikely this fix will be released into bionic-updates. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Or you can directly download the proposed debs from this (amd64) build page: https://launchpad.net/ubuntu/+source/bluez/5.48-0ubuntu3.2/+build/17810460 please someone test on Bionic! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1759836 Title: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in bluez source package in Bionic: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Invalid Status in bluez source package in Disco: Fix Released Status in linux source package in Disco: Invalid Status in systemd source package in Disco: Invalid Status in bluez source package in Eoan: Fix Released Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Invalid Status in bluez package in Debian: New Bug description: [impact] on specific Dell systems, with a specific usb bluetooth device built- in, the udev rule 'hid2hci' provided by the 'bluez' package causes an endless loop of uevents resulting from 'bind' or 'unbind' kernel uevents. These new events were added to the kernel after the 'hid2hci' udev rule was written. [test case] the specific Dell system is required to be able to reproduce this, or at least the specific usb bluetooth hardware included in that system. Reproducing this is reportedly easy, for example comment 75 indicates it happens on every boot. When this happens, any process monitor (e.g. ps, top, etc) will show the 'udevd' process using 100% of a cpu, and 'udevadm monitor' should show repeated 'bind' and 'unbind' events as mentioned in comment 39. [regression potential] as this alters what kernel uevents the 'hid2hci' udev rule processes, regressions would involve the affected usb bluetooth device failing to be set up, or otherwise not processing the uevents correctly. [other info] this is not fixed yet upstream, as of my last check, but has been submitted upstream as mentioned in comment 95. original description: -- The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+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 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
@frank-heimes, thank you for the testing and also for your additional comments. This fix was once accepted to bionic-proposed, while it does not have a test case in the bug description nor the description follows the SRU template: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template . Ensuring that is the job of the SRU uploader, and the first time is was skipped and I also missed that. Since the bug did not exist in 18.04 I'm marking it invalid instead of performing the SRU again. ** Changed in: systemd (Ubuntu Bionic) Status: Incomplete => Invalid ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image Status in Ubuntu on IBM z Systems: Fix Released Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Invalid Bug description: Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC image on a z/VM guest leads to a kernel panic: /lib/debian-installer/start-udev: line 15: can't create /sys/module/scsi_mod/par ameters/scan: Permission denied ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ exitcode=0x00 000100 ¬0.845071| ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic #157-Ubun tu ¬0.845077|7d107c20 7d107cb0 0002 000 0 7d107d50 7d107cc8 7d107cc8 00114732 008b 009a304c 009f11d0 000b 7d107d10 7d107cb0 040001cdf800 00114732 7d107cb0 7d107d10 ¬0.845089| Call Trace: ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) ¬0.845095| ¬<001146e2>| show_stack+0x72/0xf8 ¬0.845099| ¬<00555752>| dump_stack+0x82/0xb8 ¬0.845101| ¬<00286390>| panic+0x108/0x250 ¬0.845104| ¬<00166228>| do_exit+0xac0/0xba0 ¬0.845106| ¬<001663c8>| do_group_exit+0x50/0xe0 ¬0.845108| ¬<00166488>| __wake_up_parent+0x0/0x28 ¬0.845111| ¬<007eadda>| system_call+0xee/0x28c ¬0.845113| ¬<03ff8953983a>| 0x3ff8953983a 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0010F8CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+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 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image
I also set verification-done, since it is verified that the bug does not occur with .31 . -- 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/1784454 Title: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image Status in Ubuntu on IBM z Systems: Fix Released Status in debian-installer package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in systemd source package in Xenial: Fix Released Status in systemd source package in Bionic: Invalid Bug description: Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC image on a z/VM guest leads to a kernel panic: /lib/debian-installer/start-udev: line 15: can't create /sys/module/scsi_mod/par ameters/scan: Permission denied ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ exitcode=0x00 000100 ¬0.845071| ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic #157-Ubun tu ¬0.845077|7d107c20 7d107cb0 0002 000 0 7d107d50 7d107cc8 7d107cc8 00114732 008b 009a304c 009f11d0 000b 7d107d10 7d107cb0 040001cdf800 00114732 7d107cb0 7d107d10 ¬0.845089| Call Trace: ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) ¬0.845095| ¬<001146e2>| show_stack+0x72/0xf8 ¬0.845099| ¬<00555752>| dump_stack+0x82/0xb8 ¬0.845101| ¬<00286390>| panic+0x108/0x250 ¬0.845104| ¬<00166228>| do_exit+0xac0/0xba0 ¬0.845106| ¬<001663c8>| do_group_exit+0x50/0xe0 ¬0.845108| ¬<00166488>| __wake_up_parent+0x0/0x28 ¬0.845111| ¬<007eadda>| system_call+0xee/0x28c ¬0.845113| ¬<03ff8953983a>| 0x3ff8953983a 00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0010F8CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+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 1847248] [NEW] No NIC on a Raspberry PI 3+ with updated firmware
Public bug reported: After updating the firmware to the latest version from github.com/raspberry/firmware, the NIC on a PI 3+ running Bionic is no longer recognized/initialized. In fact, no USB devices are discovered at all. [3.528034] irq 41: nobody cared (try booting with the "irqpoll" option) [3.536895] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.15.18-bionic8 #12 [3.545826] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) [3.554271] Call trace: [3.558792] dump_backtrace+0x0/0x1e0 [3.564576] show_stack+0x24/0x30 [3.569991] dump_stack+0xbc/0xf4 [3.575376] __report_bad_irq+0x3c/0xf8 [3.581295] note_interrupt+0x2d8/0x328 [3.587208] handle_irq_event_percpu+0x68/0x98 [3.593691] handle_irq_event+0x50/0x80 [3.599588] handle_level_irq+0xc4/0x150 [3.605559] generic_handle_irq+0x34/0x50 [3.611596] bcm2836_chained_handle_irq+0x4c/0x68 [3.618342] generic_handle_irq+0x34/0x50 [3.624368] __handle_domain_irq+0x68/0xc0 [3.630482] bcm2836_arm_irqchip_handle_irq+0x74/0xe0 [3.637574] el1_irq+0xec/0x198 [3.642700] arch_cpu_idle+0x34/0x1e8 [3.648377] default_idle_call+0x28/0x44 [3.654304] do_idle+0x180/0x1f8 [3.659472] cpu_startup_entry+0x28/0x30 [3.665368] secondary_start_kernel+0x128/0x138 [3.671866] handlers: [3.676012] [<69f2db41>] dwc_otg_common_irq [3.682840] [<1adf5720>] dwc_otg_pcd_irq [3.689374] [<39428d36>] usb_hcd_irq [3.695541] Disabling IRQ #41 [6.814911] usb 1-1: device descriptor read/64, error -110 [ 22.242909] Indeed it is in host mode hprt0 = 1101 [ 22.434928] usb 1-1: device descriptor read/64, error -110 [ 22.575695] Indeed it is in host mode hprt0 = 1101 [ 22.774865] usb 1-1: new high-speed USB device number 3 using dwc_otg [ 27.874889] Indeed it is in host mode hprt0 = 1101 [ 28.066866] usb 1-1: device descriptor read/64, error -110 [ 43.490915] Indeed it is in host mode hprt0 = 1101 [ 43.682842] usb 1-1: device descriptor read/64, error -110 [ 43.794933] usb usb1-port1: attempt power cycle ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Package changed: linux (Ubuntu Bionic) => linux-raspi2 (Ubuntu 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/1847248 Title: No NIC on a Raspberry PI 3+ with updated firmware Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Bionic: New Bug description: After updating the firmware to the latest version from github.com/raspberry/firmware, the NIC on a PI 3+ running Bionic is no longer recognized/initialized. In fact, no USB devices are discovered at all. [3.528034] irq 41: nobody cared (try booting with the "irqpoll" option) [3.536895] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.15.18-bionic8 #12 [3.545826] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) [3.554271] Call trace: [3.558792] dump_backtrace+0x0/0x1e0 [3.564576] show_stack+0x24/0x30 [3.569991] dump_stack+0xbc/0xf4 [3.575376] __report_bad_irq+0x3c/0xf8 [3.581295] note_interrupt+0x2d8/0x328 [3.587208] handle_irq_event_percpu+0x68/0x98 [3.593691] handle_irq_event+0x50/0x80 [3.599588] handle_level_irq+0xc4/0x150 [3.605559] generic_handle_irq+0x34/0x50 [3.611596] bcm2836_chained_handle_irq+0x4c/0x68 [3.618342] generic_handle_irq+0x34/0x50 [3.624368] __handle_domain_irq+0x68/0xc0 [3.630482] bcm2836_arm_irqchip_handle_irq+0x74/0xe0 [3.637574] el1_irq+0xec/0x198 [3.642700] arch_cpu_idle+0x34/0x1e8 [3.648377] default_idle_call+0x28/0x44 [3.654304] do_idle+0x180/0x1f8 [3.659472] cpu_startup_entry+0x28/0x30 [3.665368] secondary_start_kernel+0x128/0x138 [3.671866] handlers: [3.676012] [<69f2db41>] dwc_otg_common_irq [3.682840] [<1adf5720>] dwc_otg_pcd_irq [3.689374] [<39428d36>] usb_hcd_irq [3.695541] Disabling IRQ #41 [6.814911] usb 1-1: device descriptor read/64, error -110 [ 22.242909] Indeed it is in host mode hprt0 = 1101 [ 22.434928] usb 1-1: device descriptor read/64, error -110 [ 22.575695] Indeed it is in host mode hprt0 = 1101 [ 22.774865] usb 1-1: new high-speed USB device number 3 using dwc_otg [ 27.874889] Indeed it is in host mode hprt0 = 1101 [ 28.066866] usb 1-1: device descriptor read/64, error -110 [ 43.490915] Indeed it is in host mode hprt0 = 1101 [ 43.682842] usb 1-1: device descriptor read/64, error -110 [ 43.794933] usb usb1-port1: attempt power cy
[Kernel-packages] [Bug 1823151] [NEW] Raspberry Pi 3B plus cpuinfo
You have been subscribed to a public bug: # OS ``` $ uname -a Linux host-name 4.15.0-1033-raspi2 #35-Ubuntu SMP PREEMPT Fri Mar 15 15:53:58 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic ``` # expected cpuinfo with "model name", "Hardware", "Revision" etc. some example from raspbian armhf ``` processor : 0 model name : ARMv7 Processor rev 4 (v7l) BogoMIPS: 38.40 Features: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 . . . Hardware: BCM2835 Revision: a02082 Serial : f13010a2 ``` # actual cpuinfo This causes golang unable to detect platform. ``` $ cat /proc/cpuinfo processor : 0 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 processor : 1 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 processor : 2 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 processor : 3 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 ``` ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: arm64 cpuinfo raspberrypi rpi -- Raspberry Pi 3B plus cpuinfo https://bugs.launchpad.net/bugs/1823151 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 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 1847250] [NEW] update firmware for sound sof driver to fix the hang issue on several Dell machines
Public bug reported: 1. the issue can be duplicated after re-SWDL. 2. can enter into system when we disable audio in BIOS interface. 3. Can enter into system when we uninstall the audio driver. 4. Can enter into system when we remove Chipset driver in GCF and re- preload. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Critical Assignee: Hui Wang (hui.wang) Status: New ** Tags: originate-from-1841562 originate-from-1845415 somerville ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => Critical ** Tags added: originate-from-1845415 somerville ** Tags added: originate-from-1841562 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1847250 Title: update firmware for sound sof driver to fix the hang issue on several Dell machines Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Bug description: 1. the issue can be duplicated after re-SWDL. 2. can enter into system when we disable audio in BIOS interface. 3. Can enter into system when we uninstall the audio driver. 4. Can enter into system when we remove Chipset driver in GCF and re- preload. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847250/+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 1823151] Re: Raspberry Pi 3B plus cpuinfo
** Package changed: cpuinfo (Ubuntu) => linux-raspi2 (Ubuntu) ** Also affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1823151 Title: Raspberry Pi 3B plus cpuinfo Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Bionic: New Bug description: # OS ``` $ uname -a Linux host-name 4.15.0-1033-raspi2 #35-Ubuntu SMP PREEMPT Fri Mar 15 15:53:58 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic ``` # expected cpuinfo with "model name", "Hardware", "Revision" etc. some example from raspbian armhf ``` processor : 0 model name: ARMv7 Processor rev 4 (v7l) BogoMIPS : 38.40 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32 CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4 . . . Hardware : BCM2835 Revision : a02082 Serial: f13010a2 ``` # actual cpuinfo This causes golang unable to detect platform. ``` $ cat /proc/cpuinfo processor : 0 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 processor : 1 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 processor : 2 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 processor : 3 BogoMIPS: 38.40 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd03 CPU revision: 4 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1823151/+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 1847250] Re: update firmware for sound sof driver to fix the hang issue on several Dell machines
** Description changed: - 1. the issue can be duplicated after re-SWDL. + We expect this firmware update could be released with 19.10 - 2. can enter into system when we disable audio in BIOS interface. + [Impact] + We have a couple of Dell machines, after installing the system, it + will hang randomly, and this issue was reported by factory, they met + this issue a couple of times. Then we tried to reproduce this issue, + finally reproduced it. - 3. Can enter into system when we uninstall the audio driver. + [Fix] + Intel debugged this issue as well, and they provided 4 kernel patches + and a new firmware, we tested them, they really can fix the issue. + And the patches were sent the SRU already, now it is time to update + firmware. - 4. Can enter into system when we remove Chipset driver in GCF and re- - preload. + [Test Case] + Install the system repeatedly and there is no hang issue anymore. + + [Regression Risk] + Low, Intel told us there is no ABI change for the firmware, so + it is safe to run this firmware both with the old driver (not applied + those 4 patches) and the new driver (applied those 4 patches). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1847250 Title: update firmware for sound sof driver to fix the hang issue on several Dell machines Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Bug description: We expect this firmware update could be released with 19.10 [Impact] We have a couple of Dell machines, after installing the system, it will hang randomly, and this issue was reported by factory, they met this issue a couple of times. Then we tried to reproduce this issue, finally reproduced it. [Fix] Intel debugged this issue as well, and they provided 4 kernel patches and a new firmware, we tested them, they really can fix the issue. And the patches were sent the SRU already, now it is time to update firmware. [Test Case] Install the system repeatedly and there is no hang issue anymore. [Regression Risk] Low, Intel told us there is no ABI change for the firmware, so it is safe to run this firmware both with the old driver (not applied those 4 patches) and the new driver (applied those 4 patches). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1847250/+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 1847256] [NEW] Support Raspberry PI 4
Public bug reported: Add support for the Raspberry PI 4 to Bionic 4.15. ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1847256 Title: Support Raspberry PI 4 Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Bionic: New Bug description: Add support for the Raspberry PI 4 to Bionic 4.15. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847256/+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 1847109] Re: Ubuntu 18.04 - wrong cpu-mf counter number
Kernel SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2019-October/thread.html#104595 Changing status to 'In Progress'. ** Description changed: + SRU Justification: + == + + [Impact] + + * wrong cpu-mf counter number of LAST_HOST_TRANSLATIONS + + [Fix] + + * 81507f38d427ebed3291a3c153a798937c998140 81507f38 "s390/cpum_cf: + correct counter number of LAST_HOST_TRANSLATIONS" + + [Test Case] + + * inspect the counter number of the LAST_HOST_TRANSLATIONS (virtual) + file + + * cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS + + * returns 'event=0x00e9', but should be 'event=0x00e8' + + * event is only available on z14 and higher, hence Canonical can only do + regression testing - IBM the functional verification + + [Regression Potential] + + * very minimal, patch just changes one hex number in one code line + + * change is limited to z14 (and higher) hardware counters only + + [Other Info] + + * fix/patch got upstream accepted with 4.16 + + * hence it's already in (cosmic and) disco and eoan and only need to be applied to bionic 4.15 + __ + Kernel: Linux t35lp11 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:15:19 UTC 2019 s390x s390x s390x GNU/Linux Description/Reproduction: The cpu-mf counter LAST_HOST_TRANSLATIONS has the wrong number. # cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS event=0x00e9 should be event=0x00e8 Fix already available: commit 81507f38d427ebed3291a3c153a798937c998140 ** Changed in: ubuntu-z-systems Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847109 Title: Ubuntu 18.04 - wrong cpu-mf counter number Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: == [Impact] * wrong cpu-mf counter number of LAST_HOST_TRANSLATIONS [Fix] * 81507f38d427ebed3291a3c153a798937c998140 81507f38 "s390/cpum_cf: correct counter number of LAST_HOST_TRANSLATIONS" [Test Case] * inspect the counter number of the LAST_HOST_TRANSLATIONS (virtual) file * cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS * returns 'event=0x00e9', but should be 'event=0x00e8' * event is only available on z14 and higher, hence Canonical can only do regression testing - IBM the functional verification [Regression Potential] * very minimal, patch just changes one hex number in one code line * change is limited to z14 (and higher) hardware counters only [Other Info] * fix/patch got upstream accepted with 4.16 * hence it's already in (cosmic and) disco and eoan and only need to be applied to bionic 4.15 __ Kernel: Linux t35lp11 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:15:19 UTC 2019 s390x s390x s390x GNU/Linux Description/Reproduction: The cpu-mf counter LAST_HOST_TRANSLATIONS has the wrong number. # cat /sys/devices/cpum_cf/events/LAST_HOST_TRANSLATIONS event=0x00e9 should be event=0x00e8 Fix already available: commit 81507f38d427ebed3291a3c153a798937c998140 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1847109/+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 1843207] Re: Doesn't boot on Raspberry Pi 4
See LP #1847163. -- 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/1843207 Title: Doesn't boot on Raspberry Pi 4 Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Eoan: New Bug description: linux-raspi2 from Eoan (19.10) doesn't boot on Raspberry Pi 4 due to missing kernel modules for the new hardware components. It would be nice if these got included. Also it only boots the kernel when the Pi is configured for 1GB RAM or less. (Then gets stuck on missing root FS because the microSD isn't detected.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1843207/+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 1843207] Re: Doesn't boot on Raspberry Pi 4
Full link: https://bugs.launchpad.net/bugs/1847163 ** Also affects: linux-raspi2 (Ubuntu Eoan) Importance: Undecided Status: New -- 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/1843207 Title: Doesn't boot on Raspberry Pi 4 Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Eoan: New Bug description: linux-raspi2 from Eoan (19.10) doesn't boot on Raspberry Pi 4 due to missing kernel modules for the new hardware components. It would be nice if these got included. Also it only boots the kernel when the Pi is configured for 1GB RAM or less. (Then gets stuck on missing root FS because the microSD isn't detected.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1843207/+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 1828166] Re: perf top problem on z with Ubuntu 18.04
** Description changed: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start" * 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390" Disco needs also as prereq: - * 6738028dd57df064b969d8392c943ef3b3ae705d 6738028 perf record: Fix s390 - missing module symbol and warning for non-root users - + * 6738028dd57df064b969d8392c943ef3b3ae705d 6738028 "perf record: Fix + s390 missing module symbol and warning for non-root users" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as medium since this happens only while using the perf top tool * and just 3 files are changed, and one of them is arch/s390/util/machine.c * but symbol and machine header in /tools/perf/util modified and several loc added [Other Info] * cherry-pick was possible to bionic-master-next and to disco-master- next (but used '--strategy=recursive -X theirs' for disco) * adding the patches to disco is to avoid regressions _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Bug description: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * b9c0a64901d5bdec6eafd38d1dc8fa0e2974fccb b9c0a64 "perf annotate: Fix s390 gap between kernel end and module start" * 12a6d2940b5f02b4b9f71ce098e3bb02bc24a9ea 12a6d29 "perf record: Fix module size on s390" Disco needs also as prereq: * 6738028dd57df064b969d8392c943ef3b3ae705d 6738028 "perf record: Fix s390 missing module symbol and warning for non-root users" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as medium since this happens only while using the perf top tool * and just 3 files are changed, and one of them is arch/s390/util/machine.c * but symbol and machine header in /tools/perf/util modified and several loc added [Other Info] * cherry-pick was possible to bionic-master-next and to disco-master- next (but used '--strategy=recursive -X theirs' for disco) * adding the patches to disco is to avoid regressions _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output
[Kernel-packages] [Bug 1841313] Re: Asus X451MA does not boot with linux > 4.15.0-55
For the record, I had exactly the same issue with an Asus X550MD. Fortunately, the new HWE kernel (5.0.0) in 18.04 works properly. I will have this Asus X550MD until the 11 of October at least: if you want me to do some tests, do not hesitate to ask. -- 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/1841313 Title: Asus X451MA does not boot with linux > 4.15.0-55 Status in linux package in Ubuntu: Confirmed Bug description: Hi, On an Asus X451MA running Linux Mint 18.3 (Ubuntu 16.04.3), last kernel update from 4.15.0-55 to 4.15.0-58 prevents it from booting: it hangs at the beginning of boot. I tested with kernel 4.15.0-59 from "xenial-proposed" and with a live image of Ubuntu 18.04.2 and the issue remains. I could not test with a more recent kernel on this same install because it requires libssl1.1 that is not available in the Xenial repositories. I suppose it does not help, but a picture from live Ubuntu 18.04.2 is attached. I will provide more information with apport very soon. Do not hesitate to ask if I can provide other details or test other versions / parameters. Regards, Yvan --- ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marie-claude 1541 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=d93009cf-a1ab-47ec-811c-d76dfbc4926d InstallationDate: Installed on 2017-04-08 (868 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: enp3s0f2 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b404 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 04ca:2006 Lite-On Technology Corp. Broadcom BCM43142A0 Bluetooth Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X451MA Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=a34dd005-da91-42c3-95c6-b25185f3ee21 ro intel_idle.max_cstate=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-55-generic N/A linux-backports-modules-4.15.0-55-generic N/A linux-firmware 1.157.22 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no Tags: sylvia sylvia Uname: Linux 4.15.0-55-generic x86_64 UnreportableReason: Le rapport fait référence à un paquet non installé. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: False dmi.bios.date: 04/10/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X451MA.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X451MA 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.:bvrX451MA.216:bd04/10/2015:svnASUSTeKCOMPUTERINC.:pnX451MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX451MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X451MA 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/1841313/+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 1597415] Re: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument
** Tags added: disco eoan -- 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/1597415 Title: systemd-udevd: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Hi, the symptom is this error message in my system's logs: juin 29 16:56:39 vougeot systemd-udevd[522]: Error calling EVIOCSKEYCODE on device node '/dev/input/event9' (scan code 0x150, key code 190): Invalid argument According to /proc/bus/input/devices the corresponding input device is: I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input10 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=13 B: KEY=1000b0400 0 e 0 B: MSC=10 This laptop is a Dell Latitude E6520. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu6 Uname: Linux 4.6.3-040603-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE CustomUdevRuleFiles: 60-ssd-scheduler.rules Date: Wed Jun 29 17:43:01 2016 EcryptfsInUse: Yes MachineType: Dell Inc. Latitude E6520 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.6.3-040603-generic root=UUID=749a9901-bdd3-4b5f-b80e-69414667e058 ro enable_mtrr_cleanup mtrr_spare_reg_nr=1 mtrr_gran_size=32M mtrr_chunk_size=128M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to xenial on 2016-04-09 (80 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0NVF5K dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd11/14/2013:svnDellInc.:pnLatitudeE6520:pvr01:rvnDellInc.:rn0NVF5K:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6520 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597415/+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 1847212] Re: touchpad not working after upgrade to 5.0.0-31 kernel
** Attachment added: "/proc/bus/input/devices at -31 kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847212/+attachment/5295436/+files/devices31 -- 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/1847212 Title: touchpad not working after upgrade to 5.0.0-31 kernel Status in linux package in Ubuntu: Confirmed Bug description: touchpad is not avaliable after upgrade to linux-image-5.0.0-31-generic It works on 5.0.0-29 kernel. Laptop model: MSI GS40 6QE-091RU ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-31-generic 5.0.0-31.33 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vkovalen 1900 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Oct 8 10:37:31 2019 InstallationDate: Installed on 2019-05-18 (142 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 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A1IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-14A1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: GS40 6QE Phantom dmi.product.sku: Default string dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847212/+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 1847212] Re: touchpad not working after upgrade to 5.0.0-31 kernel
missing device: I: Bus=0011 Vendor=0002 Product=000e Version= N: Name="ETPS/2 Elantech Touchpad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input6 U: Uniq= H: Handlers=mouse0 event5 B: PROP=5 B: EV=b B: KEY=e420 1 0 0 0 0 B: ABS=66180001103 -- 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/1847212 Title: touchpad not working after upgrade to 5.0.0-31 kernel Status in linux package in Ubuntu: Confirmed Bug description: touchpad is not avaliable after upgrade to linux-image-5.0.0-31-generic It works on 5.0.0-29 kernel. Laptop model: MSI GS40 6QE-091RU ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-31-generic 5.0.0-31.33 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vkovalen 1900 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Oct 8 10:37:31 2019 InstallationDate: Installed on 2019-05-18 (142 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 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A1IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-14A1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: GS40 6QE Phantom dmi.product.sku: Default string dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847212/+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 1847212] Re: touchpad not working after upgrade to 5.0.0-31 kernel
** Attachment added: "/proc/bus/input/devices at -29 kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847212/+attachment/5295437/+files/devices29 -- 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/1847212 Title: touchpad not working after upgrade to 5.0.0-31 kernel Status in linux package in Ubuntu: Confirmed Bug description: touchpad is not avaliable after upgrade to linux-image-5.0.0-31-generic It works on 5.0.0-29 kernel. Laptop model: MSI GS40 6QE-091RU ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-31-generic 5.0.0-31.33 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vkovalen 1900 F pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Oct 8 10:37:31 2019 InstallationDate: Installed on 2019-05-18 (142 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 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 0cf3:e300 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS40 6QE Phantom ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=84c66d52-4ba6-49d7-8d50-e582f93d9b5c ro quiet nouveau.modeset=0 rd.driver.blacklist=nouveau acpi_osi=! "acpi_osi=Windows 2009" acpi_backlight=vendor resume=UUID=f7c3465a-6b62-428f-8477-67b678e6fe6e RelatedPackageVersions: linux-restricted-modules-5.0.0-31-generic N/A linux-backports-modules-5.0.0-31-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14A1IMS.113 dmi.board.asset.tag: Default string dmi.board.name: MS-14A1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.C dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14A1IMS.113:bd01/15/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS406QEPhantom:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14A1:rvrREV0.C:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: GS40 6QE Phantom dmi.product.sku: Default string dmi.product.version: REV:0.C dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847212/+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 1846641] Re: eoan/linux: 5.3.0-17.18 -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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Testing - phase-changed: Saturday, 05. October 2019 01:36 UTC + phase: Ready for Testing + phase-changed: Tuesday, 08. October 2019 14:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1846636 eoan/linux-aws: bug 1846613 eoan/linux-azure: bug 1846616 eoan/linux-gcp: bug 1846623 eoan/linux-kvm: bug 1846628 eoan/linux-oracle: bug 1846630 eoan/linux-raspi2: bug 1846611 eoan/linux-snapdragon: bug 1846634 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/1846641 Title: eoan/linux: 5.3.0-17.18 -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: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in debian-installer source package in Eoan: New Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Testing phase-changed: Tuesday, 08. October 2019 14:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe-edge: bug 1846636 eoan/linux-aws: bug 1846613 eoan/linux-azure: bug 1846616 eoan/linux-gcp: bug 1846623 eoan/linux-kvm: bug 1846628 eoan/linux-oracle: bug 1846630 eoan/linux-raspi2: bug 1846611 eoan/linux-snapdragon: bug 1846634 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846641/+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 1846995] Re: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1846995 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Doing a do-release-upgrade -d from 19.04 to 19.10. The upgrade crashed out part way through, automatically reporting this bug. update-initramfs: Generating /boot/initrd.img-5.3.0-13-generic Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.39.2-3) ... Processing triggers for libc-bin (2.30-0ubuntu2) ... Processing triggers for menu (2.1.47ubuntu3) ... Errors were encountered while processing: nvidia-dkms-390 nvidia-driver-390 Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (624.7 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 390.129-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Oct 7 01:17:46 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2018-04-23 (531 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180421.1) Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-10-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1846995/+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 1846424] Re: 19.10 ZFS Update failed on 2019-10-02
Sorry, you were right about the meaning of import/export and rmdir, but my excuse is, that it has been very early in the morning. However I have the same update problem on an ext4 installation of Ubuntu 19.10 on the same laptop. It gives the same error on two zfs modules, but of course without the zfs-initramfs module. So that has nothing to do with, how that system has been booted or which "How-To" has been used to boot from ZFS. It is just a very standard zfs installation on ext4 with two datapools and that is not an unofficial, experimental setup. For proof see the results on an update this morning in the file zfs- ext4. I purged zfsutils-linux and reinstalled it again on the ext4 system. After rebooting and importing the datapools the first time after the purge again, everything worked fine with the new version 12 of zfs. Unfortunately I can't use that trick, when I boot from ZFS. I think that proofs, that there is nothing wrong with the datapools itself or ZFS itself. So both version 11 and 12 of ZFS works fine, but you have a faulty update process for standard zfs and the same fault occurs on my version of "Boot from ZFS". ** Attachment added: "zfs-ext4" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+attachment/5295464/+files/zfs-ext4 -- 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/1846424 Title: 19.10 ZFS Update failed on 2019-10-02 Status in zfs-linux package in Ubuntu: Invalid Bug description: On all my systems the update from zfs-initrams_0.8.1-1ubuntu12_amd64.deb failed the same is true for zfs-zed and zfsutils-linux. The system still runs on 0.8.1-1ubuntu11_amd64. The first error message was about a failing mount and at the end it announced that all 3 modules were not updated. I have the error on Xubuntu 19.10, Ubuntu Mate 19.10 on my laptop i5-2520M and in a VBox VM on a Ryzen 3 2200G with Ubuntu 19.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+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 1846641] Re: eoan/linux: 5.3.0-17.18 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846641 Title: eoan/linux: 5.3.0-17.18 -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 debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in debian-installer source package in Eoan: New Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Release phase-changed: Tuesday, 08. October 2019 15:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy trackers: bionic/linux-hwe-edge: bug 1846636 eoan/linux-aws: bug 1846613 eoan/linux-azure: bug 1846616 eoan/linux-gcp: bug 1846623 eoan/linux-kvm: bug 1846628 eoan/linux-oracle: bug 1846630 eoan/linux-raspi2: bug 1846611 eoan/linux-snapdragon: bug 1846634 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846641/+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 1847293] [NEW] linux-gcp: -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 -- variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-gcp (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-gcp (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.10.08-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux-gcp (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-gcp (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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 -- + variant: debs ** Tags added: kernel-sru-cycle-d2019.10.08-1 -- 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/1847293 Title: linux-gcp: -proposed tracker Status in Kernel SRU Workflow: New Status in Kernel SRU Workflow au
[Kernel-packages] [Bug 1847291] [NEW] linux-aws: -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 -- variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-aws (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-aws (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.10.08-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux-aws (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-aws (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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 -- + variant: debs ** Tags added: kernel-sru-cycle-d2019.10.08-1 -- 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/1847291 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain sta
[Kernel-packages] [Bug 1847292] [NEW] linux-azure: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: linux-azure stakeholder signoff (linux-azure-signoff) Status: New ** Affects: linux-azure (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-azure (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.10.08-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux-azure (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/stakeholder-signoff Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/stakeholder-signoff Assignee: (unassigned) => linux-azure stakeholder signoff (linux-azure-signoff) ** Changed in: linux-azure (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as st
[Kernel-packages] [Bug 1847290] [NEW] linux-raspi2: -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 -- variant: debs ** Affects: kernel-sru-workflow Importance: Undecided Status: New ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: linux-raspi2 (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-raspi2 (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.10.08-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux-raspi2 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-raspi2 (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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 -- + variant: debs ** Tags added: kernel-sru-cycle-d2019.10.08-1 -- 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/1847290 Title: linux-raspi2: -proposed tracker Status in Kernel SRU Workflow: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubun
[Kernel-packages] [Bug 1846424] Re: 19.10 ZFS Update failed on 2019-10-02
That has the same error so you are using the same two pools. Please follow the instructions I’ve given and fix this once so you are in a fully working state. Once things are working, then you can retry whatever upgrade steps you think break it. -- 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/1846424 Title: 19.10 ZFS Update failed on 2019-10-02 Status in zfs-linux package in Ubuntu: Invalid Bug description: On all my systems the update from zfs-initrams_0.8.1-1ubuntu12_amd64.deb failed the same is true for zfs-zed and zfsutils-linux. The system still runs on 0.8.1-1ubuntu11_amd64. The first error message was about a failing mount and at the end it announced that all 3 modules were not updated. I have the error on Xubuntu 19.10, Ubuntu Mate 19.10 on my laptop i5-2520M and in a VBox VM on a Ryzen 3 2200G with Ubuntu 19.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1846424/+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 1730746] Re: Processes hang on attempted access of WDC WD30-EZRX 3TB HDD
Launchpad has imported 25 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=197875. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-11-14T22:06:16+00:00 chuck.burt+kernel.org wrote: When booted under kernel 4.13.x, processes (such as parted, boot-info, gparted, etc) always hang when attempting to run due to a Western Digital Green WD30-EZRX 3TB HDD. Drive works as expected under kernel 4.10.x (even when all other things are the same about the system but only booted kernel is different). Full specs of the machine if useful: https://www.support.hp.com/id- en/document/c03277050 More details on Ubuntu's LaunchPad (where they asked me to come here to file an upstream bug): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730746 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730746/comments/6 On 2017-11-14T22:26:27+00:00 bvanassche wrote: Please provide the output of the following command after having reproduced the hang: dmesg -c >/dev/null; echo w > /proc/sysrq-trigger; dmesg Additionally, if you know how to build the kernel yourself, it would be helpful if you could bisect this issue. Documentation is available e.g. at https://git-scm.com/docs/git-bisect. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730746/comments/8 On 2017-11-29T14:07:59+00:00 chuck.burt+kernel.org wrote: Created attachment 260925 Output of requested command I reproduced the hang and ran the command as requested. See attached file output-20171129.txt Building the kernel is something I could attempt tackling, but as a newbie I'm highly likely to mess something up. Either way, it will be a few weeks before I can get to it (best case). So I _really_ hope this provides the clue needed! Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730746/comments/9 On 2017-11-29T14:14:44+00:00 chuck.burt+kernel.org wrote: Created attachment 260927 Output of requested command as su After reading the first few lines of the last attachment, it occurred to me that running this command as su might be useful. See attached. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730746/comments/10 On 2017-11-29T14:34:15+00:00 chuck.burt+kernel.org wrote: Created attachment 260929 Output of requested command as su Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730746/comments/11 On 2017-11-29T16:36:47+00:00 bvanassche wrote: So command processing got stuck. Since there are two code paths in recent kernels we need to know whether or not scsi-mq was used. Hence please provide the output of the following command: for d in /sys/block/*; do sfx=""; [ -e "$d/mq" ] && sfx=" [mq]"; echo "$d$sfx"; done If the above command reports that scsi-mq is being used for the WDC disk, please check whether the following command resolves the lockup: for d in /sys/kernel/debug/block/*/state; do echo kick >$d; done Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730746/comments/12 On 2017-11-29T20:01:10+00:00 chuck.burt+kernel.org wrote: > # for d in /sys/block/*; do sfx=""; [ -e "$d/mq" ] && sfx=" [mq]"; echo > "$d$sfx"; done > /sys/block/loop0 [mq] > /sys/block/loop1 [mq] > /sys/block/loop2 [mq] > /sys/block/loop3 [mq] > /sys/block/loop4 [mq] > /sys/block/loop5 [mq] > /sys/block/loop6 [mq] > /sys/block/loop7 [mq] > /sys/block/sda > /sys/block/sdb > /sys/block/sdc > /sys/block/sr0 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730746/comments/13 On 2017-11-29T20:16:11+00:00 bvanassche wrote: That's weird, there are no known queue lockup bugs in the legacy block/SCSI core layers. Is the WDC harddisk perhaps controlled by a HBA? Can you provide the output of lspci (run as root)? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730746/comments/14 On 2017-11-30T16:04:40+00:00 chuck.burt+kernel.org wrote: Created attachment 260953 Output of lspci on 4.10.x kernel I won't be able to boot into the newer kernel for about a week, however since `lspci` is hardware-oriented, sharing the output under the older kernel in case it's helpful. Please let me know if you want me to run
[Kernel-packages] [Bug 1846641] Re: eoan/linux: 5.3.0-17.18 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => 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 -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Ready for Testing - phase-changed: Tuesday, 08. October 2019 14:05 UTC + phase: Ready for Promote to Release + phase-changed: Tuesday, 08. October 2019 15:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-release: Pending -- ready to copy trackers: bionic/linux-hwe-edge: bug 1846636 eoan/linux-aws: bug 1846613 eoan/linux-azure: bug 1846616 eoan/linux-gcp: bug 1846623 eoan/linux-kvm: bug 1846628 eoan/linux-oracle: bug 1846630 eoan/linux-raspi2: bug 1846611 eoan/linux-snapdragon: bug 1846634 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/1846641 Title: eoan/linux: 5.3.0-17.18 -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 debian-installer package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in debian-installer source package in Eoan: New Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Release phase-changed: Tuesday, 08. October 2019 15:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-release: Pending -- ready to copy trackers: bionic/linux-hwe-edge: bug 1846636 eoan/linux-aws: bug 1846613 eoan/linux-azure: bug 1846616 eoan/linux-gcp: bug 1846623 eoan/linux-kvm: bug 1846628 eoan/linux-oracle: bug 1846630 eoan/linux-raspi2: bug 1846611 eoan/linux-snapdragon: bug 1846634 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846641/+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 1844021] Re: Suspend stopped working from 4.4.0-157 onwards
I wont have access to that particular machine until Fri, but I did verify I could update another install in a VM. The only weirdness I saw was that after installing with dpkg -i *.deb, aptitude wanted to remove the headers since it depends on libssl1.1 > 1.1.0 which Mint does not have I guess. I figured it would not affect what we're testing here. I'll report back on Fri when I verify on real hardware. And thanks! -- 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/1844021 Title: Suspend stopped working from 4.4.0-157 onwards Status in linux package in Ubuntu: Incomplete Bug description: Since upgrading the kernel above 4.4.0-154, starting with 4.4.0-157, suspend does not work for me anymore. Never had such an issue in the last 6 years. This is the relevant output when suspend fails: [ 328.25] PM: Suspending system (mem) [ 328.288902] Suspending console(s) (use no_console_suspend to debug) [ 328.289118] wlp1s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) [ 328.289209] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [ 328.289570] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 328.289600] sd 0:0:0:0: [sda] Stopping disk [ 328.291700] sd 1:0:0:0: [sdb] Stopping disk [ 328.312413] xhci_hcd :03:00.0: WARN: xHC save state timeout [ 328.312456] suspend_common(): xhci_pci_suspend+0x0/0x70 returns -110 [ 328.312461] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110 [ 328.312465] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110 [ 328.312483] PM: Device :03:00.0 failed to suspend async: error -110 [ 328.848109] PM: Some devices failed to suspend, or early wake event detected This is my relevant lspci -v output: 03:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller (prog-if 30 [XHCI]) Subsystem: Samsung Electronics Co Ltd ASM1042 SuperSpeed USB Host Controller Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f050 (64-bit, non-prefetchable) [size=32K] Capabilities: Kernel driver in use: xhci_hcd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844021/+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 1776563]
I was trying another kernel parameters and noapic seems to work. It is not needed to disable the whole ACPI "service" https://www.icrwatch.com/ , however I don't know how important apic is. On kernel 4.18 even temperature sensors appear. -- 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/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+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 1847298] [NEW] eoan/linux: -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: Ready for Packaging phase-changed: Tuesday, 08. October 2019 15:57 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-hwe-edge: bug 1847297 eoan/linux-aws: bug 1847291 eoan/linux-azure: bug 1847292 eoan/linux-gcp: bug 1847293 eoan/linux-kvm: bug 1847294 eoan/linux-oracle: bug 1847295 eoan/linux-raspi2: bug 1847290 eoan/linux-snapdragon: bug 1847296 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/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.10.08-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the t
[Kernel-packages] [Bug 1847296] [NEW] eoan/linux-snapdragon: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Holding before Packaging phase-changed: Tuesday, 08. October 2019 15:57 UTC reason: prepare-package: Holding -- waiting for master bug 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/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: linux-snapdragon (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-snapdragon (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.10.08-1 kernel-sru-derivative-of-1847298 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux-snapdragon (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-snapdragon (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: linux-snapdragon (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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 -- + variant: debs ** Tags added: kernel-sru-cycle-d2019.10.08-1 ** 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: 1847298 variant: debs ** Tags added: kernel-sru-deri
[Kernel-packages] [Bug 1847295] [NEW] eoan/linux-oracle: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Packaging phase-changed: Tuesday, 08. October 2019 15:56 UTC reason: prepare-package: Holding -- waiting for master bug 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/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-oracle (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-oracle (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.10.08-1 kernel-sru-derivative-of-1847298 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux-oracle (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-oracle (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-oracle (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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
[Kernel-packages] [Bug 1847294] [NEW] eoan/linux-kvm: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Packaging phase-changed: Tuesday, 08. October 2019 15:56 UTC reason: prepare-package: Holding -- waiting for master bug 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/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-kvm (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-kvm (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.10.08-1 kernel-sru-derivative-of-1847298 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux-kvm (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-kvm (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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 -- + variant: debs ** Tags added: kernel-sru-cycle-d2019.10.08-1 ** 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: 1847298 variant: debs ** Tags added: kernel-sru-derivative-of-1847298 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance:
[Kernel-packages] [Bug 1847291] 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: 1847298 variant: debs ** Tags added: kernel-sru-derivative-of-1847298 ** 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/1847291 Title: eoan/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 prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Packaging phase-changed: Tuesday, 08. October 2019 15:56 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847291/+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 1847292] Re: linux-azure: -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + kernel-stable-master-bug: 1847298 variant: debs ** Tags added: kernel-sru-derivative-of-1847298 ** 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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1847292 Title: eoan/linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Tuesday, 08. October 2019 15:56 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847292/+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 1847293] Re: linux-gcp: -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + kernel-stable-master-bug: 1847298 variant: debs ** Tags added: kernel-sru-derivative-of-1847298 ** 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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1847293 Title: eoan/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 prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Tuesday, 08. October 2019 15:56 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847293/+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 1847290] Re: linux-raspi2: -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: 1847298 variant: debs ** Tags added: kernel-sru-derivative-of-1847298 ** 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-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1847290 Title: eoan/linux-raspi2: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Packaging phase-changed: Tuesday, 08. October 2019 15:55 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847290/+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 1847298] Re: eoan/linux: -proposed tracker
** Summary changed: - linux: -proposed tracker + eoan/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: Tuesday, 08. October 2019 15:57 UTC + reason: + prepare-package: Pending -- version not specified + trackers: + bionic/linux-hwe-edge: bug 1847297 + eoan/linux-aws: bug 1847291 + eoan/linux-azure: bug 1847292 + eoan/linux-gcp: bug 1847293 + eoan/linux-kvm: bug 1847294 + eoan/linux-oracle: bug 1847295 + eoan/linux-raspi2: bug 1847290 + eoan/linux-snapdragon: bug 1847296 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/1847298 Title: eoan/linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New 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 -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Packaging phase-changed: Tuesday, 08. October 2019 15:57 UTC reason: prepare-package: Pending -- version not specified trackers: bionic/linux-hwe-edge: bug 1847297 eoan/linux-aws: bug 1847291 eoan/linux-azure: bug 1847292 eoan/linux-gcp: bug 1847293 eoan/linux-kvm: bug 1847294 eoan/linux-oracle: bug 1847295 eoan/linux-raspi2: bug 1847290 eoan/linux-snapdragon: bug 1847296 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847298/+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 1847292] Re: eoan/linux-azure: -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + eoan/linux-azure: -proposed tracker ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 + packages: + lrm: linux-restricted-modules-azure + main: linux-azure + meta: linux-meta-azure + signed: linux-signed-azure + phase: Holding before Packaging + phase-changed: Tuesday, 08. October 2019 15:56 UTC + reason: + prepare-package: Holding -- waiting for master bug variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1847292 Title: eoan/linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Tuesday, 08. October 2019 15:56 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847292/+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 1847291] Re: eoan/linux-aws: -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + eoan/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: 1847298 + packages: + lrm: linux-restricted-modules-aws + main: linux-aws + meta: linux-meta-aws + phase: Holding before Packaging + phase-changed: Tuesday, 08. October 2019 15:56 UTC + reason: + prepare-package: Holding -- waiting for master bug variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1847291 Title: eoan/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 prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Holding before Packaging phase-changed: Tuesday, 08. October 2019 15:56 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847291/+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 1847293] Re: eoan/linux-gcp: -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + eoan/linux-gcp: -proposed tracker ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 + packages: + lrm: linux-restricted-modules-gcp + main: linux-gcp + meta: linux-meta-gcp + signed: linux-signed-gcp + phase: Holding before Packaging + phase-changed: Tuesday, 08. October 2019 15:56 UTC + reason: + prepare-package: Holding -- waiting for master bug variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1847293 Title: eoan/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 prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Packaging phase-changed: Tuesday, 08. October 2019 15:56 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847293/+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 1847295] Re: eoan/linux-oracle: -proposed tracker
** Summary changed: - linux-oracle: -proposed tracker + eoan/linux-oracle: -proposed tracker ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 + packages: + lrm: linux-restricted-modules-oracle + main: linux-oracle + meta: linux-meta-oracle + signed: linux-signed-oracle + phase: Holding before Packaging + phase-changed: Tuesday, 08. October 2019 15:56 UTC + reason: + prepare-package: Holding -- waiting for master bug variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1847295 Title: eoan/linux-oracle: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Holding before Packaging phase-changed: Tuesday, 08. October 2019 15:56 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847295/+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 1847296] Re: eoan/linux-snapdragon: -proposed tracker
** Summary changed: - linux-snapdragon: -proposed tracker + eoan/linux-snapdragon: -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: 1847298 + packages: + main: linux-snapdragon + meta: linux-meta-snapdragon + phase: Holding before Packaging + phase-changed: Tuesday, 08. October 2019 15:57 UTC + reason: + prepare-package: Holding -- waiting for master bug variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1847296 Title: eoan/linux-snapdragon: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-snapdragon package in Ubuntu: Confirmed Status in linux-snapdragon source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Holding before Packaging phase-changed: Tuesday, 08. October 2019 15:57 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847296/+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 1847294] Re: eoan/linux-kvm: -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + eoan/linux-kvm: -proposed tracker ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 + packages: + main: linux-kvm + meta: linux-meta-kvm + phase: Holding before Packaging + phase-changed: Tuesday, 08. October 2019 15:56 UTC + reason: + prepare-package: Holding -- waiting for master bug variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1847294 Title: eoan/linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Packaging phase-changed: Tuesday, 08. October 2019 15:56 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847294/+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 1846611] Re: eoan/linux-raspi2: -proposed tracker
*** This bug is a duplicate of bug 1847290 *** https://bugs.launchpad.net/bugs/1847290 ** This bug has been marked a duplicate of bug 1847290 eoan/linux-raspi2: -proposed tracker -- 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/1846611 Title: eoan/linux-raspi2: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1846641 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Ready for Packaging phase-changed: Friday, 04. October 2019 03:21 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846611/+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 1846613] Re: eoan/linux-aws: -proposed tracker
*** This bug is a duplicate of bug 1847291 *** https://bugs.launchpad.net/bugs/1847291 ** This bug has been marked a duplicate of bug 1847291 eoan/linux-aws: -proposed tracker -- 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/1846613 Title: eoan/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 prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1846641 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Ready for Packaging phase-changed: Friday, 04. October 2019 03:21 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846613/+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 1846634] Re: eoan/linux-snapdragon: -proposed tracker
*** This bug is a duplicate of bug 1847296 *** https://bugs.launchpad.net/bugs/1847296 ** This bug has been marked a duplicate of bug 1847296 eoan/linux-snapdragon: -proposed tracker -- 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/1846634 Title: eoan/linux-snapdragon: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-snapdragon package in Ubuntu: Confirmed Status in linux-snapdragon source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1846641 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Ready for Packaging phase-changed: Friday, 04. October 2019 03:22 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846634/+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 1846623] Re: eoan/linux-gcp: -proposed tracker
*** This bug is a duplicate of bug 1847293 *** https://bugs.launchpad.net/bugs/1847293 ** This bug has been marked a duplicate of bug 1847293 eoan/linux-gcp: -proposed tracker -- 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/1846623 Title: eoan/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 prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1846641 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Packaging phase-changed: Friday, 04. October 2019 03:22 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846623/+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 1846630] Re: eoan/linux-oracle: -proposed tracker
*** This bug is a duplicate of bug 1847295 *** https://bugs.launchpad.net/bugs/1847295 ** This bug has been marked a duplicate of bug 1847295 eoan/linux-oracle: -proposed tracker -- 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/1846630 Title: eoan/linux-oracle: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1846641 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Ready for Packaging phase-changed: Friday, 04. October 2019 03:22 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846630/+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 1847290] Re: eoan/linux-raspi2: -proposed tracker
** Summary changed: - linux-raspi2: -proposed tracker + eoan/linux-raspi2: -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: 1847298 + packages: + main: linux-raspi2 + meta: linux-meta-raspi2 + phase: Holding before Packaging + phase-changed: Tuesday, 08. October 2019 15:55 UTC + reason: + prepare-package: Holding -- waiting for master bug variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1847290 Title: eoan/linux-raspi2: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1847298 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Packaging phase-changed: Tuesday, 08. October 2019 15:55 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847290/+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 1846628] Re: eoan/linux-kvm: -proposed tracker
*** This bug is a duplicate of bug 1847294 *** https://bugs.launchpad.net/bugs/1847294 ** This bug has been marked a duplicate of bug 1847294 eoan/linux-kvm: -proposed tracker -- 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/1846628 Title: eoan/linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1846641 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Packaging phase-changed: Friday, 04. October 2019 03:22 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1846628/+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
