<!DOCTYPE html> <html><head> <meta charset="UTF-8"> </head><body>Dear AMD Developers,At first congratulations for the DC code submission to the 4.15 kernel. Unfortunately the major regression which I reported on 29.09., 06.10., 02.11. and 05.11. still exists. But this time I got additional debugging information maybe this helps to fix it.Summary: I am running Xubuntu 17.10 with the amd-staging-drm-next kernel patched to 4.14.0. The latest build which I tested is from includes all commits up to now (including 2017-11-17 19:51:57 (GMT) commit 85d09ce5e5039644487e9508d6359f9f4cf64427).Some vblank operations make the kernel crash and hang up the whole system. The error is reproducible by enabling the screen lock or the suspend mode. The system can not return to proper state from either of these (after all I am not 100% sure it is the same error). Debugging is easier with screen lock. Attached you can find the kernel crash and the dce110_vblank_set function modified by some kernel prints. It looks like the function is called twice and does not work the second time. The whole code around dce110_vblank_set also looks interrupt-ish - could this be a race condition or timing problem? Objects being cleared from memory and then accessed by dce110_vblank_set?Bug reports on this issue: <a href="https://github.com/M-Bab/linux-kernel-amdgpu-binaries/issues/37">https://github.com/M-Bab/linux-kernel-amdgpu-binaries/issues/37</a> <a href="https://github.com/M-Bab/linux-kernel-amdgpu-binaries/issues/29">https://github.com/M-Bab/linux-kernel-amdgpu-binaries/issues/29</a> Many regards, Martin (M-bab)</body></html>