From: Seth Forshee <seth.forshee@canonical.com>
To: Dave Airlie <airlied@redhat.com>,
Alex Deucher <alexander.deucher@amd.com>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Seth Forshee <seth.forshee@canonical.com>
Subject: radeon issues on MacBook Pro 8,2
Date: Thu, 19 Jan 2012 11:18:08 -0600 [thread overview]
Message-ID: <20120119171808.GB23144@ubuntu-macmini> (raw)
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.
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.
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.
Thanks,
Seth
next reply other threads:[~2012-01-19 17:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 17:18 Seth Forshee [this message]
2012-01-19 19:48 ` radeon issues on MacBook Pro 8,2 Alex Deucher
2012-01-19 20:53 ` Seth Forshee
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=20120119171808.GB23144@ubuntu-macmini \
--to=seth.forshee@canonical.com \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.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).