From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 68235] Display freezes after login with kernel 3.11.0-rc5 on Cayman with dpm=1 Date: Fri, 13 Sep 2013 06:04:04 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1087215542==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id A7FF7E5CF7 for ; Thu, 12 Sep 2013 23:04:04 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1087215542== Content-Type: multipart/alternative; boundary="1379052244.bB50Afc0.25589"; charset="us-ascii" --1379052244.bB50Afc0.25589 Date: Fri, 13 Sep 2013 06:04:04 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D68235 --- Comment #25 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 =3D eg_pi->mclk_edc_wr_enable_threshol= d; > >=20=20 > > - pi->voltage_control =3D > > - radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_VDDC, 0); > > + pi->voltage_control =3D false; > > +// radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_VDDC, 0); > >=20=20 > > - pi->mvdd_control =3D > > - radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_MVDDC, 0); > > + pi->mvdd_control =3D false; > > +// radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_MVDDC, 0); > >=20=20 > > - eg_pi->vddci_control =3D > > - radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_VDDCI, 0); > > + eg_pi->vddci_control =3D false; > > +// radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_VDDCI, 0); > >=20=20 > > rv770_get_engine_memory_ss(rdev); >=20 > 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 =3D radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_VDDC, 0); However, I inevitably end up with a hang ei= ther 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 combinatio= ns) and they don't seem to change a thing about the hang. --=20 You are receiving this mail because: You are the assignee for the bug. --1379052244.bB50Afc0.25589 Date: Fri, 13 Sep 2013 06:04:04 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 25 on bug 68235<= /a> 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 ha=
ngs:
> > @@ -4152,14 +4152,14 @@ int ni_dpm_init(struct ra=
deon_device *rdev)
> >  	}
> >  	ni_pi->mclk_rtt_mode_threshold =3D eg_pi->mclk_edc_wr_ena=
ble_threshold;
> >=20=20
> > -	pi->voltage_control =3D
> > -		radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_VDDC, =
0);
> > +	pi->voltage_control =3D false;
> > +//		radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_VDDC=
, 0);
> >=20=20
> > -	pi->mvdd_control =3D
> > -		radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_MVDDC,=
 0);
> > +	pi->mvdd_control =3D false;
> > +//		radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_MVDD=
C, 0);
> >=20=20
> > -	eg_pi->vddci_control =3D
> > -		radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_VDDCI,=
 0);
> > +	eg_pi->vddci_control =3D false;
> > +//		radeon_atom_is_voltage_gpio(rdev, SET_VOLTAGE_TYPE_ASIC_VDDC=
I, 0);
> >=20=20
> >  	rv770_get_engine_memory_ss(rdev);
>=20
> 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 let=
ting
pi->voltage_control =3D radeon_atom_is_voltage_gpio(rdev,
SET_VOLTAGE_TYPE_ASIC_VDDC, 0); However, I inevitably end up with a hang ei=
ther
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 fa=
iled"
error, thus not hanging but preventing any dpm.

I can patch everything else or nothing at all (I tried different combinatio=
ns)
and they don't seem to change a thing about the hang.


You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1379052244.bB50Afc0.25589-- --===============1087215542== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1087215542==--