mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John M Flinchbaugh <glynis@butterfly.hjsoft.com>
To: linux-kernel@vger.kernel.org
Subject: observations of swsusp and s3
Date: Fri, 16 Jul 2004 08:01:10 -0400	[thread overview]
Message-ID: <20040716120110.GA26122@butterfly.hjsoft.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]

1. using kernel 2.6.7 on my dell inspiron 3800, i've noticed that the 
clock that assigns start times to processes is running behind, and i 
suspect it could have something to do with having suspended (s4) the 
machine:

john@density:~$ date
Fri Jul 16 07:42:29 EDT 2004
john@density:~$ ps u | grep ps
john      4194  0.0  0.2  2528  848 pts/11   R+   Jul15   0:00 ps u
john      4195  0.0  0.1  1576  460 pts/11   S+   Jul15   0:00 grep ps

2. swsusp will fail to get free enough space if laptop_mode is
enabled.  disabling laptop_mode (in /proc/sys) before s4
suspending allows it to work.  i was pretty sure it should have
worked, since i only have 384M ram and i saw 600M swap free.

3. when swsusp was broken, i found that s3 actually worked for
the most part.  my script switches from my x session on vt7 to
vt12, suspends, and when it resumes, i have it chvt back to 12.
this enabled the display again nicely.  if i try to switch to a
console login (vt1-6), they're completely black.  closing the
lcd lid and reopening it turns it back on, so it's _really_
close to functioning nicely.

-- 
____________________}John Flinchbaugh{______________________
| glynis@hjsoft.com         http://www.hjsoft.com/~glynis/ |
~~Powered by Linux: Reboots are for hardware upgrades only~~

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-07-16 12:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16 12:01 John M Flinchbaugh [this message]
2004-07-17 16:01 ` 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=20040716120110.GA26122@butterfly.hjsoft.com \
    --to=glynis@butterfly.hjsoft.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®