linux-kernel - Re: Memory allocation problem with 2.6.22 after suspend/resume cycle

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 23 Sep 2007 15:03:47 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	"Christian P. Schmidt" <charlie@...add.de>
Cc:	linux-kernel@...r.kernel.org, Pavel Machek <pavel@....cz>,
	Len Brown <lenb@...nel.org>
Subject: Re: Memory allocation problem with 2.6.22 after suspend/resume cycle

On Sunday, 23 September 2007 14:38, Christian P. Schmidt wrote:
> 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.

That, most probably, is the source of the problem.  Please see:
http://bugzilla.kernel.org/show_bug.cgi?id=8943

> >> 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?

32-bit, but please do that without the ATI driver.

Greetings,
Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/