From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262231AbUCACwT (ORCPT ); Sun, 29 Feb 2004 21:52:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262227AbUCACvu (ORCPT ); Sun, 29 Feb 2004 21:51:50 -0500 Received: from nsmtp.pacific.net.th ([203.121.130.117]:17897 "EHLO nsmtp.pacific.net.th") by vger.kernel.org with ESMTP id S262222AbUCACvs (ORCPT ); Sun, 29 Feb 2004 21:51:48 -0500 Date: Mon, 01 Mar 2004 10:51:21 +0800 From: "Michael Frank" To: "Micha Feigin" , "Software suspend" , linux-kernel@vger.kernel.org Subject: Re: [Swsusp-devel] Re: Dropping CONFIG_PM_DISK? References: <1ulUA-33w-3@gated-at.bofh.it> <20040229161721.GA16688@hell.org.pl> <20040229162317.GC283@elf.ucw.cz> <20040229213302.GA23719@luna.mooo.com> Content-Type: text/plain; charset=US-ASCII; format=flowed delsp=yes MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-ID: In-Reply-To: <20040229213302.GA23719@luna.mooo.com> User-Agent: Opera M2/7.50 (Linux, build 600) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sun, 29 Feb 2004 23:33:02 +0200, Micha Feigin wrote: > On Mon, Mar 01, 2004 at 02:10:09AM +0800, Michael Frank wrote: >> On Sun, 29 Feb 2004 18:32:21 +0100, M?ns Rullg?rd wrote: >> >> >Pavel Machek writes: >> > >> >>Hi! >> >> >> >>>> Would there be any major screaming if I tried to drop CONFIG_PM_DISK? >> >>>> It seems noone is maintaining it, equivalent functionality is provided >> >>>> by swsusp, and it is confusing users... >> >>> >> >>>It may be ugly, it may be unmaintained, but I get the impression that it >> >>>works for some people for whom swsusp doesn't. So unless swsusp works for >> >>>everyone or Nigel's swsusp2 is merged, I'd suggest leaving that in. >> >> >> >>Do you have example when pmdisk works and swsusp does not? I'm not >> >>aware of any in recent history... >> > >> >For me, none of them (pmdisk, swsusp and swsusp2) work. I did manage >> >to get pmdisk to resume once, and swsusp2 makes it half-way through >> >the resume. >> >> Hate to hear this - 2.0 is said to work _flawlessly_ on 2.4.24 and >> on 2.6.2 within the bounds of more complex PM/driver issues. >> >> 2.4.25 and 2.6.3 patches are undergoing testing. >> >> If you like to try again, please have a look at http://swsusp.sf.net. >> >> There is also comprehensive FAQ and Howto on the site. >> >> You also will find a lot of user support wrt specific HW. >> >> Myself is running 2.0 on 2.4.2[345] without any stability issues >> whatsoever this year. >> >> In short, I am confident we can make it work for you! >> > > Same for me. No problems with 2.4.[345] and also works nicely on > 2.6.[123] as long as dri is not running (PM problems). > > Only one problem that is not caused by swsusp but is a bit of a head > ache. X will ocationaly crash when changing VT to the console. I > originally thought it was a problem with my dri resume patch for > mach64, but the resume kicks in only when entering X and not when > leaving so its got to be something else. Yeah, too bad - that 2.4 style PM got depreciated and let die before the "new-driver-model" PM is working - that perfectly good drivers were rewritten from scratch, but without functioning PM support :-( Regards Michael