<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">Fantastic!, it works!<br><br>I forced it by just writing (like your quirk):<br><br> /* quirk for rs4xx HP laptops to make them resume<br> * - they hang on resume inside the dynclk 1 table.<br> */<br> return;<br><br>Just before the /* DYN CLK 1 */ line in the radeon_combios.c file.<br><br>So, can you modify your patch to encompass my chipset? actually I know of several xpress 200 different chipset that have this issue, see for example: <br><br>https://bugs.launchpad.net/ubuntu/+source/linux/+bug/305301?comments=all<br>or<br>https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/577340<br><br>I will contact this bug reporters and will try to get them to try by modifying the kernel source.<br><br>I recently opened up a bug report upstream, to which you replied with the same
solution. Perhaps that provides the ideal framework for a slight change in your patch?<br><br>Thanks a lot!<br><br>Andres<br><br>--- On <b>Sat, 7/10/10, Dave Airlie <i><airlied@gmail.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Dave Airlie <airlied@gmail.com><br>Subject: Re: Debian bugs: 588601, 588602: xpress 200m 5955 => resume from suspend fails with KMS enabled<br>To: "Andres Cimmarusti" <andrescimmarusti@yahoo.com><br>Cc: xorg-driver-ati@lists.x.org<br>Date: Saturday, July 10, 2010, 2:39 AM<br><br><div id="yiv48453585"><a rel="nofollow" target="_blank" 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 rel="nofollow" ymailto="mailto:andrescimmarusti@yahoo.com" target="_blank" href="/mc/compose?to=andrescimmarusti@yahoo.com">andrescimmarusti@yahoo.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td style="font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; font-size: inherit; line-height: inherit; font-size-adjust: inherit; font-stretch: inherit; -x-system-font: none;" valign="top">
I dedicated a large portion of the day to finding a clue to this one. Following this advice: <a rel="nofollow" target="_blank" href="http://lxr.linux.no/#linux+v2.6.34.1/Documentation/power/s2ram.txt">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 rel="nofollow" target="_blank" href="http://lxr.free-electrons.com/source/drivers/acpi/ec.c">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 rel="nofollow" target="_blank" href="http://ubuntuforums.org/showthread.php?t=505890">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 rel="nofollow" ymailto="mailto:xorg-driver-ati@lists.x.org" target="_blank" href="/mc/compose?to=xorg-driver-ati@lists.x.org">xorg-driver-ati@lists.x.org</a><br>
<a rel="nofollow" target="_blank" href="http://lists.x.org/mailman/listinfo/xorg-driver-ati">http://lists.x.org/mailman/listinfo/xorg-driver-ati</a><br>
<br></blockquote></div><br>
</div></blockquote></td></tr></table><br>