A web search shows the problem has already been "git bisected" by users on Bugzilla with a workaround [0]. And according to > Ahzo 2019-10-11 18:33:10 UTC > b

A web search shows the problem has already been "git bisected" by users on Bugzilla with a workaround [0]. And according to > Ahzo 2019-10-11 18:33:10 UTC > bisection between these two, while backporting 533aed278afe on every step, lead to commit 2a91f272e34c, which failed to boot and thus had to be skipped, and commit e0128efb08b3d628d767ec8578e77cdd7ecc8f81 looks like a likely root cause. Indeed, adding 'return 0;' at the beginning of uvd_v6_0_enc_ring_test_ib makes the problem unreproducible, even on the latest linux 5.4-rc2. And, > Ahzo 2019-10-11 18:37:48 UTC > By the way, some of the kernel NULL pointer dereferences, that can happen after a resume failure, also happen always on shutdown. Attached patch prevents them. Do you know how to build a kernel? I suggest you to build Linux 5.4 (you can avoid reconfiguring the kernel by using /proc/config.gz) with the code workaround (adding 'return 0;' at the beginning of uvd_v6_0_enc_ring_test_ib) applied, and see whether it fixes your problem. You should also check the NULL pointer patch and see whether it's already included in the source code by manual inspection, if not, also apply the patch. If it fixes your problems, report it to the Bugzilla thread. Nevertheless, I still recommend you to try reproducing it in Linux 5.9 first and see whether you can reproduce the original problem. The comments in Bugzilla suggests that the latest kernel has already fixed the issue. > Alex Deucher 2020-10-01 14:59:58 UTC > The original issue reported in this bug was fixed long ago. If Linux 5.9 fixes it, good. If not, see whether the error messages are different. If so, you should chase the new issue instead of the original issue. --- [0] https://bugzilla.kernel.org/show_bug.cgi?id=204241 https://bugzilla.kernel.org/show_bug.cgi?id=204241