[Kernel-packages] [Bug 2009164] Re: Fix screen that remains blank forever after it gets locked
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1009.9 --- linux-oem-6.1 (6.1.0-1009.9) jammy; urgency=medium * jammy/linux-oem-6.1: 6.1.0-1009.9 -proposed tracker (LP: #2011921) * Fix spurious wakeup from S5 when TBT dock is plugged (LP: #2012846) - ACPICA: MADT: Add loong_arch-specific APICs support - ACPICA: Events: Support fixed PCIe wake event * The panel get blank for too long after disconnecting dock with monitors (LP: #2013114) - drm/i915/tc: Abort DP AUX transfer on a disconnected TC port * Packaging resync (LP: #1786013) - debian/dkms-versions -- update from kernel-versions (main/2023.03.20) * Jammy update: v6.1.22 upstream stable release (LP: #2013346) - interconnect: qcom: osm-l3: fix icc_onecell_data allocation - interconnect: qcom: sm8450: switch to qcom_icc_rpmh_* function - interconnect: qcom: qcm2290: Fix MASTER_SNOC_BIMC_NRT - perf/core: Fix perf_output_begin parameter is incorrectly invoked in perf_event_bpf_output - perf: fix perf_event_context->time - tracing/hwlat: Replace sched_setaffinity with set_cpus_allowed_ptr - drm/amd/display: Include virtual signal to set k1 and k2 values - drm/amd/display: fix k1 k2 divider programming for phantom streams - drm/amd/display: Remove OTG DIV register write for Virtual signals. - mptcp: refactor passive socket initialization - mptcp: use the workqueue to destroy unaccepted sockets - mptcp: fix UaF in listener shutdown - drm/amd/display: Fix DP MST sinks removal issue - arm64: dts: qcom: sm8450: Mark UFS controller as cache coherent - power: supply: bq24190: Fix use after free bug in bq24190_remove due to race condition - power: supply: da9150: Fix use after free bug in da9150_charger_remove due to race condition - arm64: dts: imx8dxl-evk: Disable hibernation mode of AR8031 for EQOS - arm64: dts: imx8dxl-evk: Fix eqos phy reset gpio - ARM: dts: imx6sll: e70k02: fix usbotg1 pinctrl - ARM: dts: imx6sll: e60k02: fix usbotg1 pinctrl - ARM: dts: imx6sl: tolino-shine2hd: fix usbotg1 pinctrl - arm64: dts: imx8mn: specify #sound-dai-cells for SAI nodes - arm64: dts: imx93: add missing #address-cells and #size-cells to i2c nodes - NFS: Fix /proc/PID/io read_bytes for buffered reads - xsk: Add missing overflow check in xdp_umem_reg - iavf: fix inverted Rx hash condition leading to disabled hash - iavf: fix non-tunneled IPv6 UDP packet type and hashing - iavf: do not track VLAN 0 filters - intel/igbvf: free irq on the error path in igbvf_request_msix() - igbvf: Regard vf reset nack as success - igc: fix the validation logic for taprio's gate list - i2c: imx-lpi2c: check only for enabled interrupt flags - i2c: mxs: ensure that DMA buffers are safe for DMA - i2c: hisi: Only use the completion interrupt to finish the transfer - scsi: scsi_dh_alua: Fix memleak for 'qdata' in alua_activate() - nfsd: don't replace page in rq_pages if it's a continuation of last page - net: dsa: b53: mmap: fix device tree support - net: usb: smsc95xx: Limit packet length to skb->len - efi/libstub: smbios: Use length member instead of record struct size - qed/qed_sriov: guard against NULL derefs from qed_iov_get_vf_info - xirc2ps_cs: Fix use after free bug in xirc2ps_detach - net: phy: Ensure state transitions are processed from phy_stop() - net: mdio: fix owner field for mdio buses registered using device-tree - net: mdio: fix owner field for mdio buses registered using ACPI - net: stmmac: Fix for mismatched host/device DMA address width - thermal/drivers/mellanox: Use generic thermal_zone_get_trip() function - mlxsw: core_thermal: Fix fan speed in maximum cooling state - drm/i915: Print return value on error - drm/i915/fbdev: lock the fbdev obj before vma pin - drm/i915/guc: Rename GuC register state capture node to be more obvious - drm/i915/guc: Fix missing ecodes - drm/i915/gt: perform uc late init after probe error injection - net: qcom/emac: Fix use after free bug in emac_remove due to race condition - net: usb: lan78xx: Limit packet length to skb->len - net/ps3_gelic_net: Fix RX sk_buff length - net/ps3_gelic_net: Use dma_mapping_error - octeontx2-vf: Add missing free for alloc_percpu - bootconfig: Fix testcase to increase max node - keys: Do not cache key in task struct if key is requested from kernel thread - ice: check if VF exists before mode check - iavf: fix hang on reboot with ice - i40e: fix flow director packet filter programming - bpf: Adjust insufficient default bpf_jit_limit - net/mlx5e: Set uplink rep as NETNS_LOCAL - net/mlx5e: Block entering switchdev mode with ns inconsistency - net/mlx5: Fix steering rules cleanup - net/mlx5e: Overcome slow response for first macsec ASO WQE - net/mlx5: Read the TC mapping of all
[Kernel-packages] [Bug 2009164] Re: Fix screen that remains blank forever after it gets locked
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009164 Title: Fix screen that remains blank forever after it gets locked Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] Once screen is locked under gnome-shell, the screen never wakes up and remains in blank forever. [Fix] "drm/i915: Create resized LUTs for ivb+ split gamma mode" makes gamma LUT operations in atomic context, so userspace can no longer misuse libdrm. "drm/i915: Rework legacy LUT handling" starts to use the reworked gamma LUT. Pull the whole series and series they depends upon to properly support gamma LUT. [Test] The easier way to reproduce the issue is to 1) Login under Wayland 2) Logout and login under X 3) Go back to wayland 4) Super + L to screenlock With the LUT reworked series applied, screen can always come back alive. [Where problems could occur] Regression can happen on refactoring patches with "no functional change intended", let alone overhauls like this one. So only OEM-6.1 and Unstable are targeted to contain the potential regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009164] Re: Fix screen that remains blank forever after it gets locked
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.9 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009164 Title: Fix screen that remains blank forever after it gets locked Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] Once screen is locked under gnome-shell, the screen never wakes up and remains in blank forever. [Fix] "drm/i915: Create resized LUTs for ivb+ split gamma mode" makes gamma LUT operations in atomic context, so userspace can no longer misuse libdrm. "drm/i915: Rework legacy LUT handling" starts to use the reworked gamma LUT. Pull the whole series and series they depends upon to properly support gamma LUT. [Test] The easier way to reproduce the issue is to 1) Login under Wayland 2) Logout and login under X 3) Go back to wayland 4) Super + L to screenlock With the LUT reworked series applied, screen can always come back alive. [Where problems could occur] Regression can happen on refactoring patches with "no functional change intended", let alone overhauls like this one. So only OEM-6.1 and Unstable are targeted to contain the potential regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009164] Re: Fix screen that remains blank forever after it gets locked
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009164 Title: Fix screen that remains blank forever after it gets locked Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] Once screen is locked under gnome-shell, the screen never wakes up and remains in blank forever. [Fix] "drm/i915: Create resized LUTs for ivb+ split gamma mode" makes gamma LUT operations in atomic context, so userspace can no longer misuse libdrm. "drm/i915: Rework legacy LUT handling" starts to use the reworked gamma LUT. Pull the whole series and series they depends upon to properly support gamma LUT. [Test] The easier way to reproduce the issue is to 1) Login under Wayland 2) Logout and login under X 3) Go back to wayland 4) Super + L to screenlock With the LUT reworked series applied, screen can always come back alive. [Where problems could occur] Regression can happen on refactoring patches with "no functional change intended", let alone overhauls like this one. So only OEM-6.1 and Unstable are targeted to contain the potential regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009164] Re: Fix screen that remains blank forever after it gets locked
The issue was there for quite a while, just being exposed by the steps listed in "Test" section as QA needs to login to Xorg to collect some info. So fixing this issue is crucial to our internal QA process. And 41 commits is for OEM kernel, Lunar requires much less commits. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009164 Title: Fix screen that remains blank forever after it gets locked Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: [Impact] Once screen is locked under gnome-shell, the screen never wakes up and remains in blank forever. [Fix] "drm/i915: Create resized LUTs for ivb+ split gamma mode" makes gamma LUT operations in atomic context, so userspace can no longer misuse libdrm. "drm/i915: Rework legacy LUT handling" starts to use the reworked gamma LUT. Pull the whole series and series they depends upon to properly support gamma LUT. [Test] The easier way to reproduce the issue is to 1) Login under Wayland 2) Logout and login under X 3) Go back to wayland 4) Super + L to screenlock With the LUT reworked series applied, screen can always come back alive. [Where problems could occur] Regression can happen on refactoring patches with "no functional change intended", let alone overhauls like this one. So only OEM-6.1 and Unstable are targeted to contain the potential regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009164] Re: Fix screen that remains blank forever after it gets locked
Does it work with earlier kernels, meaning is this bug a regression in itself? Backporting 41 commits to an LTS kernel might cause issues in the future.. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009164 Title: Fix screen that remains blank forever after it gets locked Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: [Impact] Once screen is locked under gnome-shell, the screen never wakes up and remains in blank forever. [Fix] "drm/i915: Create resized LUTs for ivb+ split gamma mode" makes gamma LUT operations in atomic context, so userspace can no longer misuse libdrm. "drm/i915: Rework legacy LUT handling" starts to use the reworked gamma LUT. Pull the whole series and series they depends upon to properly support gamma LUT. [Test] The easier way to reproduce the issue is to 1) Login under Wayland 2) Logout and login under X 3) Go back to wayland 4) Super + L to screenlock With the LUT reworked series applied, screen can always come back alive. [Where problems could occur] Regression can happen on refactoring patches with "no functional change intended", let alone overhauls like this one. So only OEM-6.1 and Unstable are targeted to contain the potential regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009164] Re: Fix screen that remains blank forever after it gets locked
** Tags added: oem-priority originate-from-2006667 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009164 Title: Fix screen that remains blank forever after it gets locked Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: [Impact] Once screen is locked under gnome-shell, the screen never wakes up and remains in blank forever. [Fix] "drm/i915: Create resized LUTs for ivb+ split gamma mode" makes gamma LUT operations in atomic context, so userspace can no longer misuse libdrm. "drm/i915: Rework legacy LUT handling" starts to use the reworked gamma LUT. Pull the whole series and series they depends upon to properly support gamma LUT. [Test] The easier way to reproduce the issue is to 1) Login under Wayland 2) Logout and login under X 3) Go back to wayland 4) Super + L to screenlock With the LUT reworked series applied, screen can always come back alive. [Where problems could occur] Regression can happen on refactoring patches with "no functional change intended", let alone overhauls like this one. So only OEM-6.1 and Unstable are targeted to contain the potential regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
