ChanServ changed the topic of #linux-msm to:
marvin24_ has joined #linux-msm
marvin24 has quit [Ping timeout: 480 seconds]
lumag_ has quit [Remote host closed the connection]
lumag_ has joined #linux-msm
qyousef_ has joined #linux-msm
qyousef has quit [Ping timeout: 480 seconds]
pevik has joined #linux-msm
jhovold has joined #linux-msm
srinik has quit [Killed (NickServ (Too many failed password attempts.))]
srinik has joined #linux-msm
<vknecht[m]> robclark: thanks, Jessica's patches seem to have helped with bringing panel back up reliabily after suspend/screen-off, even if I still get many mdp5_pipe_release warns eg. after 09:56:17 in this log : https://sebsauvage.net/paste/?68d9d18335dafad5#OkjIWcdaBhSA9Xo7hFSE5gOqXivzDAYZUknWmg7HfN0=
pevik has quit [Ping timeout: 480 seconds]
pevik has joined #linux-msm
pevik has quit [Quit: Lost terminal]
pespin has joined #linux-msm
pespin has quit []
pespin has joined #linux-msm
lumag_ has quit [Ping timeout: 480 seconds]
minecrell has quit [Read error: Connection reset by peer]
minecrell has joined #linux-msm
svarbanov has quit [Remote host closed the connection]
svarbanov has joined #linux-msm
svarbanov has quit [Ping timeout: 480 seconds]
<robclark> hmm, if I had to take a guess, in the system suspend path the atomic helper tries to disable already disabled planes? So maybe that WARN_ON() should be removed? Perhaps you could `echo 0x1f > /sys/modules/drm/parameters/debug` and then trigger suspend, hopefully that would confirm or disprove the theory?
<robclark> vknecht[m]: ^^^
lumag_ has joined #linux-msm
<vknecht[m]> robclark: couldn't say if warn is undue, here's 0x1f logs when pressing button for panel off, then for back at ~ 17:41:04.272 : https://sebsauvage.net/paste/?a331dbb600455501#xXyziK0iDvb2UyIL7s8xd1ViN2tgcGNwdGEcI6OSMI0=
<vknecht[m]> (it's drm_hwc with " drm_hwcomposer: Add non-blocking commit support" cherry-picked, if that matters)
<robclark> hmm, ok so plane is enabled.. so I guess before jessica_24's patch you'd see the warn_on splat once or occasionally.. but now it causes the atomic-check to fail so we never recover from the bad state.. this would kinda paper over the problem and make things less spammy, I think. But not sure how we get into that state in the first place
pespin_ has joined #linux-msm
pespin has quit [Ping timeout: 480 seconds]
<vknecht[m]> still getting one warn on panel back on : https://pastebin.com/dkCh6ae7
lumag_ has quit [Remote host closed the connection]
lumag_ has joined #linux-msm
jhovold has quit [Ping timeout: 480 seconds]
lumag_ has quit [Remote host closed the connection]
lumag_ has joined #linux-msm