From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: 2.6.25-rc2 System no longer powers off after suspend-to-disk. Screen becomes green. Date: Wed, 20 Feb 2008 21:45:00 +0100 Message-ID: <200802202145.01882.rjw@sisk.pl> References: <200802202114.43007.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: suspend-devel-bounces@lists.sourceforge.net Errors-To: suspend-devel-bounces@lists.sourceforge.net To: Linus Torvalds Cc: Jeff Chua , Dave Airlie , Greg KH , lkml , suspend-devel@lists.sourceforge.net, linux-acpi@vger.kernel.org, Jesse Barnes List-Id: linux-acpi@vger.kernel.org On Wednesday, 20 of February 2008, Linus Torvalds wrote: > > On Wed, 20 Feb 2008, Rafael J. Wysocki wrote: > > > > I think we should export the target sleep state somehow. > > Yeah. By *not* using "->suspend()" for freezing or hibernate. > > Please, Rafael - just make the f*cking suspend-to-disk use other routines > already. Okay, I think I'll just start sending patches for that, but rather not earlier than in the 2.6.27 time frame. No one else works on that and I've been busy with other things recently. Besides, I'm not even a full time kernel developer ... > 99% of all hardware needs to do exactly *nothing* on suspend-to-disk, and the > ones that really do need things tend to need to not do a whole lot. > > For example, the "freeze" action for USB (which is one of the hardest > things to suspend) should literally be something like just setting the > controller STOP bit, and waiting for it to have stopped. The "unfreeze" > should be to just clear the stop bit, while the "restart" should be just a > controller reset to use the current memory image. > > NONE OF THIS HAS ABSOLUTELY ANYTHING TO DO WITH SUSPEND. > > It never did. I've told people so for years. Maybe actually seeing the > problems will make people realize. I think so. > So please, we shouldn't call "->suspend[_late]" or "->resume[_early]" at > all. Not with PMSG_FREEZE, not with PMSG_*anything*. > > Can we please get this fixed some day? Yes, we can (hopefully). Thanks, Rafael ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/