Bug#1026234: linux-image-6.0.0-5-amd64: i915 driver fails on resume

To: Floris Bruynooghe <flub@devork.be>, 1026234@bugs.debian.org
Subject: Bug#1026234: linux-image-6.0.0-5-amd64: i915 driver fails on resume
From: Salvatore Bonaccorso <carnil@debian.org>
Date: Tue, 20 Dec 2022 06:55:47 +0100
Message-id: <[🔎] Y6FOY3A0o1P5369J@eldamar.lan>
Reply-to: Salvatore Bonaccorso <carnil@debian.org>, 1026234@bugs.debian.org
In-reply-to: <[🔎] 874jtup66k.fsf@devork.be>
References: <[🔎] 167122251554.179465.12775226383287989931.reportbug@fredriksen.zt.devork.be> <[🔎] Y5zaDzqq7KLhs3cv@eldamar.lan> <[🔎] 87pmcjt4mn.fsf@devork.be> <[🔎] Y5zpMFJulOy4fBN2@eldamar.lan> <[🔎] 167122251554.179465.12775226383287989931.reportbug@fredriksen.zt.devork.be> <[🔎] 874jtup66k.fsf@devork.be> <[🔎] 167122251554.179465.12775226383287989931.reportbug@fredriksen.zt.devork.be>
Hi Floris,

