Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751130AbVIBMR0 (ORCPT ); Fri, 2 Sep 2005 08:17:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751195AbVIBMR0 (ORCPT ); Fri, 2 Sep 2005 08:17:26 -0400 Received: from anf141.internetdsl.tpnet.pl ([83.17.87.141]:8368 "EHLO ogre.sisk.pl") by vger.kernel.org with ESMTP id S1751130AbVIBMRZ (ORCPT ); Fri, 2 Sep 2005 08:17:25 -0400 From: "Rafael J. Wysocki" To: Andrew Morton Subject: Re: 2.6.13-mm1: swsusp problem (was: PCMCIA problem) Date: Fri, 2 Sep 2005 16:17:42 +0200 User-Agent: KMail/1.8.2 Cc: Pavel Machek , linux-kernel@vger.kernel.org, Greg KH References: <20050901035542.1c621af6.akpm@osdl.org> <20050902040926.6e02c4e8.akpm@osdl.org> <200509021345.14168.rjw@sisk.pl> In-Reply-To: <200509021345.14168.rjw@sisk.pl> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200509021617.42482.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1907 Lines: 47 On Friday, 2 of September 2005 13:45, Rafael J. Wysocki wrote: > On Friday, 2 of September 2005 13:09, Andrew Morton wrote: > > Pavel Machek wrote: > > > > > > > One more piece of information. This is the one that loops: > > > > > > > > echo 30 > /sys/class/firmware/timeout > > > > > > Try echo -n ... > > > > Or revert gregkh-driver-sysfs-strip_leading_trailing_whitespace.patch. > > Obviously if you write 30\n and the write returns 2 then the shell will > > then try to write the \n. That returns zero and the shell tries again, ad > > infinitum. > > > > Rant. It took me two full days to weed out and fix all the crap people > > sent me to get -mm1 into a state where it vaguely compiled and booted. And > > it's untested nonsense like this which wrecks the whole effort for many > > testers. > > > > I suppose this is as good as anything.... > > Thanks for the fix. :-) > > Now, (using the fact that Pavel already is in the CC list ;-)) there's another > issue I have with swsusp, which is broken in a funny way. Namely, after > resuming from disk the box immediately goes into standby from which it > can be woken up by pressing the power button, but then it oopses, > goes into standby (or something similar) again, and hangs solid (unfortunately > I can't get the traces right now). Sorry for the noise. This problem has been fixed by the same patch (ie suspend is initiated by writing a string to a file on sysfs etc.). Greetings, Rafael -- - Would you tell me, please, which way I ought to go from here? - That depends a good deal on where you want to get to. -- Lewis Carroll "Alice's Adventures in Wonderland" - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/