https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #88 from ReddestDream <reddestdr...@gmail.com> ---
>The question then becomes: Why doesn't the race condition happen with only one
>screen? Perhaps it's a matter of speed. With a single display, the driver
>detect the displays, read/parse the EDID data, initialize in time. But then
>that doesn't explain why the crash still occurs if you boot with one
>DisplayPort monitor and attach another after X is running.
I do suspect it's a matter of speed and complexity when you have more monitors.
Also maybe the clock it tries to set (the value of hard_min_level) is different
if you only have one monitor and somehow that takes more time (resetting it
away from some default).
I do wonder if maybe in:
"[SetUclkToHightestDpmLevel] Set hard min uclk failed!",
return ret);
It should return -EINVAL instead. Maybe then it would reset and try again
instead of just ignoring it and continuing with initialization anyway, leading
to instability.
>One thing I've been trying to work out is the difference between vega21_ppt.c
>and vega20_hwmgr.c is, as they both contain slightly different or identical
>versions of the same functions. It looks like the functions in vega20_hwmgr.c
>take precedence but it's strange to see this duplication and both files are
>worked on in the commit history.
Hmm. That is interesting. I'll take a look.
--
You are receiving this mail because:
You are the assignee for the bug._______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