On Sat, Dec 17, 2022 at 01:26:27PM +0100, Floris Bruynooghe wrote:
> Hi Salvatore,
> 
> On Fri 16 Dec 2022 at 22:54 +0100, Salvatore Bonaccorso wrote:
> > On Fri, Dec 16, 2022 at 10:34:08PM +0100, Floris Bruynooghe wrote:
> >> On Fri 16 Dec 2022 at 21:50 +0100, Salvatore Bonaccorso wrote:
> >> > On Fri, Dec 16, 2022 at 09:28:35PM +0100, Floris Bruynooghe wrote:
> >> >> Package: src:linux
> >> >> Version: 6.0.10-2
> >> >> Severity: important
> >> >> 
> >> >> Dear Maintainer,
> >> >> 
> >> >> Since the 6.0.0-5 kernel the i915 graphics driver often fails on resume.
> >> >> Downgrading to the 6.0.0-4 kernel fixes it and the driver works
> >> >> flawlessly across resume, changing displays etc.
> >> >> 
> >> >> On the -5 kernel the following errors are observed when the driver
> >> >> crashes:
> >> >> 
> >> >> Dec 13 11:26:58 fredriksen kernel: drm card0-DP-9: PM: parent card0 should not be sleeping
> >> >> Dec 13 11:26:58 fredriksen kernel: drm card0-DP-10: PM: parent card0 should not be sleeping
> >> >> Dec 13 11:26:58 fredriksen kernel: drm card0-DP-11: PM: parent card0 should not be sleeping
> >> >> Dec 13 11:26:58 fredriksen kernel: i915 0000:00:02.0: [drm] *ERROR* Sending link address failed with -5
> >> >> Dec 13 11:26:58 fredriksen kernel: ------------[ cut here ]------------
> >> >> Dec 13 11:26:58 fredriksen kernel: i915 0000:00:02.0: drm_WARN_ON(dig_port->tc_mode != TC_PORT_DISCONNECTED)
> >> >> Dec 13 11:26:58 fredriksen kernel: WARNING: CPU: 0 PID: 27095 at drivers/gpu/drm/i915/display/intel_tc.c:711 int>
> >> >> Dec 13 11:26:58 fredriksen kernel: Modules linked in: usblp ctr ccm rfcomm cmac algif_hash algif_skcipher af_alg>
> >> >> Dec 13 11:26:58 fredriksen kernel:  snd_sof_utils ecdh_generic snd_soc_hdac_hda ecc snd_hda_ext_core snd_soc_acp>
> >> >> Dec 13 11:26:58 fredriksen kernel:  configfs efivarfs ip_tables x_tables autofs4 btrfs blake2b_generic libcrc32c>
> >> >> Dec 13 11:26:58 fredriksen kernel: CPU: 0 PID: 27095 Comm: kworker/u32:101 Not tainted 6.0.0-5-amd64 #1  Debian >
> >> >> Dec 13 11:26:58 fredriksen kernel: Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
> >> >> Dec 13 11:26:58 fredriksen kernel: Workqueue: events_unbound async_run_entry_fn
> >> >> Dec 13 11:26:58 fredriksen kernel: RIP: 0010:intel_tc_port_sanitize+0x2d2/0x490 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 a7 44 42 e3 48 c7 c1 f8 a6 d6 c0>
> >> >> Dec 13 11:26:58 fredriksen kernel: RSP: 0018:ffffa84dc5debc08 EFLAGS: 00010286
> >> >> Dec 13 11:26:58 fredriksen kernel: RAX: 0000000000000000 RBX: ffff9c8120650000 RCX: 0000000000000000
> >> >> Dec 13 11:26:58 fredriksen kernel: RDX: 0000000000000001 RSI: ffffffffa4b7eeea RDI: 00000000ffffffff
> >> >> Dec 13 11:26:58 fredriksen kernel: RBP: 0000000000000000 R08: ffffffffa5262260 R09: 00000000a5b5348a
> >> >> Dec 13 11:26:58 fredriksen kernel: R10: ffffffffffffffff R11: 000000000000004a R12: ffff9c81101a2000
> >> >> Dec 13 11:26:58 fredriksen kernel: R13: ffff9c8101f19900 R14: 0000000000000000 R15: ffff9c81101a2000
> >> >> Dec 13 11:26:58 fredriksen kernel: FS:  0000000000000000(0000) GS:ffff9c883f400000(0000) knlGS:0000000000000000
> >> >> Dec 13 11:26:58 fredriksen kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> >> >> Dec 13 11:26:58 fredriksen kernel: CR2: 000055710e140b16 CR3: 00000002db810003 CR4: 0000000000770ef0
> >> >> Dec 13 11:26:58 fredriksen kernel: PKRU: 55555554
> >> >> Dec 13 11:26:58 fredriksen kernel: Call Trace:
> >> >> Dec 13 11:26:58 fredriksen kernel:  <TASK>
> >> >> Dec 13 11:26:58 fredriksen kernel:  intel_ddi_sync_state+0x3f/0x90 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  intel_modeset_setup_hw_state+0x3b1/0x1410 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? _raw_spin_lock_irq+0x19/0x40
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? wait_for_completion+0x91/0x160
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? drm_modeset_lock+0x63/0xd0 [drm]
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? ww_mutex_lock+0x14/0x80
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? __intel_display_resume+0x1a/0xe0 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  __intel_display_resume+0x1a/0xe0 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  intel_display_resume+0xfc/0x140 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  i915_drm_resume+0xba/0x130 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? pci_pm_poweroff_noirq+0x100/0x100
> >> >> Dec 13 11:26:58 fredriksen kernel:  dpm_run_callback+0x47/0x150
> >> >> Dec 13 11:26:58 fredriksen kernel:  device_resume+0x88/0x190
> >> >> Dec 13 11:26:58 fredriksen kernel:  async_resume+0x19/0x30
> >> >> Dec 13 11:26:58 fredriksen kernel:  async_run_entry_fn+0x2d/0x130
> >> >> Dec 13 11:26:58 fredriksen kernel:  process_one_work+0x1c4/0x380
> >> >> Dec 13 11:26:58 fredriksen kernel:  worker_thread+0x4d/0x380
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? rescuer_thread+0x3a0/0x3a0
> >> >> Dec 13 11:26:58 fredriksen kernel:  kthread+0xe6/0x110
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? kthread_complete_and_exit+0x20/0x20
> >> >> Dec 13 11:26:58 fredriksen kernel:  ret_from_fork+0x1f/0x30
> >> >> Dec 13 11:26:58 fredriksen kernel:  </TASK>
> >> >> Dec 13 11:26:58 fredriksen kernel: ---[ end trace 0000000000000000 ]---
> >> >> Dec 13 11:26:58 fredriksen kernel: ------------[ cut here ]------------
> >> >> Dec 13 11:26:58 fredriksen kernel: i915 0000:00:02.0: drm_WARN_ON(dig_port->tc_lock_wakeref)
> >> >> Dec 13 11:26:58 fredriksen kernel: WARNING: CPU: 0 PID: 27095 at drivers/gpu/drm/i915/display/intel_tc.c:712 int>
> >> >> Dec 13 11:26:58 fredriksen kernel: Modules linked in: usblp ctr ccm rfcomm cmac algif_hash algif_skcipher af_alg>
> >> >> Dec 13 11:26:58 fredriksen kernel:  snd_sof_utils ecdh_generic snd_soc_hdac_hda ecc snd_hda_ext_core snd_soc_acp>
> >> >> Dec 13 11:26:58 fredriksen kernel:  configfs efivarfs ip_tables x_tables autofs4 btrfs blake2b_generic libcrc32c>
> >> >> Dec 13 11:26:58 fredriksen kernel: CPU: 0 PID: 27095 Comm: kworker/u32:101 Tainted: G        W          6.0.0-5->
> >> >> Dec 13 11:26:58 fredriksen kernel: Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
> >> >> Dec 13 11:26:58 fredriksen kernel: Workqueue: events_unbound async_run_entry_fn
> >> >> Dec 13 11:26:58 fredriksen kernel: RIP: 0010:intel_tc_port_sanitize+0x312/0x490 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 67 44 42 e3 48 c7 c1 30 a7 d6 c0>
> >> >> Dec 13 11:26:58 fredriksen kernel: RSP: 0018:ffffa84dc5debc08 EFLAGS: 00010286
> >> >> Dec 13 11:26:58 fredriksen kernel: RAX: 0000000000000000 RBX: ffff9c8120650000 RCX: 0000000000000000
> >> >> Dec 13 11:26:58 fredriksen kernel: RDX: 0000000000000001 RSI: ffffffffa4b7eeea RDI: 00000000ffffffff
> >> >> Dec 13 11:26:58 fredriksen kernel: RBP: 0000000000000000 R08: ffffffffa5262260 R09: 00000000a5b5484a
> >> >> Dec 13 11:26:58 fredriksen kernel: R10: ffffffffffffffff R11: 000000000000003a R12: ffff9c81101a2000
> >> >> Dec 13 11:26:58 fredriksen kernel: R13: ffff9c8101f19900 R14: 0000000000000000 R15: ffff9c81101a2000
> >> >> Dec 13 11:26:58 fredriksen kernel: FS:  0000000000000000(0000) GS:ffff9c883f400000(0000) knlGS:0000000000000000
> >> >> Dec 13 11:26:58 fredriksen kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> >> >> Dec 13 11:26:58 fredriksen kernel: CR2: 000055710e140b16 CR3: 00000002db810003 CR4: 0000000000770ef0
> >> >> Dec 13 11:26:58 fredriksen kernel: PKRU: 55555554
> >> >> Dec 13 11:26:58 fredriksen kernel: Call Trace:
> >> >> Dec 13 11:26:58 fredriksen kernel:  <TASK>
> >> >> Dec 13 11:26:58 fredriksen kernel:  intel_ddi_sync_state+0x3f/0x90 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  intel_modeset_setup_hw_state+0x3b1/0x1410 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? _raw_spin_lock_irq+0x19/0x40
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? wait_for_completion+0x91/0x160
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? drm_modeset_lock+0x63/0xd0 [drm]
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? ww_mutex_lock+0x14/0x80
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? __intel_display_resume+0x1a/0xe0 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  __intel_display_resume+0x1a/0xe0 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  intel_display_resume+0xfc/0x140 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  i915_drm_resume+0xba/0x130 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? pci_pm_poweroff_noirq+0x100/0x100
> >> >> Dec 13 11:26:58 fredriksen kernel:  dpm_run_callback+0x47/0x150
> >> >> Dec 13 11:26:58 fredriksen kernel:  device_resume+0x88/0x190
> >> >> Dec 13 11:26:58 fredriksen kernel:  async_resume+0x19/0x30
> >> >> Dec 13 11:26:58 fredriksen kernel:  async_run_entry_fn+0x2d/0x130
> >> >> Dec 13 11:26:58 fredriksen kernel:  process_one_work+0x1c4/0x380
> >> >> Dec 13 11:26:58 fredriksen kernel:  worker_thread+0x4d/0x380
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? rescuer_thread+0x3a0/0x3a0
> >> >> Dec 13 11:26:58 fredriksen kernel:  kthread+0xe6/0x110
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? kthread_complete_and_exit+0x20/0x20
> >> >> Dec 13 11:26:58 fredriksen kernel:  ret_from_fork+0x1f/0x30
> >> >> Dec 13 11:26:58 fredriksen kernel:  </TASK>
> >> >> Dec 13 11:26:58 fredriksen kernel: ---[ end trace 0000000000000000 ]---
> >> >> Dec 13 11:26:58 fredriksen kernel: ------------[ cut here ]------------
> >> >> Dec 13 11:26:58 fredriksen kernel: i915 0000:00:02.0: drm_WARN_ON(dig_port->tc_mode != TC_PORT_DISCONNECTED)
> >> >> Dec 13 11:26:58 fredriksen kernel: WARNING: CPU: 0 PID: 27095 at drivers/gpu/drm/i915/display/intel_tc.c:711 int>
> >> >> Dec 13 11:26:58 fredriksen kernel: Modules linked in: usblp ctr ccm rfcomm cmac algif_hash algif_skcipher af_alg>
> >> >> Dec 13 11:26:58 fredriksen kernel:  snd_sof_utils ecdh_generic snd_soc_hdac_hda ecc snd_hda_ext_core snd_soc_acp>
> >> >> Dec 13 11:26:58 fredriksen kernel:  configfs efivarfs ip_tables x_tables autofs4 btrfs blake2b_generic libcrc32c>
> >> >> Dec 13 11:26:58 fredriksen kernel: CPU: 0 PID: 27095 Comm: kworker/u32:101 Tainted: G        W          6.0.0-5->
> >> >> Dec 13 11:26:58 fredriksen kernel: Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
> >> >> Dec 13 11:26:58 fredriksen kernel: Workqueue: events_unbound async_run_entry_fn
> >> >> Dec 13 11:26:58 fredriksen kernel: RIP: 0010:intel_tc_port_sanitize+0x2d2/0x490 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 a7 44 42 e3 48 c7 c1 f8 a6 d6 c0>
> >> >> Dec 13 11:26:58 fredriksen kernel: RSP: 0018:ffffa84dc5debc08 EFLAGS: 00010286
> >> >> Dec 13 11:26:58 fredriksen kernel: RAX: 0000000000000000 RBX: ffff9c8120650000 RCX: 0000000000000000
> >> >> Dec 13 11:26:58 fredriksen kernel: RDX: 0000000000000001 RSI: ffffffffa4b7eeea RDI: 00000000ffffffff
> >> >> Dec 13 11:26:58 fredriksen kernel: RBP: 0000000000000000 R08: ffffffffa5262260 R09: 00000000a5b55c0a
> >> >> Dec 13 11:26:58 fredriksen kernel: R10: ffffffffffffffff R11: 000000000000004a R12: ffff9c810a2a2000
> >> >> Dec 13 11:26:58 fredriksen kernel: R13: ffff9c8101f19900 R14: 0000000000000000 R15: ffff9c810a2a2000
> >> >> Dec 13 11:26:58 fredriksen kernel: FS:  0000000000000000(0000) GS:ffff9c883f400000(0000) knlGS:0000000000000000
> >> >> Dec 13 11:26:58 fredriksen kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> >> >> Dec 13 11:26:58 fredriksen kernel: CR2: 000055710e140b16 CR3: 00000002db810003 CR4: 0000000000770ef0
> >> >> Dec 13 11:26:58 fredriksen kernel: PKRU: 55555554
> >> >> Dec 13 11:26:58 fredriksen kernel: Call Trace:
> >> >> Dec 13 11:26:58 fredriksen kernel:  <TASK>
> >> >> Dec 13 11:26:58 fredriksen kernel:  intel_ddi_sync_state+0x3f/0x90 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  intel_modeset_setup_hw_state+0x3b1/0x1410 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? _raw_spin_lock_irq+0x19/0x40
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? wait_for_completion+0x91/0x160
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? drm_modeset_lock+0x63/0xd0 [drm]
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? ww_mutex_lock+0x14/0x80
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? __intel_display_resume+0x1a/0xe0 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  __intel_display_resume+0x1a/0xe0 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  intel_display_resume+0xfc/0x140 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  i915_drm_resume+0xba/0x130 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? pci_pm_poweroff_noirq+0x100/0x100
> >> >> Dec 13 11:26:58 fredriksen kernel:  dpm_run_callback+0x47/0x150
> >> >> Dec 13 11:26:58 fredriksen kernel:  device_resume+0x88/0x190
> >> >> Dec 13 11:26:58 fredriksen kernel:  async_resume+0x19/0x30
> >> >> Dec 13 11:26:58 fredriksen kernel:  async_run_entry_fn+0x2d/0x130
> >> >> Dec 13 11:26:58 fredriksen kernel:  process_one_work+0x1c4/0x380
> >> >> Dec 13 11:26:58 fredriksen kernel:  worker_thread+0x4d/0x380
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? rescuer_thread+0x3a0/0x3a0
> >> >> Dec 13 11:26:58 fredriksen kernel:  kthread+0xe6/0x110
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? kthread_complete_and_exit+0x20/0x20
> >> >> Dec 13 11:26:58 fredriksen kernel:  ret_from_fork+0x1f/0x30
> >> >> Dec 13 11:26:58 fredriksen kernel:  </TASK>
> >> >> Dec 13 11:26:58 fredriksen kernel: ---[ end trace 0000000000000000 ]---
> >> >> Dec 13 11:26:58 fredriksen kernel: ------------[ cut here ]------------
> >> >> Dec 13 11:26:58 fredriksen kernel: i915 0000:00:02.0: drm_WARN_ON(dig_port->tc_lock_wakeref)
> >> >> Dec 13 11:26:58 fredriksen kernel: WARNING: CPU: 0 PID: 27095 at drivers/gpu/drm/i915/display/intel_tc.c:712 int>
> >> >> Dec 13 11:26:58 fredriksen kernel: Modules linked in: usblp ctr ccm rfcomm cmac algif_hash algif_skcipher af_alg>
> >> >> Dec 13 11:26:58 fredriksen kernel:  snd_sof_utils ecdh_generic snd_soc_hdac_hda ecc snd_hda_ext_core snd_soc_acp>
> >> >> Dec 13 11:26:58 fredriksen kernel:  configfs efivarfs ip_tables x_tables autofs4 btrfs blake2b_generic libcrc32c>
> >> >> Dec 13 11:26:58 fredriksen kernel: CPU: 0 PID: 27095 Comm: kworker/u32:101 Tainted: G        W          6.0.0-5->
> >> >> Dec 13 11:26:58 fredriksen kernel: Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022
> >> >> Dec 13 11:26:58 fredriksen kernel: Workqueue: events_unbound async_run_entry_fn
> >> >> Dec 13 11:26:58 fredriksen kernel: RIP: 0010:intel_tc_port_sanitize+0x312/0x490 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel: Code: 4c 8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 67 44 42 e3 48 c7 c1 30 a7 d6 c0>
> >> >> Dec 13 11:26:58 fredriksen kernel: RSP: 0018:ffffa84dc5debc08 EFLAGS: 00010286
> >> >> Dec 13 11:26:58 fredriksen kernel: RAX: 0000000000000000 RBX: ffff9c8120650000 RCX: 0000000000000000
> >> >> Dec 13 11:26:58 fredriksen kernel: RDX: 0000000000000001 RSI: ffffffffa4b7eeea RDI: 00000000ffffffff
> >> >> Dec 13 11:26:58 fredriksen kernel: RBP: 0000000000000000 R08: ffffffffa5262260 R09: 00000000a5b56fda
> >> >> Dec 13 11:26:58 fredriksen kernel: R10: ffffffffffffffff R11: 000000000000003a R12: ffff9c810a2a2000
> >> >> Dec 13 11:26:58 fredriksen kernel: R13: ffff9c8101f19900 R14: 0000000000000000 R15: ffff9c810a2a2000
> >> >> Dec 13 11:26:58 fredriksen kernel: FS:  0000000000000000(0000) GS:ffff9c883f400000(0000) knlGS:0000000000000000
> >> >> Dec 13 11:26:58 fredriksen kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> >> >> Dec 13 11:26:58 fredriksen kernel: CR2: 000055710e140b16 CR3: 00000002db810003 CR4: 0000000000770ef0
> >> >> Dec 13 11:26:58 fredriksen kernel: PKRU: 55555554
> >> >> Dec 13 11:26:58 fredriksen kernel: Call Trace:
> >> >> Dec 13 11:26:58 fredriksen kernel:  <TASK>
> >> >> Dec 13 11:26:58 fredriksen kernel:  intel_ddi_sync_state+0x3f/0x90 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  intel_modeset_setup_hw_state+0x3b1/0x1410 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? _raw_spin_lock_irq+0x19/0x40
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? wait_for_completion+0x91/0x160
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? drm_modeset_lock+0x63/0xd0 [drm]
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? ww_mutex_lock+0x14/0x80
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? __intel_display_resume+0x1a/0xe0 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  __intel_display_resume+0x1a/0xe0 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  intel_display_resume+0xfc/0x140 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  i915_drm_resume+0xba/0x130 [i915]
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? pci_pm_poweroff_noirq+0x100/0x100
> >> >> Dec 13 11:26:58 fredriksen kernel:  dpm_run_callback+0x47/0x150
> >> >> Dec 13 11:26:58 fredriksen kernel:  device_resume+0x88/0x190
> >> >> Dec 13 11:26:58 fredriksen kernel:  async_resume+0x19/0x30
> >> >> Dec 13 11:26:58 fredriksen kernel:  async_run_entry_fn+0x2d/0x130
> >> >> Dec 13 11:26:58 fredriksen kernel:  process_one_work+0x1c4/0x380
> >> >> Dec 13 11:26:58 fredriksen kernel:  worker_thread+0x4d/0x380
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? rescuer_thread+0x3a0/0x3a0
> >> >> Dec 13 11:26:58 fredriksen kernel:  kthread+0xe6/0x110
> >> >> Dec 13 11:26:58 fredriksen kernel:  ? kthread_complete_and_exit+0x20/0x20
> >> >> Dec 13 11:26:58 fredriksen kernel:  ret_from_fork+0x1f/0x30
> >> >> Dec 13 11:26:58 fredriksen kernel:  </TASK>
> >> >> Dec 13 11:26:58 fredriksen kernel: ---[ end trace 0000000000000000 ]---
> >> >> Dec 13 11:26:58 fredriksen kernel: i915 0000:00:02.0: [drm] *ERROR* Link Training Unsuccessful
> >> >> Dec 13 11:26:58 fredriksen kernel: i915 0000:00:02.0: [drm] *ERROR* Failed to get ACT after 3000ms, last status: 00
> >> >
> >> > The issue above seems related to
> >> > https://gitlab.freedesktop.org/drm/intel/-/issues/7021 and the
> >> > upstream fix https://git.kernel.org/linus/e8162192636577dcfd87a530b7e6ab10559d6089
> >> >
> >> > Would you be able to test a kernel build with the above applied?
> >> 
> >> Sure, I can test this if I can manage to build a package.  Are there any
> >> instructions on how to apply such a patch to the debian kernel package
> >> and build a new .deb that I can follow?  I assume somehow start from
> >> `apt-get source` and then apply the patch and rebuild?
> >
> > Hiere is a guide on how to do a build with only applying patches on
> > top:
> >
> > https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
> > (follow the instructions in section 4.2).
> >
> > Does this helps?
> 
> Thanks!  Yes I managed to follow that and build a package with the patch.
> 
> Unfortunately it does make it worse, now upon resume the screen is never
> usable anymore (wayland or tty).  There is however no more error from
> the driver in the system log.

