From: Seth Forshee <seth.forshee@canonical.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Dave Airlie <airlied@redhat.com>,
Alex Deucher <alexander.deucher@amd.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Seth Forshee <seth.forshee@canonical.com>
Subject: Re: radeon issues on MacBook Pro 8,2
Date: Thu, 19 Jan 2012 14:53:17 -0600 [thread overview]
Message-ID: <20120119205317.GC23144@ubuntu-macmini> (raw)
In-Reply-To: <CADnq5_MiLE0XSpbrd66003DVxdR9c4MgQav3BD+bWtrKvbf+7Q@mail.gmail.com>
On Thu, Jan 19, 2012 at 02:48:52PM -0500, Alex Deucher wrote:
> On Thu, Jan 19, 2012 at 12:18 PM, Seth Forshee
> <seth.forshee@canonical.com> wrote:
> > I'm seeing several issues related to the radeon driver on a MacBook Pro
> > 8,2 with the following graphics card:
> >
> > ATI Technologies Inc Whistler [AMD Radeon HD 6600M Series] [1002:6741]
> >
> > All problems were observed when using kernel version 3.2.1. None are
> > seen when using fglrx.
> >
> > 1. Excessive power draw. When using the radeon driver ACPI reports a
> > power draw of about 30W on an idle desktop. Using fglrx brings this
> > number down to 15W.
>
> 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 notice
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.
> > 2. Occasional long delays when suspending. When this happens I see
> > messages like following in dmesg:
> >
> > [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
> > [drm:atom_execute_table_locked] *ERROR* atombios stuck executing D44E (len 62, WS 0, PS 0) @ 0xD46A
> >
> > Sometimes one of suspend or resume hangs completely, but I can't
> > tell which and am not sure whether or not it's related. I'm also
> > testing a Mac Mini with the exact same card which does not seem to
> > suffer from this issue.
> >
> > I ran a bisections that identified f8d0edd (drm/radeon/kms: improve
> > DP detect logic) as introducing problems with suspend, and reverting
> > this patch on top of 3.2.1 does seem to eliminate both issues.
> >
>
> 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.
> > 3. When the LVDS panel is powered off and back on, the display
> > flickers, as if the backlight is cycling rapidly between low and
> > high brightness. If the panel is left on this effect gradually
> > lessens and is eventually no longer noticable. This is not seen with
> > fglrx.
> >
>
> 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/<pci bus id>
> echo 1 > rom
> cat rom > /tmp/vbios.rom
> echo 0 > rom
>
> 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
next prev parent reply other threads:[~2012-01-19 20:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 17:18 radeon issues on MacBook Pro 8,2 Seth Forshee
2012-01-19 19:48 ` Alex Deucher
2012-01-19 20:53 ` Seth Forshee [this message]
2012-01-20 15:53 ` Seth Forshee
2012-01-20 19:38 ` Alex Deucher
2012-01-20 21:12 ` Seth Forshee
2012-01-20 21:39 ` Alex Deucher
2012-01-20 23:08 ` Seth Forshee
2012-02-01 1:06 ` Seth Forshee
2012-02-01 14:32 ` Alex Deucher
2012-01-20 21:09 ` Pasi Kärkkäinen
2012-01-20 23:26 ` Seth Forshee
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=20120119205317.GC23144@ubuntu-macmini \
--to=seth.forshee@canonical.com \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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).