[Kernel-packages] [Bug 1960839] Re: Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
** Changed in: linux-firmware (Ubuntu)
Status: Invalid => Fix Released
** Changed in: linux-firmware (Ubuntu)
Importance: Undecided => Medium
--
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/1960839
Title:
Missing firmware /lib/firmware/intel/ice/ddp/ice.pkg for ice driver
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Bionic:
Fix Committed
Bug description:
[Impact]
* Missing firmware for Intel ICE driver on Bionic,
which is supported by the HWE kernel from Focal.
[Fix]
* commit 9ae61e7d8658 ("ice: Add package file for Intel E800 series driver")
brings the Bionic package in line with Focal (ice-1.3.4.0.pkg,LICENSE.ice)
[Test Case]
* Without firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: Direct firmware load for intel/ice/ddp/ice.pkg failed
with error -2
ice :98:00.0: The DDP package file was not found or could not be
read. Entering Safe Mode
ice :98:00.0: Package download failed. Advanced features disabled -
Device now in Safe Mode
* With firmware:
ice :98:00.0: firmware 5.4.5 api 1.7.6 nvm 2.40 0x8000706a 0.0.0
build 0x391f7640
ice :98:00.0: The DDP package was successfully loaded: ICE OS Default
Package version 1.3.4.0
ice :98:00.0: DCB is enabled in the hardware, max number of TCs
supported on this port are 8
ice :98:00.0: FW LLDP is disabled, DCBx/LLDP in SW mode.
[Where problems could occur]
* Systems with devices managed by the ice driver on Bionic HWE kernel
from Focal.
* The firmware enables advanced features, increasing driver exposure
and device activity.
* This has been available on Focal, which helps with some chance of issues
being hit and
reported previously (e.g. bug 1939855, searched for 'kernel ice driver' on
bugs.lp.net).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1960839/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951580] Re: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Jammy) -- 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/1951580 Title: backport-iwlwifi-dkms fails to build with kernel 5.15 jammy Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in backport-iwlwifi-dkms source package in Jammy: Fix Released Bug description: [Impact] backport-iwlwifi-dkms fails to build on the latest jammy kernel 5.15: CC [M] /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.o In file included from /tmp/backport-iwlwifi-dkms/backport-include/asm-generic/bug.h:3, from ./arch/x86/include/asm/bug.h:84, from ./include/linux/bug.h:5, from /tmp/backport-iwlwifi-dkms/backport-include/linux/bug.h:3, from /tmp/backport-iwlwifi-dkms/backport-include/linux/kernel.h:4, from ./include/linux/skbuff.h:13, from /tmp/backport-iwlwifi-dkms/backport-include/linux/skbuff.h:3, from ./include/linux/if_ether.h:19, from /tmp/backport-iwlwifi-dkms/backport-include/linux/if_ether.h:3, from ./include/linux/etherdevice.h:20, from /tmp/backport-iwlwifi-dkms/backport-include/linux/etherdevice.h:3, from /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:6: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c: In function ‘iwl_mei_free_shared_mem’: /tmp/backport-iwlwifi-dkms/drivers/net/wireless/intel/iwlwifi/mei/main.c:243:17: error: implicit declaration of function ‘mei_cldev_dma_unmap’ [-Werror=implicit-function-declaration] 243 | WARN_ON(mei_cldev_dma_unmap(cldev)); | ^~~ [Test case] sudo apt install backport-iwlwifi-dkms [Fix] The driver assumes that kernels > 5.13 provide mei_cldev_dma_map/unmap() when CONFIG_WLAN_VENDOR_INTEL_MEI is defined. However these functions and the config option are not available at all in recent kernels. So instead of relying on the specific kernel version simply rely on the availability of CONFIG_WLAN_VENDOR_INTEL_MEI to determine if the kernel has the required functions defined, or if the driver needs to provide a custom implementation of these functions. [Regression potential] We may see build errors in newer kernel if CONFIG_WLAN_VENDOR_INTEL_MEI is merged upstream and these functions are actually provided by recent kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1951580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in nvidia-settings source package in Impish: Fix Released Status in ubuntu-drivers-common source package in Impish: Fix Released Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Released Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939855] Re: [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands
** No longer affects: focal (Ubuntu) ** No longer affects: focal (Ubuntu Focal) ** Project changed: dellserver => ubuntu-translations ** No longer affects: ubuntu-translations ** Changed in: linux (Ubuntu) Status: Invalid => Fix Released ** Changed in: linux (Ubuntu) Importance: Undecided => High -- 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/1939855 Title: [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] When we run the command, ethtool -d with Intel cards (ice driver), the kernel crashes because of the ice driver. The same works fine with HWE kernel (5.11). Here, we do not see any crash. [FIXES] ice: Fix bad register reads The "ethtool -d" handler reads registers in the ice_regs_dump_list array and returns read values back to the userspace. commitID: 1fba4a8a92706c89716449b1aab1b6879f438d34 https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/ethernet/intel/ice?id=1fba4a8a92706c89716449b1aab1b6879f438d34 [TESTING] Install Focal on a system with an E810 network device. Ensure the network device has an IP address and has connectivity Run ethtool -d Expected result: Prints a register dump for the specified network device [REGRESSION RISK] The regression risk is low [OTHER INFO] I have added the fix, built the kernel and tested the fix. https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e810_ethtool_fix_next To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939855/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
** Changed in: kdump-tools (Ubuntu) Status: Fix Committed => In Progress -- 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/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in kdump-tools package in Ubuntu: In Progress Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in kdump-tools source package in Groovy: Invalid Status in makedumpfile source package in Groovy: Won't Fix Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963799] [NEW] no path found matching pattern /usr/bin/ss
Public bug reported: SUMMARY There's a problem that maybe is caused by packaging of the iproute2 package. STEPS TO REPRODUCE $ which ss /usr/bin/ss $ dpkg -S /usr/bin/ss dpkg-query: no path found matching pattern /usr/bin/ss. # In Spanish: dpkg-query: no se ha encontrado ningún paquete que corresponda con el patrón /usr/bin/ss. $ dpkg -S /bin/ss iproute2: /bin/ss A POSSIBLY EXPECTED RESULT $ dpkg -S /usr/bin/ss iproute2: /usr/bin/ss OR ANOTHER POSSIBLY EXPECTED RESULT $ which ss /bin/ss OS VERSION Operating System: Kubuntu 21.10 THANKS! ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1963799 Title: no path found matching pattern /usr/bin/ss Status in iproute2 package in Ubuntu: New Bug description: SUMMARY There's a problem that maybe is caused by packaging of the iproute2 package. STEPS TO REPRODUCE $ which ss /usr/bin/ss $ dpkg -S /usr/bin/ss dpkg-query: no path found matching pattern /usr/bin/ss. # In Spanish: dpkg-query: no se ha encontrado ningún paquete que corresponda con el patrón /usr/bin/ss. $ dpkg -S /bin/ss iproute2: /bin/ss A POSSIBLY EXPECTED RESULT $ dpkg -S /usr/bin/ss iproute2: /usr/bin/ss OR ANOTHER POSSIBLY EXPECTED RESULT $ which ss /bin/ss OS VERSION Operating System: Kubuntu 21.10 THANKS! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1963799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963802] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1963802 Title: lenovo x260: unable to suspend or power off cleanly Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to the new 5.15 kernel in Jammy development I've been unable to suspend or power of my x260 successfully. suspend - laptop appears to have suspended with the power led pulsing but then won't resume power off - laptop appears to have powered off but infact has not - power led is off - have to hold down power button to 5s to fully power off. I was convinced this was a hardware issue so tried with a 20.04 live image which completed both operations sucessfully. I've tried all 5.15 kernels including the one in jammy-proposed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jamespage 3148 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 6 11:17:25 2022 InstallationDate: Installed on 2018-10-18 (1234 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-05-12 (298 days ago) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963802/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1963802] [NEW] lenovo x260: unable to suspend or power off cleanly
Public bug reported: Since upgrading to the new 5.15 kernel in Jammy development I've been unable to suspend or power of my x260 successfully. suspend - laptop appears to have suspended with the power led pulsing but then won't resume power off - laptop appears to have powered off but infact has not - power led is off - have to hold down power button to 5s to fully power off. I was convinced this was a hardware issue so tried with a 20.04 live image which completed both operations sucessfully. I've tried all 5.15 kernels including the one in jammy-proposed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jamespage 3148 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 6 11:17:25 2022 InstallationDate: Installed on 2018-10-18 (1234 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-05-12 (298 days ago) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy -- 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/1963802 Title: lenovo x260: unable to suspend or power off cleanly Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to the new 5.15 kernel in Jammy development I've been unable to suspend or power of my x260 successfully. suspend - laptop appears to have suspended with the power led pulsing but then won't resume power off - laptop appears to have powered off but infact has not - power led is off - have to hold down power button to 5s to fully power off. I was convinced this was a hardware issue so tried with a 20.04 live image which completed both operations sucessfully. I've tried all 5.15 kernels including the one in jammy-proposed. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-18-generic 5.15.0-18.18 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jamespage 3148 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 6 11:17:25 2022 InstallationDate: Installed on 2018-10-18 (1234 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20F6CTO1WW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220302.gitee0667aa-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2021-05-12 (298 days ago) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/
[Kernel-packages] [Bug 1963805] [NEW] Failed to grab modeset ownership
Public bug reported: Starting from package 495, I notice lots of messages like that in dmesg: [89502.662730] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [89502.662850] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [89502.662899] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [89502.662944] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [92090.669597] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [92090.669715] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [92090.669766] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownership [92090.669813] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to grab modeset ownershi With 495 it was 1 message after boot, and one after each waking up of the monitor from sleep. With 510 there are numerous error messages per wake up. I have followed up with nvidia: https://forums.developer.nvidia.com/t/ubuntu-21-10-failed-to-grab-modeset-ownership-with-495-44/193867/35 but ultimately their employee tells that this is expected behavour, and something else triggers the message. [quote="amrits, post:37, topic:193867, full:true"] HI All, The warning message is expected. When a client (such as the modesetting driver) attempts to open our DRM device node while modesetting permission is already acquired by something else (like the NVIDIA X driver), it has to fail, but the kernel won’t let us return a failure after v5.9-rc1, so we print this message. It won’t impact functionality of the NVIDIA X driver that already has modesetting permission. Safe to ignore as long as long as you didn’t need the other client to actually get modesetting permission. If you want to suppress the error, you would need to find which client is attempting to open the NVIDIA DRM device node and prevent it from doing so. [/quote] I use Ubuntu 21.10 with all updates. Description:Ubuntu 21.10 Release:21.10 nvidia-headless-510: Installed: (none) Candidate: 510.54-0ubuntu0.21.10.1 Version table: 510.54-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-proposed/restricted amd64 Packages 510.47.03-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/restricted amd64 Packages nvidia-compute-utils-510: Installed: 510.54-0ubuntu0.21.10.1 Candidate: 510.54-0ubuntu0.21.10.1 Version table: *** 510.54-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-proposed/restricted amd64 Packages 100 /var/lib/dpkg/status 510.47.03-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/restricted amd64 Packages nvidia-dkms-510: Installed: 510.54-0ubuntu0.21.10.1 Candidate: 510.54-0ubuntu0.21.10.1 Version table: *** 510.54-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-proposed/restricted amd64 Packages 100 /var/lib/dpkg/status 510.47.03-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/restricted amd64 Packages nvidia-driver-510: Installed: 510.54-0ubuntu0.21.10.1 Candidate: 510.54-0ubuntu0.21.10.1 Version table: *** 510.54-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-proposed/restricted amd64 Packages 100 /var/lib/dpkg/status 510.47.03-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/restricted amd64 Packages nvidia-utils-510: Installed: 510.54-0ubuntu0.21.10.1 Candidate: 510.54-0ubuntu0.21.10.1 Version table: *** 510.54-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-proposed/restricted amd64 Packages 100 /var/lib/dpkg/status 510.47.03-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-updates/restricted amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/restricted amd64 Packages nvidia-kernel-common-510: Installed: 510.54-0ubuntu0.21.10.1 Candidate: 510.54-0ubuntu0.21.10.1 Version table: *** 510.54-0ubuntu0.21.10.1 500 500 http://pl.archive.ubuntu.com/ubuntu impish-proposed/restricted amd64 Packages 100 /var/lib/dpkg/status 510.47
[Kernel-packages] [Bug 1961406] Re: Known bug in IGC kernel module causes shutdown bug in z690 environments
** Summary changed: - Known bug in IGC causes shutdown bug in z690 environments + Known bug in IGC kernel module causes shutdown bug in z690 environments -- 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/1961406 Title: Known bug in IGC kernel module causes shutdown bug in z690 environments Status in linux package in Ubuntu: Confirmed Bug description: I own a Asus z690 Apex board, and shutdown hangs because of a bug in IGC driver. I cannot provide any logs because this happens after filesystem driver has been shut down and display/graphics have been turned of. The PC simply never turns off. I can disable the network interface in UEFI Bios, then the problem disappears. As far as I know a newer 5.15.x version already contains a fix. Since most users that own a AlderLake / z690 will be affected by this bug it should be fixed before release. I read about some MSI boards does not have that problem, but any other mainboards (asus, asrocks, gigabyte etc) seem to have this bug. I updated my bios and tried different shutdown commands without success Related links: - https://groups.google.com/g/linux.debian.bugs.dist/c/i6buM9KpulI?pli=1 - https://bbs.archlinux.org/viewtopic.php?id=272338 - https://www.reddit.com/r/Fedora/comments/r3hxt0/restartshut_down_problem_on_kernel_5154201/ ``` phoenix@dev:~$ lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 phoenix@dev:~$ cat /proc/version_signature Ubuntu 5.15.0-18.18-generic 5.15.12 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.18.18 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Feb 18 13:37:10 2022 InstallationDate: Installed on 2021-06-11 (252 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: ASUS System Product Name ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-18-generic root=UUID=1d617086-e30d-4dd3-a313-3b435ea89649 ro quiet splash mitigations=off systemd.unified_cgroup_hierarchy=false vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-18-generic N/A linux-backports-modules-5.15.0-18-generic N/A linux-firmware 20220124.git0c6a7b3b-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-01-14 (34 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 11.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS Z690 APEX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd01/26/2022:br11.1:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSZ690APEX:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961406/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953575] Re: Update gvnic driver code
** Changed in: linux-gcp (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Impish) Status: In Progress => Fix Committed ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1953575 Title: Update gvnic driver code Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Focal: Fix Committed Status in linux-gcp source package in Impish: Fix Committed Bug description: The GCE internal team responsible for gVNIC would like to have driver updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. [Impact] Missing functionality from the Google gvnic driver [Test Plan] Confirm that gvnic module still loads and operates the gvnic driver. More extensive testing done by the gvnic developers at GCE [Regression potential] Possible regression in gvnic behaviour or functionality. Changes are confined to the gvnic driver code so regression potential is limited to gvnic only. List of changes: 3712db620c613 gve: DQO: Configure interrupts on device up a9fd7559a367a gve: Check TX QPL was actually assigned c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check f48adc2842b17 gve: DQO: Remove incorrect prefetch 98fd04939ae7e gve: Simplify code and axe the use of a deprecated API 56c0904d8491d gve: Propagate error codes to caller 86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo() ea364622fb118 gve: Fix warnings reported for DQO patchset 8890e8783c6e6 gve: DQO: Add RX path abfc55f80d423 gve: DQO: Add TX path ef63867982913 gve: DQO: Add ring allocation and initialization dc3e0aef11bf0 gve: DQO: Add core netdev features 873fd9825efd7 gve: Update adminq commands to support DQO queues 543dc0e670472 gve: Add DQO fields for core data structures b580730931348 gve: Add dqo descriptors 74e123d3c62b2 gve: Add support for DQO RX PTYPE map a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic 3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format` a6b09c93c1735 gve: Introduce a new model for device options 34d6b75678979 gve: Add support for raw addressing in the tx path 30b6221596699 Revert "gve: Check TX QPL was actually assigned" 98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument 5fc5c482008b5 gve: Move some static functions to a common file ed1e0daeee1ac gve: Rx Buffer Recycling da57760d6370d gve: Add support for raw addressing to the rx path b512608f33d8e gve: Add support for raw addressing device option e85394c77cdce gve: Enable Link Speed Reporting in the driver. 8961791d8ba16 gve: Batch AQ commands for creating and destroying queues. 50bafd6d5a041 gve: NIC stats for report-stats and for ethtool feccb84085904 gve: Add Gvnic stats AQ command and ethtool show/set-priv-flags. 08578185ab296 gve: Use dev_info/err instead of netif_info/err. 613ed2d16246f gve: Add stats for gve. 250d220740d21 gve: Get and set Rx copybreak via ethtool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1953575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953575] Re: Update gvnic driver code
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1953575 Title: Update gvnic driver code Status in linux-gcp package in Ubuntu: In Progress Status in linux-gcp source package in Focal: Fix Committed Status in linux-gcp source package in Impish: Fix Committed Bug description: The GCE internal team responsible for gVNIC would like to have driver updates backported for both Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. [Impact] Missing functionality from the Google gvnic driver [Test Plan] Confirm that gvnic module still loads and operates the gvnic driver. More extensive testing done by the gvnic developers at GCE [Regression potential] Possible regression in gvnic behaviour or functionality. Changes are confined to the gvnic driver code so regression potential is limited to gvnic only. List of changes: 3712db620c613 gve: DQO: Configure interrupts on device up a9fd7559a367a gve: Check TX QPL was actually assigned c69a8892d5836 gve: fix the wrong AdminQ buffer overflow check f48adc2842b17 gve: DQO: Remove incorrect prefetch 98fd04939ae7e gve: Simplify code and axe the use of a deprecated API 56c0904d8491d gve: Propagate error codes to caller 86cd2b58d1e63 gve: DQO: Fix off by one in gve_rx_dqo() ea364622fb118 gve: Fix warnings reported for DQO patchset 8890e8783c6e6 gve: DQO: Add RX path abfc55f80d423 gve: DQO: Add TX path ef63867982913 gve: DQO: Add ring allocation and initialization dc3e0aef11bf0 gve: DQO: Add core netdev features 873fd9825efd7 gve: Update adminq commands to support DQO queues 543dc0e670472 gve: Add DQO fields for core data structures b580730931348 gve: Add dqo descriptors 74e123d3c62b2 gve: Add support for DQO RX PTYPE map a9a3bfdd5f679 gve: adminq: DQO specific device descriptor logic 3e6d068c103f8 gve: Introduce per netdev `enum gve_queue_format` a6b09c93c1735 gve: Introduce a new model for device options 34d6b75678979 gve: Add support for raw addressing in the tx path 30b6221596699 Revert "gve: Check TX QPL was actually assigned" 98478993bb3f9 gve: Make gve_rx_slot_page_info.page_offset an absolute offset ff4b20bb7e5f4 gve: gve_rx_copy: Move padding to an argument 5fc5c482008b5 gve: Move some static functions to a common file ed1e0daeee1ac gve: Rx Buffer Recycling da57760d6370d gve: Add support for raw addressing to the rx path b512608f33d8e gve: Add support for raw addressing device option e85394c77cdce gve: Enable Link Speed Reporting in the driver. 8961791d8ba16 gve: Batch AQ commands for creating and destroying queues. 50bafd6d5a041 gve: NIC stats for report-stats and for ethtool feccb84085904 gve: Add Gvnic stats AQ command and ethtool show/set-priv-flags. 08578185ab296 gve: Use dev_info/err instead of netif_info/err. 613ed2d16246f gve: Add stats for gve. 250d220740d21 gve: Get and set Rx copybreak via ethtool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1953575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1962731] Re: No SYS%LPI residency in suspend when ethernet is connected
** Changed in: linux-signed-oem-5.14 (Ubuntu) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1962731 Title: No SYS%LPI residency in suspend when ethernet is connected Status in OEM Priority Project: New Status in linux-signed-oem-5.14 package in Ubuntu: New Bug description: Try the command # turbostat -S --show Pkg%pc2,Pkg%pc3,Pkg%pc6,Pkg%pc7,Pkg%pc8,Pkg%pc9,Pk%pc10,CPU%LPI,SYS%LPI rtcwake -m mem -s 15 ... Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 9.78 0.25 0.86 6.21 4.37 0.00 67.53 67.67 0.00 There is no SYS%LPI residency. Unplug ethernet, the residency become Pkg%pc2 Pkg%pc3 Pkg%pc6 Pkg%pc7 Pkg%pc8 Pkg%pc9 Pk%pc10 CPU%LPI SYS%LPI 8.63 0.13 0.07 22.56 1.24 0.00 53.95 54.08 53.82 The ethernet controller is I219-LM. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1024-oem 5.14.0-1024.26 ProcVersionSignature: Ubuntu 5.14.0-1024.26-oem 5.14.21 Uname: Linux 5.14.0-1024-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 2 05:24:51 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-pidgeot+X92 InstallationDate: Installed on 2021-11-03 (118 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962731/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956515] Re: Linux Mint don't start with battery .
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956515 Title: Linux Mint don't start with battery . Status in linux package in Ubuntu: Expired Bug description: Linux mint 20.2 (kernel 5.4.0-44, 5.4.0-43) don't start with battery in Lenovo Ideapad S145 (Amd Ryzen 5 3500 U, Cinnamon 5.0.7) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956562] Re: 5.15 kernel selftest srv6_end_dt4_l3vpn_test.sh failure
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956562 Title: 5.15 kernel selftest srv6_end_dt4_l3vpn_test.sh failure Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Script srv6_end_dt4_l3vpn_test.sh reports the following failure (upstream issue): 15321 19:35:52 DEBUG| [stdout] # 15322 19:35:52 DEBUG| [stdout] # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant 15323 19:35:52 DEBUG| [stdout] # 15324 19:35:56 DEBUG| [stdout] # 15325 19:35:56 DEBUG| [stdout] # TEST: Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] 15326 19:36:00 DEBUG| [stdout] # 15327 19:36:00 DEBUG| [stdout] # TEST: Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] 15328 19:36:04 DEBUG| [stdout] # 15329 19:36:04 DEBUG| [stdout] # TEST: Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] 15330 19:36:08 DEBUG| [stdout] # 15331 19:36:08 DEBUG| [stdout] # TEST: Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] 15332 19:36:08 DEBUG| [stdout] # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1956562/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956561] Re: 5.15 kernel selftest srv6_end_dt46_l3vpn_test.sh failure
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1956561 Title: 5.15 kernel selftest srv6_end_dt46_l3vpn_test.sh failure Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Bug description: Kernel selftest srv6_end_dt46_l3vpn_test.sh reports the following error (it seems to be an upstream issue): 15187 19:34:40 DEBUG| [stdout] # 15188 19:34:40 DEBUG| [stdout] # TEST SECTION: SRv6 VPN connectivity test among hosts in the same tenant 15189 19:34:40 DEBUG| [stdout] # 15190 19:34:41 DEBUG| [stdout] # 15191 19:34:41 DEBUG| [stdout] # TEST: IPv6 Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [ OK ] 15192 19:34:45 DEBUG| [stdout] # 15193 19:34:45 DEBUG| [stdout] # TEST: IPv4 Hosts connectivity: hs-t100-1 -> hs-t100-2 (tenant 100) [FAIL] 15194 19:34:45 DEBUG| [stdout] # 15195 19:34:45 DEBUG| [stdout] # TEST: IPv6 Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [ OK ] 15196 19:34:49 DEBUG| [stdout] # 15197 19:34:49 DEBUG| [stdout] # TEST: IPv4 Hosts connectivity: hs-t100-2 -> hs-t100-1 (tenant 100) [FAIL] 15198 19:34:50 DEBUG| [stdout] # 15199 19:34:50 DEBUG| [stdout] # TEST: IPv6 Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [ OK ] 15200 19:34:54 DEBUG| [stdout] # 15201 19:34:54 DEBUG| [stdout] # TEST: IPv4 Hosts connectivity: hs-t200-3 -> hs-t200-4 (tenant 200) [FAIL] 15202 19:34:54 DEBUG| [stdout] # 15203 19:34:54 DEBUG| [stdout] # TEST: IPv6 Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [ OK ] 15204 19:34:58 DEBUG| [stdout] # 15205 19:34:58 DEBUG| [stdout] # TEST: IPv4 Hosts connectivity: hs-t200-4 -> hs-t200-3 (tenant 200) [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1956561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927067] Re: Add s2idle support on AMD Renoir and Cezanne
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1927067 Title: Add s2idle support on AMD Renoir and Cezanne 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: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] S2idle doesn't work on AMD Renoir and Cezanne. [Fix] Backport AMD PMC driver and pull many new patches let AMDGPU support s2idle. [Test] Suspend the laptop and the system freezes. With the patch applied, suspend works but with some caveats: 1) Keyboard sometimes can't wake up the laptop. 2) Touchpad sometimes can wake up the laptop. 3) RTC can't wake up the laptop. (Hardware Limitation) [Where problems could occur] Most changes are limited to logic of suspend/resume, and specific to Renoir GFX. However, there are some refactoring patches may cause unintended results, so AMDGPU may break for sleep/hibernation/runtime suspend on non-Renoir GFXs. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1927067/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
