From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Deucher Subject: Re: [Regression, post-2.6.34] Hibernation broken on machines with radeon/KMS and r300 Date: Mon, 14 Jun 2010 12:00:29 -0400 Message-ID: References: <201006141653.03879.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <201006141653.03879.rjw@sisk.pl> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: "Rafael J. Wysocki" Cc: linux-kernel@vger.kernel.org, dri-devel , Dave Airlie , Andrew Morton , Linus Torvalds , linux-pm@lists.linux-foundation.org List-Id: linux-pm@vger.kernel.org On Mon, Jun 14, 2010 at 10:53 AM, Rafael J. Wysocki wrote: > Alex, Dave, > > I'm afraid hibernation is broken on all machines using radeon/KMS with r3= 00 > after commit ce8f53709bf440100cb9d31b1303291551cf517f > (drm/radeon/kms/pm: rework power management). =A0At least, I'm able to re= produce > the symptom, which is that the machine hangs hard around the point where = an > image is created (probably during the device thaw phase), on two different > boxes with r300 (the output of lspci from one of them is attached for > reference, the other one is HP nx6325). > > Suspend to RAM appears to work fine at least on one of the affected boxes. > > Unfortunately, the commit above changes a lot of code and it's not too ea= sy to > figure out what's wrong with it and I didn't have the time to look more i= nto > details of this failure. =A0However, it looks like you use .suspend() and > .resume() callbacks as .freeze() and .thaw() which may not be 100% correct > (in fact it looks like the "legacy" PCI suspend/resume is used, which is = not > recommended any more). > Does it work any better after Dave's last drm pull request? With the latest changes, pm should not be a factor unless it's explicitly enabled via sysfs. Alex > Thanks, > Rafael >