<a href="http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commit;h=580b4fffbbdc3c899ee1f8189ba321bd60b48840">http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commit;h=580b4fffbbdc3c899ee1f8189ba321bd60b48840</a><br>
<br>I added this qurik upstream, it may need to be extended to other rs4xx, its worth a try.<br><br>Dave.<br><br><div class="gmail_quote">On Sat, Jul 10, 2010 at 4:13 PM, Andres Cimmarusti <span dir="ltr"><<a href="mailto:andrescimmarusti@yahoo.com">andrescimmarusti@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td style="font: inherit;" valign="top">
I dedicated a large portion of the day to finding a clue to this one. Following this advice: <a href="http://lxr.linux.no/#linux+v2.6.34.1/Documentation/power/s2ram.txt" target="_blank">http://lxr.linux.no/#linux+v2.6.34.1/Documentation/power/s2ram.txt</a><div>
I was able to extract a trace from the failed resume process:</div><div><br></div><div><div>Magic number: 0:981:799</div><div>hash matches drivers/base/power/main.c:523</div><div>pci 0000:01:05.0: hash matches</div><div>
ec PNP0C09:00: hash matches</div>
</div><div><br></div><div>The first hash match is none other than my ATI Radeon card as I easily verified with lspci:</div><div><br></div><div><div>01:05.0 VGA compatible controller: ATI Technologies Inc Radeon XPRESS 200M 5955 (PCIE)</div>
</div><div><br></div><div>However, the above link says that the likely
culprit in the failed resume process is the last hash match. This
corresponds to the EC driver: </div><div><a href="http://lxr.free-electrons.com/source/drivers/acpi/ec.c" target="_blank">http://lxr.free-electrons.com/source/drivers/acpi/ec.c</a></div>
<div><br></div><div>My card was, till recently, listed under embedded
graphics at the AMD/ATI website. So there appears to be some conflict
when using KMS between radeon and ec that causes the kernel to hang
(that explains why I can't ssh into my computer to get a trace). For
this reason I've cloned the original bug and reported the copy as a
kernel bug.</div>
<div>I will try to delve deeper into the matter by activating more verbose debugging symbols for acpi.</div><div><br></div><div>I would appreciate some advice and guidance, since I'm flying half-blind (I will try to follow the information present here <a href="http://ubuntuforums.org/showthread.php?t=505890" target="_blank">http://ubuntuforums.org/showthread.php?t=505890</a>)</div>
<div><br></div><div>Cheers,</div><div><br></div><font color="#888888"><div>Andres</div>
</font></td></tr></tbody></table><br>
<br>_______________________________________________<br>
xorg-driver-ati mailing list<br>
<a href="mailto:xorg-driver-ati@lists.x.org">xorg-driver-ati@lists.x.org</a><br>
<a href="http://lists.x.org/mailman/listinfo/xorg-driver-ati" target="_blank">http://lists.x.org/mailman/listinfo/xorg-driver-ati</a><br>
<br></blockquote></div><br>