From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: 2.6.21-rc4-mm1 Date: Tue, 20 Mar 2007 21:58:48 +0100 Message-ID: <200703202158.50063.rjw@sisk.pl> References: <20070319205623.299d0378.akpm@linux-foundation.org> <46004080.6080202@gmail.com> <20070320202141.GA3604@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20070320202141.GA3604@elf.ucw.cz> Content-Disposition: inline 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: Pavel Machek Cc: Andrew Morton , linux-pm@lists.osdl.org, Jiri Slaby , linux-kernel@vger.kernel.org List-Id: linux-pm@vger.kernel.org On Tuesday, 20 March 2007 21:21, Pavel Machek wrote: > Hi! > = > > >>>> Also, it might be useful to add a temporary /proc/freeze-unfreeze = thing > > >>>> which will simply do a freeze/unfreeze cycle. Then we can apply v= arious > > >>>> workloads to the machine while madly stressing the freezer code. = > > >>> echo testproc > /sys/power/disk; echo disk > /sys/power/state ... is > > >>> pretty much what you want. > > >> Ok, I'll try this. > > > = > > > It will not help you -- probably -- it is equivalent to just running > > > s2ram. But it should make "successful" testing easier, because you no > > > longer need machine with working suspend to test refrigerator. > > = > > Aha, I didn't read it carefully. Suspend is working, but not in this ke= rnel. > > I haven't tried s2ram in this version. Should I (I'm away from it) -- w= ould > > it show something? > = > No, probably not. git bisect would help, but I guess it is easier to > let Rafael sort it out. Actually, the problem is 100% reproducible on my system too and I doubt it's caused by the recent freezer patches. Investigating. Rafael