From: "Christian P. Schmidt" <charlie@digadd.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>,
Len Brown <lenb@kernel.org>
Subject: Re: Memory allocation problem with 2.6.22 after suspend/resume cycle
Date: Sun, 23 Sep 2007 15:38:46 +0300 [thread overview]
Message-ID: <46F65E56.8090701@digadd.de> (raw)
In-Reply-To: <200709230000.09722.rjw@sisk.pl>
Rafael J. Wysocki wrote:
> On Saturday, 22 September 2007 17:41, Christian P. Schmidt wrote:
>> Hi all,
>>
>> I'm having a strange problem, of course not reproducible. Sometimes
>> after a suspend (to ram) and resume cycle, the kernel will try to free
>> all memory. This means, all running applications are flushed to swap (as
>> long as it is available), caches and buffers stay at around 15MB each.
>>
>> The following video (traded quality for bandwidth) shows what happens on
>> the way from no swap to "swapon -a" (that's the unreadable thing in the
>> small shell): http://digadd.de/swapping.avi
>>
>> The system:
>> Linux dnnote 2.6.22.5 #1 SMP PREEMPT Sat Aug 25 18:39:21 AST 2007 x86_64
>> Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz GenuineIntel GNU/Linux
>
> Are you using an ATI binary graphics driver?
Yes. I do not (yet) have a choice... can't wait for the open source drivers.
>> A 32bit Kernel is unable to suspend/resume at all. No idea why. dmesg
>> shows nothing, logs show nothing. Any ideas for debugging are welcome.
>
> Well, that's interesting.
>
> Can you try in the minimal configuration (ie. boot with init=/bin/bash,
> mount /sys, mount /proc and run "echo mem > /sys/power/disk)?
Which? the 32bit or the 64bit?
Regards,
Chris
> Greetings,
> Rafael
next prev parent reply other threads:[~2007-09-23 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 15:41 Memory allocation problem with 2.6.22 after suspend/resume cycle Christian P. Schmidt
2007-09-22 22:00 ` Rafael J. Wysocki
2007-09-23 12:38 ` Christian P. Schmidt [this message]
2007-09-23 13:03 ` Rafael J. Wysocki
2007-09-23 16:19 ` Christian P. Schmidt
2007-09-23 18:28 ` Rafael J. Wysocki
2007-09-23 19:18 ` Christian P. Schmidt
2007-09-23 20:12 ` 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=46F65E56.8090701@digadd.de \
--to=charlie@digadd.de \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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.