public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Laurent Riffard <laurent.riffard@free.fr>
Cc: linux-pm@lists.osdl.org
Subject: Re: BUG while suspending to swap on LVM
Date: Tue, 15 Aug 2006 14:55:30 +0200	[thread overview]
Message-ID: <200608151455.30626.rjw@sisk.pl> (raw)
In-Reply-To: <44E1BFDF.4000105@free.fr>

On Tuesday 15 August 2006 14:36, Laurent Riffard wrote:
> Le 14.08.2006 23:53, Rafael J. Wysocki a écrit :
> > On Monday 14 August 2006 23:37, Rafael J. Wysocki wrote:
> >> On Monday 14 August 2006 23:25, Laurent Riffard wrote:
> >>> Le 14.08.2006 22:50, Rafael J. Wysocki a écrit :
> >>>> On Monday 14 August 2006 22:03, Laurent Riffard wrote:
> >>>>> Le 14.08.2006 21:16, Rafael J. Wysocki a écrit :
> >>>>>> On Monday 14 August 2006 19:48, Laurent Riffard wrote:
> >>>>>>> Le 14.08.2006 19:30, Rafael J. Wysocki a écrit :
> > ]--snip--[
> >>> 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.
> > 
> > Could you please try to revert the following patches (in this order):
> > 
> > swsusp-use-memory-bitmaps-during-resume.patch
> > swsusp-introduce-memory-bitmaps.patch
> > swsusp-struct-snapshot_handle-cleanup.patch
> > swsusp-clean-up-browsing-of-pfns.patch
> > swsusp-read-speedup-cleanup-2.patch
> > swsusp-read-speedup-cleanup.patch
> > swsusp-read-speedup-fix.patch
> > swsusp-read-speedup.patch
> > swsusp-read-timer.patch
> > swsusp-write-speedup.patch
> > swsusp-write-timer.patch
> > 
> > from 2.6.18-rc4-mm1 and see if that helps?
> > 
> > Rafael
> 
> The bad guy is swsusp-read-speedup.patch. (I did a bisection on the
> -mm kernel).

It looks like we'll have to tell Andrew about that.

Rafael


-- 
You never change things by fighting the existing reality.
		R. Buckminster Fuller

  reply	other threads:[~2006-08-15 12:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 16:49 BUG while suspending to swap on LVM Laurent Riffard
2006-08-14 17:30 ` Rafael J. Wysocki
2006-08-14 17:48   ` Laurent Riffard
2006-08-14 19:16     ` Rafael J. Wysocki
2006-08-14 20:03       ` Laurent Riffard
2006-08-14 20:50         ` Rafael J. Wysocki
2006-08-14 21:25           ` Laurent Riffard
2006-08-14 21:37             ` Rafael J. Wysocki
2006-08-14 21:53               ` Rafael J. Wysocki
2006-08-15 12:36                 ` Laurent Riffard
2006-08-15 12:55                   ` Rafael J. Wysocki [this message]
2006-08-14 22:29               ` Laurent Riffard
2006-08-14 22:35                 ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200608151455.30626.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=laurent.riffard@free.fr \
    --cc=linux-pm@lists.osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox