public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org, Stefan Seyfried <seife@suse.de>,
	ncunningham@linuxmail.org, pascal.schmidt@email.de
Subject: swsusp: 8-order allocation failure on demand (was: Re: 2.6.9-rc2-mm1 swsusp bug report.)
Date: Thu, 14 Oct 2004 23:47:51 +0200	[thread overview]
Message-ID: <200410142347.51241.rjw@sisk.pl> (raw)
In-Reply-To: <200410131929.11308.rjw@sisk.pl>

On Wednesday 13 of October 2004 19:29, Rafael J. Wysocki wrote:
> On Tuesday 12 of October 2004 10:55, Pavel Machek wrote:
> > Hi!
> > 
> > > > > Ok... And I guess it is nearly impossible to trigger this on demand,
> > > > > right?
> > > 
> > > I think it is possible.  Seemingly, on my box it's only a question of 
the 
> > > number of apps started.  I think I can work out a method to trigger it
> > > 90% of the time or so.  Please let me know if it's worthy of doing.
> > 
> > Yes, it would certainly help with testing...

Well, I can do that, it seems, 100% of the time.

The method is to do "init 5" (my default runlevel is 3, because vts become 
unreadable after I start X), log into KDE (as a non-root), start some X apps 
at random (eg. I run gkrellm, kmail, konqueror, Mozilla FireFox 32-bit w/ 
Flash plugin, and konsole with "su -") and run updatedb (as root, of course).

Apparently, running updatedb is essential.  After it finishes, on my box, you 
can forget of suspending to disk from under the X+KDE combo, even if the X 
apps (ie. kmail, konqueror, FireFox) are stopped before.  However, if 
updatedb is not run, the box usually suspends successfully.

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-10-14 21:46 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2HO0C-4xh-29@gated-at.bofh.it>
     [not found] ` <2I5b2-88s-15@gated-at.bofh.it>
     [not found]   ` <2I5E5-6h-19@gated-at.bofh.it>
     [not found]     ` <2I7Zd-1TK-11@gated-at.bofh.it>
2004-09-25  1:05       ` 2.6.9-rc2-mm1 swsusp bug report Pascal Schmidt
2004-09-25 10:16         ` Pavel Machek
2004-10-10 18:17           ` Jan Rychter
2004-10-11 13:32             ` Pavel Machek
2004-10-11 14:53               ` Jan Rychter
2004-10-17 19:10                 ` Pavel Machek
2004-10-17 21:40                   ` Nigel Cunningham
2004-10-11  9:56           ` Stefan Seyfried
2004-10-11 14:59             ` Pavel Machek
2004-10-11 17:18               ` Stefan Seyfried
2004-10-11 19:58                 ` Rafael J. Wysocki
2004-10-12  8:55                   ` Pavel Machek
2004-10-13 17:29                     ` Rafael J. Wysocki
2004-10-14 21:47                       ` Rafael J. Wysocki [this message]
2004-10-14 21:54                         ` swsusp: 8-order allocation failure on demand (update) Rafael J. Wysocki
2004-10-16 16:43                           ` Pavel Machek
2004-10-16 19:31                             ` Rafael J. Wysocki
2004-10-16 20:40                               ` Pavel Machek
2004-10-16 21:05                                 ` Rafael J. Wysocki
2004-10-16 21:25                                   ` Pavel Machek

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=200410142347.51241.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@linuxmail.org \
    --cc=pascal.schmidt@email.de \
    --cc=pavel@suse.cz \
    --cc=seife@suse.de \
    /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