Kernel bug related to drivers/gpu/drm/ttm/ttm_bo.c

Christopher Klooz py0xc3 at my.mail.de
Fri Jun 2 16:02:43 UTC 2023


See also (maybe this user experiences the same bug?): 
https://bugzilla.redhat.com/show_bug.cgi?id=2193325

To provide direct links: My original post in "Kernel bug related to 
drivers/gpu/drm/ttm/ttm_bo.c" relates to:

https://gitlab.com/py0xc31/public-tmp-storage/-/blob/main/retry6.3.4/firefoxCrash-noPidof-kernelerror-6.3.4.pstate-passive.CUT.log

https://gitlab.com/py0xc31/public-tmp-storage/-/blob/main/retry6.3.4/firefoxCrash-noPidof-kernelerror-6.3.4.pstate-passive.preHALT.log

Some logs contain issues involving BOTH "amdgpu" and (one or more) 
CPU(s), but a few refer to only one of the two, and some others none of 
the two but only a reference to a kernel BUG. But sometimes logs are 
frozen before any log can be written.

Currently, most logs do no longer contain much about amdgpu; but an 
earlier log with more amdgpu-related entries was 
https://gitlab.com/py0xc31/public-tmp-storage/-/blob/main/2nd/root-journalctl.-r.-b.-1.FirstFirefoxInsideTabFreeze_thenRemainingFirefoxFreeze_thenSystemFreeze.16-31-55screenClockFrozen.kernel6.2.15.amd_pstate-passive.log 
(which is also contained/elaborated in my bug report I referred to in my 
original post). The latter (older) log is widely comparable to the other 
user's bug report and it is also from roughly the same time 
(beginning-mid May). Maybe some Fedora updates in between trigger the 
bug differently, causing different logs.

Another user with potentially the same issue can be found with an 
extract from their logs here: 
https://bodhi.fedoraproject.org/updates/FEDORA-2023-26325e5399 (the post 
of the user "benthaase")



More information about the dri-devel mailing list