On Thu 2006-06-29 00:37:57, Sebastian Kügler wrote:
> On Thursday 29 June 2006 00:24, Pavel Machek wrote:
> > > > Okay, can I get some details? Like how much memory does system have,
> > > > what stress test causes the failure?
> > >
> > > The machine has 1GB of RAM, filling it up beyond 500MB, maybe 600MB
> > > usually made swsusp a problem. I'd need to close apps then to be able to
> > > suspend.
> >
> > I'm pretty sure I do suspending with most of RAM full. You have
> > big-enough swap partition, right?
>
> 1 GB, it might not be completely empty though. I probably only hit swsusp
> limit much earlier than suspend2's (which after 34 suspend/resume cycles and
> heavy use in between I did not hit yet).
Okay, can we get bugzilla.kernel.org report? (assigned-to me)
This really should not happen, and I did not see swsusp fail like that
for quite a long time. I _could_ make it fail with make -j on kernel,
and similar crazy loads, but on nothing reasonable.
dmesg from failed run would be nice, too.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
