From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757251Ab0FON27 (ORCPT ); Tue, 15 Jun 2010 09:28:59 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:39332 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753138Ab0FON25 convert rfc822-to-8bit (ORCPT ); Tue, 15 Jun 2010 09:28:57 -0400 From: "Rafael J. Wysocki" To: =?utf-8?q?Rafa=C5=82_Mi=C5=82ecki?= Subject: Re: [Regression, post-2.6.34] Hibernation broken on machines with radeon/KMS and r300 Date: Tue, 15 Jun 2010 15:27:01 +0200 User-Agent: KMail/1.13.3 (Linux/2.6.35-rc3-rjw+; KDE/4.4.3; x86_64; ; ) Cc: Alex Deucher , linux-kernel@vger.kernel.org, "dri-devel" , Dave Airlie , Andrew Morton , Linus Torvalds , linux-pm@lists.linux-foundation.org References: <201006141653.03879.rjw@sisk.pl> <201006142103.54616.rjw@sisk.pl> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 8BIT Message-Id: <201006151527.01794.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Monday, June 14, 2010, Rafał Miłecki wrote: > 2010/6/14 Rafael J. Wysocki : > > On Monday, June 14, 2010, Alex Deucher wrote: > >> 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 r300 > >> > after commit ce8f53709bf440100cb9d31b1303291551cf517f > >> > (drm/radeon/kms/pm: rework power management). At least, I'm able to reproduce > >> > 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 easy to > >> > figure out what's wrong with it and I didn't have the time to look more into > >> > details of this failure. However, 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? > > > > Nope. The symptom is slightly different, though, because now it hangs after > > turning off the screen. > > "Just" turning the screen off (like dpms force off) or turning it off > while suspending? Turning it off while suspending. > Maybe it could be worth enabling drm.debug option and logging using > netconsole or similar... That doesn't work during suspend, unfortunately. Perhaps I'll try to use a serial console if I don't fugure out what's wrong. Rafael