Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756002Ab0BATwF (ORCPT ); Mon, 1 Feb 2010 14:52:05 -0500 Received: from fg-out-1718.google.com ([72.14.220.156]:62870 "EHLO fg-out-1718.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754697Ab0BATwD (ORCPT ); Mon, 1 Feb 2010 14:52:03 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=GQ98Qv+xeDWunO0lDckVbjPLtW9W7zvPqqEkIQo0I9LxxALBvqulwaqQKYOcRBYvpW GO4p34rt6I8B225Rx0JKq4djwyzZM8v5HpgP5y2khmVVW4TMH2EtWmxctV3piMMPStHO E0jqB8H5fafFfvXQbRlRvD5Doa9jDRKvOtv/s= Subject: Re: [RFC][PATCH] PM: Force GFP_NOIO during suspend/resume (was: Re: [linux-pm] Memory allocations in .suspend became very unreliable) From: Maxim Levitsky To: "Rafael J. Wysocki" Cc: KOSAKI Motohiro , linux-pm@lists.linux-foundation.org, LKML , linux-mm , Andrew Morton , Benjamin Herrenschmidt In-Reply-To: <1264883863.13861.3.camel@maxim-laptop> References: <1263549544.3112.10.camel@maxim-laptop> <201001170138.37283.rjw@sisk.pl> <1264866419.27933.0.camel@maxim-laptop> <201001301947.10453.rjw@sisk.pl> <1264883863.13861.3.camel@maxim-laptop> Content-Type: text/plain; charset="UTF-8" Date: Mon, 01 Feb 2010 21:51:56 +0200 Message-ID: <1265053916.26421.1.camel@maxim-laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1314 Lines: 38 On Sat, 2010-01-30 at 22:37 +0200, Maxim Levitsky wrote: > On Sat, 2010-01-30 at 19:47 +0100, Rafael J. Wysocki wrote: > > On Saturday 30 January 2010, Maxim Levitsky wrote: > > > On Sun, 2010-01-17 at 01:38 +0100, Rafael J. Wysocki wrote: > > > > Hi, > > > > > > > > I thing the snippet below is a good summary of what this is about. > > > > > > Any progress on that? > > > > Well, I'm waiting for you to report back: > > http://patchwork.kernel.org/patch/74740/ > > > > The patch is appended once again for convenience. > > Ah, sorry! > > I used the second version (with the locks) and it works for sure (~500 > cycles) > > However, as I discovered today, it takes the lock also for GFP_ATOMIC, > and thats why I see several backtraces in the kernel log. Anyway this > isn't important. > > I forgot all about this patch, and I am compiling the kernel right away. > Will put the kernel through the hibernate loop tonight. I did 123 hibernate cycles on my notebook. Everything is fine. This patch very very likely is working. Best regards, Maxim Levitsky -- 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/