Ok, so might be two issues, of which one is solved with the patch.

> Only when e.g. shutting down does plymouth manage to display things
> again, or when restarting the display manager (lightdm, which uses X11)
> via ssh from another machine manages to restart the display.  These ways
> of getting the screen back are the same as before the patch.

Ok. Now two more questions: I assume the 6.0.12-1 which should now be
in testing as well does not solve the problem as well? And in case
not, would you be able to do a bisect of the the changes between 6.0.8
upstream (included with 6.0.8-1 upload with ABI 4) and 6.0.10
(included with 6.0.10-1 and ABI 5)?

https://wiki.debian.org/DebianKernel/GitBisect

There were a vew i915 related changes between the two versions in
stable upstream.

Regards,
Salvatore
Reply to:
Follow-Ups:
- Bug#1026234: linux-image-6.0.0-5-amd64: i915 driver fails on resume
  - From: Floris Bruynooghe <flub@devork.be>
References:
- Bug#1026234: linux-image-6.0.0-5-amd64: i915 driver fails on resume
  - From: Floris Bruynooghe <flub@devork.be>
- Bug#1026234: linux-image-6.0.0-5-amd64: i915 driver fails on resume
  - From: Salvatore Bonaccorso <carnil@debian.org>
- Bug#1026234: linux-image-6.0.0-5-amd64: i915 driver fails on resume
  - From: Floris Bruynooghe <flub@devork.be>
- Bug#1026234: linux-image-6.0.0-5-amd64: i915 driver fails on resume
  - From: Salvatore Bonaccorso <carnil@debian.org>
- Bug#1026234: linux-image-6.0.0-5-amd64: i915 driver fails on resume
  - From: Floris Bruynooghe <flub@devork.be>
Prev by Date: linux_6.0.12-1~bpo11+1_source.changes is NEW
Next by Date: Processing of ethtool_6.1-1_sourceonly.changes
Previous by thread: Bug#1026234: linux-image-6.0.0-5-amd64: i915 driver fails on resume
Next by thread: Bug#1026234: linux-image-6.0.0-5-amd64: i915 driver fails on resume
Index(es):
- Date
- Thread