Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754145AbZLCUQS (ORCPT ); Thu, 3 Dec 2009 15:16:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753854AbZLCUQR (ORCPT ); Thu, 3 Dec 2009 15:16:17 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:48282 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753586AbZLCUQQ (ORCPT ); Thu, 3 Dec 2009 15:16:16 -0500 Date: Thu, 3 Dec 2009 21:16:16 +0100 From: Pavel Machek To: Alan Jenkins Cc: Mel Gorman , "Rafael J. Wysocki" , pm list , linux-kernel , Kernel Testers List Subject: Re: [PATCH] uswsusp: automatically free the in-memory image once s2disk has finished with it Message-ID: <20091203201616.GA11689@elf.ucw.cz> References: <200912012253.08522.rjw@sisk.pl> <4B16545B.3090703@tuffmail.co.uk> <20091202122019.GD1457@csn.ul.ie> <4B16797C.3010304@tuffmail.co.uk> <20091202211107.GA20830@elf.ucw.cz> <20091202220718.GI1457@csn.ul.ie> <20091202221524.GB20830@elf.ucw.cz> <20091202222516.GD26702@csn.ul.ie> <20091203075301.GA29440@elf.ucw.cz> <4B17B5B8.1060105@tuffmail.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B17B5B8.1060105@tuffmail.co.uk> X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1798 Lines: 41 Hi! > >>>>What's wrong with it? The hang is likely because the allocator has no > >>>>memory to work with. The patch in question makes small changes to the > >>>>amount of available memory but it shouldn't matter on uni-core. Some > >>>>structures are slightly larger but it's extremely borderline. I'm at a > >>>>loss to explain actually why it makes a difference untill things were > >>>>extremely borderline to begin with. > >>>We reserve 4MB, for such purposes, and we already wrote image to disk > >>>with such constrains, so memory should not be _too_ tight. > >>> > >>>Can you try increasing PAGES_FOR_IO to 8MB or something like that? > >>> > >>What's wrong with just freeing the memory that is no longer required? > > > >Nothing. But 4MB was enough to power down before, it is not enough > >now, and I'd like to understand why. > > Here's a new datum: > > Applying this patch has left a less frequent hang. So far it has > happened twice. (Once playing last night, and once today testing > hibernation with KMS enabled). > > This hang happens at a different point. It happens _before_ writing > out the hibernation image. That is, I don't see the textual > progress bar, and if I force a power-cycle then it doesn't resume > (and complains about uncleanly unmounted filesystems). Can you drop the patches, and try increasing PAGES_FOR_IO to 8MB? That should give you enough memory... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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/