Comment # 7 on bug 1207837 from 
Created attachment 864810 [details]
journal with dock connections and disconnections between suspensions

(In reply to Takashi Iwai from comment #6)
> Try to check whether Secure Boot is set on BIOS.  You'll need to turn it off
> for booting with the unofficial kernels.

Doh! I forgot that. Thanks, now I'm able to use the 6.0.x branch.

I was able to reproduce the behaviour as I described, so there is something
between 6.0 and 6.1 that changed that breaks waking up the displays, as Jiri
mentioned.

Also, I was able to crash the latest 6.1.x kernel playing with
resuming/suspending and connecting/disconnecting the dock while the laptop is
suspended.

I'm adding the log. Let me know if a new bug should be created.

Here are the steps to crash the latest 6.1.x kernel (there are 9 steps below):
1) Boot the laptop, dock disconnected.
2) Connect the dock.
3) Suspend the system.
4) Disconnect the dock while suspended.
5) Wake up the laptop, with the dock disconnected. Here the kernel complains
with the following messages (but does not crash).

> Feb 09 20:21:14.590862 laptop kernel: [drm:dm_late_init [amdgpu]] *ERROR* DM_MST: Failed to start MST
> Feb 09 20:21:14.590913 laptop kernel: [drm:amdgpu_device_ip_late_init [amdgpu]] *ERROR* late_init of IP block <dm> failed -5
> Feb 09 20:21:14.590941 laptop kernel: amdgpu 0000:06:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0xe0 returns -5
> Feb 09 20:21:14.591133 laptop kernel: amdgpu 0000:06:00.0: PM: failed to resume async: error -5
> Feb 09 20:21:14.591328 laptop kernel: OOM killer enabled.

6) Suspend the laptop.
7) Connect the dock while suspended.
8) Wake up the laptop (dock connected at this point).
9) Kernel crash:

