Comme=
nt # 12
on bug 10715=
2
from dwagner
Indeed, I found my theory confirmed by many experiments: If I =
use a script like
> #!/bin/bash
> cd /sys/class/drm/card0/device
> echo manual >power_dpm_force_performance_level
> # low
> echo 0 >pp_dpm_mclk=20
> echo 0 >pp_dpm_sclk
> # medium
> #echo 1 >pp_dpm_mclk=20
> #echo 1 >pp_dpm_sclk
> # high
> #echo 1 >pp_dpm_mclk=20
> #echo 6 >pp_dpm_sclk
to enforce just any performance level, then the crashes do not occur anymor=
e -
also with the "low frame rate video test".
So it seems that the transition from one "dpm" performance level =
to another,
with a certain probability, causes these crashes. And the more often the
transitions occur, the sooner one will experience them.
The dynamic power management issue can now be pursued with the original bug
report https://bugs.freedesktop.org/show_bug.=
cgi?id=3D102322 for the
vm_update_mode=3D0 case - there is probably not much sense in keeping this =
bug
report open just because errors also occur with wm_update_mode=3D3, just le=
ss
often.