dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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	[thread overview]
Message-ID: <bug-68235-502-pYpLAVUelz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68235-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1919 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=68235

--- Comment #25 from Alexandre Demers <alexandre.f.demers@gmail.com> ---
(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.

[-- Attachment #1.2: Type: text/html, Size: 3076 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-09-13  6:04 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-18  1:33 [Bug 68235] New: Display freezes after login with kernel 3.11.0-rc5 on Cayman with dpm=1 bugzilla-daemon
2013-08-18  1:35 ` [Bug 68235] " bugzilla-daemon
2013-08-22  4:42 ` bugzilla-daemon
2013-08-23  2:33 ` bugzilla-daemon
2013-08-25  3:50 ` bugzilla-daemon
2013-08-26 15:13 ` bugzilla-daemon
2013-08-26 15:53 ` bugzilla-daemon
2013-08-27  5:10 ` bugzilla-daemon
2013-08-27  6:32 ` bugzilla-daemon
2013-09-03  3:57 ` bugzilla-daemon
2013-09-03  4:47 ` bugzilla-daemon
2013-09-03 23:42 ` bugzilla-daemon
2013-09-03 23:43 ` bugzilla-daemon
2013-09-07  0:12 ` bugzilla-daemon
2013-09-10 17:31 ` bugzilla-daemon
2013-09-10 18:15 ` bugzilla-daemon
2013-09-10 19:55 ` bugzilla-daemon
2013-09-10 19:55 ` bugzilla-daemon
2013-09-10 20:40 ` bugzilla-daemon
2013-09-11  1:46 ` bugzilla-daemon
2013-09-12  4:00 ` bugzilla-daemon
2013-09-12  5:36 ` bugzilla-daemon
2013-09-12 13:26 ` bugzilla-daemon
2013-09-12 13:31 ` bugzilla-daemon
2013-09-12 14:53 ` bugzilla-daemon
2013-09-13  6:04 ` bugzilla-daemon [this message]
2013-09-13 19:13 ` bugzilla-daemon
2013-09-13 22:25 ` bugzilla-daemon
2013-09-13 22:32 ` bugzilla-daemon
2013-09-14  1:19 ` bugzilla-daemon
2013-09-17 14:19 ` bugzilla-daemon
2013-09-17 14:34 ` bugzilla-daemon
2013-09-17 22:54 ` bugzilla-daemon
2013-09-18 21:44 ` bugzilla-daemon
2013-09-18 21:46 ` bugzilla-daemon
2013-09-19  0:37 ` bugzilla-daemon
2013-09-19  5:32 ` bugzilla-daemon
2013-09-19  5:44 ` bugzilla-daemon
2013-09-19  6:15 ` bugzilla-daemon
2013-09-19  6:30 ` bugzilla-daemon
2013-09-19 13:38 ` bugzilla-daemon
2013-09-19 14:46 ` bugzilla-daemon
2013-09-19 15:34 ` bugzilla-daemon
2013-09-19 21:49 ` bugzilla-daemon
2013-09-21 19:45 ` bugzilla-daemon
2013-09-21 19:45 ` bugzilla-daemon
2013-09-22 16:51 ` bugzilla-daemon
2013-09-22 16:55 ` bugzilla-daemon
2013-09-23  2:50 ` bugzilla-daemon
2013-09-23  3:04 ` bugzilla-daemon
2013-09-23 14:07 ` bugzilla-daemon
2013-09-23 16:15 ` bugzilla-daemon
2013-09-25  1:47 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-68235-502-pYpLAVUelz@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).