gnuiyl has quit [Remote host closed the connection]
gnuiyl has joined #linux-msm
jacobk has joined #linux-msm
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
jhovold has joined #linux-msm
zstas_ has joined #linux-msm
jacobk_ has joined #linux-msm
jacobk is now known as Guest8127
jacobk_ is now known as jacobk
Guest8127 has quit [Ping timeout: 480 seconds]
srinik has joined #linux-msm
zstas_ has quit [Ping timeout: 480 seconds]
zstas has joined #linux-msm
zstas has quit [Ping timeout: 480 seconds]
svarbanov has quit [Quit: Leaving]
svarbanov has joined #linux-msm
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-msm
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-msm
pespin has joined #linux-msm
sydarn has joined #linux-msm
<sydarn>
Hi everyone, I am new here. I contribute to a gaming focused OS for arm devices based no mainline linux and mesa. I am new to msm, and we relatively recently started supporting an sm8250 based device. We encountered an issue where display output freezes, and weirdly enough when you touch the screen it then resumes. I was trying to debug this issue and noticed that I got more output in dmesg 6.14-rc1 than the former. The extra output is "Loaded GMU firmwa
<sydarn>
re v2.1.8". I find it weird that it would reload the GMU firmware, do you have any idea of why that could happen? Or how I can further debug this?
<sydarn>
I did do `echo 0x19F | sudo tee /sys/module/drm/parameters/debug` when it had frozen and dumped dmesg: https://clbin.com/kcjMK