[Kernel-packages] [Bug 1880645] Re: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H
** Changed in: ubuntu-kernel-tests Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1880645 Title: icmp_redirect.sh in net from ubuntu_kernel_selftests failed on F-OEM-5.6 / F-OEM-5.10 / F-OEM-5.13 / F / G / H Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Won't Fix Status in linux source package in Groovy: Won't Fix Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.13 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Bug description: [Impact] The IPv6: mtu exception plus redirect test in icmp_redirect.sh test from kselftest/net is expected to fail due to a known bug in the IPv6 logic. When trying to run this test you will see this sub test fail with: TEST: IPv6: mtu exception plus redirect [FAIL] and thus causing non-zero return value for this script. [Fix] * 0a36a75c681880 selftests: icmp_redirect: support expected failures This fix can be cherry-picked into all affected series. And it has already landed on Unstable, test passed with Impish 5.13. Although we have this script in Focal kernel as well, but it's not being executed at all. This is another issue that will be dealt in a different bug report. [Test] Run the patched icmp_redirect.sh test manually in tools/testing/selftests/net, this sub-test will be marked as XFAIL and the return value of this script will be 0: $ sudo ./icmp_redirect.sh # Routing with nexthop objects and VRF # TEST: IPv6: mtu exception plus redirect [XFAIL] Tests passed: 36 Tests failed: 0 Tests xfailed: 4 $ echo $? 0 [Where problems could occur] Change limited to testing tool, not affecting actual kernel functionality. The only possible issue that I can think of is that as this script is no longer complaining about this failure, people might forgot there is such an issue exist in ipv6. [Original Bug Report] Issue found on Focal 5.6.0-1011.11-oem ubuntu@rizzo:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ sudo ./icmp_redirect.sh ### Legacy routing ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL] ### Legacy routing with VRF ### TEST: IPv4: redirect exception [ OK ] TEST: IPv6: redirect exception [ OK ] TEST: IPv4: redirect exception plus mtu [ OK ] TEST: IPv6: redirect exception plus mtu [ OK ] TEST: IPv4: routing reset [ OK ] TEST: IPv6: routing reset [ OK ] TEST: IPv4: mtu exception [ OK ] TEST: IPv6: mtu exception [ OK ] TEST: IPv4: mtu exception plus redirect [ OK ] TEST: IPv6: mtu exception plus redirect [FAIL]
[Kernel-packages] [Bug 1941773] Re: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver
attached journal.log file, done after trying to boot with 5.13.13 (kernel panic) and rebooting with functional kernel (5.13.8) ** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+attachment/5521049/+files/journal.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941773 Title: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver Status in linux package in Ubuntu: Confirmed Bug description: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (13 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (14 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940262] Re: The modalias in 470 is not compatible to 460
Reuploading the script ** Attachment removed: "nvidia_supported" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1940262/+attachment/5521045/+files/nvidia_supported ** Attachment added: "nvidia_supported" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1940262/+attachment/5521048/+files/nvidia_supported -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1940262 Title: The modalias in 470 is not compatible to 460 Status in OEM Priority Project: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Committed Bug description: There are many modalias be removed from 470 those supporting in 460. If 470 is a LTS version and 460 will be transited to 470 then the driver installing will have different behavior between both version. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941773] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1941773/+attachment/5521047/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941773 Title: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver Status in linux package in Ubuntu: Confirmed Bug description: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (13 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (14 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941773] Re: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver
apport information ** Description changed: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (13 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65.1 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: KDE + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2021-08-12 (14 days ago) + InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) + Package: linux (not installed) + Tags: hirsute + Uname: Linux 5.13.8-051308-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1941773/+attachment/5521046/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941773 Title: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver Status in linux package in Ubuntu: Confirmed Bug description: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (13 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (14 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940262] Re: The modalias in 470 is not compatible to 460
** Tags added: originate-from-1941823 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1940262 Title: The modalias in 470 is not compatible to 460 Status in OEM Priority Project: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Committed Bug description: There are many modalias be removed from 470 those supporting in 460. If 470 is a LTS version and 460 will be transited to 470 then the driver installing will have different behavior between both version. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940262] Re: The modalias in 470 is not compatible to 460
I would like to propose fix to nvidia_supported script that parses README.txt. On the line with RTX A5000, there are 2 spaces after the PCI IDs. Current nvidia_supported script assumes there are at least 3 spaces before VDPAU features column, which is not the case in this line. My proposal of parsing this list is to use offset to get the column of Device PCI ID, and get 1-3 hex strings after the offset. ** Attachment added: "nvidia_supported" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1940262/+attachment/5521045/+files/nvidia_supported -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1940262 Title: The modalias in 470 is not compatible to 460 Status in OEM Priority Project: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Committed Bug description: There are many modalias be removed from 470 those supporting in 460. If 470 is a LTS version and 460 will be transited to 470 then the driver installing will have different behavior between both version. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941829] Re: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
** Tags added: 4.15 5.10 5.11 5.13 5.4 bionic focal hirsute ** Tags added: impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941829 Title: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] The memory-hotplug test has been intermittently timing out (or trashing the test VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now. While the offline memory test obey ratio limit, the same test with error injection does not and tries to offline all the hotpluggable memory, spamming system logs with hundreds of thousands of dump_page() entries, slowing system down (to the point the test itself timesout and gets terminated) and excessive fs occupation: ... [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 mapping:c001fc03e950 index:0xe7b [ 9784.393355] def_blk_aops [ 9784.393356] flags: 0x382062(referenced|active|workingset|private) [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 c001fc03e950 [ 9784.393359] raw: 0e7b c6607b18 0003 c490d000 [ 9784.393359] page dumped because: migration failure [ 9784.393360] page->mem_cgroup:c490d000 [ 9784.393416] migrating pfn 1f46d failed ret:1 ... $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l 2405558 $ ls -la /var/log/kern.log -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log [Fix] * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test [Test Plan] Run the memory-hotplug test, this log spamming issue should not happen again. [Where problems could occur] If this fix is incorrect we might be unable to catch some other issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1941829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941829] Re: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Bionic) Status: New => Invalid ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: New => Invalid ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Impish) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-oem-5.13 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- 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/1941829 Title: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] The memory-hotplug test has been intermittently timing out (or trashing the test VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now. While the offline memory test obey ratio limit, the same test with error injection does not and tries to offline all the hotpluggable memory, spamming system logs with hundreds of thousands of dump_page() entries, slowing system down (to the point the test itself timesout and gets terminated) and excessive fs occupation: ... [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 mapping:c001fc03e950 index:0xe7b [ 9784.393355] def_blk_aops [ 9784.393356] flags: 0x382062(referenced|active|workingset|private) [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 c001fc03e950 [ 9784.393359] raw: 0e7b c6607b18 0003 c490d000 [ 9784.393359] page dumped because: migration failure [ 9784.393360] page->mem_cgroup:c490d000 [ 9784.393416] migrating pfn 1f46d failed ret:1 ... $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l 2405558 $ ls -la /var/log/kern.log -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log [Fix] * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test [Test Plan] Run the memory-hotplug test, this log spamming issue should not happen again. [Where problems could occur] If this fix is incorrect we might be unable to catch some other issue. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1941829] 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 1941829 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/1941829 Title: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: New Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Hirsute: New Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: New Status in linux source package in Impish: Incomplete Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: New Bug description: [Impact] The memory-hotplug test has been intermittently timing out (or trashing the test VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now. While the offline memory test obey ratio limit, the same test with error injection does not and tries to offline all the hotpluggable memory, spamming system logs with hundreds of thousands of dump_page() entries, slowing system down (to the point the test itself timesout and gets terminated) and excessive fs occupation: ... [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 mapping:c001fc03e950 index:0xe7b [ 9784.393355] def_blk_aops [ 9784.393356] flags: 0x382062(referenced|active|workingset|private) [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 c001fc03e950 [ 9784.393359] raw: 0e7b c6607b18 0003 c490d000 [ 9784.393359] page dumped because: migration failure [ 9784.393360] page->mem_cgroup:c490d000 [ 9784.393416] migrating pfn 1f46d failed ret:1 ... $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l 2405558 $ ls -la /var/log/kern.log -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log [Fix] * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test [Test Plan] Run the memory-hotplug test, this log spamming issue should not happen again. [Where problems could occur] If this fix is incorrect we might be unable to catch some other issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1941829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941829] [NEW] ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
Public bug reported: [Impact] The memory-hotplug test has been intermittently timing out (or trashing the test VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now. While the offline memory test obey ratio limit, the same test with error injection does not and tries to offline all the hotpluggable memory, spamming system logs with hundreds of thousands of dump_page() entries, slowing system down (to the point the test itself timesout and gets terminated) and excessive fs occupation: ... [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 mapping:c001fc03e950 index:0xe7b [ 9784.393355] def_blk_aops [ 9784.393356] flags: 0x382062(referenced|active|workingset|private) [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 c001fc03e950 [ 9784.393359] raw: 0e7b c6607b18 0003 c490d000 [ 9784.393359] page dumped because: migration failure [ 9784.393360] page->mem_cgroup:c490d000 [ 9784.393416] migrating pfn 1f46d failed ret:1 ... $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l 2405558 $ ls -la /var/log/kern.log -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log [Fix] * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test [Test Plan] Run the memory-hotplug test, this log spamming issue should not happen again. [Where problems could occur] If this fix is incorrect we might be unable to catch some other issue. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: ubuntu-kernel-selftests ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: ubuntu-kernel-selftests -- 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/1941829 Title: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The memory-hotplug test has been intermittently timing out (or trashing the test VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now. While the offline memory test obey ratio limit, the same test with error injection does not and tries to offline all the hotpluggable memory, spamming system logs with hundreds of thousands of dump_page() entries, slowing system down (to the point the test itself timesout and gets terminated) and excessive fs occupation: ... [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 mapping:c001fc03e950 index:0xe7b [ 9784.393355] def_blk_aops [ 9784.393356] flags: 0x382062(referenced|active|workingset|private) [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 c001fc03e950 [ 9784.393359] raw: 0e7b c6607b18 0003 c490d000 [ 9784.393359] page dumped because: migration failure [ 9784.393360] page->mem_cgroup:c490d000 [ 9784.393416] migrating pfn 1f46d failed ret:1 ... $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l 2405558 $ ls -la /var/log/kern.log -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log [Fix] * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test [Test Plan] Run the memory-hotplug test, this log spamming issue should not happen again. [Where problems could occur] If this fix is incorrect we might be unable to catch some other issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1941829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933686] Re: I use two monitors (the laptop monitor and an other), but only the extern is working
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1933686 Title: I use two monitors (the laptop monitor and an other), but only the extern is working Status in linux package in Ubuntu: Expired Bug description: If I boot ubuntu in recovery mode and resume booting, only the laptop monitor is working. In the older version ..-16 booth monitors worked well ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 25 19:41:25 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Xe Graphics [103c:881d] InstallationDate: Installed on 2021-06-25 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Laptop 15-dw3xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=735cc3d9-c94e-4579-95a3-15d5740641e8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2021 dmi.bios.release: 15.43 dmi.bios.vendor: Insyde dmi.bios.version: F.43 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 881D dmi.board.vendor: HP dmi.board.version: 50.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 50.24 dmi.modalias: dmi:bvnInsyde:bvrF.43:bd03/31/2021:br15.43:efr50.24:svnHP:pnHPLaptop15-dw3xxx:pvrType1ProductConfigId:rvnHP:rn881D:rvr50.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-dw3xxx dmi.product.sku: 428Z9EA#ABD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
** Changed in: linux-oem-5.6 (Ubuntu Focal) Assignee: (unassigned) => zeeshan saleem (zeeshan-saleem) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: == SRU Justification == [Impact] Touchpad on sereval Lenovo ThinkBook doesn't work. [Fix] Maintain method calling ordering by calling _REG before issuing _STA, as ACPI spec suggested, for I2C ACPI devices. [Test] Positive feedback from several users. [Regression Potential] If there are some systems that rely on the wrong calling ordering then there's a regression risk. However it's rather unlikely. == Original Bug Report == This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941773] Re: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver
Could you run `apport-collect 1941773` again since lots of file missing. And can you paste the kernel panic here? Doing `journalctl -k -b -1 > journal.log` after reboot and attach the journal.log here would be helpful. 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/1941773 Title: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver Status in linux package in Ubuntu: Confirmed Bug description: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (13 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
@Michael and Robert, All patches were sent to the ubuntu kernel maillist to review, and please wait for the formal 5.11.0-generic kernel of the next cycle. @Robert, All patches were backported from sofproject or upstream kernel, and maybe the kconfig is not same when building the sof kernel and ubuntu kernel. The patches were also sent to ubuntu 5.13 and 5.14 kernel, please wait for those kernels of next cycle (please watch the impish status). -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
The dmesg of 5.13 kept showing the error as follow août 26 11:18:46 syncom kernel: Workqueue: kacpid acpi_os_execute_deferred août 26 11:18:46 syncom kernel: RIP: 0010:acpi_ds_exec_end_op+0x182/0x779 But it didn't show in kernel 5.11. That's pretty confusing to me. I may need more ACPI debug message for it. Before doing that, can you test the following kernels for me so that I can narrow down the range of culprit.Thanks https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.12/ https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14-rc3/ -- 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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected Status in linux package in Ubuntu: Confirmed Bug description: Hello, My laptop run well with last 5.4 linux kernel even if I connect my thunderbolt dock. When trying to boot with 5.11.0-25 or 5.11.0-27 (hwe) kernel with dock and 2 monitors connected, the kernel panic after 3 or 4 seconds. Without the dock, he work fine. After a lot of try, I was able to boot sometime on 5.11 with the dock, but randomly and only if I only connect 1 extra monitor (I usually use two). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jmaillar 1988 F pulseaudio /dev/snd/controlC1: jmaillar 1988 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 EcryptfsInUse: Yes HibernationDevice: RESUME=none MachineType: Dell Inc. Precision 7530 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 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=b21fab6e-02fe-4295-a308-9da15f339a36 ro ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-27-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-20 (483 days ago) UserGroups: adm audio cdrom dip disk input kismet kvm libvirt libvirtd lpadmin lxd netdev plugdev sambashare sudo systemd-network users vboxusers video wireshark _MarkForUpload: True dmi.bios.date: 05/25/2021 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.1 dmi.board.name: 0425K7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.1:bd05/25/2021:br1.16:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn0425K7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7530 dmi.product.sku: 0831 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2015-11-27T14:42:56.796345 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940377] 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 1940377 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/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
** Changed in: linux (Ubuntu) Assignee: (unassigned) => AaronMa (mapengyu) -- 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/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
** Also affects: linux (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/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
@Gabriel Can you also check linux-image-generic-hwe-20.04 on focal ? it's 5.11 as well. linux-image-generic-hwe-20.04 5.11.0.27.29~20.04.11 -- 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/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941788] Re: amdgpu page fault in journalctl
Thanks for the bug report. Unfortunately since you have an unsupported
PPA ("oibaf") and kernel installed, we can't technically call this an
Ubuntu bug. Does the same problem happen with the official Ubuntu
kernel?
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Tags added: amdgpu
** 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/1941788
Title:
amdgpu page fault in journalctl
Status in linux package in Ubuntu:
Incomplete
Bug description:
This is what I am having in the jouralctl logs:
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu:
MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty
UTCL2 client ID: VCN0 (0x2b)
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu:
MORE_FAULTS: 0x1
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu:
WALKER_ERROR: 0x0
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu:
PERMISSION_FAULTS: 0x3
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu:
MAPPING_ERROR: 0x0
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault
(src_id:0 ring:0 vmid:7 pasid:32771, for process vivaldi-bin pid 62181 thread
vivaldi-bi:cs0 pid 62192)
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting
at address 0x800100a44000 from client 0x12 (VMC)
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu:
MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty
UTCL2 client ID: VCN0 (0x2b)
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu:
MORE_FAULTS: 0x1
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu:
WALKER_ERROR: 0x0
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu:
PERMISSION_FAULTS: 0x3
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu:
MAPPING_ERROR: 0x0
Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault
(src_id:0 ring:0 vmid:7 pasid:32771, for process vivaldi-bin pid 62181 thread
vivaldi-bi:cs0 pid 62192)
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting
at address 0x8001013a from client 0x12 (VMC)
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu:
MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty
UTCL2 client ID: VCN0 (0x2b)
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu:
MORE_FAULTS: 0x1
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu:
WALKER_ERROR: 0x0
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu:
PERMISSION_FAULTS: 0x3
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu:
MAPPING_ERROR: 0x0
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault
(src_id:0 ring:0 vmid:7 pasid:32771, for process vivaldi-bin pid 62181 thread
vivaldi-bi:cs0 pid 62192)
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting
at address 0x8001013c8000 from client 0x12 (VMC)
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu:
MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty
UTCL2 client ID: VCN0 (0x2b)
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu:
MORE_FAULTS: 0x1
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu:
WALKER_ERROR: 0x0
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu:
PERMISSION_FAULTS: 0x3
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu:
MAPPING_ERROR: 0x0
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault
(src_id:0 ring:0 vmid:7 pasid:32771, for process vivaldi-bin pid 62181 thread
vivaldi-bi:cs0 pid 62192)
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting
at address 0x8001013a2000 from client 0x12 (VMC)
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu:
MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty
UTCL2 client ID: VCN0 (0x2b)
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu:
MORE_FAULTS: 0x1
Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu:
WALKER_ERROR: 0x0
Aug 26 17:17:27 dagon kernel: amdgpu
[Kernel-packages] [Bug 1941788] [NEW] amdgpu page fault in journalctl
You have been subscribed to a public bug: This is what I am having in the jouralctl logs: Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: VCN0 (0x2b) Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:0 vmid:7 pasid:32771, for process vivaldi-bin pid 62181 thread vivaldi-bi:cs0 pid 62192) Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x800100a44000 from client 0x12 (VMC) Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: VCN0 (0x2b) Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 26 17:11:02 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:0 vmid:7 pasid:32771, for process vivaldi-bin pid 62181 thread vivaldi-bi:cs0 pid 62192) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x8001013a from client 0x12 (VMC) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: VCN0 (0x2b) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:0 vmid:7 pasid:32771, for process vivaldi-bin pid 62181 thread vivaldi-bi:cs0 pid 62192) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x8001013c8000 from client 0x12 (VMC) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: VCN0 (0x2b) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:0 vmid:7 pasid:32771, for process vivaldi-bin pid 62181 thread vivaldi-bi:cs0 pid 62192) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x8001013a2000 from client 0x12 (VMC) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: VCN0 (0x2b) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: RW: 0x0 Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:0 vmid:7 pasid:32771, for process vivaldi-bin pid 62181 thread vivaldi-bi:cs0 pid 62192) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: in page starting at address 0x8001013c9000 from client 0x12 (VMC) Aug 26 17:17:27 dagon kernel: amdgpu :03:00.0: amdgpu: MMVM_L2_PROTECTION_FAULT_STATUS:0x00705631 Aug 26 17:17:27 dagon kernel: amdgpu
[Kernel-packages] [Bug 1939205] Re: sound dummy output 21.04
** 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/1939205 Title: sound dummy output 21.04 Status in linux package in Ubuntu: Confirmed Bug description: no more sound device /output since dist upgrade from 20.10 to 21.04 tried both official ubuntu kernel 5.11.0.26 and newer 5.13.8-051308-generic alsa log: http://alsa-project.org/db/?f=07dfaad1d5d30948449dc36f0caaf39c99145cce lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 apt-cache policy pkgname N: Unable to locate package pkgname ubuntu-bug linux: package not installed cat /proc/version_signature > version.log cat: /proc/version_signature: No such file or directory sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error be descriptive in helping as im a newbie to linux troubleshoot :) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2013-05-11 (3025 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) Package: linux (not installed) RebootRequiredPkgs: linux-image-5.11.0-31-generic linux-base Tags: hirsute Uname: Linux 5.13.9-051309-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to hirsute on 2021-07-19 (34 days ago) UserGroups: adm audio cdrom dip lpadmin netdev plugdev pulse pulse-access sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939205/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941808] 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/1941808 Title: AMD desktop fails to suspend Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 5.11.0-31-generic from 5.11.0-25-generic my system is no longer able to enter deep sleep when I choose "Suspend" from the Gnome power menu. The display goes blank for about 3 seconds and then comes back to the login screen. Machine setup: Desktop PC Ubuntu 21.04 Linux version 5.11.0-17-generic AMD Ryzen 3900X Asus X590 PRIME PRO motherboard NVIDIA P400 GPU The following appears in dmesg: [ 193.035190] PM: suspend entry (deep) [ 193.043644] Filesystems sync: 0.008 seconds [ 193.221385] rfkill: input handler enabled [ 193.223342] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 193.225169] OOM killer disabled. [ 193.225170] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 193.226377] printk: Suspending console(s) (use no_console_suspend to debug) [ 193.227086] serial 00:04: disabled [ 193.236938] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 [ 193.236948] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16 [ 193.236955] PM: Device :0b:00.3 failed to suspend async: error -16 [ 193.433850] PM: Some devices failed to suspend, or early wake event detected [ 193.434781] serial 00:04: activated [ 193.439638] nvme nvme1: Shutdown timeout set to 8 seconds [ 193.441267] nvme nvme0: 32/0/0 default/read/poll queues [ 193.467431] nvme nvme1: 32/0/0 default/read/poll queues [ 193.729944] usb 5-2.3: reset high-speed USB device number 3 using xhci_hcd [ 193.746614] ata1: SATA link down (SStatus 0 SControl 300) [ 193.746619] ata2: SATA link down (SStatus 0 SControl 300) [ 193.864008] OOM killer enabled. [ 193.864009] Restarting tasks ... done. [ 193.865012] PM: suspend exit [ 193.865069] PM: suspend entry (s2idle) [ 193.869519] Filesystems sync: 0.004 seconds [ 193.907792] Freezing user space processes ... (elapsed 0.007 seconds) done. [ 193.915352] OOM killer disabled. [ 193.915353] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 193.916464] printk: Suspending console(s) (use no_console_suspend to debug) [ 193.917046] serial 00:04: disabled [ 193.925345] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 [ 193.925355] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16 [ 193.925362] PM: Device :0b:00.3 failed to suspend async: error -16 [ 194.118212] PM: Some devices failed to suspend, or early wake event detected [ 194.119120] serial 00:04: activated [ 194.123827] nvme nvme1: Shutdown timeout set to 8 seconds [ 194.126322] nvme nvme0: 32/0/0 default/read/poll queues [ 194.150499] nvme nvme1: 32/0/0 default/read/poll queues [ 194.413459] usb 5-2.3: reset high-speed USB device number 3 using xhci_hcd [ 194.434238] ata2: SATA link down (SStatus 0 SControl 300) [ 194.434256] ata1: SATA link down (SStatus 0 SControl 300) [ 194.547373] OOM killer enabled. [ 194.547374] Restarting tasks ... done. [ 194.548195] PM: suspend exit [ 194.694550] rfkill: input handler disabled I see pci device mentioned is: 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-31-generic 5.11.0-31.33 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacob 2034 F pulseaudio /dev/snd/controlC0: jacob 2034 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 16:57:09 2021 InstallationDate: Installed on 2020-10-28 (302 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp5s0no wireless extensions. docker0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=f721d5df-ceec-434a-919a-0680ee380996 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 RfKill: SourcePackage: linux
[Kernel-packages] [Bug 1941808] Re: AMD desktop fails to suspend
Actually it appears that one usb device was the source of the problem. It's not a common USB device so it's not likely worth fixing. Bus 005 Device 003: ID 28f3:4000 Clover Network, Inc. Flex -- 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/1941808 Title: AMD desktop fails to suspend Status in linux package in Ubuntu: New Bug description: Since upgrading to 5.11.0-31-generic from 5.11.0-25-generic my system is no longer able to enter deep sleep when I choose "Suspend" from the Gnome power menu. The display goes blank for about 3 seconds and then comes back to the login screen. Machine setup: Desktop PC Ubuntu 21.04 Linux version 5.11.0-17-generic AMD Ryzen 3900X Asus X590 PRIME PRO motherboard NVIDIA P400 GPU The following appears in dmesg: [ 193.035190] PM: suspend entry (deep) [ 193.043644] Filesystems sync: 0.008 seconds [ 193.221385] rfkill: input handler enabled [ 193.223342] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 193.225169] OOM killer disabled. [ 193.225170] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 193.226377] printk: Suspending console(s) (use no_console_suspend to debug) [ 193.227086] serial 00:04: disabled [ 193.236938] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 [ 193.236948] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16 [ 193.236955] PM: Device :0b:00.3 failed to suspend async: error -16 [ 193.433850] PM: Some devices failed to suspend, or early wake event detected [ 193.434781] serial 00:04: activated [ 193.439638] nvme nvme1: Shutdown timeout set to 8 seconds [ 193.441267] nvme nvme0: 32/0/0 default/read/poll queues [ 193.467431] nvme nvme1: 32/0/0 default/read/poll queues [ 193.729944] usb 5-2.3: reset high-speed USB device number 3 using xhci_hcd [ 193.746614] ata1: SATA link down (SStatus 0 SControl 300) [ 193.746619] ata2: SATA link down (SStatus 0 SControl 300) [ 193.864008] OOM killer enabled. [ 193.864009] Restarting tasks ... done. [ 193.865012] PM: suspend exit [ 193.865069] PM: suspend entry (s2idle) [ 193.869519] Filesystems sync: 0.004 seconds [ 193.907792] Freezing user space processes ... (elapsed 0.007 seconds) done. [ 193.915352] OOM killer disabled. [ 193.915353] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 193.916464] printk: Suspending console(s) (use no_console_suspend to debug) [ 193.917046] serial 00:04: disabled [ 193.925345] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 [ 193.925355] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16 [ 193.925362] PM: Device :0b:00.3 failed to suspend async: error -16 [ 194.118212] PM: Some devices failed to suspend, or early wake event detected [ 194.119120] serial 00:04: activated [ 194.123827] nvme nvme1: Shutdown timeout set to 8 seconds [ 194.126322] nvme nvme0: 32/0/0 default/read/poll queues [ 194.150499] nvme nvme1: 32/0/0 default/read/poll queues [ 194.413459] usb 5-2.3: reset high-speed USB device number 3 using xhci_hcd [ 194.434238] ata2: SATA link down (SStatus 0 SControl 300) [ 194.434256] ata1: SATA link down (SStatus 0 SControl 300) [ 194.547373] OOM killer enabled. [ 194.547374] Restarting tasks ... done. [ 194.548195] PM: suspend exit [ 194.694550] rfkill: input handler disabled I see pci device mentioned is: 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-31-generic 5.11.0-31.33 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacob 2034 F pulseaudio /dev/snd/controlC0: jacob 2034 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 16:57:09 2021 InstallationDate: Installed on 2020-10-28 (302 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp5s0no wireless extensions. docker0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=f721d5df-ceec-434a-919a-0680ee380996 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A
[Kernel-packages] [Bug 1941808] [NEW] AMD desktop fails to suspend
Public bug reported: Since upgrading to 5.11.0-31-generic from 5.11.0-25-generic my system is no longer able to enter deep sleep when I choose "Suspend" from the Gnome power menu. The display goes blank for about 3 seconds and then comes back to the login screen. Machine setup: Desktop PC Ubuntu 21.04 Linux version 5.11.0-17-generic AMD Ryzen 3900X Asus X590 PRIME PRO motherboard NVIDIA P400 GPU The following appears in dmesg: [ 193.035190] PM: suspend entry (deep) [ 193.043644] Filesystems sync: 0.008 seconds [ 193.221385] rfkill: input handler enabled [ 193.223342] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 193.225169] OOM killer disabled. [ 193.225170] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 193.226377] printk: Suspending console(s) (use no_console_suspend to debug) [ 193.227086] serial 00:04: disabled [ 193.236938] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 [ 193.236948] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16 [ 193.236955] PM: Device :0b:00.3 failed to suspend async: error -16 [ 193.433850] PM: Some devices failed to suspend, or early wake event detected [ 193.434781] serial 00:04: activated [ 193.439638] nvme nvme1: Shutdown timeout set to 8 seconds [ 193.441267] nvme nvme0: 32/0/0 default/read/poll queues [ 193.467431] nvme nvme1: 32/0/0 default/read/poll queues [ 193.729944] usb 5-2.3: reset high-speed USB device number 3 using xhci_hcd [ 193.746614] ata1: SATA link down (SStatus 0 SControl 300) [ 193.746619] ata2: SATA link down (SStatus 0 SControl 300) [ 193.864008] OOM killer enabled. [ 193.864009] Restarting tasks ... done. [ 193.865012] PM: suspend exit [ 193.865069] PM: suspend entry (s2idle) [ 193.869519] Filesystems sync: 0.004 seconds [ 193.907792] Freezing user space processes ... (elapsed 0.007 seconds) done. [ 193.915352] OOM killer disabled. [ 193.915353] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 193.916464] printk: Suspending console(s) (use no_console_suspend to debug) [ 193.917046] serial 00:04: disabled [ 193.925345] PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 [ 193.925355] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16 [ 193.925362] PM: Device :0b:00.3 failed to suspend async: error -16 [ 194.118212] PM: Some devices failed to suspend, or early wake event detected [ 194.119120] serial 00:04: activated [ 194.123827] nvme nvme1: Shutdown timeout set to 8 seconds [ 194.126322] nvme nvme0: 32/0/0 default/read/poll queues [ 194.150499] nvme nvme1: 32/0/0 default/read/poll queues [ 194.413459] usb 5-2.3: reset high-speed USB device number 3 using xhci_hcd [ 194.434238] ata2: SATA link down (SStatus 0 SControl 300) [ 194.434256] ata1: SATA link down (SStatus 0 SControl 300) [ 194.547373] OOM killer enabled. [ 194.547374] Restarting tasks ... done. [ 194.548195] PM: suspend exit [ 194.694550] rfkill: input handler disabled I see pci device mentioned is: 0b:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-31-generic 5.11.0-31.33 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jacob 2034 F pulseaudio /dev/snd/controlC0: jacob 2034 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 16:57:09 2021 InstallationDate: Installed on 2020-10-28 (302 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp5s0no wireless extensions. docker0 no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=f721d5df-ceec-434a-919a-0680ee380996 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-14 (104 days ago) dmi.bios.date: 08/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4021 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO 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:
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
Just for comparison, the same PC but a different distribution with the 5.13.12 kernel. I found not in the Ubuntu /proc/modules amdgpu or radeon, but in the other Linux installation. I believe thats is the problem. ** Attachment added: "cat /proc/modules" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5521000/+files/Modules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941803] [NEW] Add the upcoming BlueField-3 device ID
Public bug reported: SRU Justification: Add device ID for BlueField-3 * Explain the bug(s) Not a bug * How to test System should recognize BlueField-3 from lspci * What it could break. Nothing will break ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1941803 Title: Add the upcoming BlueField-3 device ID Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: Add device ID for BlueField-3 * Explain the bug(s) Not a bug * How to test System should recognize BlueField-3 from lspci * What it could break. Nothing will break To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1941803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "alsa-info vmlinuz-5.11.0-25-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520991/+files/alsa-info.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "lspci vmlinuz-5.11.0-31-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520997/+files/lspci-vmlinuz-5.11.0.-31-generic.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "aplay -l vmlinuz-5.11.0-25-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520990/+files/aplay.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "alsa-info vmlinuz-5.11.0-31-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520992/+files/alsa-info-vmlinuz-5.11.0.-31-generic.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "cat/proc/asound/cards vmlinuz-5.11.0-25-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520994/+files/ProcAsoundCards.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "dmesg vmlinuz-5.11.0-25-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520995/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "lsmod vmlinuz-5.11.0-25-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520993/+files/lsmod.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "lspci vmlinuz-5.11.0-25-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520996/+files/lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
Exactly the same problem occurs with the 5.11.0-31-generic kernel, only the audio output does not work. I think I'm déjà vu. https://bugzilla.kernel.org/show_bug.cgi?id=207515 ** Bug watch added: Linux Kernel Bug Tracker #207515 https://bugzilla.kernel.org/show_bug.cgi?id=207515 -- 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/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941741] Re: Bluetooth not working
I spoke too soon. WLAN does not work in some cases, maybe if there is the same ID for 2 and 5 GHz. ** Attachment added: "dmesg-suspend.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.13/+bug/1941741/+attachment/5520982/+files/dmesg-suspend.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941741 Title: Bluetooth not working Status in linux-signed-oem-5.13 package in Ubuntu: New Bug description: I made a fresh install on a XPS 13 9310 with ubuntu-20.04.2.0-desktop- amd64.iso. It installed the Kernel from linux-image-5.6.0-1047-oem and upgrades to linux-image-5.10.0-1044-oem automatically. With the later kernel, WiFi and Bluetooth stopped working. There were also issues at shutdown. I then installed linux-image-5.13.0-1010-oem which solved the WiFi problem, but Bluetooth still doesn't work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-1010-oem 5.13.0-1010.11 ProcVersionSignature: Ubuntu 5.13.0-1010.11-oem 5.13.1 Uname: Linux 5.13.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 13:31:41 2021 InstallationDate: Installed on 2021-08-25 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.13 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-5.13/+bug/1941741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941798] [NEW] Focal update: v5.4.140 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.140 upstream stable release from git://git.kernel.org/ Revert "ACPICA: Fix memory leak caused by _CID repair function" ALSA: seq: Fix racy deletion of subscriber arm64: dts: ls1028a: fix node name for the sysclk ARM: imx: add missing iounmap() ARM: imx: add missing clk_disable_unprepare() ARM: dts: imx6qdl-sr-som: Increase the PHY reset duration to 10ms ARM: dts: colibri-imx6ull: limit SDIO clock to 25MHz ARM: imx: fix missing 3rd argument in macro imx_mmdc_perf_init ARM: dts: imx: Swap M53Menlo pinctrl_power_button/pinctrl_power_out pins arm64: dts: armada-3720-turris-mox: remove mrvl,i2c-fast-mode ALSA: usb-audio: fix incorrect clock source setting clk: stm32f4: fix post divisor setup for I2S/SAI PLLs ARM: dts: am437x-l4: fix typo in can@0 node omap5-board-common: remove not physically existing vdds_1v8_main fixed-regulator spi: imx: mx51-ecspi: Reinstate low-speed CONFIGREG delay spi: imx: mx51-ecspi: Fix low-speed CONFIGREG delay calculation scsi: sr: Return correct event when media event code is 3 media: videobuf2-core: dequeue if start_streaming fails dmaengine: imx-dma: configure the generic DMA type to make it work net, gro: Set inner transport header offset in tcp/udp GRO hook net: dsa: sja1105: overwrite dynamic FDB entries with static ones in .port_fdb_add net: dsa: sja1105: invalidate dynamic FDB entries learned concurrently with statically added ones net: phy: micrel: Fix detection of ksz87xx switch net: natsemi: Fix missing pci_disable_device() in probe and remove gpio: tqmx86: really make IRQ optional sctp: move the active_key update after sh_keys is added nfp: update ethtool reporting of pauseframe control net: ipv6: fix returned variable type in ip6_skb_dst_mtu mips: Fix non-POSIX regexp bnx2x: fix an error code in bnx2x_nic_load() net: pegasus: fix uninit-value in get_interrupt_interval net: fec: fix use-after-free in fec_drv_remove net: vxge: fix use-after-free in vxge_device_unregister blk-iolatency: error out if blk_get_queue() failed in iolatency_set_limit() Bluetooth: defer cleanup of resources in hci_unregister_dev() USB: usbtmc: Fix RCU stall warning USB: serial: option: add Telit FD980 composition 0x1056 USB: serial: ch341: fix character loss at high transfer rates USB: serial: ftdi_sio: add device ID for Auto-M3 OP-COM v2 firmware_loader: use -ETIMEDOUT instead of -EAGAIN in fw_load_sysfs_fallback firmware_loader: fix use-after-free in firmware_fallback_sysfs ALSA: hda/realtek: add mic quirk for Acer SF314-42 ALSA: usb-audio: Add registration quirk for JBL Quantum 600 usb: cdns3: Fixed incorrect gadget state usb: gadget: f_hid: added GET_IDLE and SET_IDLE handlers usb: gadget: f_hid: fixed NULL pointer dereference usb: gadget: f_hid: idle uses the highest byte for duration usb: otg-fsm: Fix hrtimer list corruption clk: fix leak on devm_clk_bulk_get_all() unwind scripts/tracing: fix the bug that can't parse raw_trace_func tracing / histogram: Give calculation hist_fields a size optee: Clear stale cache entries during initialization tee: add tee_shm_alloc_kernel_buf() optee: Fix memory leak when failing to register shm pages tpm_ftpm_tee: Free and unregister TEE shared memory during kexec staging: rtl8723bs: Fix a resource leak in sd_int_dpc staging: rtl8712: get rid of flush_scheduled_work media: rtl28xxu: fix zero-length control request pipe: increase minimum default pipe size to 2 pages ext4: fix potential htree corruption when growing large_dir directories serial: tegra: Only print FIFO error message when an error occurs serial: 8250_mtk: fix uart corruption issue when rx power off serial: 8250: Mask out floating 16/32-bit bus bits MIPS: Malta: Do not byte-swap accesses to the CBUS UART serial: 8250_pci: Enumerate Elkhart Lake UARTs via dedicated driver serial: 8250_pci: Avoid irq sharing for MSI(-X) interrupts. timers: Move clearing of base::timer_running under base:: Lock pcmcia: i82092: fix a null pointer dereference bug md/raid10: properly indicate failure when ending a failed write request KVM: x86: accept userspace interrupt only if no event is injected KVM: Do not leak memory for duplicate debugfs directories KVM: x86/mmu: Fix per-cpu counter corruption on 32-bit builds arm64: vdso: Avoid ISB after reading from cntvct_el0 soc: ixp4xx: fix printing resources spi: meson-spicc: fix memory leak in meson_spicc_remove soc: ixp4xx/qmgr: fix invalid __iomem access perf/x86/amd: Don't touch the AMD64_EVENTSEL_HOSTONLY bit inside the guest bpf, selftests: Adjust few selftest result_unpriv outcomes
[Kernel-packages] [Bug 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
Hello TimK., or anyone else affected, Accepted zfs-linux into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.8.3-1ubuntu12.13 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: zfs-linux (Ubuntu Focal) Status: Confirmed => Fix Committed -- 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/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Committed Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941796] [NEW] Focal update: v5.4.139 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.139 upstream stable release
from git://git.kernel.org/
btrfs: delete duplicated words + other fixes in comments
btrfs: do not commit logs and transactions during link and rename operations
btrfs: fix race causing unnecessary inode logging during link and rename
btrfs: fix lost inode on log replay after mix of fsync, rename and inode
eviction
regulator: rt5033: Fix n_voltages settings for BUCK and LDO
spi: stm32h7: fix full duplex irq handler handling
ASoC: tlv320aic31xx: fix reversed bclk/wclk master bits
r8152: Fix potential PM refcount imbalance
qed: fix possible unpaired spin_{un}lock_bh in _qed_mcp_cmd_and_union()
net: Fix zero-copy head len calculation.
nvme: fix nvme_setup_command metadata trace event
ACPI: fix NULL pointer dereference
Revert "Bluetooth: Shutdown controller after workqueues are flushed or
cancelled"
firmware: arm_scmi: Ensure drivers provide a probe function
firmware: arm_scmi: Add delayed response status check
bpf: Inherit expanded/patched seen count from old aux data
bpf: Do not mark insn as seen under speculative path verification
bpf: Fix leakage under speculation on mispredicted branches
bpf: Test_verifier, add alu32 bounds tracking tests
bpf, selftests: Add a verifier test for assigning 32bit reg states to 64bit ones
bpf, selftests: Adjust few selftest outcomes wrt unreachable code
spi: mediatek: Fix fifo transfer
Linux 5.4.139
UBUNTU: upstream stable to v5.4.139
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ v5.4.139 upstream stable release
+ from git://git.kernel.org/
-v5.4.139 upstream stable release
-from git://git.kernel.org/
+ btrfs: delete duplicated words + other fixes in comments
+ btrfs: do not commit logs and transactions during link and rename operations
+ btrfs: fix race causing unnecessary inode logging during link and rename
+ btrfs: fix lost inode on log replay after mix of fsync, rename and inode
eviction
+ regulator: rt5033: Fix n_voltages settings for BUCK and LDO
+ spi: stm32h7: fix full duplex irq handler handling
+ ASoC: tlv320aic31xx: fix reversed bclk/wclk master bits
+ r8152: Fix potential PM refcount imbalance
+ qed: fix possible unpaired spin_{un}lock_bh in _qed_mcp_cmd_and_union()
+ net: Fix zero-copy head len calculation.
+ nvme: fix nvme_setup_command metadata trace event
+ ACPI: fix NULL pointer dereference
+ Revert "Bluetooth: Shutdown controller after workqueues are flushed or
cancelled"
+ firmware: arm_scmi: Ensure drivers provide a probe function
+ firmware: arm_scmi: Add delayed response status check
+ bpf: Inherit expanded/patched seen count from old aux data
+ bpf: Do not mark insn as seen under speculative path verification
+ bpf: Fix leakage under speculation on mispredicted branches
+ bpf: Test_verifier, add alu32 bounds tracking tests
+ bpf, selftests: Add a verifier test for assigning 32bit
[Kernel-packages] [Bug 1941793] [NEW] Ubuntu linux-base is missing /boot/vmlinu[xz]-* match
Public bug reported: Please merge https://salsa.debian.org/kernel-team/linux- base/-/commit/1ed6758e3c3f4ee21a8988d2cd83637ede095892 into Ubuntu's linux-base package. It allows recognizing custom kernels (as often needed for embedded scenarios) that are uncompressed, thus prefixed vmlinux-. See also https://github.com/siemens/meta-iot2050/issues/161 for the background. ** Affects: linux-base (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1941793 Title: Ubuntu linux-base is missing /boot/vmlinu[xz]-* match Status in linux-base package in Ubuntu: New Bug description: Please merge https://salsa.debian.org/kernel-team/linux- base/-/commit/1ed6758e3c3f4ee21a8988d2cd83637ede095892 into Ubuntu's linux-base package. It allows recognizing custom kernels (as often needed for embedded scenarios) that are uncompressed, thus prefixed vmlinux-. See also https://github.com/siemens/meta-iot2050/issues/161 for the background. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1941793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941789] Re: Impish update: v5.13.13 upstream stable release
** Changed in: linux (Ubuntu Impish) Status: Confirmed => Fix Committed ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.13.13 upstream stable release + from git://git.kernel.org/ -v5.13.13 upstream stable release -from git://git.kernel.org/ + mtd: cfi_cmdset_0002: fix crash when erasing/writing AMD cards + io_uring: Use WRITE_ONCE() when writing to sq_flags + USB: core: Avoid WARNings for 0-length descriptor requests + USB: core: Fix incorrect pipe calculation in do_proc_control() + dmaengine: xilinx_dma: Fix read-after-free bug when terminating transfers + dmaengine: usb-dmac: Fix PM reference leak in usb_dmac_probe() + spi: spi-mux: Add module info needed for autoloading + net: xfrm: Fix end of loop tests for list_for_each_entry + ARM: dts: am43x-epos-evm: Reduce i2c0 bus speed for tps65218 + dmaengine: of-dma: router_xlate to return -EPROBE_DEFER if controller is not yet available + scsi: pm80xx: Fix TMF task completion race condition + scsi: megaraid_mm: Fix end of loop tests for list_for_each_entry() + scsi: scsi_dh_rdac: Avoid crash during rdac_bus_attach() + scsi: core: Avoid printing an error if target_alloc() returns -ENXIO + scsi: core: Fix capacity set to zero after offlinining device + drm/amdgpu: fix the doorbell missing when in CGPG issue for renoir. + qede: fix crash in rmmod qede while automatic debug collection + ARM: dts: nomadik: Fix up interrupt controller node names + net: usb: pegasus: Check the return value of get_geristers() and friends; + net: usb: lan78xx: don't modify phy_device state concurrently + perf/x86: Fix out of bound MSR access + spi: cadence-quadspi: Fix check condition for DTR ops + drm/amd/display: Fix Dynamic bpp issue with 8K30 with Navi 1X + drm/amd/display: workaround for hard hang on HPD on native DP + kyber: make trace_block_rq call consistent with documentation + mtd: rawnand: Add a check in of_get_nand_secure_regions() + arm64: dts: qcom: c630: fix correct powerdown pin for WSA881x + arm64: dts: qcom: msm8992-bullhead: Remove PSCI + arm64: dts: qcom: msm8992-bullhead: Fix cont_splash_mem mapping + iommu: Check if group is NULL before remove device + cpufreq: arm_scmi: Fix error path when allocation failed + arm64: dts: qcom: msm8994-angler: Disable cont_splash_mem + arm64: dts: qcom: sdm845-oneplus: fix reserved-mem + mt76: fix enum type mismatch + mtd: rawnand: Fix probe failure due to of_get_nand_secure_regions() + soc: fsl: qe: convert QE interrupt controller to platform_device + cpufreq: armada-37xx: forbid cpufreq for 1.2 GHz variant + dccp: add do-while-0 stubs for dccp_pr_debug macros + virtio: Protect vqs list access + vhost-vdpa: Fix integer overflow in vhost_vdpa_process_iotlb_update() + bus: ti-sysc: Fix error handling for sysc_check_active_timer() + vhost: Fix the calculation in vhost_overflow() + vdpa_sim: Fix return value check for vdpa_alloc_device() + vp_vdpa: Fix return value check for vdpa_alloc_device() + vDPA/ifcvf: Fix return value check for vdpa_alloc_device() + vdpa/mlx5: Avoid destroying MR on empty iotlb + vdpa/mlx5: Fix queue type selection logic + drm/mediatek: Add AAL output size configuration + drm/mediatek: Add component_del in OVL and COLOR remove function + bpf: Clear zext_dst of dead insns + bnxt: don't lock the tx queue from napi poll + bnxt: disable napi before canceling DIM + bnxt: make sure xmit_more + errors does not miss doorbells + bnxt: count Tx drops + soc: fsl: qe: fix static checker warning + net: 6pack: fix slab-out-of-bounds in decode_data + ptp_pch: Restore dependency on PCI + bnxt_en: Disable aRFS if running on 212 firmware + bnxt_en: Add missing DMA memory barriers + vrf: Reset skb conntrack connection on VRF rcv + virtio-net: use NETIF_F_GRO_HW instead of NETIF_F_LRO + mac80211: fix locking in ieee80211_restart_work() + net: qlcnic: add missed unlock in qlcnic_83xx_flash_read32 + ixgbe, xsk: clean up the resources in ixgbe_xsk_pool_enable error path + sch_cake: fix srchost/dsthost hashing mode + net: mdio-mux: Don't ignore memory allocation errors + net: mdio-mux: Handle
[Kernel-packages] [Bug 1941789] [NEW] Impish update: v5.13.13 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.13.13 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: Confirmed ** Affects: linux (Ubuntu Impish) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: Confirmed ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941789 Title: Impish update: v5.13.13 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.13.13 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941789/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917616] Re: vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal
Found on xenial/linux-oracle/4.15.0-1080.88~16.04.1
--
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/1917616
Title:
vmx test from ubuntu_kvm_unit_tests failed on Bionic/Focal
Status in ubuntu-kernel-tests:
Triaged
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
Appearing in bionic 5.4.0-67.75~18.04.1 affecting lowlatency and hwe
flavors.
2538. 02/25 00:10:11 DEBUG| utils:0153| [stdout] Unhandled exception 13 #GP
at ip 004071a3
2539. 02/25 00:10:11 DEBUG| utils:0153| [stdout] error_code=
rflags=00010006 cs=0008
2540. 02/25 00:10:11 DEBUG| utils:0153| [stdout] rax=0078
rcx=0809 rdx= rbx=0009
2541. 02/25 00:10:11 DEBUG| utils:0153| [stdout] rbp=0047efdf
rsi=0042568d rdi=0042568d
2542. 02/25 00:10:11 DEBUG| utils:0153| [stdout] r8=000a
r9=03f8 r10=000d r11=
2543. 02/25 00:10:11 DEBUG| utils:0153| [stdout] r12=
r13= r14=00403dcc r15=
2544. 02/25 00:10:11 DEBUG| utils:0153| [stdout] cr0=80010031
cr2=e000 cr3=00477000 cr4=2020
2545. 02/25 00:10:11 DEBUG| utils:0153| [stdout] cr8=0007
2546. 02/25 00:10:11 DEBUG| utils:0153| [stdout] STACK: @4071a3 40170b 4004dd
2547. 02/25 00:10:11 DEBUG| utils:0153| [stdout] FAIL vmx
2548. 02/25 00:10:11 ERROR| test:0414| Exception escaping from test:
2549. Traceback (most recent call last):
2550. File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
2551. _call_test_function(self.execute, *p_args, **p_dargs)
2552. File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
2553. return func(*args, **dargs)
2554. File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
2555. postprocess_profiled_run, args, dargs)
2556. File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
2557. self.run_once(*args, **dargs)
2558. File
"/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py",
line 80, in run_once
2559. raise error.TestError("Test failed for {}".format(test_name))
2560. TestError: Test failed for vmx
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1917616/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
Also on: xenial/linux-oracle/4.15.0-1080.88~16.04.1
--
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/1932966
Title:
kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
Status in ubuntu-kernel-tests:
Confirmed
Status in linux-kvm package in Ubuntu:
Confirmed
Status in linux-kvm source package in Bionic:
Confirmed
Bug description:
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
18:27:11 DEBUG| [stderr] emulation failure
18:27:11 DEBUG| [stderr] RAX=000a RBX=e000
RCX=03fd RDX=03f8
18:27:11 DEBUG| [stderr] RSI=00419991 RDI=00419991
RBP=0051b440 RSP=0051b420
18:27:11 DEBUG| [stderr] R8 =000a R9 =03f8
R10=000d R11=
18:27:11 DEBUG| [stderr] R12=e000 R13=
R14=d000 R15=
18:27:11 DEBUG| [stderr] RIP=00400a0c RFL=00010006 [-P-] CPL=0
II=0 A20=1 SMM=0 HLT=0
18:27:11 DEBUG| [stderr] ES =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] CS =0008 00a09b00 DPL=0
CS64 [-RA]
18:27:11 DEBUG| [stderr] SS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] DS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] FS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] GS =0010 0051a4d0 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] LDT= 8200 DPL=0 LDT
18:27:11 DEBUG| [stderr] TR =0080 0041207a 8b00 DPL=0
TSS64-busy
18:27:11 DEBUG| [stderr] GDT= 0041100a 106f
18:27:11 DEBUG| [stderr] IDT= 0041 0fff
18:27:11 DEBUG| [stderr] CR0=80010011 CR2=
CR3=01007000 CR4=0220
18:27:11 DEBUG| [stderr] DR0= DR1=
DR2= DR3=
18:27:11 DEBUG| [stderr] DR6=0ff0 DR7=0400
18:27:11 DEBUG| [stderr] EFER=0500
18:27:11 DEBUG| [stderr] Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66
0f 6f 45 e0 <0f> 11 03 48 89 de 48 8d 7d e0 e8 f8 f9 ff ff 0f b6 f8 be a1 8f 41
00 b8 00 00 00 00 e8 05
18:28:40 DEBUG| [stderr] qemu-system-x86_64: terminating on signal 15 from
pid 13634 (timeout)
18:28:40 DEBUG| [stdout] FAIL emulator (timeout; duration=90s)
[...]
TestError: Test failed for emulator
18:28:40 ERROR| child process failed
18:28:40 DEBUG| Traceback (most recent call last):
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/parallel.py", line 25,
in fork_start
18:28:40 DEBUG| l()
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/job.py", line 505, in
18:28:40 DEBUG| l = lambda: test.runtest(self, url, tag, args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/test.py", line 125, in
runtest
18:28:40 DEBUG| job.sysinfo.log_after_each_iteration)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
913, in runtest
18:28:40 DEBUG| mytest._exec(args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
411, in _exec
18:28:40 DEBUG| _call_test_function(self.execute, *p_args, **p_dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
823, in _call_test_function
18:28:40 DEBUG| return func(*args, **dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
291, in execute
18:28:40 DEBUG| postprocess_profiled_run, args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
212, in _call_run_once
18:28:40 DEBUG| self.run_once(*args, **dargs)
18:28:40 DEBUG| File
"/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py",
line 82, in run_once
18:28:40 DEBUG| raise error.TestError("Test failed for
{}".format(test_name))
18:28:40 DEBUG| TestError: Test failed for emulator
18:28:41 INFO | ERROR ubuntu_kvm_unit_tests.emulator
ubuntu_kvm_unit_tests.emulator timestamp=1624040921localtime=Jun 18
18:28:41 Test failed for emulator
18:28:41 INFO | END ERROR ubuntu_kvm_unit_tests.emulator
ubuntu_kvm_unit_tests.emulator timestamp=1624040921localtime=Jun 18
18:28:41
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1932966/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 1941657] Re: Server boot failure after adding checks for ACPI IRQ override
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu Hirsute)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1941657
Title:
Server boot failure after adding checks for ACPI IRQ override
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Bug description:
SRU Justification:
Impact:
The commit 0ec4e55e9f57 ("ACPI: resources: Add checks for ACPI IRQ
override") introduces regression on some platforms, at least it makes
the UART can't get correct irq setting on two different platforms, and
it makes the kernel can't bootup on these two platforms.
discussion regarding the regression:
https://bugzilla.kernel.org/show_bug.cgi?id=213031#c32
Fix: Revert "ACPI: resources: Add checks for ACPI IRQ override"
Risk: Reverting this patch will keep LP#1909814 ("Keyboard not working")
unfixed.
https://launchpad.net/bugs/1909814
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941657/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940261] Re: ubuntu_seccomp 11-basic-basic_errors failure on X/oracle
Found on: bionic/linux-azure-4.15/4.15.0-1122.135 ** Tags added: azure bionic hinted sru-20210816 -- 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/1940261 Title: ubuntu_seccomp 11-basic-basic_errors failure on X/oracle Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-oracle package in Ubuntu: New Status in linux source package in Xenial: Incomplete Status in linux-oracle source package in Xenial: New Status in linux source package in Bionic: Incomplete Status in linux-oracle source package in Bionic: New Bug description: Xenial/Oracle 4.15.0-1079.87~16.04.1 fails 11-basic-basic_errors test from ubuntu_seccomp on all Oracle cloud instances: batch name: 11-basic-basic_errors test mode: c test type: basic Test 11-basic-basic_errors%%001-1 result: FAILURE 11-basic-basic_errors rc=255 Base kernel bionic/linux-oracle/4.15.0-1079.87 is OK. Previous cycle (xenial/linux-oracle/4.15.0-1077.85~16.04.1) is OK, so this looks like regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1940261/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941773] Re: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver
** 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/1941773 Title: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver Status in linux package in Ubuntu: Confirmed Bug description: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (13 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941773] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1941773/+attachment/5520940/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941773 Title: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver Status in linux package in Ubuntu: Incomplete Bug description: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (13 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941773] Re: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver
apport information ** Tags added: apport-collected hirsute ** Description changed: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu65.1 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: KDE + DistroRelease: Ubuntu 21.04 + InstallationDate: Installed on 2021-08-12 (13 days ago) + InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) + Package: linux (not installed) + Tags: hirsute + Uname: Linux 5.13.8-051308-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1941773/+attachment/5520939/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941773 Title: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver Status in linux package in Ubuntu: Incomplete Bug description: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (13 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941785] [NEW] ec2-hibinit-agent: Add support for IMDSv2
Public bug reported:
[Impact]
Amazon has requested support for IMDSv2 support in ec2-hibinit-agent.
[Fix]
Backport a portion of https://github.com/aws/amazon-ec2-hibinit-
agent.git commit 9d9bca5c61fa9256289e68c88bd3747af2f62e28 ("Add IMDSv2
support")
[Test Case]
Initiate hibernation in an AWS AMI configured for hibernation.
Test an AMI not configured for hibernation.
[Where problems could occur]
Hibernation may stop functioning.
** Affects: ec2-hibinit-agent (Ubuntu)
Importance: Undecided
Status: New
** Affects: ec2-hibinit-agent (Ubuntu Impish)
Importance: Undecided
Status: New
** Package changed: linux (Ubuntu) => ec2-hibinit-agent (Ubuntu)
** Also affects: ec2-hibinit-agent (Ubuntu Impish)
Importance: Undecided
Status: New
** Description changed:
[Impact]
- Current ec2 hibernation init agents do not have support for IMDSv2.
+ Amazon has requested support for IMDSv2 support in ec2-hibinit-agent.
[Fix]
Backport a portion of https://github.com/aws/amazon-ec2-hibinit-
agent.git commit 9d9bca5c61fa9256289e68c88bd3747af2f62e28 ("Add IMDSv2
support")
[Test Case]
Initiate hibernation in an AWS AMI configured for hibernation.
Test an AMI not configured for hibernation.
[Where problems could occur]
Hibernation may stop functioning.
--
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/1941785
Title:
ec2-hibinit-agent: Add support for IMDSv2
Status in ec2-hibinit-agent package in Ubuntu:
New
Status in ec2-hibinit-agent source package in Impish:
New
Bug description:
[Impact]
Amazon has requested support for IMDSv2 support in ec2-hibinit-agent.
[Fix]
Backport a portion of https://github.com/aws/amazon-ec2-hibinit-
agent.git commit 9d9bca5c61fa9256289e68c88bd3747af2f62e28 ("Add IMDSv2
support")
[Test Case]
Initiate hibernation in an AWS AMI configured for hibernation.
Test an AMI not configured for hibernation.
[Where problems could occur]
Hibernation may stop functioning.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1941785/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929923] Comment bridged from LTC Bugzilla
--- Comment From boris.m...@de.ibm.com 2021-08-26 13:23 EDT--- Problem could not be reproduced by Canonical. Further detailed information requested by Canonical was not provided to them since May. In the meantime, the new point release Ubuntu Server LTS 20.04.3 is available. This means that 20.04.2 which the bug was opened against, has become obsolete. Therefore, closing / rejecting the bug. Changing Status:->REJECTED (UNREPRODUCIBLE) -- 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/1929923 Title: [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic - rq_qos_wake_function Status in Ubuntu on IBM z Systems: Invalid Status in linux package in Ubuntu: Invalid Bug description: ---Problem Description--- kernel panic rq_qos_wake_function ---uname output--- Linux version 5.4.0-71-generic Machine Type = s390x ---Debugger--- A debugger is not configured Stack trace output: May 15 20:21:04 data1 kernel: Call Trace: May 15 20:21:04 data1 kernel: ([<00234091e670>] 0x234091e670) May 15 20:21:04 data1 kernel: [<003e10047e3a>] rq_qos_wake_function+0x8a/0xa0 May 15 20:21:04 data1 kernel: [<003e0fbec482>] __wake_up_common+0xa2/0x1b0 May 15 20:21:04 data1 kernel: [<003e0fbec984>] __wake_up_common_lock+0x94/0xe0 May 15 20:21:04 data1 kernel: [<003e0fbec9fa>] __wake_up+0x2a/0x40 May 15 20:21:04 data1 kernel: [<003e1005ee70>] wbt_done+0x90/0xe0 May 15 20:21:04 data1 kernel: [<003e10047f42>] __rq_qos_done+0x42/0x60 May 15 20:21:04 data1 kernel: [<003e10033cb0>] blk_mq_free_request+0xe0/0x140 May 15 20:21:04 data1 kernel: [<003e101d46f0>] dm_softirq_done+0x140/0x230 May 15 20:21:04 data1 kernel: [<003e100326c0>] blk_done_softirq+0xc0/0xe0 May 15 20:21:04 data1 kernel: [<003e103fc084>] __do_softirq+0x104/0x360 May 15 20:21:04 data1 kernel: [<003e0fb9da1e>] irq_exit+0x9e/0xc0 May 15 20:21:04 data1 kernel: [<003e0fb28ae8>] do_IRQ+0x78/0xb0 May 15 20:21:04 data1 kernel: [<003e103fb588>] ext_int_handler+0x130/0x134 May 15 20:21:04 data1 kernel: [<003e101d4416>] dm_mq_queue_rq+0x36/0x1d0 May 15 20:21:04 data1 kernel: Last Breaking-Event-Address: May 15 20:21:04 data1 kernel: [<003e0fbce75e>] wake_up_process+0xe/0x20 May 15 20:21:04 data1 kernel: Kernel panic - not syncing: Fatal exception in interrupt Oops output: no System Dump Info: The system was configured to capture a dump, however a dump was not produced. -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941773] 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 1941773 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/1941773 Title: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver Status in linux package in Ubuntu: Incomplete Bug description: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941773] [NEW] kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver
Public bug reported: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot of kernel panic info" https://bugs.launchpad.net/bugs/1941773/+attachment/5520916/+files/image0.jpeg ** Description changed: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 + kubuntu 21.04 + laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. -- 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/1941773 Title: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver Status in linux package in Ubuntu: New Bug description: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
** Tags added: sru-20210816 -- 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/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Confirmed Status in linux source package in Hirsute: Confirmed Bug description: Testing failed on focal/linux 5.4.0-44.48: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/l/linux/20200812_171444_31971@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/arm64/l/linux/20200812_210509_145fd@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/ppc64el/l/linux/20200812_165855_1dabd@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200812_153600_9c7cb@/log.gz psock_snd.sh output: 16:28:30 DEBUG| [stdout] # selftests: net: psock_snd.sh 16:28:31 DEBUG| [stdout] # dgram 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # dgram bind 16:28:31 DEBUG| [stdout] # tx: 128 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw bind 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw qdisc bypass 16:28:31 DEBUG| [stdout] # tx: 142 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vlan 16:28:31 DEBUG| [stdout] # tx: 146 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw vnet hdr 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off 16:28:31 DEBUG| [stdout] # tx: 152 16:28:31 DEBUG| [stdout] # rx: 142 16:28:31 DEBUG| [stdout] # rx: 100 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw csum_off with bad offset (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:31 DEBUG| [stdout] # raw min size 16:28:31 DEBUG| [stdout] # tx: 42 16:28:31 DEBUG| [stdout] # rx: 0 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size 16:28:31 DEBUG| [stdout] # tx: 1514 16:28:31 DEBUG| [stdout] # rx: 1472 16:28:31 DEBUG| [stdout] # OK 16:28:31 DEBUG| [stdout] # 16:28:31 DEBUG| [stdout] # raw mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:31 DEBUG| [stdout] # raw vlan mtu size + 1 (fails) 16:28:31 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # dgram mtu size 16:28:32 DEBUG| [stdout] # tx: 1500 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # dgram mtu size + 1 (fails) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Message too long 16:28:32 DEBUG| [stdout] # raw truncate hlen (fails: does not arrive) 16:28:32 DEBUG| [stdout] # tx: 14 16:28:32 DEBUG| [stdout] # ./psock_snd: recv: Resource temporarily unavailable 16:28:32 DEBUG| [stdout] # raw truncate hlen - 1 (fails: EINVAL) 16:28:32 DEBUG| [stdout] # ./psock_snd: write: Invalid argument 16:28:32 DEBUG| [stdout] # raw gso min size 16:28:32 DEBUG| [stdout] # tx: 1525 16:28:32 DEBUG| [stdout] # rx: 1473 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] # raw gso min size - 1 (fails) 16:28:32 DEBUG| [stdout] # tx: 1524 16:28:32 DEBUG| [stdout] # rx: 1472 16:28:32 DEBUG| [stdout] # OK 16:28:32 DEBUG| [stdout] # 16:28:32 DEBUG| [stdout] not ok 22 selftests: net: psock_snd.sh # exit=1 This failure is similar to bug 1884234, however, this test didn't fail on ADT with focal/linux before 5.4.0-44.48. To manage
[Kernel-packages] [Bug 1929923] Re: [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic - rq_qos_wake_function
Updating status to 'Invalid' due to inactivity. ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-z-systems Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929923 Title: [UBUNTU 20.04] LPAR becomes unresponsive after the Kernel panic - rq_qos_wake_function Status in Ubuntu on IBM z Systems: Invalid Status in linux package in Ubuntu: Invalid Bug description: ---Problem Description--- kernel panic rq_qos_wake_function ---uname output--- Linux version 5.4.0-71-generic Machine Type = s390x ---Debugger--- A debugger is not configured Stack trace output: May 15 20:21:04 data1 kernel: Call Trace: May 15 20:21:04 data1 kernel: ([<00234091e670>] 0x234091e670) May 15 20:21:04 data1 kernel: [<003e10047e3a>] rq_qos_wake_function+0x8a/0xa0 May 15 20:21:04 data1 kernel: [<003e0fbec482>] __wake_up_common+0xa2/0x1b0 May 15 20:21:04 data1 kernel: [<003e0fbec984>] __wake_up_common_lock+0x94/0xe0 May 15 20:21:04 data1 kernel: [<003e0fbec9fa>] __wake_up+0x2a/0x40 May 15 20:21:04 data1 kernel: [<003e1005ee70>] wbt_done+0x90/0xe0 May 15 20:21:04 data1 kernel: [<003e10047f42>] __rq_qos_done+0x42/0x60 May 15 20:21:04 data1 kernel: [<003e10033cb0>] blk_mq_free_request+0xe0/0x140 May 15 20:21:04 data1 kernel: [<003e101d46f0>] dm_softirq_done+0x140/0x230 May 15 20:21:04 data1 kernel: [<003e100326c0>] blk_done_softirq+0xc0/0xe0 May 15 20:21:04 data1 kernel: [<003e103fc084>] __do_softirq+0x104/0x360 May 15 20:21:04 data1 kernel: [<003e0fb9da1e>] irq_exit+0x9e/0xc0 May 15 20:21:04 data1 kernel: [<003e0fb28ae8>] do_IRQ+0x78/0xb0 May 15 20:21:04 data1 kernel: [<003e103fb588>] ext_int_handler+0x130/0x134 May 15 20:21:04 data1 kernel: [<003e101d4416>] dm_mq_queue_rq+0x36/0x1d0 May 15 20:21:04 data1 kernel: Last Breaking-Event-Address: May 15 20:21:04 data1 kernel: [<003e0fbce75e>] wake_up_process+0xe/0x20 May 15 20:21:04 data1 kernel: Kernel panic - not syncing: Fatal exception in interrupt Oops output: no System Dump Info: The system was configured to capture a dump, however a dump was not produced. -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1929923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
@Hui That kernel works! Was this a change not merged into sofproject as of yet? Thank you for all your hard work by the way! -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786575] Re: Dell XPS 15 9570 - Thermal Shutdown Event & Annoying Full-Speed Fan Spin Up
Thermald in bionic is relatively ancient. One may see better results with newer LTS versions of Ubuntu, such as focal. If this is still and issue perhaps upgrading to Focal 21.04 is worth trying. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1786575 Title: Dell XPS 15 9570 - Thermal Shutdown Event & Annoying Full-Speed Fan Spin Up Status in thermald package in Ubuntu: Incomplete Bug description: Main Problems: - Incorrect performance throttling results in Thermal Shutdown Event (~100C on CPU) as reported in BIOS log - System fan during system idle powers at full speed for 1 second every minute or so (could also be GPU fan) Environment: Dell BIOS: 1.3.0 (Also present in 1.2.0, 1.1.3) CPU: Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz Operating Systems: Ubuntu 18.04.1 LTS Thermald Version: 1.7 Ubuntu Thermald Package: 1.7.0-5ubuntu1 Kernel: 4.17.14-041714-generic (Also present with 4.15.0-29, 4.15.0-30, 4.17.11-041711) Intel Microcode: 3.20180425.1~ubuntu0.18.04.2 Nvidia Driver: 396.51-0ubuntu0~gpu18.04.1 TLP Package: 1.1-2ubuntu1 I've documented this issue on the thermald Github page with thermald debug logs and configuration: https://github.com/intel/thermal_daemon/issues/161 Basically, I've attempted to set the temperature for B0D4 to as low as 85000 and while the debug log seems to indicate the trip has be made, the CPU scailing isn't working to keep the CPU from thermal shutdown. Disabling Turbo Boost prevents shutdown of the system. I'd expect thermald to performance throttle the CPU correctly to prevent it from a thermal overheat event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1786575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941756] [NEW] touchpad not working and not found in /proc/bus/input/devices
Public bug reported: I installed Ubuntu 20.04.3 on a Fujitsu Lifeboob U7510, and the touchpad s not working: it is also not present in the file /proc/bus/input/devices, and seems not to be detected by the system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 15:56:01 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "output of cat /proc/bus/input/devices" https://bugs.launchpad.net/bugs/1941756/+attachment/5520900/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1941756 Title: touchpad not working and not found in /proc/bus/input/devices Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: I installed Ubuntu 20.04.3 on a Fujitsu Lifeboob U7510, and the touchpad s not working: it is also not present in the file /proc/bus/input/devices, and seems not to be detected by the system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 15:56:01 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1941756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786575] Re: Dell XPS 15 9570 - Thermal Shutdown Event & Annoying Full-Speed Fan Spin Up
** Changed in: thermald (Ubuntu) Importance: Undecided => Medium ** Changed in: thermald (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: thermald (Ubuntu) Status: New => Confirmed ** Changed in: thermald (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1786575 Title: Dell XPS 15 9570 - Thermal Shutdown Event & Annoying Full-Speed Fan Spin Up Status in thermald package in Ubuntu: Incomplete Bug description: Main Problems: - Incorrect performance throttling results in Thermal Shutdown Event (~100C on CPU) as reported in BIOS log - System fan during system idle powers at full speed for 1 second every minute or so (could also be GPU fan) Environment: Dell BIOS: 1.3.0 (Also present in 1.2.0, 1.1.3) CPU: Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz Operating Systems: Ubuntu 18.04.1 LTS Thermald Version: 1.7 Ubuntu Thermald Package: 1.7.0-5ubuntu1 Kernel: 4.17.14-041714-generic (Also present with 4.15.0-29, 4.15.0-30, 4.17.11-041711) Intel Microcode: 3.20180425.1~ubuntu0.18.04.2 Nvidia Driver: 396.51-0ubuntu0~gpu18.04.1 TLP Package: 1.1-2ubuntu1 I've documented this issue on the thermald Github page with thermald debug logs and configuration: https://github.com/intel/thermal_daemon/issues/161 Basically, I've attempted to set the temperature for B0D4 to as low as 85000 and while the debug log seems to indicate the trip has be made, the CPU scailing isn't working to keep the CPU from thermal shutdown. Disabling Turbo Boost prevents shutdown of the system. I'd expect thermald to performance throttle the CPU correctly to prevent it from a thermal overheat event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1786575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803881] Re: thermal thermal_zone4: failed to read out thermal zone (-61)
The issue is in the iwlwifi wireless driver, specifically the error -61
(ENODATA) is being reported by the call to iwl_mvm_tzone_get_temp() in
in drivers/net/wireless/intel/iwlwif/mvm/tt.c
Looking at this failure case it could be because there is a mismatch
between the expected firmware blob and the actual installed (nor not
installed) firmware blob for this driver.
Can you try installing or re-installing the linux-firmware package to
see if this helps. You may need to re-boot the machine for this to be
activated.
I suggest using:
sudo apt-get install --reinstall linux-firmware
Let us know if this allows one to read cat /sys/class/thermal/thermal_zone4/type
iwlwifi_1
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1803881
Title:
thermal thermal_zone4: failed to read out thermal zone (-61)
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
Thermald can't read zone4. It's making my fan go crazy, this issue
seems to be a bit more controlled in 18.10.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
sudo apt-cache policy thermald
thermald:
Installed: 1.7.0-5ubuntu1
Candidate: 1.7.0-5ubuntu1
Version table:
*** 1.7.0-5ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
cat /sys/class/thermal/thermal_zone4/type
iwlwifi
find /sys/class/thermal/thermal_zone4/ -type f -print -exec cat {} \;
/sys/class/thermal/thermal_zone4/uevent
/sys/class/thermal/thermal_zone4/trip_point_5_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_3_type
passive
/sys/class/thermal/thermal_zone4/trip_point_4_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_2_type
passive
/sys/class/thermal/thermal_zone4/power/runtime_active_time
0
/sys/class/thermal/thermal_zone4/power/runtime_active_kids
0
/sys/class/thermal/thermal_zone4/power/runtime_usage
0
/sys/class/thermal/thermal_zone4/power/runtime_status
unsupported
/sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms
cat: /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms:
Input/output error
/sys/class/thermal/thermal_zone4/power/async
disabled
/sys/class/thermal/thermal_zone4/power/runtime_suspended_time
0
/sys/class/thermal/thermal_zone4/power/runtime_enabled
disabled
/sys/class/thermal/thermal_zone4/power/control
auto
/sys/class/thermal/thermal_zone4/available_policies
power_allocator user_space bang_bang fair_share step_wise
/sys/class/thermal/thermal_zone4/policy
step_wise
/sys/class/thermal/thermal_zone4/trip_point_3_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_1_type
passive
/sys/class/thermal/thermal_zone4/k_d
cat: /sys/class/thermal/thermal_zone4/k_d: Input/output error
/sys/class/thermal/thermal_zone4/sustainable_power
cat: /sys/class/thermal/thermal_zone4/sustainable_power: Input/output error
/sys/class/thermal/thermal_zone4/type
iwlwifi
/sys/class/thermal/thermal_zone4/trip_point_7_type
passive
/sys/class/thermal/thermal_zone4/offset
cat: /sys/class/thermal/thermal_zone4/offset: Input/output error
/sys/class/thermal/thermal_zone4/slope
cat: /sys/class/thermal/thermal_zone4/slope: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_2_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_0_type
passive
/sys/class/thermal/thermal_zone4/trip_point_6_type
passive
/sys/class/thermal/thermal_zone4/emul_temp
cat: /sys/class/thermal/thermal_zone4/emul_temp: Permission denied
/sys/class/thermal/thermal_zone4/k_po
cat: /sys/class/thermal/thermal_zone4/k_po: Input/output error
/sys/class/thermal/thermal_zone4/integral_cutoff
cat: /sys/class/thermal/thermal_zone4/integral_cutoff: Input/output error
/sys/class/thermal/thermal_zone4/k_i
cat: /sys/class/thermal/thermal_zone4/k_i: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_1_temp
-32768000
/sys/class/thermal/thermal_zone4/k_pu
cat: /sys/class/thermal/thermal_zone4/k_pu: Input/output error
/sys/class/thermal/thermal_zone4/temp
46000
/sys/class/thermal/thermal_zone4/trip_point_7_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_5_type
passive
/sys/class/thermal/thermal_zone4/trip_point_0_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_6_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_4_type
passive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803881/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :
[Kernel-packages] [Bug 1941751] 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/1941751 Title: Ubuntu 2.04.2 LTS fails to wake from suspend Status in linux package in Ubuntu: Confirmed Bug description: Also reported here with additional details about my situation. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005 I filed this report to transmit the apport information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kordosky 1948 F pulseaudio /dev/snd/controlC1: kordosky 1948 F pulseaudio /dev/snd/controlC0: kordosky 1948 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 09:27:42 2021 HibernationDevice: RESUME=UUID=ad19f24f-7458-4bf8-a5ab-1088541c41c3 InstallationDate: Installed on 2018-05-24 (1189 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Precision 7520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=04bed92c-de31-4810-acb7-ecdf37bb73d4 ro nouveau.blacklist=1 quiet splash resume=UUID=ad19f24f-7458-4bf8-a5ab-1088541c41c3 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-02-05 (202 days ago) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.2 dmi.board.name: 0P1FNM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.2:bd03/09/2018:svnDellInc.:pnPrecision7520:pvr:rvnDellInc.:rn0P1FNM:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7520 dmi.product.sku: 07B0 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-12-07T13:16:30.671689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941751] [NEW] Ubuntu 2.04.2 LTS fails to wake from suspend
Public bug reported: Also reported here with additional details about my situation. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005 I filed this report to transmit the apport information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kordosky 1948 F pulseaudio /dev/snd/controlC1: kordosky 1948 F pulseaudio /dev/snd/controlC0: kordosky 1948 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 09:27:42 2021 HibernationDevice: RESUME=UUID=ad19f24f-7458-4bf8-a5ab-1088541c41c3 InstallationDate: Installed on 2018-05-24 (1189 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Precision 7520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=04bed92c-de31-4810-acb7-ecdf37bb73d4 ro nouveau.blacklist=1 quiet splash resume=UUID=ad19f24f-7458-4bf8-a5ab-1088541c41c3 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-02-05 (202 days ago) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.2 dmi.board.name: 0P1FNM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.2:bd03/09/2018:svnDellInc.:pnPrecision7520:pvr:rvnDellInc.:rn0P1FNM:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7520 dmi.product.sku: 07B0 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2018-12-07T13:16:30.671689 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1941751 Title: Ubuntu 2.04.2 LTS fails to wake from suspend Status in linux package in Ubuntu: New Bug description: Also reported here with additional details about my situation. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005 I filed this report to transmit the apport information. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kordosky 1948 F pulseaudio /dev/snd/controlC1: kordosky 1948 F pulseaudio /dev/snd/controlC0: kordosky 1948 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 09:27:42 2021 HibernationDevice: RESUME=UUID=ad19f24f-7458-4bf8-a5ab-1088541c41c3 InstallationDate: Installed on 2018-05-24 (1189 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Dell Inc. Precision 7520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=04bed92c-de31-4810-acb7-ecdf37bb73d4 ro nouveau.blacklist=1 quiet splash resume=UUID=ad19f24f-7458-4bf8-a5ab-1088541c41c3 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-02-05 (202 days ago) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.2 dmi.board.name: 0P1FNM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.2:bd03/09/2018:svnDellInc.:pnPrecision7520:pvr:rvnDellInc.:rn0P1FNM:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7520 dmi.product.sku: 07B0 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can
[Kernel-packages] [Bug 1803881] Re: thermal thermal_zone4: failed to read out thermal zone (-61)
** Changed in: thermald (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1803881
Title:
thermal thermal_zone4: failed to read out thermal zone (-61)
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
Thermald can't read zone4. It's making my fan go crazy, this issue
seems to be a bit more controlled in 18.10.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
sudo apt-cache policy thermald
thermald:
Installed: 1.7.0-5ubuntu1
Candidate: 1.7.0-5ubuntu1
Version table:
*** 1.7.0-5ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
cat /sys/class/thermal/thermal_zone4/type
iwlwifi
find /sys/class/thermal/thermal_zone4/ -type f -print -exec cat {} \;
/sys/class/thermal/thermal_zone4/uevent
/sys/class/thermal/thermal_zone4/trip_point_5_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_3_type
passive
/sys/class/thermal/thermal_zone4/trip_point_4_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_2_type
passive
/sys/class/thermal/thermal_zone4/power/runtime_active_time
0
/sys/class/thermal/thermal_zone4/power/runtime_active_kids
0
/sys/class/thermal/thermal_zone4/power/runtime_usage
0
/sys/class/thermal/thermal_zone4/power/runtime_status
unsupported
/sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms
cat: /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms:
Input/output error
/sys/class/thermal/thermal_zone4/power/async
disabled
/sys/class/thermal/thermal_zone4/power/runtime_suspended_time
0
/sys/class/thermal/thermal_zone4/power/runtime_enabled
disabled
/sys/class/thermal/thermal_zone4/power/control
auto
/sys/class/thermal/thermal_zone4/available_policies
power_allocator user_space bang_bang fair_share step_wise
/sys/class/thermal/thermal_zone4/policy
step_wise
/sys/class/thermal/thermal_zone4/trip_point_3_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_1_type
passive
/sys/class/thermal/thermal_zone4/k_d
cat: /sys/class/thermal/thermal_zone4/k_d: Input/output error
/sys/class/thermal/thermal_zone4/sustainable_power
cat: /sys/class/thermal/thermal_zone4/sustainable_power: Input/output error
/sys/class/thermal/thermal_zone4/type
iwlwifi
/sys/class/thermal/thermal_zone4/trip_point_7_type
passive
/sys/class/thermal/thermal_zone4/offset
cat: /sys/class/thermal/thermal_zone4/offset: Input/output error
/sys/class/thermal/thermal_zone4/slope
cat: /sys/class/thermal/thermal_zone4/slope: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_2_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_0_type
passive
/sys/class/thermal/thermal_zone4/trip_point_6_type
passive
/sys/class/thermal/thermal_zone4/emul_temp
cat: /sys/class/thermal/thermal_zone4/emul_temp: Permission denied
/sys/class/thermal/thermal_zone4/k_po
cat: /sys/class/thermal/thermal_zone4/k_po: Input/output error
/sys/class/thermal/thermal_zone4/integral_cutoff
cat: /sys/class/thermal/thermal_zone4/integral_cutoff: Input/output error
/sys/class/thermal/thermal_zone4/k_i
cat: /sys/class/thermal/thermal_zone4/k_i: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_1_temp
-32768000
/sys/class/thermal/thermal_zone4/k_pu
cat: /sys/class/thermal/thermal_zone4/k_pu: Input/output error
/sys/class/thermal/thermal_zone4/temp
46000
/sys/class/thermal/thermal_zone4/trip_point_7_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_5_type
passive
/sys/class/thermal/thermal_zone4/trip_point_0_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_6_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_4_type
passive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803881/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520872/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901266] Re: system sluggish, thermal keep frequency at 400MHz
Thermald 2.3-4 has been updated recently to 2.4.3-1ubuntu2 with some relevant upstream fixes. Do you mind verifying if this now addresses the issue. The updates contain the following fixes: thermald (2.4.3-1ubuntu2) hirsute * Support Jasper Lake. (LP: #1940629) - 0014-Added-Jasper-Lake-CPU-model.patch thermald (2.4.3-1ubuntu1) hirsute * Pull in bug fixes between 2.4.3 and 2.4.6 (LP: #1931565) - Disable legacy rapl cdev when rapl-mmio is in use This will prevent PL1/PL2 power limit from MSR based rapl, which may not be the correct one. - Delete all trips from zones before psvt install Initially zones has all the trips from sysfs, which may have wrong settings. Instead of deleting only for matched psvt zones, delete or all zones. In this way only zones which are in PSVT will be present. - Check for alternate names for B0D4 device B0D4 can be named as TCPU or B0D4. So search for both names if failed to find one. - Fix error for condition names The current code caps the max name as the last condition name, which is "Power_Slider". So any condition more than 56 will be printing error, with "Power_Slider" as condition name. For example for condition = 57: Unsupported condition 57 (Power_slider) - Set a very high RAPL MSR PL1 with --adaptive After upgrading Dell Latitude 5420, again noticed performance degradation. The PPCC power limit for MSR RAPL PL1 is reduced to 15W. Even though we disable MSR RAPL with --adaptive option, it is not getting disabled. So MSR RAPL limits still playing role. To fix that set a very high MSR RAPL PL1 limit so that it never causes throttling. All throttling with --adaptive option is done using RAPL-MMIO. - Special case for default PSVT When there are no adaptive tables and only one default PSVT table is present with just one entry with MAX type. Add one additional entry as done for non default case. - Increase power limit for disabled RAPL-MMIO Increase 100W to 200W as some desktop platform already have limit more than 100W. - Use Adaptive PPCC limits for RAPL MMIO Set the correct device name as RAPL-MSR so that RAPL-MMIO can also set the correct default power limits. If this fixes the issue please let us know. ** Summary changed: - system slagish, thermal keep frequency at 400MHz + system sluggish, thermal keep frequency at 400MHz ** Changed in: thermald (Ubuntu) Importance: Undecided => Medium ** Changed in: thermald (Ubuntu) Status: New => Incomplete ** Changed in: thermald (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1901266 Title: system sluggish, thermal keep frequency at 400MHz Status in thermald package in Ubuntu: Incomplete Bug description: This morning I upgraded to 20.10 from 20.04 The system was quite slow although I have a fast machine. My virtual windows 10 on virtualbox became unusable. When I tried to have the virtual machine open, I could not participate properly in a zoom call (I could still hear the people but they said that my voice was very choppy) On 20.04 I was super-happy with the speed and I could have as many apps running as I want. Based on google I started looking at % journalctl --follow and this shows quite a few errors but not repeating often enough to explain it. Then I googled some more and found that /boot/efi was writing and reading. Then I googled some more and thought I had trouble with gnome. So I reset it to default % dconf reset -f /org/gnome/ and disabled the extensions. This made things slightly better but by far not acceptable. After lots of searching I checked the frequency of the CPUs and it was at the minimum 400Hz (as shown by i7z and also other tools). I tried setting the governor with cpufreqctl and similar methods but this did not change anything. I then found an old bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769236 and tried % sudo systemctl stop thermald this seems to work. After a few seconds the frequency shown in i7z goes to ~4500 MHz and the virtual machine seems to work fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thermald 2.3-4 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 01:39:40 2020 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+merion+X66 InstallationDate: Installed on
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520873/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941044] Re: ax210 wifi adapter disappears with upgrade to linux-firmware 1.187.16
* ddaffc5e iwlwifi: add new FWs from core60-51 release (for bug 1933415) | WHENCE| 26 ++ | iwlwifi-Qu-b0-hr-b0-63.ucode | Bin 0 -> 1334856 bytes | iwlwifi-Qu-b0-jf-b0-63.ucode | Bin 0 -> 1252748 bytes | iwlwifi-Qu-c0-hr-b0-63.ucode | Bin 0 -> 1334872 bytes | iwlwifi-Qu-c0-jf-b0-63.ucode | Bin 0 -> 1252764 bytes | iwlwifi-QuZ-a0-hr-b0-63.ucode | Bin 0 -> 1334804 bytes | iwlwifi-QuZ-a0-jf-b0-63.ucode | Bin 0 -> 1252744 bytes | iwlwifi-cc-a0-63.ucode| Bin 0 -> 1298688 bytes | iwlwifi-ty-a0-gf-a0-63.ucode | Bin 0 -> 1460012 bytes | iwlwifi-ty-a0-gf-a0.pnvm | Bin 0 -> 27456 bytes | 10 files changed, 26 insertions(+) -- 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/1941044 Title: ax210 wifi adapter disappears with upgrade to linux-firmware 1.187.16 Status in linux-firmware package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 20.04.3 LTS $ uname -r 5.11.0-27-generic $ apt-cache policy linux-firmware linux-firmware: Installed: 1.187.16 $ ip a 1: lo 2: enp0s31f6 Device: Lenovo T14 Gen 2 w/ Intel AX210 WiFi [8086:2725] WiFi adapter disappears from network manager and > ip a following update to > linux-firmware 1.187.16 and a restart Able to confirm this package is the problem as the issue can be reversed by downgrading to > linux-firmware 1.187.15 Our organisation has had at least one other identical device experience the same issue before > apt-mark hold linux-firmware was pushed out. Happy to supply any other information or logs on request. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.16 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logansymons 7485 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 25 18:10:49 2021 Dependencies: IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 04f2:b6d0 Chicony Electronics Co., Ltd Integrated Camera Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20W0005AAU PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-27-generic root=/dev/mapper/my_vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.16 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET41W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0005AAU dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET41W(1.41):bd07/08/2021:br1.41:efr1.8:svnLENOVO:pn20W0005AAU:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005AAU:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0005AAU dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1941044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941044] Re: ax210 wifi adapter disappears with upgrade to linux-firmware 1.187.16
processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 140 model name : 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz stepping: 1 09:00.0 Network controller [0280]: Intel Corporation Device [8086:2725] (rev 1a) Subsystem: Intel Corporation Device [8086:0020] [ 14.331678] iwlwifi :09:00.0: enabling device ( -> 0002) [ 14.376763] iwlwifi :09:00.0: api flags index 2 larger than supported by driver [ 14.376783] iwlwifi :09:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 93.8.63.28 [ 14.377057] iwlwifi :09:00.0: loaded firmware version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm [ 14.435158] iwlwifi :09:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 [ 14.607931] iwlwifi :09:00.0: loaded PNVM version 0x324cd670 [ 14.711389] iwlwifi :09:00.0: Timeout waiting for PNVM load! [ 14.711400] iwlwifi :09:00.0: Failed to start RT ucode: -110 [ 14.711409] iwlwifi :09:00.0: iwl_trans_send_cmd bad state = 1 [ 14.915356] iwlwifi :09:00.0: firmware didn't ACK the reset - continue anyway [ 14.927676] iwlwifi :09:00.0: Failed to run INIT ucode: -110 -- 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/1941044 Title: ax210 wifi adapter disappears with upgrade to linux-firmware 1.187.16 Status in linux-firmware package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 20.04.3 LTS $ uname -r 5.11.0-27-generic $ apt-cache policy linux-firmware linux-firmware: Installed: 1.187.16 $ ip a 1: lo 2: enp0s31f6 Device: Lenovo T14 Gen 2 w/ Intel AX210 WiFi [8086:2725] WiFi adapter disappears from network manager and > ip a following update to > linux-firmware 1.187.16 and a restart Able to confirm this package is the problem as the issue can be reversed by downgrading to > linux-firmware 1.187.15 Our organisation has had at least one other identical device experience the same issue before > apt-mark hold linux-firmware was pushed out. Happy to supply any other information or logs on request. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.16 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logansymons 7485 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 25 18:10:49 2021 Dependencies: IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 04f2:b6d0 Chicony Electronics Co., Ltd Integrated Camera Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20W0005AAU PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-27-generic root=/dev/mapper/my_vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.16 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET41W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0005AAU dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET41W(1.41):bd07/08/2021:br1.41:efr1.8:svnLENOVO:pn20W0005AAU:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005AAU:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0005AAU dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1941044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520871/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940485] Re: thermald often limits CPU frequency while on AC
Two recent thermald releases may have now addressed this issue: thermald (2.4.3-1ubuntu2) hirsute; urgency=medium * Support Jasper Lake. (LP: #1940629) - 0014-Added-Jasper-Lake-CPU-model.patch thermald (2.4.3-1ubuntu1) hirsute; urgency=medium - Disable legacy rapl cdev when rapl-mmio is in use This will prevent PL1/PL2 power limit from MSR based rapl, which may not be the correct one. - Delete all trips from zones before psvt install Initially zones has all the trips from sysfs, which may have wrong settings. Instead of deleting only for matched psvt zones, delete or all zones. In this way only zones which are in PSVT will be present. - Check for alternate names for B0D4 device B0D4 can be named as TCPU or B0D4. So search for both names if failed to find one. - Fix error for condition names The current code caps the max name as the last condition name, which is "Power_Slider". So any condition more than 56 will be printing error, with "Power_Slider" as condition name. For example for condition = 57: Unsupported condition 57 (Power_slider) - Set a very high RAPL MSR PL1 with --adaptive After upgrading Dell Latitude 5420, again noticed performance degradation. The PPCC power limit for MSR RAPL PL1 is reduced to 15W. Even though we disable MSR RAPL with --adaptive option, it is not getting disabled. So MSR RAPL limits still playing role. To fix that set a very high MSR RAPL PL1 limit so that it never causes throttling. All throttling with --adaptive option is done using RAPL-MMIO. - Special case for default PSVT When there are no adaptive tables and only one default PSVT table is present with just one entry with MAX type. Add one additional entry as done for non default case. - Increase power limit for disabled RAPL-MMIO Increase 100W to 200W as some desktop platform already have limit more than 100W. - Use Adaptive PPCC limits for RAPL MMIO Set the correct device name as RAPL-MSR so that RAPL-MMIO can also set the correct default power limits. Do you mind re-testing and letting us know if this now fixes the issue? ** Changed in: thermald (Ubuntu) Status: New => In Progress ** Changed in: thermald (Ubuntu) Status: In Progress => Incomplete ** Changed in: thermald (Ubuntu) Importance: Undecided => Medium ** Changed in: thermald (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940485 Title: thermald often limits CPU frequency while on AC Status in thermald package in Ubuntu: Incomplete Bug description: I'm not entirely sure if this is a thermald issue, but on my laptop (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC, is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo frequency. Restarting thermald (with `systemctl restart thermald`) will let the system scale up to the expected ~3.8GHz boost frequency. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thermald 2.4.6-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:24:56 2021 InstallationDate: Installed on 2021-06-26 (53 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "lspci" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520870/+files/lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913186] Re: Backport the adaptive engine from v2.4.1 upstream
** Changed in: thermald (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1913186 Title: Backport the adaptive engine from v2.4.1 upstream Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Released Status in thermald source package in Groovy: Fix Released Bug description: Impact: DPTM provides an adaptive power policy that allows for improved integration between the platform and the OS. Firmware can provide a set of complex conditions to the OS, and an OS agent (in this case thermal_daemon) is responsible for evaluating them, potentially making use of information that is easily available to the OS and not the firmware. The agent evaluates each set of conditions in turn, and once the first evaluates completely it triggers a set of actions. Fix: Backport the adaptive engine (and all its dependencies) from upstream v.2.4.1 Regression potential: Both Focal and Groovy backports are substantial (Focal in particular is pretty large), so there's definitely a regression potential. On the other hand, the entire patchset is a clean backport, taking no shortcut or trying to adapt any patch, but rather picking up all the necessary dependencies to make the entire stack apply cleanly. -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] 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/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Wang Just tried the kernel you posted and it is working. Thanks Michael -- 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1880012] Re: ASUS UX533F overheating and fan off with Ubuntu 20.04 LTS
I suspect the fixes may have landed with 1.9.1-1ubuntu0.5, I'll mark this as fixed released for now. If the issue occurs again, please feel free to re-open the bug. ** Changed in: thermald (Ubuntu) Status: New => Fix Released ** Changed in: thermald (Ubuntu) Importance: Undecided => Medium ** Changed in: thermald (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1880012 Title: ASUS UX533F overheating and fan off with Ubuntu 20.04 LTS Status in thermald package in Ubuntu: Fix Released Bug description: After installing Ubuntu 20.04 LTS, my laptop's temperature goes fairly high without intensive CPU activity. The fan(s) remain **off** under heavy CPU load and the temperature goes very high. I don't suspect a material failure since I didn't notice such overheating issues anymore with my previous Ubuntu (19.04) (after using sudo prime-select intel). **Config** - ASUS UX533FN - BIOS version 304 (up-to-date) - Kernel: 5.4.0-31-generic (same issue with 5.4.0-29) - NVIDIA GeForce MX150 (with latest NVIDIA driver) Low CPU load Without running anything special, I get the following figures with `sensors` command: ... pch_cannonlake-virtual-0 Adapter: Virtual device temp1:+49.0°C BAT0-acpi-0 Adapter: ACPI interface in0: 15.60 V asus-isa- Adapter: ISA adapter cpu_fan:0 RPM coretemp-isa- Adapter: ISA adapter Package id 0: +50.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+49.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+48.0°C (high = +100.0°C, crit = +100.0°C) Core 2:+48.0°C (high = +100.0°C, crit = +100.0°C) Core 3:+50.0°C (high = +100.0°C, crit = +100.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+49.0°C (crit = +103.0°C) These figures are a too high in my opinion for low CPU load with a room temperature of 20°C. But here come's worse: Heavy CPU load == When the CPU is under load, for instance when running `sysbench cpu run` in loop, the temperature increases to 90°C, and no fan is triggered! To get a repeatable CPU load test, I run while true; do echo "One more time..." && sysbench cpu run; done Here are the figures I get in this case (from `sensors` command): ... pch_cannonlake-virtual-0 Adapter: Virtual device temp1:+65.0°C BAT0-acpi-0 Adapter: ACPI interface in0: 15.60 V asus-isa- Adapter: ISA adapter cpu_fan:0 RPM coretemp-isa- Adapter: ISA adapter Package id 0: +88.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+88.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+70.0°C (high = +100.0°C, crit = +100.0°C) Core 2:+72.0°C (high = +100.0°C, crit = +100.0°C) Core 3:+72.0°C (high = +100.0°C, crit = +100.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+86.0°C (crit = +103.0°C) Note 1: The temperature in the room for this test is 20°C. Note 2: I got almost the same issue one year ago with Ubuntu 19.04 and used the sudo prime-select intel workaround. What I already tried - installing the latest NVIDIA driver, including selecting `intel` with `prime-select` ameliorated the situation but didn't tackle the issue - running `sensors-detect` (YES to all questions) resulted in `coretemp` to be added to `/etc/modules` - running `pwmconfig` didn't work: /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sylvain1710 F pulseaudio /dev/snd/pcmC0D0p: sylvain1710 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 20:58:45 2020 InstallationDate: Installed on 2020-05-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX533FN_UX533FN ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic
[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend
I've attached the syslog. The suspend starts at 07:39 with a lid closure. The resume starts at 08:36. This was presumably after I had to hard power-cycle it because you can see the power-off. Various key- presses and short presses on the power button just prior to 08:36 produced nothing in the log. In fact, I had to hard reboot thee times to get the system back. It hung after picking the kernel version in grub twice. One with a black screen. The other with a Dell screen and with Ubuntu underneath and a rotating progress meter. I don't see that screen on a normal boot. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+attachment/5520868/+files/logfile.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 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-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933938] Re: Missing CNVi firmware for Intel AX211/AX201 on ADL
** Tags added: originate-from-1941066 -- 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/1933938 Title: Missing CNVi firmware for Intel AX211/AX201 on ADL Status in HWE Next: New Status in intel: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Incomplete Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: Incomplete Status in linux-oem-5.13 source package in Focal: Incomplete Status in linux source package in Impish: Incomplete Status in linux-firmware source package in Impish: Incomplete Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.sfi * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: ??? To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "gpu-manager.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520869/+files/gpu-manager.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520867/+files/dmesg -- 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/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520863/+files/syslog -- 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/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520864/+files/Xorg.0.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "/var/log/apt/history" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520865/+files/history.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] Re: After grub menu system not start, i muststart the System over the recovery mode.
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+attachment/5520866/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941749] [NEW] After grub menu system not start, i muststart the System over the recovery mode.
Public bug reported: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1601:bd10/26/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug hirsute ** Attachment added: "boot.log" https://bugs.launchpad.net/bugs/1941749/+attachment/5520843/+files/boot.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941749 Title: After grub menu system not start, i muststart the System over the recovery mode. Status in linux package in Ubuntu: Confirmed Bug description: After the last apt upgrade, will the System not start. In the recovery mode start the system but the GUI run only in the X11 session. And my second screen will never be detect. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: patrick2333 F pulseaudio /dev/snd/controlC2: patrick2333 F pulseaudio /dev/snd/controlC0: patrick2333 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Aug 26 14:59:54 2021 InstallationDate: Installed on 2019-03-08 (901 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190124) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=de_AT:de TERM=xterm-256color PATH=(custom, no user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=f477375b-c0ec-4383-9340-ed5d17ce2df7 ro recovery nomodeset dis_ucode_ldr PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1601 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows
A recent update of thermald 1.9.1-1ubuntu0.5 in focal contains many of the upstream thermald patches that have been backported to support more modern laptops. The Intel fixes included are as follows: - Disable legacy rapl cdev when rapl-mmio is in use This will prevent PL1/PL2 power limit from MSR based rapl, which may not be the correct one. - Delete all trips from zones before psvt install Initially zones has all the trips from sysfs, which may have wrong settings. Instead of deleting only for matched psvt zones, delete or all zones. In this way only zones which are in PSVT will be present. - Check for alternate names for B0D4 device B0D4 can be named as TCPU or B0D4. So search for both names if failed to find one. - Fix error for condition names The current code caps the max name as the last condition name, which is "Power_Slider". So any condition more than 56 will be printing error, with "Power_Slider" as condition name. For example for condition = 57: Unsupported condition 57 (Power_slider) - Set a very high RAPL MSR PL1 with --adaptive After upgrading Dell Latitude 5420, again noticed performance degradation. The PPCC power limit for MSR RAPL PL1 is reduced to 15W. Even though we disable MSR RAPL with --adaptive option, it is not getting disabled. So MSR RAPL limits still playing role. To fix that set a very high MSR RAPL PL1 limit so that it never causes throttling. All throttling with --adaptive option is done using RAPL-MMIO. - Special case for default PSVT When there are no adaptive tables and only one default PSVT table is present with just one entry with MAX type. Add one additional entry as done for non default case. - Increase power limit for disabled RAPL-MMIO Increase 100W to 200W as some desktop platform already have limit more than 100W. - Use Adaptive PPCC limits for RAPL MMIO Set the correct device name as RAPL-MSR so that RAPL-MMIO can also set the correct default power limits. Can folk check if this helps with the issue? ** Changed in: thermald (Ubuntu) Importance: Undecided => High ** Changed in: thermald (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: thermald (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1763144 Title: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows Status in linux package in Ubuntu: Invalid Status in thermald package in Ubuntu: Incomplete Bug description: A ThinkPad T480s under windows has a power limit of 44W, both short and long term, with a thermal maximum of about 93C or so. Under Linux, the power limits are 44W and 15W (short) or so, and the thermal limit is 80C, causing a significant performance loss. Looking at MSR and MCHBAR values, we can see that the values are correctly at 44W in the MSR, but the MCHBAR is set to a lower value: $ sudo rdmsr -a 0x610 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 42816000dd8160 $ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0 0x0042816000dd8078 Setting the MCHBAR to the same value as the MSR register solves the problem. At some point intel-rapl seems to reduce overall frequency to 600 MHz, though. The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24 -d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting in performance comparative to Windows. Most of the analysis is based on the analysis in https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/ This applies to all bionic kernels I have tested so far, including Ubuntu 4.15.0-13.14-generic 4.15.10 --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: jak5881 F...m pulseaudio /dev/snd/controlC2: jak5881 F pulseaudio /dev/snd/controlC1: jak5881 F pulseaudio /dev/snd/controlC0: jak5881 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-03-14 (28 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 RelatedPackageVersions: linux-restricted-modules-4.15.0-13-generic N/A linux-backports-modules-4.15.0-13-generic N/A linux-firmware 1.173 Tags: bionic
[Kernel-packages] [Bug 1769236] Re: CPU frequency stuck at minimum value
@Gerald, did thermald 1.9.1-1ubuntu0.5 help resolve the issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1769236 Title: CPU frequency stuck at minimum value Status in linux package in Ubuntu: Confirmed Status in thermald package in Ubuntu: Incomplete Bug description: I installed the Kubuntu variant of Ubuntu 18.04 on a new HP Spectre 13 laptop. Performance is poor. The CPU (an i7-8550U) is running at 400MHz, and never speeds up, even when running some of the Phoronix Test Suite benchmarks. I can use cpupower to switch to the "performance" cpufreq governor, but cannot change the frequency with either governor. Here is the output of some experiments I ran while Phoronix's c-ray test was running. __ gjditchf@copperplate:/var/log$ cat /proc/cpuinfo | grep MHz cpu MHz : 400.008 cpu MHz : 400.002 cpu MHz : 400.002 cpu MHz : 400.003 cpu MHz : 400.005 cpu MHz : 400.003 cpu MHz : 400.001 cpu MHz : 400.004 gjditchf@copperplate:/var/log$ cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: Cannot determine or is not supported. hardware limits: 400 MHz - 4.00 GHz available cpufreq governors: performance powersave current policy: frequency should be within 400 MHz and 1.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency: Unable to call hardware current CPU frequency: 400 MHz (asserted by call to kernel) boost state support: Supported: yes Active: yes gjditchf@copperplate:/var/log$ sudo cpupower frequency-set -f 1.60GHz Setting cpu: 0 Error setting new values. Common errors: - Do you have proper administration rights? (super-user?) - Is the governor you requested available and modprobed? - Trying to set an invalid policy? - Trying to set a specific frequency, but userspace governor is not available, for example because of hardware which cannot be set to a specific frequency or because the userspace governor isn't loaded? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 12:57:25 2018 InstallationDate: Installed on 2018-04-28 (6 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gjditchf 1190 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-28 (10 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:564e Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:564f Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre Laptop 13-af0xx Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=ab54f00a-7dd6-4d75-a664-682f777c841c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin monotone plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/13/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83A2 dmi.board.vendor: HP dmi.board.version: 55.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.06:bd10/13/2017:svnHP:pnHPSpectreLaptop13-af0xx:pvrType1ProductConfigId:rvnHP:rn83A2:rvr55.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre Laptop 13-af0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage
[Kernel-packages] [Bug 1931565] Re: pull in latest thermald bug fixes into thermald
** Changed in: thermald (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1931565 Title: pull in latest thermald bug fixes into thermald Status in thermald package in Ubuntu: In Progress Status in thermald source package in Focal: Fix Released Status in thermald source package in Hirsute: Fix Released Bug description: == SRU Justification [ HIRSUTE ] == The upstream thermald 2.4.6 has been released with some more bug fixes that are pertinent to H/W available in older releases such as Hirsute. These fix a variety of issues found on H/W in the field and such as over-throttling, handling alternate ACPI object names for B0D4, handling trip zones which may have wrong settings and disabling the legacy rapl cdev when rapl-mmio is available. == The fixes == Pull in these fixes: From 2.4.6: commit 273a53a11da2a7302ad7a5bc7e3bf04f221ce4e2 Author: Srinivas Pandruvada Date: Mon Jun 7 16:47:47 2021 -0700 Use Adaptive PPCC limits for RAPL MMIO Set the correct device name as RAPL-MSR so that RAPL-MMIO can also set the correct default power limits. commit 2dd67300448fa4a2aa8f3e00ee5b604c73a1f7d9 Author: Srinivas Pandruvada Date: Mon Jun 7 16:45:14 2021 -0700 Increase power limit for disabled RAPL-MMIO Increase 100W to 200W as some desktop platform already have limit more than 100W. commit 3de1004a49d0d157573bbdc1097b2fbed056879f Author: Srinivas Pandruvada Date: Sun Jun 6 19:19:15 2021 -0700 Special case for default PSVT When there are no adaptive tables and only one default PSVT table is present with just one entry with MAX type. Add one additional entry as done for non default case. From 2.4.5: commit 301a89284e9d74a9a1f8315c1673a548dcacda8c Author: Srinivas Pandruvada Date: Sat May 29 10:50:44 2021 -0700 Set a very high RAPL MSR PL1 with --adaptive After upgrading Dell Latitude 5420, again noticed performance degradation. The PPCC power limit for MSR RAPL PL1 is reduced to 15W. Even though we disable MSR RAPL with --adaptive option, it is not getting disabled. So MSR RAPL limits still playing role. To fix that set a very high MSR RAPL PL1 limit so that it never causes throttling. All throttling with --adaptive option is done using RAPL-MMIO. From 2.4.4: commit ea4491971059259e46daad10ae850d3d530b02f2 Author: Srinivas Pandruvada Date: Thu Mar 11 10:06:15 2021 -0800 Fix error for condition names The current code caps the max name as the last condition name, which is "Power_Slider". So any condition more than 56 will be printing error, with "Power_Slider" as condition name. For example for condition = 57: Unsupported condition 57 (Power_slider) This is confusing during debug, so print "UNKNOWN" for condition name 56. commit 9115f2fb0b296a22a62908f2718ca873af2a452f Author: Srinivas Pandruvada Date: Tue Mar 9 16:36:13 2021 -0800 This is confusing during debug, so print "UNKNOWN" for condition name 56. commit 9115f2fb0b296a22a62908f2718ca873af2a452f Author: Srinivas Pandruvada Date: Tue Mar 9 16:36:13 2021 -0800 Check for alternate names for B0D4 device B0D4 can be named as TCPU or B0D4. So search for both names if failed to find one. commit 660ee6f1f6351e6c291c0699147231be402c2bb8 Author: Srinivas Pandruvada Date: Tue Mar 9 16:33:08 2021 -0800 Delete all trips from zones before psvt install Initially zones has all the trips from sysfs, which may have wrong settings. Instead of deleting only for matched psvt zones, delete for all zones. In this way only zones which are in PSVT will be present. commit 1ad03424f7f3d339521635f08377b323375b2747 Author: Srinivas Pandruvada Date: Tue Mar 9 11:36:27 2021 -0800 Disable legacy rapl cdev when rapl-mmio is in use Explicitly disable legacy rapl based on MSR interface when rapl-mmio is in use. This will prevent PL1/PL2 power limit from MSR based rapl, which may not be the correct one. commit 45832e16290fec7353513b1ce03533b73b18f0c6 Author: Colin Ian King Date: Thu Mar 18 11:22:38 2021 + Fix spelling mistakes found using codespell There are a handful of spelling mistakes in comments and literal strings found by codespell. Fix these. Signed-off-by: Colin Ian King == Test plan == Actually this is problematic as the changes affect different H/W in different ways and testing to touch all these changes requires full CPU exercising to try and trip thermal overrun. test plan is as follows: 1. install -proposed thermald, run with debug logging enabled 2. run stress-ng --cpu 0 for a few hours
[Kernel-packages] [Bug 1936237] Re: use the upstream version for the kernel packaging
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Tags added: apport-collected -- 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/1936237 Title: use the upstream version for the kernel packaging Status in linux package in Ubuntu: Triaged Bug description: please use the upstream version for the kernel packaging. apw, sforshee, xnox: is there any way to see which upstream version the linux package is based on? doko, if you are running it? /proc/version_signature has the full upstream version doko, for general inquiries we also have: https://people.canonical.com/~kernel/info/kernel-version-map.txt though impish is missing for some reason apw, no, just looking at the package doko, with like apt-cache ... likely no apw, could you add that information to the changlog, when you're uploading? doko, i guess it would be reasonably easy to do... what is going to consume it? doko, are you interested in when it changes? just *knowing* which upstream version is used it feels like it should be in the package description for "something" or even better, a linux-libc-dev with a real upstream version in the package version we have always avoided having the third digit so we don't explode the librarian with new orig files all the time perhaps we could put somehting on that linux-libc-dev though with the upstream version in it if that would make life easier for you? documenting it in the changelog would be ok as well, assuming that you can parse that kind of information are you intending to consume it as a human, or scripted yes, or have a different binary version for every binary package built human i almost want to put a versioned provides on it then if something ever did care it could actually do something about it and what would be the package that you provide? linux-libc-dev-mainline (= foo) perhaps apw: TBH I wonder whether the "avoid new orig files" is still the right tradeoff. The size of a linux orig tarball looks rather less significant now than it did when we started this practice cjwatson, we would provide a new .orig for every single SRU cycle in the normal run of things, for every single kernel. so 180M for each of 82 kernels. which by my calculation is 14TB every 3 weeks? Hm yeah, I suppose ... I always forget what an absurdly enormous number of kernels you have or are you able to collesce the orig by contents? as there is more like only 4 for every cycle. No Well maybe if they're actually bitwise-identical they are bitwise identicle i assume you _arn't_ currently sharing the bits, but you might be able to? I think we are actually But I'll check after this meeting ack and thanks apw: Oh right, yeah, they get temporarily added as duplicates and then librarian-gc deduplicates them so the space usage wouldn't be an issue in the end? So it'd still be a TB a month or so, which isn't entirely insignificant Maybe better not change it until the librarian is on PS5 and we get a feel for what space usage looks like there Actually no, neither apw nor I can multiply apparently 180M * 82 is 14G not 14T ;p That makes rather more sense, I was wondering how you'd manage to generate like a sixth of the librarian's total storage size in three weeks So <1G extra per three weeks is noise and will not really be noticed from our point of view. I can't speak to whatever extra rebase work it might require of course. And of course it would presumably require some tooling changes. I do think it would be ultimately the right thing to do though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909005] Re: Ubuntu does not resume (wake up) from suspend
I have the same problem. There is no response to any key presses (no fan, as others reported) and I have to hard restart with the power button. Dell Precision 7520 Ubuntu 20.04.2 LTS Quadro M2200 GPU Nvidia driver 470.57.02 Kernel: 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux One note: I was able to fix this issue back in March of '21 by adding the following to /etc/default/grub #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" #changed by me on 3/18/21 GRUB_CMDLINE_LINUX_DEFAULT="quiet splash resume=UUID=ad19f24f-7458-4bf8-a5ab-108 8541c41c3" This fix stopped working after a kernel/driver update in July '21. Not sure which one. This doesn't work: # changed by me on 8/25/21 #GRUB_CMDLINE_LINUX="" GRUB_CMDLINE_LINUX="nouveau.blacklist=1" -- 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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Confirmed Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux- image-5.0.0-1070-oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 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-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
I have the same problem on my laptop Asus GL552VW, with i5-6300HQ GTX 960M, with NVIDIA driver 470.57 Ubuntu 21.04 My second HDMI monitor has blink screen every 30~60 seconds, and #136's solution works for me I changed the refresh rate of screen from 60Hz(default) to 74.91Hz After that, blink screen never happen again for now -- 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/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) PD: When you select a specific resolution, the second monitor "works", but it blinks, the image showed via HDMI on the second monitor blinks. So is impossible to work with it. Since all this time I was searching about this and I'm almost sure this is a problem of the GPU's Intel. But I saw this problem on askubuntu just with laptops with hybrid graphics. Always with Nvidia+Intel. (Maybe AMD+Nvidia too, but I'm not sure if they have the same problem here). WORKAROUND: I installed the 4.15 kernel, so at the moment I can work with this. Higher than 4.15 the second monitor doesn't work. Tested until 5.8 and without good results. Just with 4.15. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry:
[Kernel-packages] [Bug 1941741] Re: Bluetooth not working
** Attachment added: "dmidecode.txt" https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.13/+bug/1941741/+attachment/5520824/+files/dmidecode.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941741 Title: Bluetooth not working Status in linux-signed-oem-5.13 package in Ubuntu: New Bug description: I made a fresh install on a XPS 13 9310 with ubuntu-20.04.2.0-desktop- amd64.iso. It installed the Kernel from linux-image-5.6.0-1047-oem and upgrades to linux-image-5.10.0-1044-oem automatically. With the later kernel, WiFi and Bluetooth stopped working. There were also issues at shutdown. I then installed linux-image-5.13.0-1010-oem which solved the WiFi problem, but Bluetooth still doesn't work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-1010-oem 5.13.0-1010.11 ProcVersionSignature: Ubuntu 5.13.0-1010.11-oem 5.13.1 Uname: Linux 5.13.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 13:31:41 2021 InstallationDate: Installed on 2021-08-25 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.13 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-5.13/+bug/1941741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941741] Re: Bluetooth not working
** Attachment added: "dmesg output." https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.13/+bug/1941741/+attachment/5520823/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941741 Title: Bluetooth not working Status in linux-signed-oem-5.13 package in Ubuntu: New Bug description: I made a fresh install on a XPS 13 9310 with ubuntu-20.04.2.0-desktop- amd64.iso. It installed the Kernel from linux-image-5.6.0-1047-oem and upgrades to linux-image-5.10.0-1044-oem automatically. With the later kernel, WiFi and Bluetooth stopped working. There were also issues at shutdown. I then installed linux-image-5.13.0-1010-oem which solved the WiFi problem, but Bluetooth still doesn't work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-1010-oem 5.13.0-1010.11 ProcVersionSignature: Ubuntu 5.13.0-1010.11-oem 5.13.1 Uname: Linux 5.13.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 13:31:41 2021 InstallationDate: Installed on 2021-08-25 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.13 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-5.13/+bug/1941741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941741] [NEW] Bluetooth not working
Public bug reported: I made a fresh install on a XPS 13 9310 with ubuntu-20.04.2.0-desktop- amd64.iso. It installed the Kernel from linux-image-5.6.0-1047-oem and upgrades to linux-image-5.10.0-1044-oem automatically. With the later kernel, WiFi and Bluetooth stopped working. There were also issues at shutdown. I then installed linux-image-5.13.0-1010-oem which solved the WiFi problem, but Bluetooth still doesn't work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-1010-oem 5.13.0-1010.11 ProcVersionSignature: Ubuntu 5.13.0-1010.11-oem 5.13.1 Uname: Linux 5.13.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 13:31:41 2021 InstallationDate: Installed on 2021-08-25 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.13 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941741 Title: Bluetooth not working Status in linux-signed-oem-5.13 package in Ubuntu: New Bug description: I made a fresh install on a XPS 13 9310 with ubuntu-20.04.2.0-desktop- amd64.iso. It installed the Kernel from linux-image-5.6.0-1047-oem and upgrades to linux-image-5.10.0-1044-oem automatically. With the later kernel, WiFi and Bluetooth stopped working. There were also issues at shutdown. I then installed linux-image-5.13.0-1010-oem which solved the WiFi problem, but Bluetooth still doesn't work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-1010-oem 5.13.0-1010.11 ProcVersionSignature: Ubuntu 5.13.0-1010.11-oem 5.13.1 Uname: Linux 5.13.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 13:31:41 2021 InstallationDate: Installed on 2021-08-25 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.13 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-5.13/+bug/1941741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940972] Re: v5.13 kernel ftrace selftest fails on riscv64 unmatched
** Bug watch added: Linux Kernel Bug Tracker #214185 https://bugzilla.kernel.org/show_bug.cgi?id=214185 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=214185 Importance: Unknown Status: Unknown ** Changed in: ubuntu-kernel-tests Importance: Undecided => Medium ** Changed in: linux-riscv (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1940972 Title: v5.13 kernel ftrace selftest fails on riscv64 unmatched Status in Linux: Unknown Status in ubuntu-kernel-tests: New Status in linux-riscv package in Ubuntu: New Bug description: $ sudo make -C tools/testing/selftests TARGETS=ftrace run_tests ... # [32] ftrace - Max stack tracer [FAIL] ... Testing using 5.13.0-1002.2 the full ftrace suite takes just over 2 hours on unmatched. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1940972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941044] Re: ax210 wifi adapter disappears with upgrade to linux-firmware 1.187.16
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1941044 Title: ax210 wifi adapter disappears with upgrade to linux-firmware 1.187.16 Status in linux-firmware package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 20.04.3 LTS $ uname -r 5.11.0-27-generic $ apt-cache policy linux-firmware linux-firmware: Installed: 1.187.16 $ ip a 1: lo 2: enp0s31f6 Device: Lenovo T14 Gen 2 w/ Intel AX210 WiFi [8086:2725] WiFi adapter disappears from network manager and > ip a following update to > linux-firmware 1.187.16 and a restart Able to confirm this package is the problem as the issue can be reversed by downgrading to > linux-firmware 1.187.15 Our organisation has had at least one other identical device experience the same issue before > apt-mark hold linux-firmware was pushed out. Happy to supply any other information or logs on request. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.16 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logansymons 7485 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 25 18:10:49 2021 Dependencies: IwConfig: lono wireless extensions. enp0s31f6 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 04f2:b6d0 Chicony Electronics Co., Ltd Integrated Camera Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20W0005AAU PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-27-generic root=/dev/mapper/my_vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.16 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.41 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET41W (1.41 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0005AAU dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET41W(1.41):bd07/08/2021:br1.41:efr1.8:svnLENOVO:pn20W0005AAU:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0005AAU:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0005AAU dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1941044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936237] 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 1936237 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/1936237 Title: use the upstream version for the kernel packaging Status in linux package in Ubuntu: Incomplete Bug description: please use the upstream version for the kernel packaging. apw, sforshee, xnox: is there any way to see which upstream version the linux package is based on? doko, if you are running it? /proc/version_signature has the full upstream version doko, for general inquiries we also have: https://people.canonical.com/~kernel/info/kernel-version-map.txt though impish is missing for some reason apw, no, just looking at the package doko, with like apt-cache ... likely no apw, could you add that information to the changlog, when you're uploading? doko, i guess it would be reasonably easy to do... what is going to consume it? doko, are you interested in when it changes? just *knowing* which upstream version is used it feels like it should be in the package description for "something" or even better, a linux-libc-dev with a real upstream version in the package version we have always avoided having the third digit so we don't explode the librarian with new orig files all the time perhaps we could put somehting on that linux-libc-dev though with the upstream version in it if that would make life easier for you? documenting it in the changelog would be ok as well, assuming that you can parse that kind of information are you intending to consume it as a human, or scripted yes, or have a different binary version for every binary package built human i almost want to put a versioned provides on it then if something ever did care it could actually do something about it and what would be the package that you provide? linux-libc-dev-mainline (= foo) perhaps apw: TBH I wonder whether the "avoid new orig files" is still the right tradeoff. The size of a linux orig tarball looks rather less significant now than it did when we started this practice cjwatson, we would provide a new .orig for every single SRU cycle in the normal run of things, for every single kernel. so 180M for each of 82 kernels. which by my calculation is 14TB every 3 weeks? Hm yeah, I suppose ... I always forget what an absurdly enormous number of kernels you have or are you able to collesce the orig by contents? as there is more like only 4 for every cycle. No Well maybe if they're actually bitwise-identical they are bitwise identicle i assume you _arn't_ currently sharing the bits, but you might be able to? I think we are actually But I'll check after this meeting ack and thanks apw: Oh right, yeah, they get temporarily added as duplicates and then librarian-gc deduplicates them so the space usage wouldn't be an issue in the end? So it'd still be a TB a month or so, which isn't entirely insignificant Maybe better not change it until the librarian is on PS5 and we get a feel for what space usage looks like there Actually no, neither apw nor I can multiply apparently 180M * 82 is 14G not 14T ;p That makes rather more sense, I was wondering how you'd manage to generate like a sixth of the librarian's total storage size in three weeks So <1G extra per three weeks is noise and will not really be noticed from our point of view. I can't speak to whatever extra rebase work it might require of course. And of course it would presumably require some tooling changes. I do think it would be ultimately the right thing to do though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936237] Re: use the upstream version for the kernel packaging
no logs missing ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1936237 Title: use the upstream version for the kernel packaging Status in linux package in Ubuntu: New Bug description: please use the upstream version for the kernel packaging. apw, sforshee, xnox: is there any way to see which upstream version the linux package is based on? doko, if you are running it? /proc/version_signature has the full upstream version doko, for general inquiries we also have: https://people.canonical.com/~kernel/info/kernel-version-map.txt though impish is missing for some reason apw, no, just looking at the package doko, with like apt-cache ... likely no apw, could you add that information to the changlog, when you're uploading? doko, i guess it would be reasonably easy to do... what is going to consume it? doko, are you interested in when it changes? just *knowing* which upstream version is used it feels like it should be in the package description for "something" or even better, a linux-libc-dev with a real upstream version in the package version we have always avoided having the third digit so we don't explode the librarian with new orig files all the time perhaps we could put somehting on that linux-libc-dev though with the upstream version in it if that would make life easier for you? documenting it in the changelog would be ok as well, assuming that you can parse that kind of information are you intending to consume it as a human, or scripted yes, or have a different binary version for every binary package built human i almost want to put a versioned provides on it then if something ever did care it could actually do something about it and what would be the package that you provide? linux-libc-dev-mainline (= foo) perhaps apw: TBH I wonder whether the "avoid new orig files" is still the right tradeoff. The size of a linux orig tarball looks rather less significant now than it did when we started this practice cjwatson, we would provide a new .orig for every single SRU cycle in the normal run of things, for every single kernel. so 180M for each of 82 kernels. which by my calculation is 14TB every 3 weeks? Hm yeah, I suppose ... I always forget what an absurdly enormous number of kernels you have or are you able to collesce the orig by contents? as there is more like only 4 for every cycle. No Well maybe if they're actually bitwise-identical they are bitwise identicle i assume you _arn't_ currently sharing the bits, but you might be able to? I think we are actually But I'll check after this meeting ack and thanks apw: Oh right, yeah, they get temporarily added as duplicates and then librarian-gc deduplicates them so the space usage wouldn't be an issue in the end? So it'd still be a TB a month or so, which isn't entirely insignificant Maybe better not change it until the librarian is on PS5 and we get a feel for what space usage looks like there Actually no, neither apw nor I can multiply apparently 180M * 82 is 14G not 14T ;p That makes rather more sense, I was wondering how you'd manage to generate like a sixth of the librarian's total storage size in three weeks So <1G extra per three weeks is noise and will not really be noticed from our point of view. I can't speak to whatever extra rebase work it might require of course. And of course it would presumably require some tooling changes. I do think it would be ultimately the right thing to do though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939618] Comment bridged from LTC Bugzilla
--- Comment From fre...@de.ibm.com 2021-08-26 06:11 EDT--- Ok, I double checked the list and none of the patches needs any modifications. You can directly pick from upstream. This is the sequence: c4f762ff6b77 s390/zcrypt: Support for CCA protected key block version 2 fa226f1d81e2 s390: Replace zero-length array with flexible-array member eb3e064b8dd1 s390/zcrypt: Use scnprintf() for avoiding potential buffer 40501c70e3f0 s390/zcrypt: replace snprintf/sprintf with scnprintf 3cc7c927102d s390/ap: Remove ap device suspend and resume callbacks fcf0220abc5b s390/zcrypt: use fallthrough; 34515df25d7e s390/zcrypt: use kvmalloc instead of kmalloc for 256k alloc 41677b1d9415 s390/ap: remove power management code from ap bus and drivers bc4b295e87a8 s390/ap: introduce new ap function ap_get_qdev() 79d6c5022710 s390/zcrypt: use kzalloc 47c07bffeb32 s390/zcrypt: fix smatch warnings 74ecbef7b908 s390/zcrypt: code beautification and struct field renames 7e202acb5c43 s390/zcrypt: split ioctl function into smaller code units dc4b6ded3c17 s390/ap: rename and clarify ap state machine related stuff a303e88743f6 s390/zcrypt: provide cex4 cca sysfs attributes for cex3 c8337c47deb9 s390/ap: rework crypto config info and default domain code 0d574ad33e5b s390/zcrypt: simplify cca_findcard2 loop code 52f72feba9db s390/zcrypt: remove set_fs() invocation in zcrypt device 48175fed1dea s390/ap: remove unnecessary spin_lock_init() 32ca04bba6fd s390/zcrypt: Support for CCA APKA master keys 91ffc519c199 s390/zcrypt: introduce msg tracking in zcrypt functions 0b641cbd2444 s390/ap: split ap queue state machine state from device state 2ea2a6099ae3 s390/ap: add error response code field for ap queue devices 4f2fcccdb547 s390/ap: add card/queue deconfig state 0671cc104874 s390/sclp: Add support for SCLP AP adapter config/deconfig 5caa2af97118 s390/ap: Support AP card SCLP config and deconfig operations e0332629e33d s390/ap/zcrypt: revisit ap and zcrypt error handling 3730f5300b45 s390/zcrypt: move ap_msg param one level up the call chain 27c4f6738bdc s390/zcrypt: Introduce Failure Injection feature 4366dd725125 s390/zcrypt: fix wrong format specifications 29c2680fd2bf s390/ap: fix ap devices reference counting d39fae45c97c s390/zcrypt: return EIO when msg retry limit reached 70fac8088cfa s390/zcrypt: fix zcard and zqueue hot-unplug memleak e73a99f3287a s390/ap: Fix hanging ioctl caused by wrong msg counter -- 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/1939618 Title: EP11 cards going offline => Fix backport to U20.04LTS Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Here is the backport against current git for ubuntu 20.04. It is a zip file with a patches subdir and all the patches in there together with a series file. So just unpack it and apply with quilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1939618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
