Comment # 85
on bug 110674
from Tom B
> Yeah. I've had boots where I have my 2 4K DP monitors in and I don't get powerplay error on boot. In fact, it can go a bit and seem stable.
In addition to that, vega20_set_fclk_to_highest_dpm_level is called several
times before the card is initialized and even on 5.2.7 works. Something happens
during or just before the initialization stage that stops
smum_send_msg_to_smc_with_parameter accepting 1001 as a valid value, as it does
until that point.
I think you're right about BACO, it was worth looking at but I applied a quick
hack to ensure it's disabled:
int vega20_baco_set_state(struct pp_hwmgr *hwmgr, enum BACO_STATE state)
{
return 0;
}
int vega20_baco_get_capability(struct pp_hwmgr *hwmgr, bool *cap)
{
*cap = false;
return 0;
}
No difference, I still get the errors and wrong wattage so unless BACO is
somehow on by default and only turned off in the proper version of this code,
we can rule it out.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
