[Kernel-packages] [Bug 1767971] Re: No such man page: kernel_lockdown.7
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: manpages (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767971 Title: No such man page: kernel_lockdown.7 Status in linux package in Ubuntu: Invalid Status in manpages package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux source package in Focal: Invalid Status in manpages source package in Focal: New Status in linux source package in Groovy: Invalid Status in manpages source package in Groovy: Won't Fix Status in linux source package in Hirsute: Invalid Status in manpages source package in Hirsute: Fix Released Status in Fedora: Unknown Bug description: When booting in secure boot mode, the Bionic kernel emits the following message: [ 52.035055] Lockdown: Loading of unsigned modules is restricted; see man kernel_lockdown.7 But there is no such man page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767971/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840488] Re: Disable Bluetooth in cloud kernels
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-oracle (Ubuntu Groovy) Status: New => Won't Fix -- 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/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Won't Fix Status in linux-aws source package in Focal: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke-5.0 source package in Focal: New Status in linux-oracle source package in Focal: New Status in linux-aws source package in Groovy: Won't Fix Status in linux-gcp source package in Groovy: Won't Fix Status in linux-gke-4.15 source package in Groovy: Won't Fix Status in linux-gke-5.0 source package in Groovy: Won't Fix Status in linux-oracle source package in Groovy: Won't Fix Status in linux-aws source package in Hirsute: New Status in linux-gcp source package in Hirsute: New Status in linux-gke-4.15 source package in Hirsute: New Status in linux-gke-5.0 source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840488] Re: Disable Bluetooth in cloud kernels
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-gke-5.0 (Ubuntu Groovy) Status: New => Won't Fix -- 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/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Won't Fix Status in linux-aws source package in Focal: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke-5.0 source package in Focal: New Status in linux-oracle source package in Focal: New Status in linux-aws source package in Groovy: Won't Fix Status in linux-gcp source package in Groovy: Won't Fix Status in linux-gke-4.15 source package in Groovy: Won't Fix Status in linux-gke-5.0 source package in Groovy: Won't Fix Status in linux-oracle source package in Groovy: Won't Fix Status in linux-aws source package in Hirsute: New Status in linux-gcp source package in Hirsute: New Status in linux-gke-4.15 source package in Hirsute: New Status in linux-gke-5.0 source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840488] Re: Disable Bluetooth in cloud kernels
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-gcp (Ubuntu Groovy) Status: New => Won't Fix -- 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/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Won't Fix Status in linux-aws source package in Focal: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke-5.0 source package in Focal: New Status in linux-oracle source package in Focal: New Status in linux-aws source package in Groovy: Won't Fix Status in linux-gcp source package in Groovy: Won't Fix Status in linux-gke-4.15 source package in Groovy: Won't Fix Status in linux-gke-5.0 source package in Groovy: Won't Fix Status in linux-oracle source package in Groovy: Won't Fix Status in linux-aws source package in Hirsute: New Status in linux-gcp source package in Hirsute: New Status in linux-gke-4.15 source package in Hirsute: New Status in linux-gke-5.0 source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840488] Re: Disable Bluetooth in cloud kernels
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-gke-4.15 (Ubuntu Groovy) Status: New => Won't Fix -- 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/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Won't Fix Status in linux-aws source package in Focal: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke-5.0 source package in Focal: New Status in linux-oracle source package in Focal: New Status in linux-aws source package in Groovy: Won't Fix Status in linux-gcp source package in Groovy: Won't Fix Status in linux-gke-4.15 source package in Groovy: Won't Fix Status in linux-gke-5.0 source package in Groovy: Won't Fix Status in linux-oracle source package in Groovy: Won't Fix Status in linux-aws source package in Hirsute: New Status in linux-gcp source package in Hirsute: New Status in linux-gke-4.15 source package in Hirsute: New Status in linux-gke-5.0 source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840488] Re: Disable Bluetooth in cloud kernels
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-aws (Ubuntu Groovy) Status: New => Won't Fix -- 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/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-gcp source package in Eoan: Won't Fix Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Won't Fix Status in linux-aws source package in Focal: New Status in linux-gcp source package in Focal: Fix Committed Status in linux-gke-5.0 source package in Focal: New Status in linux-oracle source package in Focal: New Status in linux-aws source package in Groovy: Won't Fix Status in linux-gcp source package in Groovy: Won't Fix Status in linux-gke-4.15 source package in Groovy: Won't Fix Status in linux-gke-5.0 source package in Groovy: Won't Fix Status in linux-oracle source package in Groovy: Won't Fix Status in linux-aws source package in Hirsute: New Status in linux-gcp source package in Hirsute: New Status in linux-gke-4.15 source package in Hirsute: New Status in linux-gke-5.0 source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865402] Re: Stop using get_scalar_status command in Dell AIO uart backlight driver
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1865402 Title: Stop using get_scalar_status command in Dell AIO uart backlight driver Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Fix Released Bug description: [Impact] The get_scalar_status command was provided by ODM engineer and was newly introduced to determinate whether scalar is responsible for the backlight adjustment. That guy asked the scalar vendor to add this command and the command works as expected. But there is already a command in the Dell AIO scalar UART command spec. which can do the same thing since 2015, and the newly introduced get_scalar_status command is undocumented. To prevent from introducing regression in the future and to align with what Windows uses, replace this command with get_display_mode command. [Fix] Replace get_scalar_status command with get_display_mode command. [Test] Verified on new Dell AIO platforms. [Regression Potential] Low, the command is already in the spec. since 2015. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1865402/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- 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/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: In Progress 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 Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: In Progress 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 Committed 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
[Kernel-packages] [Bug 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- 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/1887661 Title: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: In Progress 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.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.6 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.6 source package in Impish: Invalid Bug description: [Impact] The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [ OK ] vxlan4 not supported TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] vxlan4 not supported TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] geneve4 not supported TEST: IPv4 over geneve4: PMTU exceptions [SKIP] geneve4 not supported TEST: IPv6 over geneve4: PMTU exceptions [SKIP] TEST: IPv4 over geneve6: PMTU exceptions [ OK ] TEST: IPv6 over geneve6: PMTU exceptions [ OK ] TEST: IPv4 over fou4: PMTU exceptions [ OK ] TEST: IPv6 over fou4: PMTU exceptions [ OK ] TEST: IPv4 over fou6: PMTU exceptions [ OK ] TEST: IPv6 over fou6: PMTU exceptions [ OK ] TEST: IPv4 over gue4: PMTU exceptions [ OK ] TEST: IPv6 over gue4: PMTU exceptions [ OK ] TEST: IPv4 over gue6: PMTU exceptions [ OK ] TEST: IPv6 over gue6: PMTU exceptions [ OK ] TEST: vti6: PMTU exceptions [ OK ] TEST: vti4: PMTU exceptions [ OK ] TEST: vti4: default MTU assignment [ OK ] TEST: vti6: default MTU assignment [ OK ] TEST: vti4: MTU setting on link creation [ OK ] TEST: vti6: MTU setting on link creation [ OK ] TEST: vti6: MTU changes on link changes [ OK ] vxlan4 not supported TEST: ipv4: cleanup of cached exceptions [SKIP] TEST: ipv6: cleanup of cached exceptions [ OK ] TEST: ipv4: list and flush cached exceptions [ OK ] TEST: ipv6: list and flush cached exceptions [ OK ] $ echo $? 1 This is because the test script treats all non-zero return code as a failure, thus it will be marked as FAILED when some sub-test got skipped. [Fix] * ef1220a7d4bbdb selftests: pmtu.sh: use $ksft_skip for skipped return code * 2a9d3716b810a4 selftests: pmtu.sh: improve the test result processing This patchset will: 1. Use the kselftest framework skip code $ksft_skip to replace the hardcoded SKIP return code. 2. Improve the result processing, the test will be marked as PASSED if nothing goes wrong and not all the tests were skipped. These have already landed in newer releases and this test does not exist in B, thus we just need this for F/F-OEM-5.6/F-OEM-5.10/G. The first patch needs to be backported (except on F-OEM-5.10) as some test cases were not added yet. The second one can be cherry-picked. [Test] Run this test directly on a patched kernel. The skipped test will cause failure to this test. [Where problems could occur] Changes limited to testing tools, it's unlikely to cause any problem to kernel functions. [Original Bug Report] Issue found on B-5.4 oracle 5.4.0-1021.21~18.04.1 The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [ OK ] vxlan4 not supported TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] vxlan4 not supported TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] geneve4 not supported TEST: IPv4 over geneve4: PMTU exceptions[SKIP] ge
[Kernel-packages] [Bug 1905728] Re: log_check / tainted_check failed in ubuntu_boot because of warnings (Found insecure W+X mapping at address) found on F/G/H-riscv
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-riscv (Ubuntu Groovy) Status: Confirmed => Won't Fix -- 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/1905728 Title: log_check / tainted_check failed in ubuntu_boot because of warnings (Found insecure W+X mapping at address) found on F/G/H-riscv Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-riscv package in Ubuntu: New Status in linux source package in Groovy: Won't Fix Status in linux-riscv source package in Groovy: Won't Fix Bug description: Issue found on 5.8.0-10-generic riscv Message reported on boot. [ 13.483103] [ cut here ] [ 13.483711] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 13.484542] WARNING: CPU: 5 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 13.485175] Modules linked in: [ 13.485606] CPU: 5 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic #12-Ubuntu [ 13.486091] epc: ffe000208f18 ra : ffe000208f18 sp : ffe1f5bfbb30 [ 13.486471] gp : ffe001728ee0 tp : ffe1f5bf5080 t0 : ffe00173ed88 [ 13.486850] t1 : ffe00173ed20 t2 : 0001fecbe000 s0 : ffe1f5bfbb80 [ 13.487250] s1 : ffe1f5bfbe10 a0 : 0053 a1 : 0020 [ 13.487633] a2 : ffe1f5bfb870 a3 : a4 : ffe0016200f8 [ 13.488040] a5 : ffe0016200f8 a6 : 00b5 a7 : ffe0006f2806 [ 13.488421] s2 : ffdff8001000 s3 : s4 : 0004 [ 13.488800] s5 : s6 : s7 : ffe1f5bfbd20 [ 13.489322] s8 : ffdff8001000 s9 : ffe00172a148 s10: ffdff8002000 [ 13.489738] s11: ffe000c16e20 t3 : 0003cec0 t4 : 0003cec0 [ 13.490119] t5 : t6 : ffe001739462 [ 13.490406] status: 0120 badaddr: cause: 0003 [ 13.490849] ---[ end trace 607c551edff1ef12 ]--- Please find attachment for the boot dmesg log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1905728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894964] Re: Unable to build ubuntu_bpf test on Groovy 5.8 KVM kernel / F-5.8-hwe (blocking net test in ubuntu_kernel_selftests to build)
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894964 Title: Unable to build ubuntu_bpf test on Groovy 5.8 KVM kernel / F-5.8-hwe (blocking net test in ubuntu_kernel_selftests to build) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Won't Fix Bug description: Issue found on 5.8.0-1001.1 - kvm Test build failed with: Warning: Kernel ABI header at 'tools/include/uapi/linux/netlink.h' differs from latest version at 'include/uapi/linux/netlink.h' Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' In file included from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:5, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/kernel.h:8, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.h:10, from /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c:8: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c: In function ‘__func_get_name’: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:37:38: warning: nested extern declaration of ‘__compiletime_assert_0’ [-Wnested-externs] 37 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) | ^ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:16:15: note: in definition of macro ‘__compiletime_assert’ 16 | extern void prefix ## suffix(void) __compiletime_error(msg); \ | ^~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/compiler.h:37:2: note: in expansion of macro ‘_compiletime_assert’ 37 | _compiletime_assert(condition, msg, __compiletime_assert_, __COUNTER__) | ^~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:39:37: note: in expansion of macro ‘compiletime_assert’ 39 | #define BUILD_BUG_ON_MSG(cond, msg) compiletime_assert(!(cond), msg) | ^~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/include/linux/build_bug.h:50:2: note: in expansion of macro ‘BUILD_BUG_ON_MSG’ 50 | BUILD_BUG_ON_MSG(condition, "BUILD_BUG_ON failed: " #condition) | ^~~~ /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/kernel/bpf/disasm.c:20:2: note: in expansion of macro ‘BUILD_BUG_ON’ 20 | BUILD_BUG_ON(ARRAY_SIZE(func_id_str) != __BPF_FUNC_MAX_ID); | ^~~~ libbpf: failed to open format: No such file or directory Error: failed to load BTF from format: No such file or directory make[1]: *** [Makefile:190: /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/vmlinux.h] Error 2 make[1]: *** Deleting file '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/tools/include/vmlinux.h' make: *** [Makefile:157: all] Error 2 Please find attachment for the complete build log. As the ubuntu_kernel_selftests needs bpf to be built first, this will block the ubuntu_kernel_selftests/net to build as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1894964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905742] Re: Add support for AMD Sienna Cichlid (RX6000)
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-firmware (Ubuntu Groovy) Status: Confirmed => Won't Fix -- 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/1905742 Title: Add support for AMD Sienna Cichlid (RX6000) Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Confirmed Status in linux-firmware source package in Groovy: Won't Fix Bug description: [Impact] RX6000 series gfx cards do not work on Ubuntu at the moment. They need new firmware recently pushed upstream. [Test case] Install the updates, see that the desktop session is running with the native driver. [Where things could go wrong] ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1905742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905728] Re: log_check / tainted_check failed in ubuntu_boot because of warnings (Found insecure W+X mapping at address) found on F/G/H-riscv
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: New => Won't Fix -- 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/1905728 Title: log_check / tainted_check failed in ubuntu_boot because of warnings (Found insecure W+X mapping at address) found on F/G/H-riscv Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-riscv package in Ubuntu: New Status in linux source package in Groovy: Won't Fix Status in linux-riscv source package in Groovy: Won't Fix Bug description: Issue found on 5.8.0-10-generic riscv Message reported on boot. [ 13.483103] [ cut here ] [ 13.483711] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 13.484542] WARNING: CPU: 5 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 13.485175] Modules linked in: [ 13.485606] CPU: 5 PID: 1 Comm: swapper/0 Not tainted 5.8.0-10-generic #12-Ubuntu [ 13.486091] epc: ffe000208f18 ra : ffe000208f18 sp : ffe1f5bfbb30 [ 13.486471] gp : ffe001728ee0 tp : ffe1f5bf5080 t0 : ffe00173ed88 [ 13.486850] t1 : ffe00173ed20 t2 : 0001fecbe000 s0 : ffe1f5bfbb80 [ 13.487250] s1 : ffe1f5bfbe10 a0 : 0053 a1 : 0020 [ 13.487633] a2 : ffe1f5bfb870 a3 : a4 : ffe0016200f8 [ 13.488040] a5 : ffe0016200f8 a6 : 00b5 a7 : ffe0006f2806 [ 13.488421] s2 : ffdff8001000 s3 : s4 : 0004 [ 13.488800] s5 : s6 : s7 : ffe1f5bfbd20 [ 13.489322] s8 : ffdff8001000 s9 : ffe00172a148 s10: ffdff8002000 [ 13.489738] s11: ffe000c16e20 t3 : 0003cec0 t4 : 0003cec0 [ 13.490119] t5 : t6 : ffe001739462 [ 13.490406] status: 0120 badaddr: cause: 0003 [ 13.490849] ---[ end trace 607c551edff1ef12 ]--- Please find attachment for the boot dmesg log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1905728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908294] Re: MCE on shutdown when nouveau driver loaded
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux (Ubuntu Groovy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1908294
Title:
MCE on shutdown when nouveau driver loaded
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Confirmed
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
Confirmed
Bug description:
[Impact]
When rebooting with the focal kernel, my system always MCEs. Installing an
nvidia driver - or simply blacklisting the nouveau driver - avoids the issue.
Sometimes it hard hangs the system, requiring a manual power cycle:
[ OK ] Reached target Reboot.
[ 402.489755] Disabling lock debugging due to kernel taint
[ 402.495319] mce: [Hardware Error]: CPU 24: Machine Check Exception: 5 Bank
6: bb800e0b
[ 402.503924] mce: [Hardware Error]: RIP !INEXACT! 10:
{intel_idle+0x87/0x130}
[ 402.512530] mce: [Hardware Error]: TSC 29fb4740af0 MISC d700
[ 402.518622] mce: [Hardware Error]: PROCESSOR 0:50654 TIME 1601415822
SOCKET 1 APIC 40 microcode 2006906
[ 402.527998] mce: [Hardware Error]: Run the above through 'mcelog --ascii'
Other times it emits the MCE tombstone, but goes ahead and reboots
itself:
[ OK ] Reached target Reboot.
[ 870.372933] Disabling lock debugging due to kernel taint
[ 870.378505] mce: [Hardware Error]: CPU 24: Machine Check Exception: 5 Bank
6: bb800e0b
[ 870.387110] mce: [Hardware Error]: RIP !INEXACT! 10:
{intel_idle+0x87/0x130}
[ 870.395716] mce: [Hardware Error]: TSC 44e0f5e602c MISC d700
[ 870.401801] mce: [Hardware Error]: PROCESSOR 0:50654 TIME 1589320331
SOCKET 1 APIC 40 microcode 264
[ 870.411185] mce: [Hardware Error]: Run the above through 'mcelog --ascii'
[ 870.420531] mce: [Hardware Error]: Machine check: Processor context corrupt
[ 870.427488] Kernel panic - not syncing: Fatal machine check
[ 870.433108] Kernel Offset: 0xc80 from 0x8100 (relocation
range: 0x8000-0xbfff)
[ 871.054820] Rebooting in 30 seconds..
[ 900.901238] ACPI MEMORY or I/O RESET_REG.
Copyright(c) 2015 American Megatrends, Inc.
0x19 : Pre-memory SB Initialization.
Copyright(c) 2016 American Megatrends, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1908294/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908501] Re: Sub-tests in kselftest/net/udpgro.sh is failing with "./udpgso_bench_rx: poll: 0x0 expected 0x1"
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux (Ubuntu Groovy)
Status: Fix Committed => Won't Fix
--
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/1908501
Title:
Sub-tests in kselftest/net/udpgro.sh is failing with
"./udpgso_bench_rx: poll: 0x0 expected 0x1"
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
In Progress
Bug description:
[Impact]
Sub test cases in kselftest/net/udpgro.sh is failing with:
./udpgso_bench_rx: poll: 0x0 expected 0x1
Complete test output of a sub test case:
multiple GRO socks
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
data type_id=3 bits_offset=0
data_end type_id=3 bits_offset=32
data_meta type_id=3 bits_offset=64
ingress_ifindex type_id=3 bits_offset=96
rx_queue_index type_id=3 bits_offset=128
[3] TYPEDEF __u32 type_id=4
[4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
[5] FUNC_PROTO (anon) return=6 args=(1 ctx)
[6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[7] FUNC xdp_dummy_prog type_id=5
[8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
[9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
[10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
[11] VAR _license type_id=9 linkage=1
[12] DATASEC license size=0 vlen=1 size == 0
./udpgso_bench_rx: poll: 0x0 expected 0x1
./udpgso_bench_rx: poll: 0x0 expected 0x1
failed
It's a bit hard to spot this as the udpgro.sh will return 0 even with
these failures present (bug 1908499)
[Fix]
* 38bf8cd821be29 ("selftests: fix poll error in udpgro.sh")
We have this test case since Focal
This patch can be cherry-picked into all the affected releases.
[Test Case]
Run the kselftest/net/udpgro.sh as root.
It will no longer complaining about this error message anymore:
./udpgso_bench_rx: poll: 0x0 expected 0x1
multiple GRO socks
BTF debug data section '.BTF' rejected: Invalid argument (22)!
- Length: 568
Verifier analysis:
magic: 0xeb9f
version: 1
flags: 0x0
hdr_len: 24
type_off: 0
type_len: 256
str_off: 256
str_len: 288
btf_total_size: 568
[1] PTR (anon) type_id=2
[2] STRUCT xdp_md size=20 vlen=5
data type_id=3 bits_offset=0
data_end type_id=3 bits_offset=32
data_meta type_id=3 bits_offset=64
ingress_ifindex type_id=3 bits_offset=96
rx_queue_index type_id=3 bits_offset=128
[3] TYPEDEF __u32 type_id=4
[4] INT unsigned int size=4 bits_offset=0 nr_bits=32 encoding=(none)
[5] FUNC_PROTO (anon) return=6 args=(1 ctx)
[6] INT int size=4 bits_offset=0 nr_bits=32 encoding=SIGNED
[7] FUNC xdp_dummy_prog type_id=5
[8] INT char size=1 bits_offset=0 nr_bits=8 encoding=SIGNED
[9] ARRAY (anon) type_id=8 index_type_id=10 nr_elems=4
[10] INT __ARRAY_SIZE_TYPE__ size=4 bits_offset=0 nr_bits=32 encoding=(none)
[11] VAR _license type_id=9 linkage=1
[12] DATASEC license size=0 vlen=1 size == 0
ok
[Where problems could occur]
The fix is limited to testing tools, no actual affect to the kernel. The
possible issue is that this patch is incorrect and it will make us ignore the
real issue in the kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1908501/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908264] Re: Disable Atari partition support for cloud kernels
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-aws (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/1908264 Title: Disable Atari partition support for cloud kernels Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-aws source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-aws source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Fix Committed Status in linux-oracle source package in Bionic: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-gcp source package in Focal: Fix Released Status in linux-gke source package in Focal: Fix Released Status in linux-gkeop source package in Focal: Fix Released Status in linux-oracle source package in Focal: Fix Released Status in linux-aws source package in Groovy: Won't Fix Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-gcp source package in Groovy: Fix Released Status in linux-oracle source package in Groovy: Fix Released Status in linux-aws source package in Hirsute: In Progress Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Status in linux-gcp source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Atari partition tables have very broad specifications, and can spontaneously show up on uncleared disks with "garbage" data. There have been reports of misinterpreted AHDI partition tables before (see [0] and [1]), usually as an unintended side-effect of using non-zeroed disks. Users of this specific partition scheme are unlikely to be on AWS instances, so we should disable them. [0] https://lore.kernel.org/linux-block/1467736712-11825-1-git-send-email-kris...@linux.vnet.ibm.com/ [1] https://mail-index.netbsd.org/port-atari/1995/11/19/0001.html [Test Case] Ensure that CONFIG_ATARI_PARTITION is not set in /boot/config-$(uname -r) [Fix] Unset CONFIG_ATARI_PARTITION in debian.aws/config/config.common.ubuntu [Regression Potential] There could be unexpected dependencies on Atari partitions that are impacted by this change. Considering Atari hardware hasn't been produced in a long time, and is unlikely to be used in AWS instances, the regression potential should be very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912316] Re: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048)
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912316 Title: log_check / kernel_tainted test from ubuntu_boot failed on Intel Cloud node grumman (failed with flag 2048) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Won't Fix Bug description: Issue found on node grumman, this is not a regression. The kernel_tainted check reports a non-zero flag 2048, this means "workaround for bug in platform firmware applied" log_check reports WARNINGs found in the dmesg: 10. 01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 7.852005] WARNING: CPU: 0 PID: 179 at /build/linux-0dlxvs/linux-4.4.0/drivers/dma/ioat/dca.c:342 ioat_dca_init+0x17c/0x1a0 [ioatdma]() 11. 01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 5.387292] WARNING: CPU: 0 PID: 181 at /build/linux-7Nk88i/linux-4.4.0/drivers/dma/ioat/dca.c:342 ioat_dca_init+0x17c/0x1a0 [ioatdma]() 12. 01/06 09:46:51 INFO |ubuntu_boo:0030| kernel: [ 6.039705] WARNING: CPU: 0 PID: 4 at /build/linux-7Nk88i/linux-4.4.0/drivers/dma/ioat/dca.c:342 ioat_dca_init+0x17c/0x1a0 [ioatdma]() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1912316/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1914685] Re: Please enable CONFIG_UBSAN_BOUNDS
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914685 Title: Please enable CONFIG_UBSAN_BOUNDS Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Confirmed Bug description: Enabling CONFIG_UBSAN_BOUNDS is fast and provides good coverage for out-of-bounds array indexing (i.e. it catchings the things that CONFIG_FORTIFY doesn't). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912772] Re: Panic on sysfs read
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-raspi (Ubuntu Groovy) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1912772 Title: Panic on sysfs read Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Focal: New Status in linux-raspi source package in Groovy: Won't Fix Status in linux-raspi source package in Hirsute: Confirmed Bug description: 1) root@fry:~# lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 2) root@fry:~# apt-cache policy linux-image-raspi linux-image-raspi: Installed: 5.8.0.1011.14 [...] 3) Nothing 4) On a Raspberry Pi 4 Rev 1.4 8GB, the kernel panics if you read the /sys/kernel/debug/regmap/dummy-avs-monitor@7d5d2000/registers file. You find a screenshot attached. Unfortunately, I don't have a serial adaptor at hand, and I didn't get netconsole working right now. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-raspi 5.8.0.1011.14 ProcVersionSignature: Ubuntu 5.8.0-1011.14-raspi 5.8.18 Uname: Linux 5.8.0-1011-raspi aarch64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.8.0-1011-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu50.3 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip Date: Fri Jan 22 11:29:32 2021 ImageMediaBuild: 20201022 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 0781:558c SanDisk Corp. Extreme Portable SSD Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 bcm2708_fb.fbwidth=1920 bcm2708_fb.fbheight=1080 bcm2708_fb.fbswap=1 smsc95xx.macaddr=DC:A6:32:E2:2A:BE vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash RelatedPackageVersions: linux-restricted-modules-5.8.0-1011-raspi N/A linux-backports-modules-5.8.0-1011-raspi N/A linux-firmware1.190.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-raspi StagingDrivers: bcm2835_v4l2 bcm2835_mmal_vchiq bcm2835_codec bcm2835_isp snd_bcm2835 vc_sm_cma UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1912772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915145] Re: add modalias for testing
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: nvidia-graphics-drivers-460 (Ubuntu Groovy) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1915145 Title: add modalias for testing Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in nvidia-graphics-drivers-460 source package in Focal: New Status in nvidia-graphics-drivers-460 source package in Groovy: Won't Fix Status in nvidia-graphics-drivers-460 source package in Hirsute: New Bug description: nvidia-graphics-drivers-460 [Impact] * To aid installer testing of the correct kernels with/without nvidia, it would be helpful to test nvidia driver installation in qemu VMs without actually needing nvidia hardware. * We already have `Modaliases: meta(dmi:*:pnUBUNTUQEMUTEST:*)` to test installs with oem-qemu-meta (aka certified install) * It would be useful to add nvidia modalias of `dmi:*:pvrUBUNTUNVIDIATEST:*` to nvidia-graphics-drivers-460 * This way we will be able to test generic with/without nvidia; and oem with/without nvidia. By combinding pn & pvr dmi modaliases. [Test Case] * Setup ubuntu qemu libvirt vm with dmi sysinfo setting product version to UBUNTUNVIDIATEST I.e. UBUNTUNVIDIATEST ... * Boot and execute ubuntu-drivers list * Observe that nvidia drivers show up as options. [Where problems could occur] * Additional mod alias will be exposed in the package metadata, and whilst it will be installed it will not be loaded. It is purely an installer test interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1915145/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1918226] Re: testbed auxverb failed with exit code 255 with linux on Groovy ADT failure
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1918226 Title: testbed auxverb failed with exit code 255 with linux on Groovy ADT failure Status in linux package in Ubuntu: Invalid Status in linux source package in Groovy: Won't Fix Bug description: Testing failed on: arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/arm64/l/linux/20210308_234307_e716b@/log.gz Looks to be a flaky test with this error occurring frequently. This is not a regression. Found a previously reported (expired) bug with the same error: https://launchpad.net/bugs/1549425 [ 6606.751232] audit: backlog limit Creating nova instance adt-groovy-arm64-linux-20210308-143145 from image adt/ubuntu-groovy-arm64-server-20210308.img (UUID 1cfb02a6-bf88-46bb-a8f1-3c6589cd939e)... Creating nova instance adt-groovy-arm64-linux-20210308-143145 from image adt/ubuntu-groovy-arm64-server-20210308.img (UUID 1cfb02a6-bf88-46bb-a8f1-3c6589cd939e)... autopkgtest [23:42:55]: ERROR: testbed failure: testbed auxverb failed with exit code 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1918226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919123] Re: Dell Precision 5550 takes up to 10 seconds to respond when coming out of sleep
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1919123 Title: Dell Precision 5550 takes up to 10 seconds to respond when coming out of sleep Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Fix Released Bug description: [Impact] On some platforms, the EC doesn't support the register reading sequence for sentelic[1], and then make the EC can't respond commands for a while when probing. It leads to the keyboard is non-responsive for around 10 seconds while waking up from s2idle. [ 44.304488] i8042: [9804] d4 -> i8042 (command) [ 44.304634] i8042: [9804] f3 -> i8042 (parameter) [ 44.304787] i8042: [9804] fa <- i8042 (interrupt, 1, 12) [ 44.304855] i8042: [9804] d4 -> i8042 (command) [ 44.304938] i8042: [9804] 66 -> i8042 (parameter) [ 44.337698] i8042: [9813] d4 -> i8042 (command) [ 44.905695] i8042: [9942] 88 -> i8042 (parameter) [ 45.497478] i8042: [10102] d4 -> i8042 (command) [ 46.098041] i8042: [10253] f3 -> i8042 (parameter) [ 46.098070] i8042: [10253] fe <- i8042 (interrupt, 1, 12) [ 46.718154] i8042: [10386] d4 -> i8042 (command) [ 47.309915] i8042: [10386] f4 -> i8042 (parameter) [ 47.918961] i8042: [10556] d4 -> i8042 (command) [ 48.402624] i8042: [10556] f6 -> i8042 (parameter) [Fix] A DMI quirk to mark this platform doesn't have aux device could avoid those commands to be sent. And the system could still using i2c interface to communicate with the touchpad. https://lkml.org/lkml/2021/3/15/126 [Test] Verified on Dell Precision 5550 [Where problem could occur] The quirk only affects the listed platform, there is no regression could occur. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1919123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851663] Re: (In)consistent autopkgtest failures on ppc64el/s390x
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: makedumpfile (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1851663 Title: (In)consistent autopkgtest failures on ppc64el/s390x Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Eoan: Won't Fix Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Won't Fix Bug description: Recently autopkgtest started to consistently fail in ppc64el / s390x. When testing manually, the kernel dump is collected and all works fine. By discussing with the package maintainer (Cascardo), it seems it started after a change in the instance type of the tests, to m1.large. This seems either a problem in the test infrastructure itself or a likely a "timing" problem in the test (i.e., requiring some pause or delay that is not currently enough). This demands investigation because those failures delay the package release for all arches, usually those releases contain important fixes. Also, the recurrent "workaround" is to mark the tests as "force- badtest" in ubuntu-hints for the 2 arches, which is in practice skipping the test, so those 2 arches are getting releases untested by the automatic infrastructure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1851663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919154] Re: Enable CONFIG_NO_HZ_FULL on supported architectures
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1919154 Title: Enable CONFIG_NO_HZ_FULL on supported architectures Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: In Progress Bug description: [Impact] The CONFIG_NO_HZ_FULL=y Kconfig option causes the kernel to avoid sending scheduling-clock interrupts to CPUs with a single runnable task, and such CPUs are said to be "adaptive-ticks CPUs". This is important for applications with aggressive real-time response constraints because it allows them to improve their worst-case response times by the maximum duration of a scheduling-clock interrupt. It is also important for computationally intensive short-iteration workloads: If any CPU is delayed during a given iteration, all the other CPUs will be forced to wait idle while the delayed CPU finishes. Thus, the delay is multiplied by one less than the number of CPUs. In these situations, there is again strong motivation to avoid sending scheduling-clock interrupts. [Test Plan] In order to verify the change will not cause performance issues in context switch we should compare the results for: ./stress-ng --seq 0 --metrics-brief -t 15 Running on a dedicated machine and with the following services disabled: smartd.service, iscsid.service, apport.service, cron.service, anacron.timer, apt-daily.timer, apt-daily-upgrade.timer, fstrim.timer, logrotate.timer, motd-news.timer, man-db.timer. The results didn't show any performance regression: https://kernel.ubuntu.com/~mhcerri/lp1919154/ [Where problems could occur] Performance degradation might happen for workloads with intensive context switching. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884568] Re: Groovy update: v5.7.4 upstream stable release
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884568 Title: Groovy update: v5.7.4 upstream stable release Status in linux package in Ubuntu: In Progress Status in linux source package in Groovy: Won't Fix 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.7.4 upstream stable release from git://git.kernel.org/ Linux 5.7.4 lib/vdso: Provide sanity check for cycles (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884567] Re: Groovy update: v5.7.3 upstream stable release
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884567 Title: Groovy update: v5.7.3 upstream stable release Status in linux package in Ubuntu: In Progress Status in linux source package in Groovy: Won't Fix 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.7.3 upstream stable release from git://git.kernel.org/ Linux 5.7.3 serial: amba-pl011: Make sure we initialize the port.lock spinlock KVM: arm64: Synchronize sysreg state on injecting an AArch32 exception KVM: arm64: Save the host's PtrAuth keys in non-preemptible context platform/x86: sony-laptop: Make resuming thermal profile safer platform/x86: sony-laptop: SNC calls should handle BUFFER types xen/pvcalls-back: test for errors when calling backend_connect() block/floppy: fix contended case in floppy_queue_rq() mmc: sdio: Fix several potential memory leaks in mmc_sdio_init_card() mmc: sdio: Fix potential NULL pointer error in mmc_sdio_init_card() ARM: dts: at91: sama5d2_ptc_ek: fix sdmmc0 node description mmc: uniphier-sd: call devm_request_irq() after tmio_mmc_host_probe() mmc: tmio: Further fixup runtime PM management at remove mmc: mmci_sdmmc: fix DMA API warning overlapping mappings mmc: sdhci-of-at91: fix CALCR register being rewritten mmc: sdhci-msm: Clear tuning done flag while hs400 tuning agp/intel: Reinforce the barrier after GTT updates perf: Add cond_resched() to task_function_call() fat: don't allow to mount if the FAT length == 0 mm/slub: fix a memory leak in sysfs_slab_add() drm/vkms: Hold gem object while still in-use Smack: slab-out-of-bounds in vsscanf ath9k: Fix general protection fault in ath9k_hif_usb_rx_cb ath9x: Fix stack-out-of-bounds Write in ath9k_hif_usb_rx_cb ath9k: Fix use-after-free Write in ath9k_htc_rx_msg ath9k: Fix use-after-free Read in ath9k_wmi_ctrl_rx ath9k: Fix use-after-free Read in htc_connect_service selftests/ftrace: Return unsupported if no error_log file scsi: megaraid_sas: Replace undefined MFI_BIG_ENDIAN macro with __BIG_ENDIAN_BITFIELD macro scsi: lpfc: Fix negation of else clause in lpfc_prep_node_fc4type scsi: megaraid_sas: TM command refire leads to controller firmware crash KVM: arm64: Make vcpu_cp1x() work on Big Endian hosts KVM: arm64: Stop writing aarch32's CSSELR into ACTLR KVM: MIPS: Fix VPN2_MASK definition for variable cpu_vmbits KVM: MIPS: Define KVM_ENTRYHI_ASID to cpu_asid_mask(&boot_cpu_data) KVM: nVMX: Consult only the "basic" exit reason when routing nested exit KVM: nSVM: leave ASID aside in copy_vmcb_control_area KVM: nSVM: fix condition for filtering async PF KVM: nVMX: Skip IBPB when switching between vmcs01 and vmcs02 media: videobuf2-dma-contig: fix bad kfree in vb2_dma_contig_clear_max_seg_size video: fbdev: w100fb: Fix a potential double free. video: vt8500lcdfb: fix fallthrough warning EDAC/skx: Use the mcmtr register to retrieve close_pg/bank_xor_enable cpufreq: Fix up cpufreq_boost_set_sw() remoteproc: Fix and restore the parenting hierarchy for vdev remoteproc: Fall back to using parent memory pool if no dedicated available proc: Use new_inode not new_inode_pseudo exfat: fix incorrect update of stream entry in __exfat_truncate() exfat: fix memory leak in exfat_parse_param() ovl: initialize error in ovl_copy_xattr ovl: fix out of bounds access warning in ovl_check_fb_len() net/mlx5e: CT: Fix ipv6 nat header rewrite actions net: sched: export __netdev_watchdog_up() net: ethernet: ti: am65-cpsw-nuss: fix ale parameters init net: ethernet: ti: ale: fix allmulti for nu type ale mptcp: fix races between shutdown and recvmsg ionic: wait on queue start until after IFF_UP mptcp: don't leak msk in token container net/mlx5: Disable reload while removing the device net: macb: Only disable NAPI on the actual error path net: cadence: macb: disable NAPI on error net/mlx5e: Fix repeated XSK usage on one channel net/mlx5: Fix fatal error handling during device load net/mlx5: drain health workqueue in case of driver load error selftests/net: in rxtimestamp getopt_long needs terminating null entry net: mvneta: do not redirect frames during reconfiguration dccp: Fix possible memleak in dccp_init and dccp_fini fir
[Kernel-packages] [Bug 1920777] Re: [SRU][G][HWE-5.8] Fix compatibility issue on some external monitors
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1920777 Title: [SRU][G][HWE-5.8] Fix compatibility issue on some external monitors Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-hwe-5.8 package in Ubuntu: Confirmed Status in linux-hwe-5.8 source package in Focal: Confirmed Status in linux source package in Groovy: Won't Fix Bug description: [Impact] Some external monitors got black screen via HDMI on laptops with Intel GPU. [Fix] Reading more of the port caps and dealing with various clock/bpc limitations. Patchset: https://patchwork.freedesktop.org/series/72928/ [Test Case] Verified on the target platform and other 2 laptops include workstation, Tested on LG/ThinkVision 4k monitors and Dell 1080p monitor, include dock station. All good. [Where problems could occur] Intel GPU may lose or mess the output. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1920777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Remove obsolete "nousb" option in kdump command-line for newer kernels
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: makedumpfile (Ubuntu Groovy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Remove obsolete "nousb" option in kdump command-line for newer kernels
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Won't Fix
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Eoan:
Won't Fix
Status in makedumpfile source package in Focal:
Confirmed
Status in makedumpfile source package in Groovy:
Won't Fix
Bug description:
[Impact]
* Kdump command-line include an obsolete "nousb" parameter by default, which
can cause a misimpression: users will think they are not booting with USB, but
they are.
* Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case
the subsystem is built-in). This was changed by commit 097a9ea0e48
("usb: make "nousb" a clear module parameter").
* USB may be pretty essential in case for example kdump users need to
decrypt a disk under LUKS, and there's only an USB keyboard connected
to the system. Given the option is innocuous since Bionic, we should
just drop it to prevent confusion.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'nousb' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is extremely low, since the "nousb" parameter
is not used since Bionic although is there. Any bugs we would have by
changing this are still valid by not removing the option - the
semantics with or without "nosub" is the same since from Bionic.
NOTICE we won't change Xenial, it can use kernel 4.4 which indeed
disables USB by taking the "nousb" parameter.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886065] Re: Move do_enforce_all from hooks.mk to arches mk
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886065 Title: Move do_enforce_all from hooks.mk to arches mk Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: Won't Fix Bug description: [Impact] When rebasing hwe kernels, we need to deal with changes from hooks.mk coming from master kernels. [Fix] Remove any contents from hooks.mk from master kernels, that is, move do_enforce_all around to arches mk files. [Test case] Kernel build works, annotation file regressions fail the build, hwe rebase works fine without hooks.mk munging. [Regression potential] We might fail the kernel build or fail to catch up an annotation file regression. Those were covered in the test case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893921] Re: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1893921 Title: ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Confirmed Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Confirmed Bug description: Testing failed on: s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/s390x/l/linux/20200901_162956_a95df@/log.gz The ipsec_offload in rtnetlink.sh from kselftests.net fails on s390x: 15:45:23 DEBUG| [stdout] # selftests: net: rtnetlink.sh 15:45:23 DEBUG| [stdout] # PASS: policy routing 15:45:23 DEBUG| [stdout] # PASS: route get 15:45:28 DEBUG| [stdout] # PASS: preferred_lft addresses have expired 15:45:28 DEBUG| [stdout] # PASS: promote_secondaries complete 15:45:28 DEBUG| [stdout] # PASS: tc htb hierarchy 15:45:29 DEBUG| [stdout] # PASS: gre tunnel endpoint 15:45:29 DEBUG| [stdout] # PASS: gretap 15:45:29 DEBUG| [stdout] # PASS: ip6gretap 15:45:29 DEBUG| [stdout] # PASS: erspan 15:45:29 DEBUG| [stdout] # PASS: ip6erspan 15:45:30 DEBUG| [stdout] # PASS: bridge setup 15:45:31 DEBUG| [stdout] # PASS: ipv6 addrlabel 15:45:31 DEBUG| [stdout] # PASS: set ifalias b14b1d80-dc0b-4a9b-9256-3ec3f86aa891 for test-dummy0 15:45:31 DEBUG| [stdout] # PASS: vrf 15:45:31 DEBUG| [stdout] # PASS: vxlan 15:45:31 DEBUG| [stdout] # FAIL: can't add fou port , skipping test 15:45:31 DEBUG| [stdout] # PASS: macsec 15:45:32 DEBUG| [stdout] # PASS: ipsec 15:45:33 DEBUG| [stdout] # 3,7c3,7 15:45:33 DEBUG| [stdout] # < sa[0]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[0]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # < sa[1] rx ipaddr=0x c0a87b03 15:45:33 DEBUG| [stdout] # < sa[1]spi=0x0009 proto=0x32 salt=0x64636261 crypt=1 15:45:33 DEBUG| [stdout] # < sa[1]key=0x31323334 35363738 39303132 33343536 15:45:33 DEBUG| [stdout] # --- 15:45:33 DEBUG| [stdout] # > sa[0]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[0]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # > sa[1] rx ipaddr=0x 037ba8c0 15:45:33 DEBUG| [stdout] # > sa[1]spi=0x0009 proto=0x32 salt=0x61626364 crypt=1 15:45:33 DEBUG| [stdout] # > sa[1]key=0x34333231 38373635 32313039 36353433 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload incorrect driver data 15:45:33 DEBUG| [stdout] # FAIL: ipsec_offload 15:45:33 DEBUG| [stdout] # PASS: bridge fdb get 15:45:33 DEBUG| [stdout] # PASS: neigh get 15:45:33 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1893921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896950] Re: d2020.09.22 cycle tracker
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Won't Fix -- 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/1896950 Title: d2020.09.22 cycle tracker Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Status in linux source package in Groovy: Won't Fix Status in linux-aws source package in Groovy: New Status in linux-azure source package in Groovy: New Status in linux-gcp source package in Groovy: New Status in linux-kvm source package in Groovy: New Status in linux-oracle source package in Groovy: New Status in linux-raspi source package in Groovy: New Status in linux-riscv source package in Groovy: New Bug description: This bug is a cycle tracking bug for the d2020.09.22 development cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-raspi (Ubuntu Groovy) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1901272 Title: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4 Status in bluez package in Ubuntu: Incomplete Status in linux-raspi package in Ubuntu: Incomplete Status in pi-bluetooth package in Ubuntu: Confirmed Status in bluez source package in Groovy: Won't Fix Status in linux-raspi source package in Groovy: Won't Fix Status in pi-bluetooth source package in Groovy: Won't Fix Bug description: Raspberry pi 4 4Gb ram Ubuntu desktop 20.10 64 bit After reboot no Bluetooth devices connect, scanning Bluetooth devices works, results with same device name (duplicated and with not set up status). Sometimes after several reboots it works. If I use power off and cycle power then it works fine each time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899826] Re: backport upstream fixes for 5.9 Linux support
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: zfs-linux (Ubuntu Groovy)
Status: Confirmed => Won't Fix
--
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/1899826
Title:
backport upstream fixes for 5.9 Linux support
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Groovy:
Won't Fix
Status in zfs-linux source package in Hirsute:
Fix Released
Bug description:
== SRU Request Groovy ==
Upstream zfs supports 5.9. it would be useful to backport these for
users who want newer kernels.
== The Fix ==
Although 6 fixes are required, 2 add changes that get removed by a
later change, so one can backport this with just the following 4
changes:
1823c8fe6a4a20971463e9b51615dad412aea9a9 ("Linux 5.9 compat: add
linux/blkdev.h include")
3e29e1971bbb4ab63dafeb592b747ef56bad3534 ("Linux 5.9 compat:
NR_SLAB_RECLAIMABLE")
d817c17100183b266aa6bf8b868e016805d51d16 ("Linux 5.9 compat: make_request_fn
replaced with submit_bio")
4b59c195ffbaebfdd5f0971a54613c0ed7c42005 ("Increase Supported Linux Kernel to
5.9")
== Regression potential ==
The first patch just includes blkdev.h to workaround a build warning,
so the results in no functional change to the working code.
The second patch removes legacy arc page free estimation by droping
the accounting for inactive anonymous pages and reclaimable pages on
the slab. This change removes a very minor component of the free
memory calculation and speeds up arc free stats calculations. There is
a potential that this small change in free page calculation may impact
systems where memory is more constrained, but the change is so small I
believe this really is insignificant.
The third patch is a build time detection of the kernel block
allocation queue due to API changes, so should not change behaviour
for current 5.8 kernels, only change behaviour for newer kernels with
the newer kernel API. Hence for the released 5.8 groovy kernel the
code will not be changed, so the regression potential for 5.8 is zero.
The final patch changes the META build data to allow the driver to
build on newer kernels, so the risk on this change is effectively
zero.
== Testing ==
Run the autotest client tests for ZFS tests:
ubuntu_zfs_smoke_tests (general functionality smoke tests)
ubuntu_zfs_fstests (file system semantics tests)
ubuntu_zfs_xfs_generic (subset of XFS tests on ZFS)
ubuntu_zfs_stress (stress-ng file system tests on a wide range of ZFS mount
options)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1899826/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900683] Re: Installing wireguard-tools pulls in the generic kernel
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-raspi (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1900683 Title: Installing wireguard-tools pulls in the generic kernel Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Groovy: Won't Fix Bug description: [Impact] Installing wireguard-tools on Groovy raspi pulls in the generic kernel: ubuntu@rpi-4b-rev1d2-2c1a:~$ uname -a Linux rpi-4b-rev1d2-2c1a 5.8.0-1004-raspi #7-Ubuntu SMP PREEMPT Fri Oct 9 14:52:59 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux ubuntu@rpi-4b-rev1d2-2c1a:~$ sudo apt install wireguard-tools Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-image-5.7.0-15-generic linux-image-virtual-wip linux-modules-5.7.0-15-generic Suggested packages: fdutils linux-doc | linux-5.7-source-5.7.0 linux-5.7-tools linux-headers-5.7.0-15-generic openresolv | resolvconf The following NEW packages will be installed: linux-image-5.7.0-15-generic linux-image-virtual-wip linux-modules-5.7.0-15-generic wireguard-tools 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 27.9 MB of archives. After this operation, 105 MB of additional disk space will be used. Do you want to continue? [Y/n] n [Test Case] See above. [Regression Potential] If the provides is wrong, users might end up pulling in incorrect packages. Just like it happens today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1900683/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900663] Re: Re-enable memory cgroups
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-raspi (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1900663 Title: Re-enable memory cgroups Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi source package in Focal: Confirmed Status in linux-raspi source package in Groovy: Won't Fix Status in linux-raspi source package in Hirsute: Fix Released Bug description: Currently, the 5.4 and 5.8 raspi kernels disable the memory cgroup by default to conserve memory [1]. This is a legacy custom modification, that is no longer needed, since the memory cgroup code has been rewritten to no longer requires large amounts of memory [2]. So the custom patch can be dropped. The patch is also the reason why the LXC ADT test fails. [1] https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-raspi/+git/focal/commit/?id=64e543b88ea2a013e1d8e014e7c92c53df1322ed [2] https://github.com/torvalds/linux/commit/1306a85aed3ec3db98945aafb7dfbe5648a1203c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1900663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: bluez (Ubuntu Groovy) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1901272 Title: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4 Status in bluez package in Ubuntu: Incomplete Status in linux-raspi package in Ubuntu: Incomplete Status in pi-bluetooth package in Ubuntu: Confirmed Status in bluez source package in Groovy: Won't Fix Status in linux-raspi source package in Groovy: Won't Fix Status in pi-bluetooth source package in Groovy: Won't Fix Bug description: Raspberry pi 4 4Gb ram Ubuntu desktop 20.10 64 bit After reboot no Bluetooth devices connect, scanning Bluetooth devices works, results with same device name (duplicated and with not set up status). Sometimes after several reboots it works. If I use power off and cycle power then it works fine each time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: pi-bluetooth (Ubuntu Groovy) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1901272 Title: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4 Status in bluez package in Ubuntu: Incomplete Status in linux-raspi package in Ubuntu: Incomplete Status in pi-bluetooth package in Ubuntu: Confirmed Status in bluez source package in Groovy: Won't Fix Status in linux-raspi source package in Groovy: Won't Fix Status in pi-bluetooth source package in Groovy: Won't Fix Bug description: Raspberry pi 4 4Gb ram Ubuntu desktop 20.10 64 bit After reboot no Bluetooth devices connect, scanning Bluetooth devices works, results with same device name (duplicated and with not set up status). Sometimes after several reboots it works. If I use power off and cycle power then it works fine each time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901272/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902093] Re: Introduce the new NVIDIA 455 series
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu. https://bugs.launchpad.net/bugs/1902093 Title: Introduce the new NVIDIA 455 series Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-455 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-455 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-455 source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux-restricted-modules source package in Groovy: Fix Released Status in nvidia-graphics-drivers-455 source package in Groovy: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] * New upstream release: - Added support for the following GPUs: GeForce RTX 3070 - Added support for using an NVIDIA-driven display as a PRIME Display Offload sink with a PRIME Display Offload source driven by the xf86-video-intel driver. - Fixed a bug in a Vulkan barrier optimization that allowed some back-to-back copies to run unordered. - Fixed a performance regression in the NVIDIA X driver which affected some X11 RENDER extension use cases. - Added AMD Secure Memory Encryption compatibility. * debian/templates/control.in: - Set support level to NFB instead of Beta. - Add support for CUDA 11. Note: this will be the initial release for Bionic and Focal. Changelog entries for the linux-restricted-modules: UBUNTU: [Packaging] NVIDIA -- provide the nvidia-prebuilt-kernel virtual package Make all the NVIDIA drivers, except for 390, provide the nvidia-prebuilt-kernel virtual package. This allows adding a generic dependency on the signed modules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902093/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905203] Re: selftests: net: fib_nexthops.sh in linux from Groovy/linux 5.8.0-30.32 ADT test failure
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1905203 Title: selftests: net: fib_nexthops.sh in linux from Groovy/linux 5.8.0-30.32 ADT test failure Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Incomplete Status in linux source package in Groovy: Won't Fix Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/amd64/l/linux/20201119_073627_7226f@/log.gz 06:29:30 DEBUG| [stdout] # selftests: net: fib_nexthop_multiprefix.sh [...] 06:29:37 DEBUG| [stdout] # 06:29:37 DEBUG| [stdout] # IPv4 nexthop api compat mode 06:29:37 DEBUG| [stdout] # 06:29:37 DEBUG| [stdout] # TEST: IPv4 default nexthop compat mode check [ OK ] 06:29:37 DEBUG| [stdout] # TEST: IPv4 compat mode on - route add notification [FAIL] 06:29:37 DEBUG| [stdout] # TEST: IPv4 compat mode on - route dump [ OK ] 06:29:38 DEBUG| [stdout] # TEST: IPv4 compat mode on - nexthop change [ OK ] 06:29:38 DEBUG| [stdout] # TEST: IPv4 set compat mode - 0 [ OK ] 06:29:38 DEBUG| [stdout] # TEST: IPv4 compat mode off - route add notification [ OK ] 06:29:38 DEBUG| [stdout] # TEST: IPv4 compat mode off - route dump [ OK ] 06:29:38 DEBUG| [stdout] # TEST: IPv4 compat mode off - nexthop change [ OK ] 06:29:38 DEBUG| [stdout] # TEST: IPv4 compat mode off - nexthop delete [ OK ] 06:29:38 DEBUG| [stdout] # TEST: IPv4 set compat mode - 1 [ OK ] [...] 06:39:44 DEBUG| [stdout] # Tests passed: 127 06:39:44 DEBUG| [stdout] # Tests failed: 1 06:39:44 DEBUG| [stdout] not ok 35 selftests: net: fib_nexthops.sh # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1905203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905627] Re: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: bluez (Ubuntu Groovy) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1905627 Title: Bluetooth stops working on Raspberry Pi 4 with bluez 5.55-0ubuntu1.1 Status in bluez package in Ubuntu: New Status in bluez source package in Groovy: Won't Fix Status in bluez source package in Hirsute: New Bug description: Bluetooth stops working after updating to bluez version 5.55-0ubuntu1.1. /usr/bin/btuart returns "bcm43xx_init Initialization timed out". Bluetooth is working again if bluez is reverted to version 5.55-0ubuntu1. I don't have any unusual setup like miniuart-bt. Release: 20.10 bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy-updates/main arm64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports groovy/main arm64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-1007.10-raspi 5.8.14 Uname: Linux 5.8.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 16:09:03 2020 ImageMediaBuild: 20200423.1 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller Lsusb: Bus 002 Device 002: ID 1058:25ee Western Digital Technologies, Inc. My Book 25EE Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:B9:18:CC vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1 root=PARTUUID=5f9d0997-1b4e-423b-ad5e-8bce1a7e1ae4 rootfstype=ext4 elevator=deadline rootwait fixrtc SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-23 (33 days ago) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1905627/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922350] Re: missing firmware reported when updating initramfs
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-firmware (Ubuntu Groovy) Status: In Progress => Won't Fix -- 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/1922350 Title: missing firmware reported when updating initramfs Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: In Progress Status in linux-firmware source package in Focal: In Progress Status in linux-firmware source package in Groovy: Won't Fix Status in linux-firmware source package in Hirsute: In Progress Bug description: [SRU Justification] [Impact] Some kernel firmwares might be landed after linux-firmware forked for each series, or for LTS series, kernels of new versions may claim additional ones that were not previously available. This leaves devices fail to function correctly while they ought to. With a checking script that enumerates all the blobs available in upstream repo and in the Ubuntu fork of a given series, e.g. hirsute, iterate through all the installed kernel modules of a given version to check if claimed firmware blobs are available in Ubuntu's fork. Following kernel version/series have been checked: * 5.11.0-14-generic/hirsute * 5.8.0-48-generic/groovy * 5.4.0-70-generic/focal * 5.6.0-1052-oem/focal * 5.8.0-48-generic/focal * 5.10.0-1019-oem/focal * 4.15.0-140-generic/bionic * 4.18.0-25-generic/bionic * 5.0.0-65-generic/bionic * 5.4.0-70-generic/bionic And it gives following files were missing in at least one of above cases: * amdgpu/arcturus_asd.bin * amdgpu/arcturus_gpu_info.bin * amdgpu/arcturus_mec.bin * amdgpu/arcturus_mec2.bin * amdgpu/arcturus_rlc.bin * amdgpu/arcturus_sdma.bin * amdgpu/arcturus_smc.bin * amdgpu/arcturus_sos.bin * amdgpu/arcturus_ta.bin * amdgpu/arcturus_vcn.bin * amdgpu/navi12_asd.bin * amdgpu/navi12_ce.bin * amdgpu/navi12_dmcu.bin * amdgpu/navi12_gpu_info.bin * amdgpu/navi12_me.bin * amdgpu/navi12_mec.bin * amdgpu/navi12_mec2.bin * amdgpu/navi12_pfp.bin * amdgpu/navi12_rlc.bin * amdgpu/navi12_sdma.bin * amdgpu/navi12_sdma1.bin * amdgpu/navi12_smc.bin * amdgpu/navi12_sos.bin * amdgpu/navi12_ta.bin * amdgpu/navi12_vcn.bin * amdgpu/navy_flounder_ce.bin * amdgpu/navy_flounder_dmcub.bin * amdgpu/navy_flounder_me.bin * amdgpu/navy_flounder_mec.bin * amdgpu/navy_flounder_mec2.bin * amdgpu/navy_flounder_pfp.bin * amdgpu/navy_flounder_rlc.bin * amdgpu/navy_flounder_sdma.bin * amdgpu/navy_flounder_smc.bin * amdgpu/navy_flounder_sos.bin * amdgpu/navy_flounder_ta.bin * amdgpu/navy_flounder_vcn.bin * amdgpu/oland_uvd.bin * amdgpu/pitcairn_uvd.bin * amdgpu/renoir_asd.bin * amdgpu/renoir_ce.bin * amdgpu/renoir_gpu_info.bin * amdgpu/renoir_me.bin * amdgpu/renoir_mec.bin * amdgpu/renoir_mec2.bin * amdgpu/renoir_pfp.bin * amdgpu/renoir_rlc.bin * amdgpu/renoir_sdma.bin * amdgpu/renoir_ta.bin * amdgpu/renoir_vcn.bin * amdgpu/sienna_cichlid_ce.bin * amdgpu/sienna_cichlid_dmcub.bin * amdgpu/sienna_cichlid_me.bin * amdgpu/sienna_cichlid_mec.bin * amdgpu/sienna_cichlid_mec2.bin * amdgpu/sienna_cichlid_pfp.bin * amdgpu/sienna_cichlid_rlc.bin * amdgpu/sienna_cichlid_sdma.bin * amdgpu/sienna_cichlid_smc.bin * amdgpu/sienna_cichlid_sos.bin * amdgpu/sienna_cichlid_ta.bin * amdgpu/sienna_cichlid_vcn.bin * amdgpu/tahiti_uvd.bin * amdgpu/vega20_ta.bin * amdgpu/verde_uvd.bin * atmel/wilc1000_wifi_firmware-1.bin * cmmb_vega_12mhz.inp * cmmb_venice_12mhz.inp * dvb_nova_12mhz.inp * dvb_nova_12mhz_b0.inp * i915/bxt_guc_33.0.0.bin * i915/glk_guc_33.0.0.bin * i915/icl_guc_33.0.0.bin * i915/kbl_guc_33.0.0.bin * i915/skl_guc_33.0.0.bin * i915/tgl_dmc_ver2_04.bin * i915/tgl_huc_7.5.0.bin * isdbt_nova_12mhz.inp * isdbt_nova_12mhz_b0.inp * isdbt_rio.inp * iwlwifi-Qu-b0-hr-b0-59.ucode * iwlwifi-Qu-b0-jf-b0-50.ucode * iwlwifi-Qu-b0-jf-b0-59.ucode * iwlwifi-Qu-c0-hr-b0-50.ucode * iwlwifi-Qu-c0-hr-b0-59.ucode * iwlwifi-QuZ-a0-hr-b0-50.ucode * iwlwifi-QuZ-a0-hr-b0-59.ucode * iwlwifi-QuZ-a0-jf-b0-50.ucode * iwlwifi-QuZ-a0-jf-b0-59.ucode * iwlwifi-cc-a0-50.ucode * iwlwifi-cc-a0-59.ucode * mediatek/mt7663pr2h.bin * mellanox/mlxsw_spectrum-13.2000.1886.mfa2 * mellanox/mlxsw_spectrum-13.2008.1310.mfa2 * mellanox/mlxsw_spectrum2-29.2008.1310.mfa2 * mellanox/mlxsw_spectrum3-30.2008.1310.mfa2 * mrvl/sdsd8977_combo_v2.bin * mrvl/sdsd8997_combo_v4.bin * rtl_nic/rtl8125a-3.fw * rtl_nic/rtl8168fp-3.fw * rtw88/rtw882
[Kernel-packages] [Bug 1914411] Re: Fix broken efifb on graphics device without driver
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1914411 Title: Fix broken efifb on graphics device without driver Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux-oem-5.10 source package in Groovy: Invalid Bug description: [Impact] EFIFB stops working after graphics device is runtime suspended in D3cold. [Fix] Prevent the graphics device from being runtime suspended. [Test] With the patch applied, using efifb on graphics device without driver always work, because the device stays at D0 all the time. [Where problems could occur] Potentially this can affect power consumption, if user expects to put graphics device to D3cold, and is fine to get a broken efifb. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1914411/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921902] Re: Security-Fix Xen XSA 371 for Kernel 5.4.0-71
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1921902
Title:
Security-Fix Xen XSA 371 for Kernel 5.4.0-71
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
In Progress
Bug description:
[SRU Justification]
See [XSA 371](http://xenbits.xen.org/xsa/advisory-371.html). commit
871997bc9e423f05c7da7c9178e62dde5df2a7f8 ("xen-blkback: fix error
handling in xen_blkbk_map()") introduced a security vulnerability.
Original Commit:
871997bc9e423f05c7da7c9178e62dde5df2a7f8 ("xen-blkback: fix error handling in
xen_blkbk_map()")
New commit with security fix:
a846738f8c3788d846ed1f587270d2f2e3d32432 ("xen-blkback: don't leak persistent
grants from xen_blkbk_map()")
[Test Plan]
none
[Where problems could occur]
Unknown
[Other Info]
- http://xenbits.xen.org/xsa/advisory-371.html
- http://xenbits.xen.org/xsa/xsa371-linux.patch
- http://xenbits.xen.org/xsa/advisory-365.html
- http://xenbits.xen.org/xsa/xsa365-linux.patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921902/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1916908] Re: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1916908 Title: Update the 460 driver, make switching between driver series more robust, and add support for Linux 5.11 Status in linux package in Ubuntu: In Progress Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-418-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-450-server package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-460-server package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-418-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460-server source package in Bionic: Fix Released Status in linux source package in Focal: In Progress Status in nvidia-graphics-drivers-390 source package in Focal: Fix Released Status in nvidia-graphics-drivers-418-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-450 source package in Focal: Fix Released Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-460-server source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Status in nvidia-graphics-drivers-390 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-418-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460-server source package in Groovy: Fix Released Bug description: Update the 460 driver, make switching between driver series more robust (LP: #1915935), and add support for Linux 5.11 [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 460 == * New upstream release (LP: #1916908): - Added support for the following GPUs: GeForce RTX 3060 - Fixed a bug with indexed ray payloads in Vulkan. - Fixed a bug where calls to vkCreateDevice could fail on Ampere GPUs when ray tracing extensions were enabled and the application was running within the Steam Linux Runtime. - Fixed a regression that could cause display corruption when using a scaled resolution after resuming from power management suspend. * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). - Advertise support for cuda-11.2-1. == 460-server == * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless (LP: #1915935). * debian/templates/dkms_nvidia.conf.in, debian/dkms_nvidia/patches/buildfix_kernel_5.11.patch: - Add support for Linux 5.11 (LP: #1916908). == 450 / 450-server == * debian/templates/control.in: - Add missing conflict/replace/provide for libnvidia-common, nvidia-compute-utils, libnvidia-compute, and nvidia-headless
[Kernel-packages] [Bug 1933074] Re: large_dir in ext4 broken
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933074 Title: large_dir in ext4 broken Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Triaged Bug description: == SRU, Bionic, Focal, Groovy, Hirsute, Impish == [Impact] Creating millions of files on ext4 partition with large_dir support by touching them will eventually trip an ext4 leaf node issue in the index hash. This occurs more frequently when also using smaller block sizes and ends up either with a EXIST or EUCLEAN failure. This occurs on the restart condition when performing do_split. [ Fix ] The fix protects do_split() from the restart condition, making it safe from both current and future ordering of goto statements in earlier sections of the code. The fix is from a patch sent upstream and cc'd to Ted Tso but didn't appear on the ext4 mailing list presumably because it got marked as SPAM. [ Test Case ] Without the fix touching tens of thousands of empty files will trip the issue. It seems to occur more frequently with memory pressure and smaller block sizes, e.g.: sudo mkdir -p /mnt/tmpfs /mnt/storage sudo mount -t tmpfs -o size=9000M tmpfs /mnt/tmpfs sudo dd if=/dev/urandom of=/mnt/tmpfs/ext4.img bs=1M sudo mkfs.ext4 -O large_dir -N 2100 -O dir_index /mnt/tmpfs/ext4.img -b 1024 -F sudo mount /mnt/tmpfs/ext4.img /mnt/storage and compile and run the attached C program (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933074/+attachment/5509402/+files/touch.c) that quickly populates /mnt/storage with empty files. Without the fix this will terminate with an -EEXIST or -EUCLEAN error on the file creation after several tens of thousands of files. [Where problems could occur] This changes the behaviour of the directory indexing hashing so there is a regression potential that this may introduce subsequent index hashing issues when needed (or not) to do a split. This patch seems to cover all the necessary cases, so I believe this risk is relatively low. I have also tested this on all the kernel series in the SRU with 21,000,000 files so I am confident we have enough test coverage to show the fix is OK. -- I believe, I found a bug in ext4 in recent kernel versions. I stumbled across this while I was trying to restore a backup to a new VM. How to reproduce this bug: 1. Use a virtual/physical machine with "Ubuntu 18.04.5 LTS" and kernel version 4.15.0-144-generic. 2. add a secondary disk to hold the test files. 3. prepare and mount the filesystem with enabled 'large_dir' flag: mkfs.ext4 -m0 /dev/sdb1; tune2fs -O large_dir /dev/sdb1; mkdir /mnt/storage; mount /dev/sdb1 /mnt/storage; 4. change to directory and create approx. 16 mio files cd /mnt/storage; i=0; while (( $i < 2000 )); do i=$(( $i + 1 )); (( $i % 1000 == 0 )) && echo $i; touch file_$i.dat || break; done Expected behaviour: - 20 mio files shoud be created without error What happened instead: - The loop aborts with an error message: # 16263100 # touch: cannot touch 'file_16263173.dat': Structure needs cleaning - dmesg gives a little more details: # [Mon Jun 21 03:15:18 2021] EXT4-fs error (device sdb): dx_probe:855: inode #2: block 146221: comm touch: directory leaf block found instead of index block Additional notes: - This occurs on kernel version 4.15.0-144-generic - Not sure, but I believe one test was run on 4.15.0-143-generic and failed too. - Did not check against 4.15.0-142-generic - On 4.15.0-141-generic, the problem does not exist. Behaviour is as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933074/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux (Ubuntu Groovy)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
Fix Released
Status in fabric-manager-460 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux-restricted-modules source package in Groovy:
Won't Fix
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
Won't Fix
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update includes fixes for the following CVEs:
CVE-2021-1093
CVE-2021-1094
CVE-2021-1095
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-450
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: nvidia-graphics-drivers-465 (Ubuntu Groovy)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
Fix Released
Status in fabric-manager-460 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux-restricted-modules source package in Groovy:
Won't Fix
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
Won't Fix
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update includes fixes for the following CVEs:
CVE-2021-1093
CVE-2021-1094
CVE-2021-1095
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
[Kernel-packages] [Bug 1934110] Re: ubuntu-host driver lacks lseek ops
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux (Ubuntu Groovy)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1934110
Title:
ubuntu-host driver lacks lseek ops
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Groovy:
Won't Fix
Status in linux source package in Hirsute:
Fix Committed
Bug description:
[ SRU Justification ][GROOVY][HIRSUTE][IMPISH]
== Impact ==
The ubuntu-host driver lacks procfs lseek ops and lseeking on the
procfs esm-token file will jump to a NULL address causing the
following splat:
942.470568] BUG: kernel NULL pointer dereference, address:
[ 942.471157] #PF: supervisor instruction fetch in kernel mode
[ 942.471724] #PF: error_code(0x0010) - not-present page
[ 942.472297] PGD 0 P4D 0
[ 942.472867] Oops: 0010 [#1] SMP PTI
[ 942.473435] CPU: 2 PID: 5661 Comm: stress-ng Not tainted 5.13.0-9-generic
#9
[ 942.474012] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0
02/06/2015
[ 942.474599] RIP: 0010:0x0
[ 942.475194] Code: Unable to access opcode bytes at RIP 0xffd6.
[ 942.475792] RSP: 0018:aacf80ff7eb8 EFLAGS: 00010246
[ 942.476383] RAX: RBX: 9eaa8a175240 RCX:
0001
[ 942.476986] RDX: RSI: RDI:
9eaa838d5800
[ 942.477600] RBP: aacf80ff7ed0 R08: 4000 R09:
0004
[ 942.478203] R10: 0002 R11: R12:
[ 942.478800] R13: R14: ffea R15:
9eaa838d5800
[ 942.479399] FS: 7f998d487f00() GS:9eaaffc8()
knlGS:
[ 942.480006] CS: 0010 DS: ES: CR0: 80050033
[ 942.480607] CR2: ffd6 CR3: 00010a774002 CR4:
00370ee0
[ 942.481219] DR0: DR1: DR2:
[ 942.481855] DR3: DR6: fffe0ff0 DR7:
0400
[ 942.482458] Call Trace:
[ 942.483052] proc_reg_llseek+0x4e/0x80
[ 942.483646] ? __fdget_pos+0x43/0x50
[ 942.484234] ksys_lseek+0x84/0xc0
[ 942.484815] __x64_sys_lseek+0x1a/0x20
[ 942.485412] do_syscall_64+0x61/0xb0
[ 942.485966] ? asm_exc_page_fault+0x8/0x30
[ 942.486476] entry_SYSCALL_64_after_hwframe+0x44/0xae
[ 942.486994] RIP: 0033:0x7f998d5c1cdb
[ 942.487512] Code: ff ff c3 0f 1f 40 00 48 8b 15 89 81 0d 00 f7 d8 64 89 02
48 c7 c0 ff ff ff ff eb ba 0f 1f 00 f3 0f 1e fa b8 08 00 00 00 0f 05 <48> 3d 00
f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 59 81 0d 00 f7 d8
[ 942.488593] RSP: 002b:7ffdf61c5328 EFLAGS: 0246 ORIG_RAX:
0008
[ 942.489148] RAX: ffda RBX: RCX:
7f998d5c1cdb
[ 942.489710] RDX: RSI: RDI:
0004
[ 942.490252] RBP: 0004 R08: 01785e4740dd R09:
562dbebb9e50
[ 942.490801] R10: 7ffdf61c5300 R11: 0246 R12:
7ffdf61c63f0
[ 942.491354] R13: 7ffdf61c53f0 R14: 0003 R15:
01e9
== Fix ==
Add the default_llseek ops:
diff --git a/ubuntu/ubuntu-host/ubuntu-host.c
b/ubuntu/ubuntu-host/ubuntu-host.c
index 1abd402..a4c0636 100644
--- a/ubuntu/ubuntu-host/ubuntu-host.c
+++ b/ubuntu/ubuntu-host/ubuntu-host.c
@@ -38,6 +38,8 @@ static ssize_t esm_token_write(struct file *f, const char
__user *buf,
static const struct proc_ops esm_token_fops = {
.proc_read = esm_token_read,
.proc_write = esm_token_write,
+ .proc_lseek = default_llseek,
+
};
== Test plan ==
modrobe ubuntu-host
stress-ng --procfs 0 -t 60
without the fix we hit the splat. With the fix it's OK.
== Where problems could occur ==
This one liner adds the missing proc_lseek op. It is hard to see where
it can cause a regression since it affects the driver no other way. I
doubt any code is relying on the current semantics of lseek not
working.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934110/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933980] Re: NVIDIA CVE-2021-{1093|1094|1094}
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux-restricted-modules (Ubuntu Groovy)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1933980
Title:
NVIDIA CVE-2021-{1093|1094|1094}
Status in fabric-manager-450 package in Ubuntu:
Fix Released
Status in fabric-manager-460 package in Ubuntu:
Fix Released
Status in libnvidia-nscq-450 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
New
Status in linux-restricted-modules package in Ubuntu:
Triaged
Status in nvidia-graphics-drivers-390 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-418-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-450-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-460-server package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-465 package in Ubuntu:
In Progress
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in fabric-manager-450 source package in Bionic:
Fix Released
Status in fabric-manager-460 source package in Bionic:
Fix Released
Status in libnvidia-nscq-450 source package in Bionic:
Fix Released
Status in linux source package in Bionic:
Triaged
Status in linux-restricted-modules source package in Bionic:
Triaged
Status in nvidia-graphics-drivers-390 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Bionic:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Bionic:
In Progress
Status in nvidia-settings source package in Bionic:
Fix Released
Status in fabric-manager-450 source package in Focal:
Fix Released
Status in fabric-manager-460 source package in Focal:
Fix Released
Status in libnvidia-nscq-450 source package in Focal:
Fix Released
Status in linux source package in Focal:
Triaged
Status in linux-restricted-modules source package in Focal:
Triaged
Status in nvidia-graphics-drivers-390 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Focal:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Focal:
In Progress
Status in nvidia-settings source package in Focal:
Fix Released
Status in fabric-manager-450 source package in Groovy:
Fix Released
Status in fabric-manager-460 source package in Groovy:
Fix Released
Status in libnvidia-nscq-450 source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Won't Fix
Status in linux-restricted-modules source package in Groovy:
Won't Fix
Status in nvidia-graphics-drivers-390 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Groovy:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Groovy:
Won't Fix
Status in nvidia-settings source package in Groovy:
Fix Released
Status in fabric-manager-450 source package in Hirsute:
Fix Released
Status in fabric-manager-460 source package in Hirsute:
Fix Released
Status in libnvidia-nscq-450 source package in Hirsute:
Fix Released
Status in linux source package in Hirsute:
Triaged
Status in linux-restricted-modules source package in Hirsute:
Triaged
Status in nvidia-graphics-drivers-390 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-418-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-450-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460 source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-460-server source package in Hirsute:
Fix Released
Status in nvidia-graphics-drivers-465 source package in Hirsute:
In Progress
Status in nvidia-settings source package in Hirsute:
Fix Released
Bug description:
As per the subject, the update includes fixes for the following CVEs:
CVE-2021-1093
CVE-2021-1094
CVE-2021-1095
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source
[Kernel-packages] [Bug 1871306] Re: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf)
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1871306 Title: [SRU] No sound from internal card chtmax98090 (missing UCM2 files in alsa-ucm-conf) Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: In Progress Status in alsa-ucm-conf source package in Groovy: Won't Fix Bug description: [Impact] There is no ucm for ASUS C300 in the 20.04 and 20.10, as a result, the audio doesn't work on this machine after installing the 20.04 or 20.10. [Fix] The ucm files for this machine are in the alsa-ucm-conf 1.2.3, cherry-pick them to ubuntu 20.04 and 20.10 [Test Case] After booting up, use speaker to play some sound, it works well, plug a headset, play sound to headphone, it basically works but has some crankling noise, it is a kernel issue for this noise. [Regression Risk] This SRU adds new ucm files, If the machine uses the audio driver of chtmax98090, it will apply this new added ucm files, there will be speaker/headphone in the UI. So the possible regression is with this SRU, users could see the audio devices in the UI but the audio doesn't work (without this SRU, users couldn't see the audio devices in the UI at all and the audio doesn't work). This possibility is low since we tested it on the ASUS C300. Asus C300 (repurposed chromembook - bios flashed by Mr.Chromebox script) - Kubuntu Focal minimal fresh installation. The sound card is detected: I see it in the Plasma Widget, in pavucontrol, in alsamixer and it's not muted. I tried and add in /usr/share/alsa/ucm/chtmax98090/ the old style use case config files: no success. I tried and unmute speakers left and right in alsamixer: no success. I rapidly tested Ubuntu Mate Focal fresh install: I had exactly the same issue. I'm running on the same rig Debian Bullseye, kernel 5.4: sound card output and input are both working perfectly - I noticed that in Kubuntu alsamixer Kubuntu when I open it I have an entry HDA IntelPCH (the HDMI card), while in Debian I find Pulseaudio. I attach the alsa-info.sh output. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.17 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Apr 7 08:55:46 2020 InstallationDate: Installed on 2020-04-04 (2 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gabriel3937 F pulseaudio /dev/snd/controlC0: gabriel3937 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-04 (3 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:07dc Intel Corp. Bus 001 Device 003: ID 13d3:5657 IMC Networks USB2.0 UVC HD Webcam Bus 001 Device 002: ID 062a:4101 MosArt Semiconductor Corp. Wireless Keyboard/Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Quawks Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=225cba91-c164-4882-95d4-4f9854a80fe9 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/17/2020 dmi.bios.vendor: coreboot dmi.bios.version: MrChromebox-4.11.2 dmi.board.name: Quawks dmi.board.vendor: GOOGLE dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.11.2:bd03/17/2020:svnGOOGLE:pnQuawks:pvr1.0:rvnGOOGLE:rnQuawks:rvr1.0:cvnGOOGLE:ct9:cvr: dmi.product.name: Quawks dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https:/
[Kernel-packages] [Bug 1893002] Re: alsa-ucm-conf: the rear mic on Lenovo p520 can't be detected when hot plugging
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1893002 Title: alsa-ucm-conf: the rear mic on Lenovo p520 can't be detected when hot plugging Status in alsa-ucm-conf package in Ubuntu: New Status in alsa-ucm-conf source package in Focal: New Status in alsa-ucm-conf source package in Groovy: Won't Fix Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1893002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908503] Re: arm64: prevent losing page dirty state
The Groovy Gorilla has reached end of life, so this bug will not be
fixed for that release
** Changed in: linux-aws (Ubuntu Groovy)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1908503
Title:
arm64: prevent losing page dirty state
Status in linux-aws package in Ubuntu:
New
Status in linux-aws source package in Bionic:
Fix Released
Status in linux-aws source package in Focal:
Fix Released
Status in linux-aws source package in Groovy:
Won't Fix
Status in linux-aws source package in Hirsute:
New
Bug description:
[Impact]
With hardware dirty bit management enabled calling pte_wrprotect() on
a dirty PTE will clean the dirty state without flushing the content of
the page to the backing store.
[Test case]
Bug reported by Amazon, a specific test case is not provided. This
problem has been hit by a customer.
[Fix]
Apply commit:
ff1712f953e27f0b0718762ec17d0adb15c9fd0b ("arm64: pgtable: Ensure dirty bit
is preserved across pte_wrprotect()")
Backport activity is minimal, it only requires to adjust the context a
bit to remove the previous pte_wrprotect() implementation.
[Regression potential]
The fix is specific for arm64 pgtable, it is an upstream fix also
marked for stable. The only potential downside could be the extra
overhead introduced by the additional call to pte_mkdirty() in
pte_wrprotect(), so worst case scenario it could introduce a
performance regression. It doesn't seem to potentially introduce any
other kind of regression / breakage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908503/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910965] Re: riscv: backport support for SiFive Unmatched
The Groovy Gorilla has reached end of life, so this bug will not be fixed for that release ** Changed in: linux (Ubuntu Groovy) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910965 Title: riscv: backport support for SiFive Unmatched Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: New Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Fix Released Bug description: == SRU Justifcation Groovy/RISCV == The SiFive HiFive Unmatched board should be supported as well as the current Unleashed. There are various upstream commits for this support and some misc fixes for the Unleashed and Unmatched that are required for this board support. == The fix(es) == The following changes since commit 7295e646e91b648b7f45b4f36eba14bfe59dd3f6: UBUNTU: Ubuntu-riscv-5.8.0-13.15 (2020-12-15 10:33:23 +0100) are available in the Git repository at: https://git.launchpad.net/~colin-king/+git/ubuntu-riscv-groovy for you to fetch changes up to 86de0730500269fee8b71fcb1be29193455c3be7: UBUNTU: [Config] Align configs with Unleashed defconfigs (2021-01-11 09:37:13 +) Colin Ian King (1): UBUNTU: [Config] Align configs with Unleashed defconfigs David Abdurachmanov (5): PCI: microsemi: Add host driver for Microsemi PCIe controller Microsemi PCIe expansion board DT entry. HACK: Revert "of/device: Really only set bus DMA mask when appropriate" SiFive Unleashed CPUFreq SiFive HiFive Unleashed: Add PWM LEDs (D1, D2, D3, D4) Greentime Hu (2): irqchip/sifive-plic: Fix broken irq_set_affinity() callback irqchip/sifive-plic: Fix getting wrong chip_data when interrupt is hierarchy Pragnesh Patel (1): clk: sifive: Add clock enable and disable ops Rob Herring (2): dt-bindings: More whitespace clean-ups in schema files dt-bindings: Explicitly allow additional properties in board/SoC schemas Sagar Kadam (2): dt-bindings: riscv: sifive-l2-cache: convert bindings to json-schema dt-bindings: riscv: convert pwm bindings to json-schema Sagar Shrikant Kadam (1): i2c: ocores: fix polling mode workaround on FU540-C000 SoC Yash Shah (6): RISC-V: Update l2 cache DT documentation to add support for SiFive FU740 RISC-V: sifive_l2_cache: Update L2 cache driver to support SiFive FU740 dt-bindings: riscv: Update DT binding docs to support SiFive FU740 SoC riscv: dts: add initial support for the SiFive FU740-C000 SoC dt-bindings: riscv: Update YAML doc to support SiFive HiFive Unmatched board riscv: dts: add initial board data for the SiFive HiFive Unmatched Zong Li (5): clk: sifive: Extract prci core to common base clk: sifive: Use common name for prci configuration clk: sifive: Add a driver for the SiFive FU740 PRCI IP block clk: sifive: Fix the wrong bit field shift dt-bindings: fu740: prci: add YAML documentation for the FU740 PRCI Documentation/devicetree/bindings/clock/sifive/fu740-prci.yaml | 60 Documentation/devicetree/bindings/gpio/sifive,gpio.yaml| 4 +- Documentation/devicetree/bindings/i2c/i2c-ocores.txt | 6 +- Documentation/devicetree/bindings/pwm/pwm-sifive.txt | 33 --- Documentation/devicetree/bindings/pwm/pwm-sifive.yaml | 72 + Documentation/devicetree/bindings/riscv/cpus.yaml | 6 + Documentation/devicetree/bindings/riscv/sifive-l2-cache.txt| 51 Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml | 127 + Documentation/devicetree/bindings/riscv/sifive.yaml| 20 +- Documentation/devicetree/bindings/serial/sifive-serial.yaml| 4 +- Documentation/devicetree/bindings/spi/spi-sifive.yaml | 10 +- arch/riscv/Kconfig | 8 + arch/riscv/Kconfig.socs| 2 +- arch/riscv/boot/dts/sifive/Makefile| 3 +- arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 5 + arch/riscv/boot/dts/sifive/fu740-c000.dtsi | 293 +++ arch/riscv/boot/dts/sifive/hifive-unleashed-a00-microsemi.dts | 28 ++ arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts| 66 + arch/riscv/boot/dts/sifive/hifive-unmatched-a00.dts| 253 + arch/riscv/configs/defconfig | 5 + debian.riscv/config/annotations| 17 +- debian.riscv/config/config.common.ubuntu
[Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu
The changes in ubuntu9.1 did make it into impish in ubuntu10. https://launchpadlibrarian.net/538731561/u-boot_2021.01+dfsg-3ubuntu9_2021.01+dfsg-3ubuntu10.diff.gz However, it looks like they were later removed from impish. https://launchpadlibrarian.net/539465636/u-boot_2021.01+dfsg-3ubuntu10_2021.01+dfsg-4ubuntu1.diff.gz -- 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/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: Fix Committed Status in u-boot-menu source package in Focal: Fix Committed Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: Confirmed Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938076] Re: sporadic system freeze after log in
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938076 Title: sporadic system freeze after log in Status in linux package in Ubuntu: New Bug description: With kernel Linux version 5.4.0-77-lowlatency (buildd@lgw01-amd64-028) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #86-Ubuntu SMP PREEMPT Thu Jun 17 03:26:36 UTC 2021 (Ubuntu 5.4.0-77.86-lowlatency 5.4.119) in Ubuntustudio I got two system freezes (video frozen, mouse and keyboard without function) some seconds after login in the last days. In the journal I see in both cases a kernel error referring to drm_kms: - Jul 26 20:26:21 marco-MS-7817 kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:42:pipe A] flip_done timed out Jul 26 20:26:22 marco-MS-7817 systemd[1]: systemd-fsckd.service: Succeeded. Jul 26 20:26:21 marco-MS-7817 systemd-timesyncd[667]: Initial synchronization to time server 91.189.94.4:123 (ntp.ubuntu.com). Jul 26 20:26:21 marco-MS-7817 systemd[1]: Starting Daily apt upgrade and clean activities... Jul 26 20:26:21 marco-MS-7817 systemd[1]: systemd-hostnamed.service: Succeeded. Jul 26 20:26:22 marco-MS-7817 systemd[1]: blueman-mechanism.service: Succeeded. Jul 26 20:26:23 marco-MS-7817 systemd[1]: apt-daily-upgrade.service: Succeeded. Jul 26 20:26:23 marco-MS-7817 systemd[1]: Finished Daily apt upgrade and clean activities. Jul 26 20:26:27 marco-MS-7817 autojack[2631]: JACK MIDI <-> ALSA sequencer MIDI bridge, version 9 built on Sun Oct 13 18:36:50 2019 Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Copyright 2006,2007 Dmitry S. Baikov Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Copyright 2007,2008,2009,2011,2012 Nedko Arnaudov Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Bridge starting... Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Using JACK server 'default' Jul 26 20:26:27 marco-MS-7817 autojack[2631]: Hardware ports will be exported. Jul 26 20:26:32 marco-MS-7817 autojack[2631]: Cannot read socket fd = 6 err = Success Jul 26 20:26:32 marco-MS-7817 autojack[2631]: CheckRes error Jul 26 20:26:32 marco-MS-7817 autojack[2631]: JackSocketClientChannel read fail Jul 26 20:26:32 marco-MS-7817 autojack[2631]: Cannot open a2j client Jul 26 20:26:32 marco-MS-7817 autojack[2631]: JackShmReadWritePtr1::~JackShmReadWritePtr1 - Init not done for -1, skipping unlock Jul 26 20:26:32 marco-MS-7817 autojack[2631]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock Jul 26 20:26:32 marco-MS-7817 autojack[2631]: JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock Jul 26 20:26:32 marco-MS-7817 autojack[2631]: ERROR: a2j_jack_client_create: Cannot create jack client Jul 26 20:26:32 marco-MS-7817 autojack[2631]: ERROR: a2j_start: a2j_new() failed. Jul 26 20:27:04 marco-MS-7817 kernel: rcu: INFO: rcu_preempt self-detected stall on CPU Jul 26 20:27:04 marco-MS-7817 kernel: rcu: 0-: (60004 ticks this GP) idle=7ca/1/0x4002 softirq=23094/23094 fqs=14881 Jul 26 20:27:04 marco-MS-7817 kernel: (t=6 jiffies g=11765 q=87882) Jul 26 20:27:04 marco-MS-7817 kernel: NMI backtrace for cpu 0 Jul 26 20:27:04 marco-MS-7817 kernel: CPU: 0 PID: 2446 Comm: jackdbus Tainted: G OE 5.4.0-77-lowlatency #86-Ubuntu Jul 26 20:27:04 marco-MS-7817 kernel: Hardware name: MSI MS-7817/H81M-E34 (MS-7817), BIOS V17.5 03/30/2015 Jul 26 20:27:04 marco-MS-7817 kernel: Call Trace: Jul 26 20:27:04 marco-MS-7817 kernel: Jul 26 20:27:04 marco-MS-7817 kernel: dump_stack+0x6d/0x8b Jul 26 20:27:04 marco-MS-7817 kernel: ? lapic_can_unplug_cpu+0x80/0x80 Jul 26 20:27:04 marco-MS-7817 kernel: nmi_cpu_backtrace.cold+0x14/0x53 Jul 26 20:27:04 marco-MS-7817 kernel: nmi_trigger_cpumask_backtrace+0xfa/0x110 Jul 26 20:27:04 marco-MS-7817 kernel: arch_trigger_cpumask_backtrace+0x19/0x20 Jul 26 20:27:04 marco-MS-7817 kernel: rcu_dump_cpu_stacks+0x99/0xcb Jul 26 20:27:04 marco-MS-7817 kernel: rcu_sched_clock_irq.cold+0x25e/0x4f0 Jul 26 20:27:04 marco-MS-7817 kernel: update_process_times+0x2c/0x60 Jul 26 20:27:04 marco-MS-7817 kernel: tick_sched_handle+0x29/0x60 Jul 26 20:27:04 marco-MS-7817 kernel: tick_sched_timer+0x3d/0x80 Jul 26 20:27:04 marco-MS-7817 kernel: __hrtimer_run_queues+0xf7/0x2c0 Jul 26 20:27:04 marco-MS-7817 kernel: ? tick_sched_do_timer+0x60/0x60 Jul 26 20:27:04 marco-MS-7817 kernel: hrtimer_interrupt+0x109/0x220 Jul 26 20:27:04 marco-MS-7817 kernel: smp_apic_timer_interrupt+0x71/0x170 Jul 26 20:27:04 marco-MS-7817 kernel: apic_timer_interrupt+0xf/0x20 Jul 26 20:27:04 marco-MS-7817 kernel: Jul 26 20:27:04 marco-MS-7817 kernel: RIP: 00
[Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu
I'm sorry to be a bother here but I don't understand how u-boot failed verification for hirsute but passed for focal when what are presumably the same patches exist in both versions of the package. How could this happen? -- 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/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: Fix Committed Status in u-boot-menu source package in Focal: Fix Committed Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: Confirmed Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932165] Re: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
I went ahead and uploaded the version number that makes me happier to the PPA (https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4630) but it seems to have only built for amd64. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932165 Title: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in lttng-modules package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in lttng-modules source package in Focal: Confirmed Bug description: [Impact] lttng-modules-dkms is reporting many build errors with linux-hwe-5.11, because of many kernel ABI changes. [Fix] Backporting the individual patches to fix all the build errors would be a lot of work and the risk to introduce regressions would be pretty high, therefore it seems safer to update to the version that is also used in impish, that works with 5.11 and it's backward compatible (so it works also with 5.4). [Test] ubuntu_lttng_smoke_test from (git://kernel.ubuntu.com/ubuntu/autotest- client-tests) [Where problems could occur] This is a major version update, so it does not contain trivial changes as backporting individual patches/fixes, so there's a risk to see regressions with lttng (however potential regressions are *only* limited to lttng). However, this way is definitely safer than backporting all the individual changes to fix the all the kernel ABI changes introduced in 5.11. [Original bug report] This is a scripted bug report about ADT failures while running lttng- modules tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210611_205859_b8295@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923638] Please test proposed package
*** This bug is a duplicate of bug 1932163 *** https://bugs.launchpad.net/bugs/1932163 Hello Seth, or anyone else affected, Accepted evdi into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evdi/1.9.1-1ubuntu4~20.04.1 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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923638 Title: [FFe] evdi/1.7.0+dfsg-1ubuntu2 fails to build with linux 5.11 Status in evdi package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in evdi source package in Focal: Fix Committed Bug description: evdi-dkms in hirsute cannot be used with the 5.11 kernel in hirsute as it will fail to build. Upstream updates for 5.11 proved problematic, and a working set of updates became available in the upstream project only recently. Unfortunately these updates are difficult to backport due to upstream changes, and if they are backported the kernel team has no access to hardware to confirm that the backports function as intended. Therefore the safest course of action seems to be to move forward to the latest upstream evdi release plus they fixes for 5.11 from git, which has been tested by a number of evdi users already. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evdi/+bug/1923638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932165] Re: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
I think a more appropriate and less confusing version number would be 2.12.5-1ubuntu2~20.04.1 given that its a backport of 2.12.5-1ubuntu2 (in Impish) and ~20.04.1 since its the appearance of 2.12.5 in Focal. Additionally, are there any plans to update the version of lttng-modules in Hirsute? I ask given that Ubuntu 20.04 LTS systems will be able to upgrade Ubuntu 21.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932165 Title: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in lttng-modules package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in lttng-modules source package in Focal: Confirmed Bug description: [Impact] lttng-modules-dkms is reporting many build errors with linux-hwe-5.11, because of many kernel ABI changes. [Fix] Backporting the individual patches to fix all the build errors would be a lot of work and the risk to introduce regressions would be pretty high, therefore it seems safer to update to the version that is also used in impish, that works with 5.11 and it's backward compatible (so it works also with 5.4). [Test] ubuntu_lttng_smoke_test from (git://kernel.ubuntu.com/ubuntu/autotest- client-tests) [Where problems could occur] This is a major version update, so it does not contain trivial changes as backporting individual patches/fixes, so there's a risk to see regressions with lttng (however potential regressions are *only* limited to lttng). However, this way is definitely safer than backporting all the individual changes to fix the all the kernel ABI changes introduced in 5.11. [Original bug report] This is a scripted bug report about ADT failures while running lttng- modules tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210611_205859_b8295@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937946] Re: Kernel hangs
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1937946 Title: Kernel hangs Status in linux package in Ubuntu: New Bug description: tim@timpc:~/Dokumente/nbased-gui$ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 This is probably the relevant part from /var/log/kern.log Jul 25 16:34:24 timpc kernel: [16627.134024] BUG: kernel NULL pointer dereference, address: Jul 25 16:34:24 timpc kernel: [16627.134028] #PF: supervisor write access in kernel mode Jul 25 16:34:24 timpc kernel: [16627.134030] #PF: error_code(0x0002) - not-present page Jul 25 16:34:24 timpc kernel: [16627.134031] PGD 0 P4D 0 Jul 25 16:34:24 timpc kernel: [16627.134035] Oops: 0002 [#1] SMP NOPTI Jul 25 16:34:24 timpc kernel: [16627.134038] CPU: 4 PID: 3506 Comm: Timer Tainted: G OE 5.4.0-80-generic #90-Ubuntu Jul 25 16:34:24 timpc kernel: [16627.134040] Hardware name: Gigabyte Technology Co., Ltd. B450 AORUS PRO/B450 AORUS PRO-CF, BIOS F2 08/08/2018 Jul 25 16:34:24 timpc kernel: [16627.134046] RIP: 0010:rb_erase+0x241/0x370 Jul 25 16:34:24 timpc kernel: [16627.134049] Code: 3b 79 10 0f 84 94 00 00 00 4c 89 41 08 4d 85 c0 75 4c a8 01 0f 85 72 fe ff ff c3 48 89 cf 48 89 51 10 48 83 cf 01 48 89 48 08 <48> 89 3a 48 8b 39 48 89 38 48 89 01 48 83 e7 fc 74 6a 48 3b 4f 10 Jul 25 16:34:24 timpc kernel: [16627.134051] RSP: 0018:9b6008727c60 EFLAGS: 00010086 Jul 25 16:34:24 timpc kernel: [16627.134053] RAX: 8fc2bee1e4a0 RBX: 9b6008727d30 RCX: 9b6008277db0 Jul 25 16:34:24 timpc kernel: [16627.134054] RDX: RSI: 8fc2bee1dfe0 RDI: 9b6008277db1 Jul 25 16:34:24 timpc kernel: [16627.134056] RBP: 9b6008727c78 R08: R09: Jul 25 16:34:24 timpc kernel: [16627.134057] R10: 8fc2bed29ac0 R11: 8fc2bed29aa0 R12: 8fc2bee1dfe0 Jul 25 16:34:24 timpc kernel: [16627.134058] R13: R14: 8fc2bee1df80 R15: Jul 25 16:34:24 timpc kernel: [16627.134060] FS: 7f082ae56700() GS:8fc2bed0() knlGS: Jul 25 16:34:24 timpc kernel: [16627.134061] CS: 0010 DS: ES: CR0: 80050033 Jul 25 16:34:24 timpc kernel: [16627.134063] CR2: CR3: 000738206000 CR4: 003406e0 Jul 25 16:34:24 timpc kernel: [16627.134064] Call Trace: Jul 25 16:34:24 timpc kernel: [16627.134067] ? timerqueue_del+0x24/0x50 Jul 25 16:34:24 timpc kernel: [16627.134073] __remove_hrtimer+0x3c/0x90 Jul 25 16:34:24 timpc kernel: [16627.134076] hrtimer_try_to_cancel+0xb7/0x110 Jul 25 16:34:24 timpc kernel: [16627.134078] hrtimer_cancel+0x15/0x20 Jul 25 16:34:24 timpc kernel: [16627.134082] futex_wait+0x21b/0x290 Jul 25 16:34:24 timpc kernel: [16627.134085] ? hrtimer_init_sleeper+0x90/0x90 Jul 25 16:34:24 timpc kernel: [16627.134088] do_futex+0x157/0x4d0 Jul 25 16:34:24 timpc kernel: [16627.134092] ? _copy_from_user+0x3e/0x60 Jul 25 16:34:24 timpc kernel: [16627.134095] __x64_sys_futex+0x13f/0x170 Jul 25 16:34:24 timpc kernel: [16627.134099] do_syscall_64+0x57/0x190 Jul 25 16:34:24 timpc kernel: [16627.134102] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jul 25 16:34:24 timpc kernel: [16627.134105] RIP: 0033:0x7f083c67d7b1 Jul 25 16:34:24 timpc kernel: [16627.134107] Code: 01 00 00 e8 51 38 00 00 4c 8b 54 24 18 8b 74 24 40 31 d2 89 44 24 44 41 b9 ff ff ff ff 45 31 c0 4c 89 f7 b8 ca 00 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 73 01 00 00 8b 7c 24 44 e8 7a 38 00 00 31 Jul 25 16:34:24 timpc kernel: [16627.134109] RSP: 002b:7f082ae55980 EFLAGS: 0246 ORIG_RAX: 00ca Jul 25 16:34:24 timpc kernel: [16627.134111] RAX: ffda RBX: 7f0830636e48 RCX: 7f083c67d7b1 Jul 25 16:34:24 timpc kernel: [16627.134112] RDX: RSI: 0089 RDI: 7f0830636e60 Jul 25 16:34:24 timpc kernel: [16627.134113] RBP: 7f0830636e38 R08: R09: Jul 25 16:34:24 timpc kernel: [16627.134114] R10: 7f082ae55a68 R11: 0246 R12: 7f0830636e5c Jul 25 16:34:24 timpc kernel: [16627.134115] R13: 7f0830636e08 R14: 7f0830636e60 R15: 7f082ae559d0 Jul 25 16:34:24 timpc kernel: [16627.134117] Modules linked in: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm edac_mce_amd kvm_amd xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge stp llc binfmt_misc nls_iso8859_1 rtl8xxxu snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi rtl8192cu snd_hda_intel rtl_usb snd_intel_dspcfg rt
[Kernel-packages] [Bug 1932159] Update Released
The verification of the Stable Release Update for bcmwl has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1932159 Title: bcmwl/6.30.223.271+bdcom-0ubuntu7~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in bcmwl package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in bcmwl source package in Focal: Fix Released Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: [Impact] This is a scripted bug report about ADT failures while running bcmwl tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/bcmwl/20210611_210047_c4a48@/log.gz [Test Plan] sudo apt-get install bcmwl-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11 [Other Info] Please migrate this package update to -security as well in order not to break users when the default hwe kernel in Focal upgrades to 5.11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1932159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932169] Update Released
The verification of the Stable Release Update for rtl8812au has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932169 Title: rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in rtl8812au package in Ubuntu: Fix Released Status in linux-hwe-5.11 source package in Focal: Invalid Status in rtl8812au source package in Focal: Fix Released Bug description: [Impact] This is a scripted bug report about ADT failures while running rtl8812au tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/r/rtl8812au/20210611_210203_38f03@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/r/rtl8812au/20210612_123816_8ffcf@/log.gz [Test Plan] sudo apt-get install rtl8812au-dkms [Where problems could occur] There could be run time regressions in the functionality of the driver due to the compatibility changes required for successful compilation against linux-hwe-5.11 [Other Info] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932160] Update Released
The verification of the Stable Release Update for broadcom-sta has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932160 Title: broadcom-sta/6.30.223.271-12 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in broadcom-sta package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in broadcom-sta source package in Focal: Fix Released Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: [Impact] This is a scripted bug report about ADT failures while running broadcom-sta tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/broadcom-sta/20210611_210407_0acfd@/log.gz [Test Plan] sudo apt-get install broadcom-sta-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11 [Other Info] Please migrate this package update to -security as well in order not to break users when the default hwe kernel in Focal upgrades to 5.11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1932160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932173] Update Released
The verification of the Stable Release Update for xtables-addons has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932173 Title: xtables-addons/3.9-1ubuntu0.2~20.04.1 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in xtables-addons package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in xtables-addons source package in Focal: Fix Released Bug description: [Impact] This is a scripted bug report about ADT failures while running xtables-addons tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/x/xtables-addons/20210611_210642_1c193@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/x/xtables-addons/20210612_124839_710ee@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/x/xtables-addons/20210611_211032_cbce4@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/x/xtables-addons/20210611_210646_8bf21@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/x/xtables-addons/20210611_210425_4d74a@/log.gz [Test Plan] sudo apt-get install xtables-addons-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11. [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934910] Update Released
The verification of the Stable Release Update for zfs-linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1934910 Title: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux- hwe-5.4/5.4.0-79.88~18.04.1 Status in linux-hwe-5.4 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Released Status in linux-hwe-5.4 source package in Bionic: New Status in zfs-linux source package in Bionic: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux source package in Groovy: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Status in zfs-linux source package in Impish: Fix Released Bug description: == zfs-linux SRU == IMPISH, HIRSUTE, GROOVY, FOCAL, BIONIC, XENIAL [Impact] The zfs debian scrub test sometimes times out on slower test systems because scrub can take a while to complete and the scrub test can time out. The test needs some more intelligence to detect this and a longer time out for slower systems. The fix now polls the scrub completion more thoroughly and increases timeout to 15 minutes. [Test Plan] Run the test with autopkgtest on slow file systems. With the fix the test has longer timeout and will pass rather than fail with a timeout. e.g. autopkgtest zfs-linux_2.0.3-8ubuntu5.dsc -- null [Where problems could occur] The timeout is hard coded to 15 minutes. This should be enough for slow devices with the small ZFS volume set used by this test. However, it may still fail if the backing store is really slow. However, we don't want the test to be blocked indefinitely waiting for a timeout, so a 15 minute scrub timeout seems to be long enough to be more than reasonable. Any longer and it's highly likely that the scrub has hung. [Other Info] This test is almost identical to the same scrub test run from the kernel team autotest zfs smoke test, so it has been exercised regularly and is known to reliably. - This is a scripted bug report about ADT failures while running zfs-linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz This is a similar issue as reported on bug 1885289, which was fixed on autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests don't use autotest, the test script run comes from the zfs-linux dkms source package, debian/tests/kernel-smoke-test-scrub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932164] Update Released
The verification of the Stable Release Update for lime-forensics has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932164 Title: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in lime-forensics package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in lime-forensics source package in Focal: Fix Committed Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: [Impact] This is a scripted bug report about ADT failures while running lime- forensics tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lime-forensics/20210611_210117_01398@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lime-forensics/20210612_122656_106de@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lime-forensics/20210611_210238_da480@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lime-forensics/20210611_210220_40c08@/log.gz [Test Plan] sudo apt-get install lime-forensics-dkms [Where problems could occur] There could be run time regressions due to the compatibility changes required for linux-hwe-5.11 [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lime-forensics/+bug/1932164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932161] Update Released
The verification of the Stable Release Update for dahdi-linux has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932161 Title: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in dahdi-linux package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in dahdi-linux source package in Focal: Fix Released Status in linux-hwe-5.11 source package in Focal: New Bug description: [Impact] This is a scripted bug report about ADT failures while running dahdi- linux tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210611_210158_32a25@/log.gz [Test Plan] sudo apt-get install dahdi-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1932161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932161] Re: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
The previous SRU of dahdi-linux was release to -security and -updates. I'd imagine this one also needs to be released to -updates and -security but I don't see that in the description, am I correct in thinking it needs to go to -security? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932161 Title: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in dahdi-linux package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in dahdi-linux source package in Focal: Fix Committed Status in linux-hwe-5.11 source package in Focal: New Bug description: [Impact] This is a scripted bug report about ADT failures while running dahdi- linux tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210611_210158_32a25@/log.gz [Test Plan] sudo apt-get install dahdi-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1932161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932164] Re: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Does this too need to go to -security and -updates? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932164 Title: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in lime-forensics package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in lime-forensics source package in Focal: Fix Committed Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: [Impact] This is a scripted bug report about ADT failures while running lime- forensics tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lime-forensics/20210611_210117_01398@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lime-forensics/20210612_122656_106de@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lime-forensics/20210611_210238_da480@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lime-forensics/20210611_210220_40c08@/log.gz [Test Plan] sudo apt-get install lime-forensics-dkms [Where problems could occur] There could be run time regressions due to the compatibility changes required for linux-hwe-5.11 [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lime-forensics/+bug/1932164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932169] Re: rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Hello Kleber, or anyone else affected, Accepted rtl8812au into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3 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: rtl8812au (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932169 Title: rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in rtl8812au package in Ubuntu: Fix Released Status in linux-hwe-5.11 source package in Focal: Invalid Status in rtl8812au source package in Focal: Fix Committed Bug description: [Impact] This is a scripted bug report about ADT failures while running rtl8812au tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/r/rtl8812au/20210611_210203_38f03@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/r/rtl8812au/20210612_123816_8ffcf@/log.gz [Test Plan] sudo apt-get install rtl8812au-dkms [Where problems could occur] There could be run time regressions in the functionality of the driver due to the compatibility changes required for successful compilation against linux-hwe-5.11 [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932169/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932173] Please test proposed package
Hello Kleber, or anyone else affected, Accepted xtables-addons into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xtables- addons/3.9-1ubuntu0.2~20.04.3 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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932173 Title: xtables-addons/3.9-1ubuntu0.2~20.04.1 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in xtables-addons package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in xtables-addons source package in Focal: Fix Committed Bug description: [Impact] This is a scripted bug report about ADT failures while running xtables-addons tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/x/xtables-addons/20210611_210642_1c193@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/x/xtables-addons/20210612_124839_710ee@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/x/xtables-addons/20210611_211032_cbce4@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/x/xtables-addons/20210611_210646_8bf21@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/x/xtables-addons/20210611_210425_4d74a@/log.gz [Test Plan] sudo apt-get install xtables-addons-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11. [Other] NB! dkms ftbfs fixes must be built in security, such that after SRU process in -proposed & -updates it can be copied into -security pocket too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932160] Re: broadcom-sta/6.30.223.271-12 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Hello Kleber, or anyone else affected, Accepted broadcom-sta into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/broadcom- sta/6.30.223.271-12ubuntu0.1 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: broadcom-sta (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932160 Title: broadcom-sta/6.30.223.271-12 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in broadcom-sta package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in broadcom-sta source package in Focal: Fix Committed Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: [Impact] This is a scripted bug report about ADT failures while running broadcom-sta tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/b/broadcom-sta/20210611_210407_0acfd@/log.gz [Test Plan] sudo apt-get install broadcom-sta-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11 [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1932160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936268] Re: Appears to still be issues with Ryzen 3000 series CPUs
** Package changed: linux-hwe-5.11 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1936268 Title: Appears to still be issues with Ryzen 3000 series CPUs Status in linux package in Ubuntu: New Bug description: There are a number of seemingly unrelated issues that are apparent on my Ryzen 5800X CPU which are not appearing on my similarly specced Ryzen 3700X. Both are running MSI X570 motherboards and MSI 1080 GTX graphics cards. Both machines are running Kubuntu 21.04. The issues become evident on a clean install system. Issues on the 5800X but not on the 3700X: 1/ All 400 series Nvidia drivers cause malfunctions on the KDE destop (reported to Nvidia https://forums.developer.nvidia.com/t/465-drivers-cause-kde-desktop-to-malfunction/183291) 2/ Very long connection times to websites - 1 minute or more (has a random element to it) 3/ Persistent failure of the KIOclient 4/ Precludes wine from seeing some .exe and .msi files (again seems random) 5/ socket related errors in most (all) applications 6/ All desktop quick launch icons do not work with the Nvidia drivers 7/ Numerous icons are presented as question marks. 8/ Numerous attempts to upload apport information not possible with returns such as: scott@scottubuntu:~$ ubuntu-bug Icon theme "Numix-Circle" not found. 1521 /usr/share/apport/apport-kde:129: DeprecationWarning: an integer is required (got type float). Implicit conversion to integers using __int__ is deprecated, and may be removed in a future version of Python. progress.setValue(value * 1000) Icon theme "Numix-Circle" not found. kf.kio.widgets: KRun(0x557289f5aba0) ERROR (stat): 149 "Timeout on server\nbugs.launchpad.net: Socket operation timed out" ***Where are these files located so I can upload them?*** It should be noted that the Nvidia driver does cause some issues once installed and are apparent on a clean install with nothing other than Kubuntu 21.04 and the Nvidia drivers installed as shown in the Nvidia link above, that being said my inability to send the apport data occurred using the Nouveau driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581594] Re: constantly shows wrong temperature (99°C )
** Changed in: libatasmart (Ubuntu Yakkety)
Status: Confirmed => Won't Fix
** Changed in: libatasmart (Ubuntu Trusty)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to libatasmart in Ubuntu.
https://bugs.launchpad.net/bugs/1581594
Title:
constantly shows wrong temperature (99°C )
Status in libatasmart:
Unknown
Status in libatasmart package in Ubuntu:
Triaged
Status in libatasmart source package in Trusty:
Won't Fix
Status in libatasmart source package in Xenial:
Confirmed
Status in libatasmart source package in Yakkety:
Won't Fix
Bug description:
Hello, here's my system info
~$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04
~$ apt-cache policy udisks2
udisks2:
Installed: 2.1.7-1ubuntu1
Candidate: 2.1.7-1ubuntu1
Version table:
*** 2.1.7-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
Here's the problem: udisks2 constantly shows that my ssd temperature is 99°C
(210°F), but in reality it's 30°C
~$ sudo smartctl -A /dev/sda
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-22-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050Pre-fail Always
- 0
9 Power_On_Hours 0x0012 100 100 000Old_age Always
- 24
12 Power_Cycle_Count 0x0012 100 100 000Old_age Always
- 51
168 Unknown_Attribute 0x0012 100 100 000Old_age Always
- 0
170 Unknown_Attribute 0x0003 100 100 010Pre-fail Always
- 231
173 Unknown_Attribute 0x0012 100 100 000Old_age Always
- 65539
192 Power-Off_Retract_Count 0x0012 100 100 000Old_age Always
- 23
194 Temperature_Celsius 0x0023 070 070 030Pre-fail Always
- 30 (Min/Max 30/30)
218 Unknown_Attribute 0x000b 100 100 050Pre-fail Always
- 0
231 Temperature_Celsius 0x0013 100 100 000Pre-fail Always
- 99
241 Total_LBAs_Written 0x0012 100 100 000Old_age Always
- 337
in the GUI app ("Disks") it shows the wrong temperature too. hddtemp
works well though:
~$ sudo hddtemp /dev/sda
/dev/sda: PNY EU SSD CS1311 240GB: 30°C
To manage notifications about this bug go to:
https://bugs.launchpad.net/libatasmart/+bug/1581594/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
Hello Shengyao, or anyone else affected, Accepted alsa-lib into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- lib/1.1.3-5ubuntu0.6 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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. ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923162] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted u-boot-menu into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/u-boot- menu/4.0.2ubuntu5~20.04.1 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. -- 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/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: Fix Committed Status in u-boot-menu source package in Focal: Fix Committed Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: Fix Committed Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923162] Re: riscv64 images fail to boot in qemu
Hello Dimitri, or anyone else affected, Accepted u-boot into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/u-boot/2021.01+dfsg-3ubuntu0~20.04.1 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: u-boot (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed-focal -- 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/1923162 Title: riscv64 images fail to boot in qemu Status in linux-riscv package in Ubuntu: Invalid Status in u-boot package in Ubuntu: Fix Released Status in u-boot-menu package in Ubuntu: Fix Released Status in linux-riscv source package in Focal: Invalid Status in u-boot source package in Focal: Fix Committed Status in u-boot-menu source package in Focal: Fix Committed Status in linux-riscv source package in Hirsute: Invalid Status in u-boot source package in Hirsute: Fix Committed Status in u-boot-menu source package in Hirsute: Fix Released Bug description: [Impact] * u-boot may crash when attempting to boot extlinux.conf which specifies fdtdir; the given u-boot config doesn't specify a dtb filename to load; autodetection tries to make one up using $soc & $board variables; and if one or both of them are not set (as it is the case for qemu) it would crash. Fix this crash by doing validation / checking when quering for $soc & $board variables in autodetectionn. [Test Plan] * Use qemu & uboot produced by the build that fixes this bug report properly and attempt to boot hirsute's riscv64+unmatched image. * It should boot correctly without a crash / qemu backtrace. [Where problems could occur] * This patch is bein upstreamed. If one is using external uboot (i.e. provided by some other vendor) it may still crash when trying to boot Ubuntu's riscv64 rootfs or cloud image. [Other Info] * Patch is being reviewed upstream https://lists.denx.de/pipermail/u-boot/2021-May/449176.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932161] Re: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Hello Kleber, or anyone else affected, Accepted dahdi-linux into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dahdi- linux/1:2.11.1~dfsg-1ubuntu6.3 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: dahdi-linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932161 Title: dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in dahdi-linux package in Ubuntu: New Status in linux-hwe-5.11 package in Ubuntu: New Status in dahdi-linux source package in Focal: Fix Committed Status in linux-hwe-5.11 source package in Focal: New Bug description: [Impact] This is a scripted bug report about ADT failures while running dahdi- linux tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/d/dahdi-linux/20210611_210158_32a25@/log.gz [Test Plan] sudo apt-get install dahdi-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dahdi-linux/+bug/1932161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932164] Re: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Hello Kleber, or anyone else affected, Accepted lime-forensics into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/lime- forensics/1.9-1ubuntu0.3 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: lime-forensics (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932164 Title: lime-forensics/1.9-1ubuntu0.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in lime-forensics package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in lime-forensics source package in Focal: Fix Committed Status in linux-hwe-5.11 source package in Focal: Invalid Bug description: [Impact] This is a scripted bug report about ADT failures while running lime- forensics tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lime-forensics/20210611_210117_01398@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lime-forensics/20210612_122656_106de@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lime-forensics/20210611_210238_da480@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lime-forensics/20210611_210220_40c08@/log.gz [Test Plan] sudo apt-get install lime-forensics-dkms [Where problems could occur] There could be run time regressions due to the compatibility changes required for linux-hwe-5.11 [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lime-forensics/+bug/1932164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934910] Re: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux-hwe-5.4/5.4.0-79.88~18.04.1
Hello Kleber, or anyone else affected, Accepted zfs-linux into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.6.5.6-0ubuntu30 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- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. 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 Xenial) Status: In Progress => 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/1934910 Title: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux- hwe-5.4/5.4.0-79.88~18.04.1 Status in linux-hwe-5.4 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: Fix Committed Status in linux-hwe-5.4 source package in Bionic: New Status in zfs-linux source package in Bionic: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Committed Status in zfs-linux source package in Hirsute: Fix Committed Status in zfs-linux source package in Impish: Fix Released Bug description: == zfs-linux SRU == IMPISH, HIRSUTE, GROOVY, FOCAL, BIONIC, XENIAL [Impact] The zfs debian scrub test sometimes times out on slower test systems because scrub can take a while to complete and the scrub test can time out. The test needs some more intelligence to detect this and a longer time out for slower systems. The fix now polls the scrub completion more thoroughly and increases timeout to 15 minutes. [Test Plan] Run the test with autopkgtest on slow file systems. With the fix the test has longer timeout and will pass rather than fail with a timeout. e.g. autopkgtest zfs-linux_2.0.3-8ubuntu5.dsc -- null [Where problems could occur] The timeout is hard coded to 15 minutes. This should be enough for slow devices with the small ZFS volume set used by this test. However, it may still fail if the backing store is really slow. However, we don't want the test to be blocked indefinitely waiting for a timeout, so a 15 minute scrub timeout seems to be long enough to be more than reasonable. Any longer and it's highly likely that the scrub has hung. [Other Info] This test is almost identical to the same scrub test run from the kernel team autotest zfs smoke test, so it has been exercised regularly and is known to reliably. - This is a scripted bug report about ADT failures while running zfs-linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz This is a similar issue as reported on bug 1885289, which was fixed on autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests don't use autotest, the test script run comes from the zfs-linux dkms source package, debian/tests/kernel-smoke-test-scrub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934910] Please test proposed package
Hello Kleber, or anyone else affected, Accepted zfs-linux into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.8.4-1ubuntu11.3 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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: In Progress => 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/1934910 Title: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux- hwe-5.4/5.4.0-79.88~18.04.1 Status in linux-hwe-5.4 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: In Progress Status in linux-hwe-5.4 source package in Bionic: New Status in zfs-linux source package in Bionic: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Committed Status in zfs-linux source package in Hirsute: Fix Committed Status in zfs-linux source package in Impish: Fix Released Bug description: == zfs-linux SRU == IMPISH, HIRSUTE, GROOVY, FOCAL, BIONIC, XENIAL [Impact] The zfs debian scrub test sometimes times out on slower test systems because scrub can take a while to complete and the scrub test can time out. The test needs some more intelligence to detect this and a longer time out for slower systems. The fix now polls the scrub completion more thoroughly and increases timeout to 15 minutes. [Test Plan] Run the test with autopkgtest on slow file systems. With the fix the test has longer timeout and will pass rather than fail with a timeout. e.g. autopkgtest zfs-linux_2.0.3-8ubuntu5.dsc -- null [Where problems could occur] The timeout is hard coded to 15 minutes. This should be enough for slow devices with the small ZFS volume set used by this test. However, it may still fail if the backing store is really slow. However, we don't want the test to be blocked indefinitely waiting for a timeout, so a 15 minute scrub timeout seems to be long enough to be more than reasonable. Any longer and it's highly likely that the scrub has hung. [Other Info] This test is almost identical to the same scrub test run from the kernel team autotest zfs smoke test, so it has been exercised regularly and is known to reliably. - This is a scripted bug report about ADT failures while running zfs-linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz This is a similar issue as reported on bug 1885289, which was fixed on autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests don't use autotest, the test script run comes from the zfs-linux dkms source package, debian/tests/kernel-smoke-test-scrub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934910] Please test proposed package
Hello Kleber, or anyone else affected, Accepted zfs-linux into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/0.7.5-1ubuntu16.12 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- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. 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. -- 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/1934910 Title: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux- hwe-5.4/5.4.0-79.88~18.04.1 Status in linux-hwe-5.4 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: In Progress Status in linux-hwe-5.4 source package in Bionic: New Status in zfs-linux source package in Bionic: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Committed Status in zfs-linux source package in Hirsute: Fix Committed Status in zfs-linux source package in Impish: Fix Released Bug description: == zfs-linux SRU == IMPISH, HIRSUTE, GROOVY, FOCAL, BIONIC, XENIAL [Impact] The zfs debian scrub test sometimes times out on slower test systems because scrub can take a while to complete and the scrub test can time out. The test needs some more intelligence to detect this and a longer time out for slower systems. The fix now polls the scrub completion more thoroughly and increases timeout to 15 minutes. [Test Plan] Run the test with autopkgtest on slow file systems. With the fix the test has longer timeout and will pass rather than fail with a timeout. e.g. autopkgtest zfs-linux_2.0.3-8ubuntu5.dsc -- null [Where problems could occur] The timeout is hard coded to 15 minutes. This should be enough for slow devices with the small ZFS volume set used by this test. However, it may still fail if the backing store is really slow. However, we don't want the test to be blocked indefinitely waiting for a timeout, so a 15 minute scrub timeout seems to be long enough to be more than reasonable. Any longer and it's highly likely that the scrub has hung. [Other Info] This test is almost identical to the same scrub test run from the kernel team autotest zfs smoke test, so it has been exercised regularly and is known to reliably. - This is a scripted bug report about ADT failures while running zfs-linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz This is a similar issue as reported on bug 1885289, which was fixed on autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests don't use autotest, the test script run comes from the zfs-linux dkms source package, debian/tests/kernel-smoke-test-scrub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934910] Please test proposed package
Hello Kleber, 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.11 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 Bionic) Status: In Progress => 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/1934910 Title: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux- hwe-5.4/5.4.0-79.88~18.04.1 Status in linux-hwe-5.4 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: In Progress Status in linux-hwe-5.4 source package in Bionic: New Status in zfs-linux source package in Bionic: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Committed Status in zfs-linux source package in Hirsute: Fix Committed Status in zfs-linux source package in Impish: Fix Released Bug description: == zfs-linux SRU == IMPISH, HIRSUTE, GROOVY, FOCAL, BIONIC, XENIAL [Impact] The zfs debian scrub test sometimes times out on slower test systems because scrub can take a while to complete and the scrub test can time out. The test needs some more intelligence to detect this and a longer time out for slower systems. The fix now polls the scrub completion more thoroughly and increases timeout to 15 minutes. [Test Plan] Run the test with autopkgtest on slow file systems. With the fix the test has longer timeout and will pass rather than fail with a timeout. e.g. autopkgtest zfs-linux_2.0.3-8ubuntu5.dsc -- null [Where problems could occur] The timeout is hard coded to 15 minutes. This should be enough for slow devices with the small ZFS volume set used by this test. However, it may still fail if the backing store is really slow. However, we don't want the test to be blocked indefinitely waiting for a timeout, so a 15 minute scrub timeout seems to be long enough to be more than reasonable. Any longer and it's highly likely that the scrub has hung. [Other Info] This test is almost identical to the same scrub test run from the kernel team autotest zfs smoke test, so it has been exercised regularly and is known to reliably. - This is a scripted bug report about ADT failures while running zfs-linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz This is a similar issue as reported on bug 1885289, which was fixed on autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests don't use autotest, the test script run comes from the zfs-linux dkms source package, debian/tests/kernel-smoke-test-scrub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934910] Re: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux-hwe-5.4/5.4.0-79.88~18.04.1
Hello Kleber, or anyone else affected, Accepted zfs-linux into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/zfs- linux/2.0.2-1ubuntu5.1 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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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 Hirsute) Status: In Progress => Fix Committed ** Changed in: zfs-linux (Ubuntu Groovy) Status: In Progress => 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/1934910 Title: zfs-linux/0.7.5-1ubuntu16.11 ADT test failure with linux- hwe-5.4/5.4.0-79.88~18.04.1 Status in linux-hwe-5.4 package in Ubuntu: New Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Xenial: In Progress Status in linux-hwe-5.4 source package in Bionic: New Status in zfs-linux source package in Bionic: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Status in zfs-linux source package in Groovy: Fix Committed Status in zfs-linux source package in Hirsute: Fix Committed Status in zfs-linux source package in Impish: Fix Released Bug description: == zfs-linux SRU == IMPISH, HIRSUTE, GROOVY, FOCAL, BIONIC, XENIAL [Impact] The zfs debian scrub test sometimes times out on slower test systems because scrub can take a while to complete and the scrub test can time out. The test needs some more intelligence to detect this and a longer time out for slower systems. The fix now polls the scrub completion more thoroughly and increases timeout to 15 minutes. [Test Plan] Run the test with autopkgtest on slow file systems. With the fix the test has longer timeout and will pass rather than fail with a timeout. e.g. autopkgtest zfs-linux_2.0.3-8ubuntu5.dsc -- null [Where problems could occur] The timeout is hard coded to 15 minutes. This should be enough for slow devices with the small ZFS volume set used by this test. However, it may still fail if the backing store is really slow. However, we don't want the test to be blocked indefinitely waiting for a timeout, so a 15 minute scrub timeout seems to be long enough to be more than reasonable. Any longer and it's highly likely that the scrub has hung. [Other Info] This test is almost identical to the same scrub test run from the kernel team autotest zfs smoke test, so it has been exercised regularly and is known to reliably. - This is a scripted bug report about ADT failures while running zfs-linux tests for linux-hwe-5.4/5.4.0-79.88~18.04.1 on bionic. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/amd64/z/zfs-linux/20210703_080055_ead94@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/arm64/z/zfs-linux/20210703_075255_bdb56@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/ppc64el/z/zfs-linux/20210703_074629_bdb56@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20210703_074343_3aa5c@/log.gz This is a similar issue as reported on bug 1885289, which was fixed on autotest-client-tests ubuntu_zfs_smoke_test. However, the ADT tests don't use autotest, the test script run comes from the zfs-linux dkms source package, debian/tests/kernel-smoke-test-scrub. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1934910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.lau
[Kernel-packages] [Bug 1932173] Re: xtables-addons/3.9-1ubuntu0.2~20.04.1 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
Hello Kleber, or anyone else affected, Accepted xtables-addons into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xtables- addons/3.9-1ubuntu0.2~20.04.2 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: xtables-addons (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932173 Title: xtables-addons/3.9-1ubuntu0.2~20.04.1 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: New Status in xtables-addons package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: New Status in xtables-addons source package in Focal: Fix Committed Bug description: [Impact] This is a scripted bug report about ADT failures while running xtables-addons tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/x/xtables-addons/20210611_210642_1c193@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/x/xtables-addons/20210612_124839_710ee@/log.gz armhf: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/x/xtables-addons/20210611_211032_cbce4@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/x/xtables-addons/20210611_210646_8bf21@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/x/xtables-addons/20210611_210425_4d74a@/log.gz [Test Plan] sudo apt-get install xtables-addons-dkms [Where problems could occur] Run time regressions could occur due to compatibility changes required for linux-hwe-5.11. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932582] Update Released
The verification of the Stable Release Update for linux-base has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932582 Title: Implement support for Intel SGX Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-5.11 package in Ubuntu: Invalid Status in linux-base package in Ubuntu: Fix Released Status in linux source package in Focal: Invalid Status in linux-azure source package in Focal: Invalid Status in linux-azure-5.11 source package in Focal: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Released Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-5.11 source package in Hirsute: Invalid Status in linux-base source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Status in linux-azure source package in Impish: Fix Released Status in linux-azure-5.11 source package in Impish: Invalid Status in linux-base source package in Impish: Fix Released Bug description: [Impact] Backport Linux kernel 5.11 SGX native support to new Azure Ubuntu 20.04 releases. [Fix] Update linux-base to add a UDEV rule to set group permissions on the SGX device. Add an environment variable to default to out-of-proc attestation. [Test] Install focal:linux-azure-5.11 or hirsute:linux-azure. Install linux-base-sgx reboot systemctl --user show-environment | grep SGX_AESM_ADDR systemctl --system show-environment | grep SGX_AESM_ADDR login via tty and check $ env | grep SGX_AESM_ADDR login via ssh and check $ env | grep SGX_AESM_ADDR [other info] SF:00308240 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934582] Re: Cannot recover after Suspend
** Tags added: hirsute ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934582 Title: Cannot recover after Suspend Status in linux package in Ubuntu: New Bug description: I'm running Ubuntu Live 21.04 from a USB drive. If I pull down the system menu and select Suspend. The laptop (HP Omen) suspends. When I close, then open the lid, the red power button lights, but the screen does not restore. No key have any effect. The same thing happens for a configured system, but this is simpler, being self-contained, and demonstrates the problem. Ubuntu 21.04 ubuntu-21.04-desktop-amd64.iso What do I expect? I expect to be able to close the laptop lid, have the computer suspend, and, when the laptop lid is reopened, have the session restored and operable. Instead, the session is not restored, and becomes unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1934387] Re: Kernel panic booting on Unmatched with kernel 5.8
** Changed in: linux-riscv-5.8 (Ubuntu) Milestone: ubuntu-20.04.3 => None -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 Status in linux-riscv-5.8 package in Ubuntu: New Bug description: This doesn't happen every time a boot is attempted, but very frequently. Log below: [ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [ 15.048759] zswap: loaded using pool lzo/zbud [ 15.053091] Key type ._fscrypt registered [ 15.056452] Key type .fscrypt registered [ 15.060276] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 15.060376] Key type fscrypt-provisioning registered [ 15.067784] GPT:7340031 != 62333951 [ 15.067790] GPT:Alternate GPT header not at the end of the disk. [ 15.082195] GPT:7340031 != 62333951 [ 15.085655] GPT: Use GNU Parted to correct GPT errors. [ 15.089268] Key type encrypted registered [ 15.090848] mmcblk0: p1 p12 p13 p14 p15 [ 15.094794] AppArmor: AppArmor sha1 policy hashing enabled [ 15.104197] ima: No TPM chip found, activating TPM-bypass! [ 15.109690] ima: Allocated hash algorithm: sha1 [ 15.114191] ima: No architecture policies found [ 15.118816] evm: Initialising EVM extended attributes: [ 15.123787] evm: security.selinux [ 15.127086] evm: security.SMACK64 [ 15.130380] evm: security.SMACK64EXEC [ 15.134030] evm: security.SMACK64TRANSMUTE [ 15.138108] evm: security.SMACK64MMAP [ 15.141755] evm: security.apparmor [ 15.145142] evm: security.ima [ 15.148081] evm: security.capability [ 15.151656] evm: HMAC attrs: 0x1 [ 18.062579] Freeing unused kernel memory: 308K [ 18.071639] [ cut here ] [ 18.075533] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 18.084242] WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 18.092116] Modules linked in: [ 18.095142] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.103320] epc: ffe00020891a ra : ffe00020891a sp : ffe1f5bebb30 [ 18.110425] gp : ffe0013206b8 tp : ffe1f5be6780 t0 : ffe001336fa0 [ 18.117650] t1 : ffe001336f38 t2 : 0001fecd4000 s0 : ffe1f5bebb80 [ 18.124859] s1 : ffe1f5bebe10 a0 : 0053 a1 : 00020020 [ 18.132067] a2 : ffe1f5beb870 a3 : a4 : ffe0012200a0 [ 18.139277] a5 : ffe0012200a0 a6 : 00c6 a7 : ffe0006ebfee [ 18.146485] s2 : ffdff8001000 s3 : s4 : 0004 [ 18.153698] s5 : s6 : s7 : ffe1f5bebd20 [ 18.160917] s8 : ffdff8001000 s9 : ffe001322148 s10: ffdff8002000 [ 18.168116] s11: ffe000c16e20 t3 : 0003cca8 t4 : 0003cca8 [ 18.175323] t5 : t6 : ffe001331462 [ 18.180605] status: 00020120 badaddr: ffe1f5bebb30 cause: 0003 [ 18.188525] ---[ end trace ecc2ef275d977b46 ]--- [ 18.193629] Checked W+X mappings: failed, 513 W+X pages found [ 18.198865] Run /init as init process Loading, please wait... Starting version 245.4-4ubuntu3.7 [ 18.683096] Unable to handle kernel paging request at virtual address 005f8141b42c [ 18.690315] Oops [#1] [ 18.692526] Modules linked in: phylink i2c_ocores(+) [ 18.697489] CPU: 0 PID: 147 Comm: systemd-udevd Tainted: GW 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.707566] epc: ffdf8141b42c ra : ffe000266012 sp : ffe1f4b3bd20 [ 18.714668] gp : ffe0013206b8 tp : ffe1f46f t0 : 0040 [ 18.721931] t1 : t2 : 000a s0 : ffe1f4b3bda0 [ 18.729123] s1 : a0 : 0003 a1 : ffe1f4a39018 [ 18.736314] a2 : 0001 a3 : a4 : ffdf8141b42c [ 18.739498] macb 1009.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 18.743528] a5 : 0003 a6 : ffe1f5603d98 a7 : ffe1f5603dc0 [ 18.743533] s2 : 0003 s3 : ffe1f4b3bdac s4 : 0001 [ 18.743537] s5 : ffe0012f02c8 s6 : ffe0012f02f0 s7 : 0002 [ 18.743542] s8 : ffe1f5d46000 s9 : 002ab15da010 s10: 0002 [ 18.743546] s11: ffe1f35a3680 t3 : 0002 t4 : 0402 [ 18.743553] t5 : ffe001220348 t6 : ffe001220350 [ 18.750909] macb 1009.ethernet: GEM doesn't support hardware ptp. [ 18.75
[Kernel-packages] [Bug 1934387] Re: Kernel panic booting on Unmatched with kernel 5.8
** Changed in: linux-riscv-5.8 (Ubuntu) Milestone: None => ubuntu-20.04.3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1934387 Title: Kernel panic booting on Unmatched with kernel 5.8 Status in linux-riscv-5.8 package in Ubuntu: New Bug description: This doesn't happen every time a boot is attempted, but very frequently. Log below: [ 15.024548] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 14df34d1a87cf37625abec039ef2bf521249b969' [ 15.038870] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 88f752e560a1e0737e31163a466ad7b70a850c19' [ 15.048759] zswap: loaded using pool lzo/zbud [ 15.053091] Key type ._fscrypt registered [ 15.056452] Key type .fscrypt registered [ 15.060276] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 15.060376] Key type fscrypt-provisioning registered [ 15.067784] GPT:7340031 != 62333951 [ 15.067790] GPT:Alternate GPT header not at the end of the disk. [ 15.082195] GPT:7340031 != 62333951 [ 15.085655] GPT: Use GNU Parted to correct GPT errors. [ 15.089268] Key type encrypted registered [ 15.090848] mmcblk0: p1 p12 p13 p14 p15 [ 15.094794] AppArmor: AppArmor sha1 policy hashing enabled [ 15.104197] ima: No TPM chip found, activating TPM-bypass! [ 15.109690] ima: Allocated hash algorithm: sha1 [ 15.114191] ima: No architecture policies found [ 15.118816] evm: Initialising EVM extended attributes: [ 15.123787] evm: security.selinux [ 15.127086] evm: security.SMACK64 [ 15.130380] evm: security.SMACK64EXEC [ 15.134030] evm: security.SMACK64TRANSMUTE [ 15.138108] evm: security.SMACK64MMAP [ 15.141755] evm: security.apparmor [ 15.145142] evm: security.ima [ 15.148081] evm: security.capability [ 15.151656] evm: HMAC attrs: 0x1 [ 18.062579] Freeing unused kernel memory: 308K [ 18.071639] [ cut here ] [ 18.075533] riscv/mm: Found insecure W+X mapping at address (ptrval)/0xffdff800 [ 18.084242] WARNING: CPU: 2 PID: 1 at arch/riscv/mm/ptdump.c:200 note_page+0x24c/0x252 [ 18.092116] Modules linked in: [ 18.095142] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.103320] epc: ffe00020891a ra : ffe00020891a sp : ffe1f5bebb30 [ 18.110425] gp : ffe0013206b8 tp : ffe1f5be6780 t0 : ffe001336fa0 [ 18.117650] t1 : ffe001336f38 t2 : 0001fecd4000 s0 : ffe1f5bebb80 [ 18.124859] s1 : ffe1f5bebe10 a0 : 0053 a1 : 00020020 [ 18.132067] a2 : ffe1f5beb870 a3 : a4 : ffe0012200a0 [ 18.139277] a5 : ffe0012200a0 a6 : 00c6 a7 : ffe0006ebfee [ 18.146485] s2 : ffdff8001000 s3 : s4 : 0004 [ 18.153698] s5 : s6 : s7 : ffe1f5bebd20 [ 18.160917] s8 : ffdff8001000 s9 : ffe001322148 s10: ffdff8002000 [ 18.168116] s11: ffe000c16e20 t3 : 0003cca8 t4 : 0003cca8 [ 18.175323] t5 : t6 : ffe001331462 [ 18.180605] status: 00020120 badaddr: ffe1f5bebb30 cause: 0003 [ 18.188525] ---[ end trace ecc2ef275d977b46 ]--- [ 18.193629] Checked W+X mappings: failed, 513 W+X pages found [ 18.198865] Run /init as init process Loading, please wait... Starting version 245.4-4ubuntu3.7 [ 18.683096] Unable to handle kernel paging request at virtual address 005f8141b42c [ 18.690315] Oops [#1] [ 18.692526] Modules linked in: phylink i2c_ocores(+) [ 18.697489] CPU: 0 PID: 147 Comm: systemd-udevd Tainted: GW 5.8.0-29-generic #31~20.04.1-Ubuntu [ 18.707566] epc: ffdf8141b42c ra : ffe000266012 sp : ffe1f4b3bd20 [ 18.714668] gp : ffe0013206b8 tp : ffe1f46f t0 : 0040 [ 18.721931] t1 : t2 : 000a s0 : ffe1f4b3bda0 [ 18.729123] s1 : a0 : 0003 a1 : ffe1f4a39018 [ 18.736314] a2 : 0001 a3 : a4 : ffdf8141b42c [ 18.739498] macb 1009.ethernet: Registered clk switch 'sifive-gemgxl-mgmt' [ 18.743528] a5 : 0003 a6 : ffe1f5603d98 a7 : ffe1f5603dc0 [ 18.743533] s2 : 0003 s3 : ffe1f4b3bdac s4 : 0001 [ 18.743537] s5 : ffe0012f02c8 s6 : ffe0012f02f0 s7 : 0002 [ 18.743542] s8 : ffe1f5d46000 s9 : 002ab15da010 s10: 0002 [ 18.743546] s11: ffe1f35a3680 t3 : 0002 t4 : 0402 [ 18.743553] t5 : ffe001220348 t6 : ffe001220350 [ 18.750909] macb 1009.ethernet: GEM doesn't support hardware ptp. [ 18.75
[Kernel-packages] [Bug 1934112] Re: Intel 100G nic get call trace for sosreport on focal ga-kenel
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1934112 Title: Intel 100G nic get call trace for sosreport on focal ga-kenel Status in linux package in Ubuntu: New Bug description: On Asus Server, when it run "sosreport -a" to the network step, the console would print below call trace and the 100G Nic port became unreachable. call trace on ga-kernel ( v5.4): https://paste.ubuntu.com/p/TC5Jn6hYGF/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1934112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929516] Update Released
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
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/1929516
Title:
Failed to load DMC firmware i915/adls_dmc_ver2_01.bin
Status in OEM Priority Project:
New
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Focal:
Fix Released
Bug description:
[SRU Justification]
[Impact]
It shows the firmware is missing, and runtime power management has been
disabled.
i915 :00:02.0: vgaarb: deactivate vga console
i915 :00:02.0: vgaarb: changed VGA decodes:
olddecodes=io+mem,decodes=io+mem:owns=io+mem
i915 :00:02.0: Direct firmware load for i915/adls_dmc_ver2_01.bin
failed with error -2
i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adls_dmc_ver2_01.bin. Disabling runtime power management.
i915 :00:02.0: [drm] DMC firmware homepage:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
[Fix]
cherry picked from linux-firmware commit 348d8a97 ("i915: Add DMC v2.01 for
ADL-S").
[Test]
Verified on Intel SDP
[Where problems could occur]
It's a new firmware for new GPU, not possible to introduce regressions.
[Other Info]
Impish has this already. And while ADL-S support begins since v5.13, only
focal (for oem-5.13) will be nominated.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1929516/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931677] Update Released
The verification of the Stable Release Update for linux-firmware has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1931677 Title: [SRU][F/G/H][linux-firmware] add realtek 8852a wifi fimware Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Groovy: Fix Released Status in linux-firmware source package in Hirsute: Fix Committed Bug description: [Impact] Realtek 8852A wifi can not work without proper firmware. [Fix] Add realtek 8852a wifi firmware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with wifi ap, connect with 2.4G/5G, all good. [Where problems could occur] It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931565] Please test proposed package
Hello Colin, or anyone else affected, Accepted thermald into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/thermald/1.9.1-1ubuntu0.5 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. -- 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 Committed Status in thermald source package in Hirsute: Fix Committed 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. Instea
[Kernel-packages] [Bug 1931565] Re: pull in latest thermald bug fixes into thermald
Given the regression potential in the description I think we should let this age a bit longer in -proposed. Let's look at releasing this in another 7 days. ** Changed in: thermald (Ubuntu Focal) Status: New => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-focal -- 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 Committed Status in thermald source package in Hirsute: Fix Committed 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
[Kernel-packages] [Bug 1931677] Re: [SRU][F/G/H][linux-firmware] add realtek 8852a wifi fimware
Hello koba, or anyone else affected, Accepted linux-firmware into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.197.2 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- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. 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: linux-firmware (Ubuntu Hirsute) Status: In Progress => Fix Committed -- 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/1931677 Title: [SRU][F/G/H][linux-firmware] add realtek 8852a wifi fimware Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Committed Status in linux-firmware source package in Groovy: Fix Committed Status in linux-firmware source package in Hirsute: Fix Committed Bug description: [Impact] Realtek 8852A wifi can not work without proper firmware. [Fix] Add realtek 8852a wifi firmware for driver. Kernel driver will be in another SRU. [Test] Verified on hardware with wifi ap, connect with 2.4G/5G, all good. [Where problems could occur] It should be low risk for adding fw for specfic hardware chip. Hirsute already got it, only SRU fw for F/G. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1931677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931435] Update Released
The verification of the Stable Release Update for crash has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1931435 Title: crash fails to build on ubuntu 20.10 (Groovy) on arm64 Status in crash package in Ubuntu: Fix Released Status in crash source package in Groovy: Fix Released Bug description: On arm64, crash fails to build with error "multiple definition of `tdesc_aarch64'" [1]. From upstream git log, seems it can be resolved with commit e770735200c02ac2414c394ea6ec5f7f033efe64 . [1] https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630861 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919275] Update Released
The verification of the Stable Release Update for crash has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL Status in crash package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in crash source package in Bionic: Fix Released Status in linux source package in Bionic: Invalid Status in crash source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in crash source package in Groovy: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility 7.2.8-1ubuntu0.18.04 fails with: crash: cannot determine VA_BITS_ACTUAL This bug has been addressed upstream and needed patches both in crash and kernel. Kernel patch : commit bbdbc11804ff0b4130e7550113b452e96a74d16e Author: Bhupesh Sharma Date: Thu May 14 00:22:37 2020 +0530 arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo Crash patch : commit 1c45cea02df7f947b4296c1dcaefa1024235ef10 Author: Bhupesh Sharma Date: Tue Jul 14 01:14:49 2020 +0530 arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ Series affected : Kenrel : This affects Focal (5.4 kernel) and Groovy (5.8 kernel). Hirsute already contains the commit and kernels prior to 5.3 are not affected. Crash : The commit is already in Hirsute. Groovy, Focal and Bionic are affected. In case of Bionic the bug appears only if 5.4 hwe kernel is used. [Test Case] On an arm64 host which runs the affected releases and kernels after creating a crashdump try to open it with crash. It will fail with : crash: cannot determine VA_BITS_ACTUAL [Where problems could occur] Kernel patch : The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ variable in vmcoreinfo. Given that this is a simple operation and that this patch landed upstream in 5.9 and no regressions have been reported, it is safe to assume that the regression potential is minimal. Any potential problem would occur in vmcoreinfo since this is where TCR_EL1.T1SZ variable is exported. Crash patch : This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible with the kernel change above for crash to be able to read it. The regression potential is small and any problem would regard reading this variable. [Other] Workaround : This bug/change in crash provides a workaround for 5.4+ https://github.com/crash-utility/crash/issues/52 kernels. While it appears as though it this was fixed it https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still doesn't seem to work with a 5.4 kernel including. I also tested https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb and it exhibits the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933201] Re: ath10k_pci QCA6174 firmware crash on suspend
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933201 Title: ath10k_pci QCA6174 firmware crash on suspend Status in linux package in Ubuntu: New Bug description: Hi, Another issue with Qualcomm Atheros QCA6174 (very similar to https://bugs.launchpad.net/ubuntu/+bug/1827879), this time using Mint 20.1/Ubuntu 20.04: when suspending laptop, firmware often (80%) crashes (see kernel log at bottom). It prevents the computer from properly suspend, and many component hang (can't poweroff properly, can't use "sudo", can't "modprobe -r" or "rmmod"…), so it basically makes the computer unusable once this happens. If I manually unload ath10k_pci module before suspend, suspend/resume works perfectly. Unfortunately, I could not find a reliable way to unload this module before suspend (either via a systemd unit or via /lib/systemd/system-sleep/ script). If I understand properly, the issue comes from the loaded firmware (/lib/firmware/ath10k/QCA6142/hw2.1/firmware-5.bin) which is proprietary so can't be fixed. However, fixing the ath10k module or the kernel so that it can recover from such a problem would be great if possible. Note that I tried with linux-image-generic (linux- headers-5.4.0-74-generic) and linux-image-generic-hwe-20.04 (linux- image-5.8.0-55-generic). Package linux-firmware is in version 1.187.14. Regards, Yvan juin 21 23:22:04 kernel: wlp2s0: deauthenticating from 38:35:fb:fa:75:64 by local choice (Reason: 3=DEAUTH_LEAVING) juin 21 23:22:04 kernel: ath10k_pci :02:00.0: firmware crashed! (guid 4f13694a-78f7-460f-95ad-ed3e8ea8ff32) juin 21 23:22:04 kernel: ath10k_pci :02:00.0: qca6174 hw2.1 target 0x0501 chip_id 0x003405ff sub 105b:e08e juin 21 23:22:04 kernel: ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features ignore-otp,no-4addr-pad crc32 10bf8e08 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 ae2e275a juin 21 23:22:04 kernel: ath10k_pci :02:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: firmware register dump: juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [00]: 0x0501 0x 0x0092E4DC 0x2EB96CFB juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [04]: 0x0092E4DC 0x00060130 0x0018 0x0041A760 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [08]: 0x2EB96CE7 0x0040 0x 0x000A5C88 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [12]: 0x0009 0x 0x0096C09C 0x0096C0A7 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [16]: 0x0096BDBC 0x0092B5C7 0x 0x009287BD juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [20]: 0x4092E4DC 0x0041A710 0x 0x0F00 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [24]: 0x809432A7 0x0041A770 0x0040D400 0xC092E4DC juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [28]: 0x80942BC4 0x0041A790 0x2EB96CE7 0x0040 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [32]: 0x80947BA7 0x0041A7B0 0x00404D88 0x0040E074 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [36]: 0x809BDECC 0x0041A7D0 0x00404D88 0x0040E074 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [40]: 0x8099638C 0x0041A7F0 0x00404D88 0x juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [44]: 0x80992076 0x0041A810 0x0044FD68 0x0046FFE8 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [48]: 0x80996BD3 0x0041A830 0x0044FD68 0x juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [52]: 0x800B4405 0x0041A850 0x00422318 0x5002 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [56]: 0x809A6C34 0x0041A8E0 0x0042932C 0x0042CA20 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: Copy Engine register dump: juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [00]: 0x00034400 1 1 3 3 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [01]: 0x00034800 24 24 379 380 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [02]: 0x00034c00 35 35 34 35 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [03]: 0x00035000 20 20 21 20 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [04]: 0x00035400 739 739 179 115 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [05]: 0x00035800 0 0 0 0 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [06]: 0x00035c00 21 21 21 21 juin 21 23:22:04 kernel: ath10k_pci :02:00.0: [07]: 0x00036000 1 1 1 1 juin 21 23:22:04 kernel: ieee80211 phy0: Hardware restart was requested juin 21 23:22:04 kernel: ath10k_pci :02:00.0: failed to delete WMI vdev 1: -108 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture:
[Kernel-packages] [Bug 1919275] Please test proposed package
Hello Ali, or anyone else affected, Accepted crash into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.2 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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL Status in crash package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in crash source package in Bionic: Fix Committed Status in linux source package in Bionic: Invalid Status in crash source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in crash source package in Groovy: Fix Committed Status in linux source package in Groovy: Fix Released Bug description: [Impact] On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility 7.2.8-1ubuntu0.18.04 fails with: crash: cannot determine VA_BITS_ACTUAL This bug has been addressed upstream and needed patches both in crash and kernel. Kernel patch : commit bbdbc11804ff0b4130e7550113b452e96a74d16e Author: Bhupesh Sharma Date: Thu May 14 00:22:37 2020 +0530 arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo Crash patch : commit 1c45cea02df7f947b4296c1dcaefa1024235ef10 Author: Bhupesh Sharma Date: Tue Jul 14 01:14:49 2020 +0530 arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ Series affected : Kenrel : This affects Focal (5.4 kernel) and Groovy (5.8 kernel). Hirsute already contains the commit and kernels prior to 5.3 are not affected. Crash : The commit is already in Hirsute. Groovy, Focal and Bionic are affected. In case of Bionic the bug appears only if 5.4 hwe kernel is used. [Test Case] On an arm64 host which runs the affected releases and kernels after creating a crashdump try to open it with crash. It will fail with : crash: cannot determine VA_BITS_ACTUAL [Where problems could occur] Kernel patch : The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ variable in vmcoreinfo. Given that this is a simple operation and that this patch landed upstream in 5.9 and no regressions have been reported, it is safe to assume that the regression potential is minimal. Any potential problem would occur in vmcoreinfo since this is where TCR_EL1.T1SZ variable is exported. Crash patch : This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible with the kernel change above for crash to be able to read it. The regression potential is small and any problem would regard reading this variable. [Other] Workaround : This bug/change in crash provides a workaround for 5.4+ https://github.com/crash-utility/crash/issues/52 kernels. While it appears as though it this was fixed it https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still doesn't seem to work with a 5.4 kernel including. I also tested https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb and it exhibits the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931435] Re: crash fails to build on ubuntu 20.10 (Groovy) on arm64
Hello Ioanna, or anyone else affected, Accepted crash into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.2 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- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. 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: crash (Ubuntu Groovy) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-groovy ** Changed in: crash (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1931435 Title: crash fails to build on ubuntu 20.10 (Groovy) on arm64 Status in crash package in Ubuntu: Fix Released Status in crash source package in Groovy: Fix Committed Bug description: On arm64, crash fails to build with error "multiple definition of `tdesc_aarch64'" [1]. From upstream git log, seems it can be resolved with commit e770735200c02ac2414c394ea6ec5f7f033efe64 . [1] https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630861 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
