Bug#1033637: Aw: Re: Bug#1033637: linux: amdgpu - External displays connected through Thinkpad Ultra Dock not turn on after suspend
Good Morning, > As a first test, I would like you to try 6.1~rc3-1~exp1. it doesn't work, it's more worst, because I don't see luks-encrypt prompt (not on external or internal monitor), If I boot without docking station it works until I connect it. I got a black screen and the system crashs: 2023-04-03T08:35:30.370524+02:00 imperator kernel: [ 36.954545] [ cut here ] 2023-04-03T08:35:30.370528+02:00 imperator kernel: [ 36.954547] WARNING: CPU: 2 PID: 1152 at drivers/gpu/drm/drm_modeset_lock.c:317 drm_modeset_lock+0xc9/0xd0 [drm] 2023-04-03T08:35:30.370529+02:00 imperator kernel: [ 36.954570] Modules linked in: rfcomm snd_usb_audio snd_usbmidi_lib hid_lenovo snd_rawmidi hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid snd_seq_dummy snd_hrtimer snd_seq snd_seq_device qrtr cmac algif_hash algif_skcipher af_alg bnep sunrpc binfmt_misc nls_ascii nls_cp437 vfat fat ext4 mbcache jbd2 squashfs btusb btrtl btbcm btintel btmtk intel_rapl_msr intel_rapl_common bluetooth rtw89_8852ae rtw89_8852a snd_acp3x_rn snd_soc_dmic snd _acp3x_pdm_dma rtw89_pci edac_mce_amd snd_soc_core snd_ctl_led rtw89_core snd_compress snd_hda_codec_realtek uvcvideo kvm_amd videobuf2_vmalloc jitterentropy_rng snd_hda_codec_generic snd_hda_codec_hdmi mac80211 videobuf2_memops kvm videobuf2_v4l2 vide obuf2_common drbg ansi_cprng videodev snd_hda_intel snd_intel_dspcfg libarc4 snd_intel_sdw_acpi ecdh_generic irqbypass snd_hda_codec ecc mc rapl crc16 snd_hda_core cfg80211 snd_pci_acp6x pcspkr snd_hwdep thinkpad_acpi snd_pci_acp5x snd_pcm wmi_bmof nvr am snd_rn_pci_acp3x platform_profile snd_timer 2023-04-03T08:35:30.370532+02:00 imperator kernel: [ 36.954599] ucsi_acpi snd_acp_config ccp ledtrig_audio typec_ucsi snd_soc_acpi sp5100_tco snd snd_pci_acp3x watchdog roles rng_core k10temp typec soundcore rfkill ac acpi_cpufreq joydev evdev serio _raw msr parport_pc ppdev lp parport fuse loop efi_pstore configfs efivarfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq zstd_compress libcrc32c crc32c_generic dm_crypt dm_mod mhi_wwan_mbim mhi_wwan_ctrl wwan amdgpu gpu_sched drm_buddy i2c_algo_bit drm_display_helper crc32_pclmul crc32c_intel cec rc_core drm_ttm_helper ghash_clmulni_intel ttm sha512_ssse3 rtsx_pci_sdmmc sha512_generic mmc_core drm_kms_helper r8169 xhci_pci nvme xhci_hcd realtek aesni_intel drm nvme_core mdio_devres crypto_simd psmouse usbcore t10_pi cryptd libphy mhi_pci_generic crc64_rocksoft_generic rtsx_pci mhi i2c_piix4 crc64_rocksoft crc_t10dif crct10dif_generic usb_common video crct10dif_pclmul crc64 crct10dif_common battery wmi i2c_scmi button 2023-04-03T08:35:30.370533+02:00 imperator kernel: [ 36.954630] CPU: 2 PID: 1152 Comm: Xorg Not tainted 6.1.0-0-amd64 #1 Debian 6.1~rc3-1~exp1 2023-04-03T08:35:30.370533+02:00 imperator kernel: [ 36.954632] Hardware name: LENOVO 20XL0012GE/20XL0012GE, BIOS R1MET53W (1.23 ) 02/23/2023 2023-04-03T08:35:30.370534+02:00 imperator kernel: [ 36.954633] RIP: 0010:drm_modeset_lock+0xc9/0xd0 [drm] 2023-04-03T08:35:30.370534+02:00 imperator kernel: [ 36.954648] Code: ff ff ff eb d5 e8 e7 b7 a0 f4 eb 91 0f 0b e9 75 ff ff ff 83 f8 8e 74 c0 83 f8 dd 75 bd 48 89 6b 18 c7 43 20 00 00 00 00 eb b0 <0f> 0b eb 80 0f 1f 00 0f 1f 44 00 00 41 57 41 56 41 5 5 41 54 49 89 2023-04-03T08:35:30.370534+02:00 imperator kernel: [ 36.954649] RSP: 0018:a3e9c16a7790 EFLAGS: 00010286 2023-04-03T08:35:30.370534+02:00 imperator kernel: [ 36.954650] RAX: RBX: a3e9c16a7d20 RCX: 2023-04-03T08:35:30.370535+02:00 imperator kernel: [ 36.954651] RDX: 8ccde27d6600 RSI: a3e9c16a7d20 RDI: 8ccde0bd6550 2023-04-03T08:35:30.370535+02:00 imperator kernel: [ 36.954652] RBP: 8ccde0bd6550 R08: 8ccde0bd6540 R09: a3e9c16a7a7c 2023-04-03T08:35:30.370536+02:00 imperator kernel: [ 36.954652] R10: 8ccdd09ab780 R11: 8ccde0bd6850 R12: 8ccde0bd6578 2023-04-03T08:35:30.370536+02:00 imperator kernel: [ 36.954653] R13: 8ccdd285b000 R14: 8cce8788 R15: 0001 2023-04-03T08:35:30.370536+02:00 imperator kernel: [ 36.954654] FS: 7f11f8211a80() GS:8cd48ee8() knlGS: 2023-04-03T08:35:30.370537+02:00 imperator kernel: [ 36.954654] CS: 0010 DS: ES: CR0: 80050033 2023-04-03T08:35:30.370537+02:00 imperator kernel: [ 36.954655] CR2: 7f6af420 CR3: 000107b9a000 CR4: 00750ee0 2023-04-03T08:35:30.370537+02:00 imperator kernel: [ 36.954656] PKRU: 5554 2023-04-03T08:35:30.370538+02:00 imperator kernel: [ 36.954656] Call Trace: 2023-04-03T08:35:30.370538+02:00 imperator kernel: [ 36.954658] 2023-04-03T08:35:30.370539+02:00 imperator kernel: [ 36.954660] drm_atomic_get_private_obj_state+0x58/0x150 [drm] 2023-04-03T08:35:30.370539+02:00 imperator kernel: [ 36.954676] compute_mst_dsc_configs_for_link+0x59/0x9e0 [amdgpu] 2023-04-03T08:35:30.370539+02:00 imperat
Bug#1033637: linux: amdgpu - External displays connected through Thinkpad Ultra Dock not turn on after suspend
On Friday, 31 March 2023 12:57:44 CEST Stefan K wrote: > when I searching my error message I got a lot of hits.. > In arch it's solved: > https://bugs.archlinux.org/task/76934 > > the patch: > https://gitlab.freedesktop.org/superm1/linux/-/commit/2145b4de3fea9908cda6be > f0693a797cc7f4ddfc.patch Oh boy, that brought back some memories ... That patch would likely indeed have solved your problem, but I'm going to take a guess and assume that you didn't actually try to apply that patch and verified that it then worked. (because it would be very difficult to apply) That patch was HUGE and therefor unacceptable to be backported to 6.1 and this issue is AFAIUI one of the reasons that it took longer then normal to declare 6.1 a LTS release. The memories refer to https://bugs.debian.org/1028451 and that got solved by a different set of patches which were accepted (and the result of *further* discussions around that issue). https://gitlab.freedesktop.org/drm/amd/-/issues/2171#note_1721571 which is the "Forwarded" of that bug, also refers to "6.1.5.arch2-1". Further discussion on that issue resulted in the aforementioned patches which were accepted. But I believe there were some corner cases expected that would not be solved and I'm guessing your issue is one of those. On Wednesday, 29 March 2023 09:59:22 CEST Stefan K wrote: > and syslog said: > [drm:dc_link_allocate_mst_payload [amdgpu]] *ERROR* Failure: pbn_per_slot==0 > not allowed. Cannot continue, returning DC_UNSUPPORTED_VALUE. That's from your initial bug report and that may be key to finding out if/why your case is indeed such a corner case and from there find. https://bugs.debian.org/1033050 may be the same or a similar issue. @Bernhard: Do you think it's the same issue? If so, that may be useful as your report contains a kernel crash with a stack trace. I don't know what to do with that, but others can. Certainly the upstream devs which this issue likely needs to be reported to. signature.asc Description: This is a digitally signed message part.
Bug#1033637: Aw: Re: Bug#1033637: linux: amdgpu - External displays connected through Thinkpad Ultra Dock not turn on after suspend
Hi, when I searching my error message I got a lot of hits.. In arch it's solved: https://bugs.archlinux.org/task/76934 the patch: https://gitlab.freedesktop.org/superm1/linux/-/commit/2145b4de3fea9908cda6bef0693a797cc7f4ddfc.patch > Gesendet: Donnerstag, 30. März 2023 um 15:37 Uhr > Von: "Diederik de Haas" > An: "Stefan K" , 1033...@bugs.debian.org > Betreff: Re: Bug#1033637: linux: amdgpu - External displays connected through > Thinkpad Ultra Dock not turn on after suspend > > Control: found -1 6.1.20-1 > > > > Unstable has version 6.1.20-1, can you test whether the issue is present > > > there too? > > Yes, it still happens with 6.1.20-1.. > > Updating metadata accordingly > > On Thursday, 30 March 2023 14:46:51 CEST Stefan K wrote: > > With Kernel 6.0.0-0.deb11.6-amd64 it works fine > > Shouldn't that be 6.1.0-0.deb11.6-amd64? > Which would be the bullseye-backports kernel for version 6.1.15-1. > > On https://snapshot.debian.org/binary/linux-image-amd64/ you can find > compiled > debs of various kernel kernel versions. The goal is to figure out what the > last > kernel was that worked properly and the first one that does not. > > As a first test, I would like you to try 6.1~rc3-1~exp1. > If that version also has the issue, then it's useful to test 6.0-1~exp1. > If 6.0-1~exp1 does NOT have the issue, but 6.1~rc3~exp1 then we know that the > issue was introduced in the 6.1 'merge window'.
Bug#1033637: Aw: Re: Bug#1033637: linux: amdgpu - External displays connected through Thinkpad Ultra Dock not turn on after suspend
that was the latest kernel which I installed on bullseye ;-) > As a first test, I would like you to try 6.1~rc3-1~exp1. > If that version also has the issue, then it's useful to test 6.0-1~exp1. > If 6.0-1~exp1 does NOT have the issue, but 6.1~rc3~exp1 then we know that the > issue was introduced in the 6.1 'merge window'. I will test this next week on Monday, because at home I don't have this setup.
Bug#1033637: linux: amdgpu - External displays connected through Thinkpad Ultra Dock not turn on after suspend
Control: found -1 6.1.20-1 > > Unstable has version 6.1.20-1, can you test whether the issue is present > > there too? > Yes, it still happens with 6.1.20-1.. Updating metadata accordingly On Thursday, 30 March 2023 14:46:51 CEST Stefan K wrote: > With Kernel 6.0.0-0.deb11.6-amd64 it works fine Shouldn't that be 6.1.0-0.deb11.6-amd64? Which would be the bullseye-backports kernel for version 6.1.15-1. On https://snapshot.debian.org/binary/linux-image-amd64/ you can find compiled debs of various kernel kernel versions. The goal is to figure out what the last kernel was that worked properly and the first one that does not. As a first test, I would like you to try 6.1~rc3-1~exp1. If that version also has the issue, then it's useful to test 6.0-1~exp1. If 6.0-1~exp1 does NOT have the issue, but 6.1~rc3~exp1 then we know that the issue was introduced in the 6.1 'merge window'. signature.asc Description: This is a digitally signed message part.
