Comme=
nt # 80
on bug 11067=
4
from Tom =
B
> I tried something like that before =
but a huge portion of the commits in that range won't build kernels that ca=
n boot (at least on my system). I ended up resorting to trying reverting in=
dividual vega20-affecting commits out of 5.1. See my results far above in =
the thread (though someone else willing to spend more time doing a deeper a=
nalysis of the code could probably take my approach much further).
That's why my focus has been finding places in the code where something
different happens based on the number of displays. Though this may be a fut=
ile
avenue of exploration as it could just be an issue of additional memory
bandwith requirements or even something that should be done differently wit=
h 2
displays that isn't.
> It does make me wonder if it's worth testing lik=
e 2 simple 1080p 60 Hz displays. Maybe that wouldn't trigger this issue. No=
t that that would really be of use to me. But it might help distinguish bet=
ween just monitor detect generally being broken and "high monitor load=
" being broken . . .
This would be an interesting test but I think 1080p 60hz monitors with
displayport are fairly uncommon and I don't have any to test with. My guess=
is
anyone with a Radeon VII, a high end card with 16gb VRAM, is likely to have=
a
high end display which could equally explain why there are no reports here =
of
people running 1080p 60hz displays.=20
My next test is going to be logging dpm_table->dpm_state.hard_min_level =
on line
3354 (just before it's sent to the smc) on both 5.0.13 and 5.2.7 to see if =
the
same hard_min_level value is sent to the smc on both kernels. This will at
least let us know whether it's something that's incorrectly setting
hard_min_level or something that prevents the smc accepting the value. My h=
unch
from my previous tests is that it's the latter but I'll try it and report b=
ack.
I know nothing about driver development so I have no idea how this stuff sh=
ould
work, I can only compare the differences between 5.0.13 and later kernels.
Anyway, thanks everyone for your input. Any information, even on things that
you tried and didn't work, is valuable as it can help us narrow down the
problem.