All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 60857] Unstable display with Radeon 760G (ASUS M4A78L-M LE)
Date: Thu, 05 Sep 2013 17:53:20 +0000	[thread overview]
Message-ID: <bug-60857-2300-WYecgJ9cJQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60857-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=60857

--- Comment #6 from Stuart Foster <smf.linux@ntlworld.com> ---
(In reply to Alex Deucher from comment #5)
> (In reply to Stuart Foster from comment #4)
> > (In reply to Alex Deucher from comment #3)
> > > Can you bisect?  Also just to be sure, the monitor in qestion is connected
> > > to the integrated chip, not the dGPU correct?  Does disabling dpm fix the
> > > issue?
> > 
> > The monitor is connected to the integrated chip on the motherboard (760G
> > [Radeon 3000]) Disabling dpm does fix the problem (radeon.dpm=0 on lilo
> > append line, the patch is still included).
> 
> So disabling pdm fixes the issue?  It would be nice to know if it's also
> fixed with dpm disabled and without the patch.
> 
> > 
> > dmesg now reports:
> > 
> >  [drm] radeon: power management initialized
> >  
> > as apposed to
> > 
> >  [drm] radeon: dpm initialized
> > 
> > There is no mention of any power mangement on the RV516 [Radeon X1300/X1550
> > Series] is that correct ?
> 
> Correct.  dpm is only supported on r6xx and newer asics.
> 
> > 
> > The problem is present in vanilla 3.11-rc1.
> 
> You mean 3.12-rc1?

No having found that turning dpm off fixed the problem I went back to the first
3.11-rc which introduced the radeon dpm code.

The problem is fixed with the patch removed and with dpm turn off.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2013-09-05 17:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 10:40 [Bug 60857] New: Unstable display with Radeon 760G (ASUS M4A78L-M LE) bugzilla-daemon
2013-09-05 13:34 ` [Bug 60857] " bugzilla-daemon
2013-09-05 14:12 ` bugzilla-daemon
2013-09-05 14:24 ` bugzilla-daemon
2013-09-05 16:27 ` bugzilla-daemon
2013-09-05 16:34 ` bugzilla-daemon
2013-09-05 17:53 ` bugzilla-daemon [this message]
2013-09-11 20:35 ` bugzilla-daemon
2013-09-13  9:11 ` bugzilla-daemon
2013-09-13  9:13 ` bugzilla-daemon
2013-09-13 13:49 ` bugzilla-daemon
2013-09-13 13:50 ` bugzilla-daemon
2013-09-13 14:41 ` bugzilla-daemon
2013-09-13 15:09 ` bugzilla-daemon
2013-09-13 15:12 ` bugzilla-daemon
2013-09-17  7:44 ` bugzilla-daemon
2013-09-17 13:09 ` bugzilla-daemon
2013-09-17 15:12 ` bugzilla-daemon
2017-10-17 17:24 ` 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-60857-2300-WYecgJ9cJQ@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.