Comment # 25
on bug 68235
from Alexandre Demers
(In reply to comment #22) > (In reply to comment #20) > > Ok, if I apply the whole suggested patch but the following, it hangs: > > @@ -4152,14 +4152,14 @@ int ni_dpm_init(struct radeon_device *rdev) > > } > > ni_pi->mclk_rtt_mode_threshold = eg_pi->mclk_edc_wr_enable_threshold; > > > > - pi->voltage_control = > > - radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_VDDC, 0); > > + pi->voltage_control = false; > > +// radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_VDDC, 0); > > > > - pi->mvdd_control = > > - radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_MVDDC, 0); > > + pi->mvdd_control = false; > > +// radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_MVDDC, 0); > > > > - eg_pi->vddci_control = > > - radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_VDDCI, 0); > > + eg_pi->vddci_control = false; > > +// radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_VDDCI, 0); > > > > rv770_get_engine_memory_ss(rdev); > > So does just applying this portion of the patch by itself fix the hang? The only way I don't have a "ni_upload_sw_state failed" is by letting pi->voltage_control = radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_VDDC, 0); However, I inevitably end up with a hang either at login or when my session is loading (however, going in a terminal before it hangs prevents any hang from happening as long as I stay in terminal). If I patch that part of code, I always have the "ni_upload_sw_state failed" error, thus not hanging but preventing any dpm. I can patch everything else or nothing at all (I tried different combinations) and they don't seem to change a thing about the hang.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
