The display becomes frozen after some time when a HDMI device is connected.

Bug #2049027 reported by Soenke
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
Mantic
Fix Released
Undecided
Roxana Nicolescu
linux-signed-hwe-6.5 (Ubuntu)
Invalid
Critical
Unassigned
Mantic
Invalid
Undecided
Unassigned

Bug Description

SRU Justification:

[Impact]

Multiple users have reported frozen displays when external HDMI device
is connected on systems with intel graphics chipsets.

[Fix]

* backport 49e0a85ec344: "drm/i915/dmc: Don't enable any pipe DMC events"
from 6.6.9

[Test Plan]

* Tested on Intel TigerLake with iris Xe Graphics and no issues so far.
It seems it affects mostly Alder Lake though, but at least it does not
cause any issues on other models.
* It has also been tested upstream https://gitlab.freedesktop.org/drm/intel/-/issues/8685

[Where problems could occur]
* We could see issues on systems with Intel Graphics when HDMI devices
are connected during power state changes.

Old description:
It is exactly this bug: https://gitlab.freedesktop.org/drm/intel/-/issues/8685

It was fixed with that kernel commit:

commit 648d7be8ecf47b0556e32550145c70db153b16fb
Author: Ville Syrjälä <email address hidden>
Date: Mon Dec 11 23:37:47 2023 +0200

    drm/i915/dmc: Don't enable any pipe DMC events

https://<email address hidden>/

which was picked for 6.6.9.

I'd like to ask whether it is possible to apply that patch to the current Ubuntu kernel?

Best
Sönke

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 11 13:11:59 2024
InstallationDate: Installed on 2023-03-01 (316 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223)
SourcePackage: linux-signed-hwe-6.5
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Soenke (me-ngeefk4xay8) wrote :
Revision history for this message
Soenke (me-ngeefk4xay8) wrote :
tags: added: patch
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-signed-hwe-6.5 (Ubuntu):
status: New → Confirmed
Revision history for this message
Aaron Rainbolt (arraybolt3) wrote :

This is occurring on the Kubuntu Focus NX Gen 2 as well.

Changed in linux-signed-hwe-6.5 (Ubuntu):
importance: Undecided → Critical
Revision history for this message
Juerg Haefliger (juergh) wrote :

If it's in stable 6.6 it should/will trickle down into the Ubuntu 6.5 kernels. We're slightly behind upstream stable, 6.6.4 is currently in the works: bug #2051231

If you can't wait you can send a patch the the ML to expedite it.
https://wiki.ubuntu.com/KernelTeam/KernelUpdates

Revision history for this message
Roxana Nicolescu (roxanan) wrote :

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051584 is picking 6.6 which includes the fix.
And it's going to be included for the next cycle for mantic and therefore hwe-6.5.

Revision history for this message
Roxana Nicolescu (roxanan) wrote :

My bad that's 6.6, not 6.9. I'll backport it asap so that will be in the next cycle

Changed in linux (Ubuntu Mantic):
status: New → In Progress
assignee: nobody → Roxana Nicolescu (roxanan)
Changed in linux-signed-hwe-6.5 (Ubuntu Mantic):
status: New → Invalid
Changed in linux-signed-hwe-6.5 (Ubuntu):
status: Confirmed → Invalid
Changed in linux (Ubuntu):
status: New → Invalid
description: updated
Changed in linux (Ubuntu Mantic):
status: In Progress → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/6.5.0-25.25 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-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic-linux' to 'verification-failed-mantic-linux'.

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-mantic-linux-v2 verification-needed-mantic-linux
Revision history for this message
Soenke (me-ngeefk4xay8) wrote :

Sorry, I can't test it as I am using the 22.04 LTS Jammy and it is occuring on my work laptop, so I can't install 23.10 to check the fix.

Revision history for this message
Marian Rainer-Harbach (marianrh) wrote :

I'm in the same situation as Soenke: The bug occurs on my work laptop on 22.04 HWE (6.5.0-17). The Jammy proposed repository only offers 6.5.0-18 currently, so I can't test this.

Revision history for this message
Roxana Nicolescu (roxanan) wrote :

Hi all,

This fix was also propagated to jammy:linux-hwe-6.5 kernel.
The version (6.5.0-25.25~22.04.1) is not in proposed yet, it should be there in a day or 2.
But we have released (6.5.0-21.21~22.04.1) to proposed#2 (we use 2 separate streams because we run a smaller security cycle in parallel with the sru cycle)

So if you use
add-apt-repository ppa:canonical-kernel-team/proposed2

You should see 6.5.0-21.21~22.04.1 version there if you run
apt install linux-image-generic-hwe-22.04

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 6.5.0-21.21

