From: Kasper Dupont <kasperd@daimi.au.dk>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19-pre8-ac5 swsusp panic
Date: Fri, 24 May 2002 17:08:06 +0200 [thread overview]
Message-ID: <3CEE5756.69DF322F@daimi.au.dk> (raw)
In-Reply-To: <20020524011322.GA6612@merlin.emma.line.org>
On my system I'm actually able to suspend and start
the system again using kernel 2.4.19-pre8-ac5. But
there are some problems.
If there is not enough free physical memory it
complaints about not enough free memory and system
continues without suspending. However runing this
program before suspending helps:
#define BUFSIZE (1024*1024*256)
int main()
{
char *buf = malloc(BUFSIZE);
int i;
for (i=0;i<BUFSIZE;i+=4096) buf[i]++;
return 0;
}
There is plenty of swap space on my system, so that
is not a problem.
When the system has been started again after a
suspend my PS/2 mouse and my serial logins are
all dead. Restarting gpm and sending a SIGHUP to
the serial logins get the connections to live up.
But if I start X all input devices die, but the
screen output is correct and keep getting updated.
Finally ntpd does complain about loosing sync.
--
Kasper Dupont -- der bruger for meget tid på usenet.
For sending spam use mailto:razor-report@daimi.au.dk
next prev parent reply other threads:[~2002-05-24 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 1:13 2.4.19-pre8-ac5 swsusp panic Matthias Andree
2002-05-24 15:08 ` Kasper Dupont [this message]
2002-05-25 8:00 ` fchabaud
2002-05-25 23:20 ` Matthias Andree
2002-05-26 6:54 ` fchabaud
2002-05-26 12:03 ` fchabaud
2002-05-27 14:01 ` Pavel Machek
2002-05-28 21:13 ` fchabaud
2002-05-28 21:19 ` Pavel Machek
2002-05-27 13:59 ` 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=3CEE5756.69DF322F@daimi.au.dk \
--to=kasperd@daimi.au.dk \
--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