From mboxrd@z Thu Jan  1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 60523] Radeon DPM not working with 2 monitors attached to
	Radeon HD5770 (Juniper)
Date: Tue, 20 Aug 2013 21:24:05 +0000
Message-ID: <bug-60523-2300-WFnoOEEiNk@https.bugzilla.kernel.org/>
References: <bug-60523-2300@https.bugzilla.kernel.org/>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org>
Received: from mail.kernel.org (mail.kernel.org [198.145.19.201])
	by gabe.freedesktop.org (Postfix) with ESMTP id 7E701E606B
	for <dri-devel@lists.freedesktop.org>;
	Tue, 20 Aug 2013 14:24:08 -0700 (PDT)
Received: from mail.kernel.org (localhost [127.0.0.1])
	by mail.kernel.org (Postfix) with ESMTP id 97D5120569
	for <dri-devel@lists.freedesktop.org>;
	Tue, 20 Aug 2013 21:24:07 +0000 (UTC)
Received: from bugzilla1.web.kernel.org (bugzilla1.web.kernel.org
	[172.20.200.51])
	by mail.kernel.org (Postfix) with ESMTP id BED7720563
	for <dri-devel@lists.freedesktop.org>;
	Tue, 20 Aug 2013 21:24:06 +0000 (UTC)
In-Reply-To: <bug-60523-2300@https.bugzilla.kernel.org/>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/dri-devel>
List-Post: <mailto:dri-devel@lists.freedesktop.org>
List-Help: <mailto:dri-devel-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=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

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

--- Comment #41 from Alex Deucher <alexdeucher@gmail.com> ---
Well, it helps a little, but I'm still able to reproduce it eventually even
with the patch.  The same kernel source is working fine on a fedora 16 system
and now exhibits this problem on Fedora 19.  So maybe it's not all gcc.

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