From mboxrd@z Thu Jan 1 00:00:00 1970 From: Seth Forshee Subject: Re: radeon issues on MacBook Pro 8,2 Date: Thu, 19 Jan 2012 14:53:17 -0600 Message-ID: <20120119205317.GC23144@ubuntu-macmini> References: <20120119171808.GB23144@ubuntu-macmini> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Alex Deucher Cc: Dave Airlie , Alex Deucher , dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Seth Forshee List-Id: dri-devel@lists.freedesktop.org On Thu, Jan 19, 2012 at 02:48:52PM -0500, Alex Deucher wrote: > On Thu, Jan 19, 2012 at 12:18 PM, Seth Forshee > wrote: > > I'm seeing several issues related to the radeon driver on a MacBook= Pro > > 8,2 with the following graphics card: > > > > =C2=A0ATI Technologies Inc Whistler [AMD Radeon HD 6600M Series] [1= 002:6741] > > > > All problems were observed when using kernel version 3.2.1. None ar= e > > seen when using fglrx. > > > > =C2=A01. Excessive power draw. When using the radeon driver ACPI re= ports a > > =C2=A0 =C2=A0power draw of about 30W on an idle desktop. Using fglr= x brings this > > =C2=A0 =C2=A0number down to 15W. >=20 > The power saving features of the open source driver are not yet as > good as the closed source driver. Please see the power management > section of this page (http://wiki.x.org/wiki/RadeonFeature) for more > info on the options currently available. The dynpm option makes a small difference, saving about 2W. I did notic= e an ocassional flash on the screen with this option, and the same flash each time I changed the power options. The only thing that improves things significatnly is the "low" profile method, which gets it down to about 18.5W. > > =C2=A02. Occasional long delays when suspending. When this happens = I see > > =C2=A0 =C2=A0messages like following in dmesg: > > > > =C2=A0 =C2=A0 =C2=A0[drm:atom_op_jump] *ERROR* atombios stuck in lo= op for more than 5secs aborting > > =C2=A0 =C2=A0 =C2=A0[drm:atom_execute_table_locked] *ERROR* atombio= s stuck executing D44E (len 62, WS 0, PS 0) @ 0xD46A > > > > =C2=A0 =C2=A0Sometimes one of suspend or resume hangs completely, b= ut I can't > > =C2=A0 =C2=A0tell which and am not sure whether or not it's related= =2E I'm also > > =C2=A0 =C2=A0testing a Mac Mini with the exact same card which does= not seem to > > =C2=A0 =C2=A0suffer from this issue. > > > > =C2=A0 =C2=A0I ran a bisections that identified f8d0edd (drm/radeon= /kms: improve > > =C2=A0 =C2=A0DP detect logic) as introducing problems with suspend,= and reverting > > =C2=A0 =C2=A0this patch on top of 3.2.1 does seem to eliminate both= issues. > > >=20 > That patch doesn't really affect the modesetting paths directly; it > looks like a red herring to me. Perhaps. I just started a run of 200 s3 cycles with the patch reverted to see if I can reproduce the issues. I can usually trigger the problem with 15 or fewer s3 cycles. > > =C2=A03. When the LVDS panel is powered off and back on, the displa= y > > =C2=A0 =C2=A0flickers, as if the backlight is cycling rapidly betwe= en low and > > =C2=A0 =C2=A0high brightness. If the panel is left on this effect g= radually > > =C2=A0 =C2=A0lessens and is eventually no longer noticable. This is= not seen with > > =C2=A0 =C2=A0fglrx. > > >=20 > For the sake of tracking this properly, it would probably be best to = file a bug: > https://bugs.freedesktop.org > Product: DRI > Component: DRM/Radeon > What connectors does your card actually have on it? Please attach a > copy of your dmesg output and vbios: > (as root) > (use lspci to get the bus id) > cd /sys/bus/pci/devices/ > echo 1 > rom > cat rom > /tmp/vbios.rom > echo 0 > rom >=20 > Also, keep in mind that this is a mac so it's likely there may be > wonky mac specific problems. I filed bug #44955 for the flickering issue. Thanks, Seth