From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laurent Riffard Subject: Re: BUG while suspending to swap on LVM Date: Tue, 15 Aug 2006 00:29:04 +0200 Message-ID: <44E0F930.4090702@free.fr> References: <44E0A995.50806@free.fr> <200608142250.06536.rjw@sisk.pl> <44E0EA33.7080801@free.fr> <200608142337.56843.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <200608142337.56843.rjw@sisk.pl> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: "Rafael J. Wysocki" Cc: linux-pm@lists.osdl.org List-Id: linux-pm@vger.kernel.org Le 14.08.2006 23:37, Rafael J. Wysocki a =E9crit : > On Monday 14 August 2006 23:25, Laurent Riffard wrote: >> Le 14.08.2006 22:50, Rafael J. Wysocki a =E9crit : >>> On Monday 14 August 2006 22:03, Laurent Riffard wrote: >>>> Le 14.08.2006 21:16, Rafael J. Wysocki a =E9crit : >>>>> On Monday 14 August 2006 19:48, Laurent Riffard wrote: >>>>>> Le 14.08.2006 19:30, Rafael J. Wysocki a =E9crit : > ]--snip--[ >>>> Does it mean it was mistaken on swap device ? >>> Yes. If your resume device is not the first swap, it won't work without >>> the patch. >> Ok, that's why I had that strange behaviour: >> - 2 swap devices online, suspend to second one: suspend works. >> - on resume, it can't find suspend signature on the 2nd swap device, so >> it continue with normal boot, fsck all FS and say something like "swap= on: = >> 1st swap device busy". I had to mkswap it. >> >> I was thinking that my initrd script was broken or I was mistyping the r= esume = >> device name in GRUB. Was funny... > = > Sorry for that. > = > This is not related to the BUG you've reported, but could you please try = to > suspend using the second swap as your resume partition with a patched ker= nel, > just to make sure the patch works? I have no boxes with two swaps to ver= ify > this ... It seems to always suspend to the first swap device, despite your patch. >>>> I did not pay attention on which swap device was online or not. >>> Please do when you test it. ;-) >> I tested with only 1 swap device online: /dev/mapper/vglinux1-lvswap: = >> same BUG happened with 2.6.18-rc4-mm1 patched. > = > Of course the patch doesn't matter if there's only one swap online. :-) > = > I have no ideas for now and I think some debug patches will be needed to = find > out what's up. > = > Greetings, > Rafael