---------------
linux (6.5.0-21.21) mantic; urgency=medium

  * mantic/linux: 6.5.0-21.21 -proposed tracker (LP: #2052603)

  * The display becomes frozen after some time when a HDMI device is connected.
    (LP: #2049027)
    - drm/i915/dmc: Don't enable any pipe DMC events

  * partproke is broken on empty loopback device (LP: #2049689)
    - block: Move checking GENHD_FL_NO_PART to bdev_add_partition()

  * CVE-2023-51781
    - appletalk: Fix Use-After-Free in atalk_ioctl

  * CVE-2023-51780
    - atm: Fix Use-After-Free in do_vcc_ioctl

  * CVE-2023-6915
    - ida: Fix crash in ida_free when the bitmap is empty

  * CVE-2024-0565
    - smb: client: fix OOB in receive_encrypted_standard()

  * CVE-2024-0582
    - io_uring: enable io_mem_alloc/free to be used in other parts
    - io_uring/kbuf: defer release of mapped buffer rings

  * CVE-2024-0646
    - net: tls, update curr on splice as well

 -- Manuel Diewald <email address hidden> Wed, 07 Feb 2024 13:06:01 +0100

Changed in linux (Ubuntu Mantic):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-lowlatency/6.5.0-21.21.1 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-mantic-linux-lowlatency' to 'verification-done-mantic-linux-lowlatency'. If the problem still exists, change the tag 'verification-needed-mantic-linux-lowlatency' to 'verification-failed-mantic-linux-lowlatency'.

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-mantic-linux-lowlatency-v2 verification-needed-mantic-linux-lowlatency
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-starfive-6.5/6.5.0-1008.9~22.04.1 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-linux-starfive-6.5' to 'verification-done-jammy-linux-starfive-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-starfive-6.5' to 'verification-failed-jammy-linux-starfive-6.5'.

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-starfive-6.5-v2 verification-needed-jammy-linux-starfive-6.5
Revision history for this message
Marian Rainer-Harbach (marianrh) wrote :

Hi Roxana,

I'm confused by your comment #11. You write about versions 6.5.0-21.21~22.04.1 and 6.5.0-25.25~22.04.1. Do both contain the fix?

As of today, I can see neither of these versions, but only 6.5.0.21.21~22.04.11 (.11, not .1!). And that version has already been released as a regular (not proposed) update.

Revision history for this message
Roxana Nicolescu (roxanan) wrote :

Yes, both contain the fix. We run two cycles in parallel (one for security that releases earlier nd contains critical fixes (mostly CVEs) and then the sru cycle that is released 2 weeks after.
This seemed critical and we decided to include in the security cycle so it will reach end users 2 weeks earlier than usual.
That's why I said it is included in both versions.
Now, please do test `6.5.0.21.21~22.04.11`, that has reached -updates indeed in the meantime so we can mark this as verified.

Note that .11 is the version of the meta package, the actual kernel package is .1

Revision history for this message
Marian Rainer-Harbach (marianrh) wrote :

Thanks for the clarification! I'm running 6.5.0-21-generic #21~22.04.1 now. I'll report if the problem occurs again (in my usage it happened every one or two days).

Revision history for this message
Marian Rainer-Harbach (marianrh) wrote :

I'm happy to report that in three working days the problem has not reoccurred. So the fix in kernel 6.5.0-21-generic #21~22.04.1 looks good to me.

Revision history for this message
Roxana Nicolescu (roxanan) wrote :

Good news. I'll mark this verified.

Revision history for this message
Roxana Nicolescu (roxanan) wrote :

Thanks for your help!

tags: added: verification-done-jammy-linux-starfive-6.5 verification-done-mantic-linux verification-done-mantic-linux-lowlatency
removed: verification-needed-jammy-linux-starfive-6.5 verification-needed-mantic-linux verification-needed-mantic-linux-lowlatency
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure/6.5.0-1016.16 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-mantic-linux-azure' to 'verification-done-mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic-linux-azure'.

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-mantic-linux-azure-v2 verification-needed-mantic-linux-azure
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws/6.5.0-1015.15 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-mantic-linux-aws' to 'verification-done-mantic-linux-aws'. If the problem still exists, change the tag 'verification-needed-mantic-linux-aws' to 'verification-failed-mantic-linux-aws'.

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-mantic-linux-aws-v2 verification-needed-mantic-linux-aws
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-hwe-6.5/6.5.0-25.25~22.04.1 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-linux-hwe-6.5' to 'verification-done-jammy-linux-hwe-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.5' to 'verification-failed-jammy-linux-hwe-6.5'.

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-hwe-6.5-v2 verification-needed-jammy-linux-hwe-6.5
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-6.5/6.5.0-1014.14 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-linux-nvidia-6.5' to 'verification-done-jammy-linux-nvidia-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-6.5' to 'verification-failed-jammy-linux-nvidia-6.5'.

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-nvidia-6.5-v2 verification-needed-jammy-linux-nvidia-6.5
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.