> Feb 09 20:21:14.854008 laptop kernel: Hardware name: LENOVO 20UJS2B905/20UJS2B905, BIOS R1CET63W(1.32 ) 04/09/2021
> Feb 09 20:21:14.854041 laptop kernel: RIP: 0010:drm_dp_atomic_release_time_slots+0x1bb/0x1f0 [drm_display_helper]
> Feb 09 20:21:14.854078 laptop kernel: Code: 08 44 8b 4b 0c 49 89 e8 48 c7 c1 ef a7 23 c1 ba 04 00 00 00 48 c7 c7 00 e3 23 c1 e8 1f 9c 95 c2 eb 8a 44 89 e8 e9 31 ff ff ff <0f> 0b 49 8b 44 24 58 4c 89 e9 48 89 ea 48 c7 c6 f0 8f 23 c1 48 8b
> Feb 09 20:21:14.854118 laptop kernel: RSP: 0018:ffffba938207b958 EFLAGS: 00010246
> Feb 09 20:21:14.854155 laptop kernel: RAX: ffff92fd84a624b8 RBX: ffff92fd84a624a0 RCX: 0000000000000001
> Feb 09 20:21:14.854185 laptop kernel: RDX: ffff92fd84a624b8 RSI: ffff92fd84a62480 RDI: ffff92fda1b02540
> Feb 09 20:21:14.854214 laptop kernel: RBP: ffff92fd85f55000 R08: ffffba938207b850 R09: ffff92fd8443e1e0
> Feb 09 20:21:14.854244 laptop kernel: R10: ffff92fe211c8a00 R11: 0000000000000000 R12: ffff92fda1b02540
> Feb 09 20:21:14.854269 laptop kernel: R13: ffff92fd84a62480 R14: ffff92fe326646c0 R15: ffff92fd8443e100
> Feb 09 20:21:14.854293 laptop kernel: FS:  00007f10b0217940(0000) GS:ffff93007f980000(0000) knlGS:0000000000000000
> Feb 09 20:21:14.854334 laptop kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> Feb 09 20:21:14.854370 laptop kernel: CR2: 00007f4d0b01943e CR3: 000000011e384000 CR4: 0000000000350ee0
> Feb 09 20:21:14.854405 laptop kernel: Call Trace:
> Feb 09 20:21:14.854441 laptop kernel:  <TASK>
> Feb 09 20:21:14.854467 laptop kernel:  drm_atomic_helper_check_modeset+0x335/0xdc0
> Feb 09 20:21:14.854512 laptop kernel:  amdgpu_dm_atomic_check+0x54/0x12c0 [amdgpu b2b447105068cd3b6d7d93eaa9a3d2a7ff3ec4c6]
> Feb 09 20:21:14.854538 laptop kernel:  ? __kmem_cache_alloc_node+0x1b1/0x320
> Feb 09 20:21:14.854567 laptop kernel:  ? amdgpu_dm_connector_atomic_duplicate_state+0x25/0xb0 [amdgpu b2b447105068cd3b6d7d93eaa9a3d2a7ff3ec4c6]
> Feb 09 20:21:14.854601 laptop kernel:  ? __kmalloc_node_track_caller+0x4a/0x150
> Feb 09 20:21:14.854635 laptop kernel:  ? __drm_atomic_helper_connector_duplicate_state+0x54/0x80
> Feb 09 20:21:14.854668 laptop kernel:  ? amdgpu_dm_connector_atomic_duplicate_state+0x38/0xb0 [amdgpu b2b447105068cd3b6d7d93eaa9a3d2a7ff3ec4c6]
> Feb 09 20:21:14.854696 laptop kernel:  drm_atomic_check_only+0x533/0xb90
> Feb 09 20:21:14.854729 laptop kernel:  drm_atomic_commit+0x58/0xf0
> Feb 09 20:21:14.854762 laptop kernel:  ? drm_plane_get_damage_clips.cold+0x1c/0x1c
> Feb 09 20:21:14.854800 laptop kernel:  drm_atomic_helper_set_config+0x70/0xb0
> Feb 09 20:21:14.854839 laptop kernel:  drm_mode_setcrtc+0x340/0x820
> Feb 09 20:21:14.854870 laptop kernel:  ? drm_mode_getcrtc+0x180/0x180
> Feb 09 20:21:14.854905 laptop kernel:  drm_ioctl_kernel+0xc1/0x160
> Feb 09 20:21:14.854939 laptop kernel:  drm_ioctl+0x1de/0x460
> Feb 09 20:21:14.854968 laptop kernel:  ? drm_mode_getcrtc+0x180/0x180
> Feb 09 20:21:14.854993 laptop kernel:  amdgpu_drm_ioctl+0x4a/0x80 [amdgpu b2b447105068cd3b6d7d93eaa9a3d2a7ff3ec4c6]
> Feb 09 20:21:14.855022 laptop kernel:  __x64_sys_ioctl+0x90/0xd0
> Feb 09 20:21:14.855046 laptop kernel:  do_syscall_64+0x5b/0x80
> Feb 09 20:21:14.855073 laptop kernel:  ? syscall_exit_to_user_mode+0x17/0x40
> Feb 09 20:21:14.855102 laptop kernel:  ? do_syscall_64+0x67/0x80
> Feb 09 20:21:14.855130 laptop kernel:  ? syscall_exit_to_user_mode+0x17/0x40
> Feb 09 20:21:14.855149 laptop kernel:  ? do_syscall_64+0x67/0x80
> Feb 09 20:21:14.855178 laptop kernel:  ? exit_to_user_mode_prepare+0x166/0x1f0
> Feb 09 20:21:14.855206 laptop kernel:  ? syscall_exit_to_user_mode+0x17/0x40
> Feb 09 20:21:14.855223 laptop kernel:  ? do_syscall_64+0x67/0x80
> Feb 09 20:21:14.855252 laptop kernel:  ? do_syscall_64+0x67/0x80
> Feb 09 20:21:14.855274 laptop kernel:  ? exc_page_fault+0x66/0x150
> Feb 09 20:21:14.855302 laptop kernel:  entry_SYSCALL_64_after_hwframe+0x63/0xcd
> Feb 09 20:21:14.855337 laptop kernel: RIP: 0033:0x7f10b07209bf

(... and continues with more and more stacktraces, one for each CPU ...)

You are receiving this mail because: