Comme=
nt # 79
on bug 11067=
4
from ReddestDream
>I tried something like that before b=
ut a huge portion of the commits in that range won't build kernels that can=
boot (at least on my system).
It's interesting that you found d1a3e239a6016f2bb42a91696056e223982e8538 to
improve the issue:
https://github.com=
/torvalds/linux/commit/d1a3e239a6016f2bb42a91696056e223982e8538#diff-0bc078=
42bc28283d64ffa6dd2ed716de
>>From Tom B.'s and my review of the code, it seems very likely that somehow a
failure to set a hard minimum properly is at the heart of the issue.=20
>This brings me to the second thing: When looking =
through the commits, I noticed that there were multiple commits that claim =
to prevent or reduce crashing in high-resolution situations (one references=
5k displays, another references 3+ 4k displays).
Yeah. I have 2 4K displays as well. But I don't think it should really be
straining the card. These commits are probably overzealous for Radeon VII.
Rather it could be that at least part of the issue, especially the excessive
power draw at idle, is just due to these commits artificially setting minim=
ums
very high. In fact, that could be why it's stable at all with just one moni=
tor,
since the code to set the minimums up is only being triggered when there are
more monitors connected.
I'd suspect a boottime configuration issue too, but others have reported
instability even when the monitors are hotplugged later on. So, it seems li=
ke
maybe the monitor detect might at least partially be okay, but the
follow-through with raising the clock minimums is broken. I suspect the iss=
ue
is in the code calculating the minimum to set, so the driver gets stuck try=
ing
to send incomplete/incorrect values to the card.
https://bbs=
.archlinux.org/viewtopic.php?id=3D247733
It does make me wonder if it's worth testing like 2 simple 1080p 60 Hz
displays. Maybe that wouldn't trigger this issue. Not that that would reall=
y be
of use to me. But it might help distinguish between just monitor detect
generally being broken and "high monitor load" being broken . . .=