All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: linux-kernel@vger.kernel.org
Cc: Pavel Machek <pavel@suse.cz>, Andrew Morton <akpm@zip.com.au>,
	Patrick Mochel <mochel@digitalimplant.org>
Subject: Re: swsusp: kill crash when too much memory is free
Date: Fri, 10 Sep 2004 12:45:46 +0200	[thread overview]
Message-ID: <200409101245.47210.rjw@sisk.pl> (raw)
In-Reply-To: <20040910094039.GC11281@atrey.karlin.mff.cuni.cz>

On Friday 10 of September 2004 11:40, Pavel Machek wrote:
> Hi!
> 
> > > If too much memory is free, swsusp dies in quite a ugly way. Even when
> > > it is not neccessary to relocate pagedir, it is proably still
> > > neccessary to relocate individual pages. Thanks to Kurt Garloff and
> > > Stefan Seyfried...
> > > 								Pavel
> > > PS: And could I have one brown paper bag, please?
> > 
> > I applied this and it didn't fix my problems with resuming, unfortunately, 
but 
> > it changed the symptoms.  Namely, if USB modules are not unloaded before 
> > suspending, I get:
> 
> > This is 100% reproducible (ie unload USB modules and dm_mod, suspend the 
> > machine, try to wake it up, hangs solid).
> > 
> > Can you tell me, please, if there's anything I can compile out/in to debug 
it 
> > a bit more?  Or can I put some printk()s somewhere in the code to get some 
> > more info?  Any suggestions welcome.
> 
> Can you try my "bigdiff"?

It's compiling.  I can't get output from the serial console right now, so I'll 
send you a summary later on.

> Also, does it work okay in 32-bit mode? 

Well, I have a 64-bit distro installed, so I would have to reinstall to check 
this ...  It's not impossible, though.  If the big diff does not help, I'll 
try to do something about it.

Greets,
RJW

-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  reply	other threads:[~2004-09-10 10:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09 15:42 swsusp: kill crash when too much memory is free Pavel Machek
2004-09-09 22:01 ` Rafael J. Wysocki
2004-09-10  9:40   ` Pavel Machek
2004-09-10 10:45     ` Rafael J. Wysocki [this message]
2004-09-10 17:26     ` Rafael J. Wysocki
2004-09-10 22:29       ` Pavel Machek
2004-09-11  9:50         ` Rafael J. Wysocki
2004-09-11 19:22           ` Rafael J. Wysocki
2004-09-11 21:59             ` Rafael J. Wysocki
2004-09-12 10:32               ` swsusp (2.6.9-rc1-mm4 + bigdiff): Unable to handle kernel paging request Rafael J. Wysocki
2004-09-12 20:42           ` swsusp: kill crash when too much memory is free Pavel Machek
2004-09-12 21:16             ` Rafael J. Wysocki
2004-09-12 21:40               ` Stefan Seyfried
2004-09-12 22:23                 ` 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=200409101245.47210.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@digitalimplant.org \
    --cc=pavel@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.