[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071121124503.GB5474@ucw.cz>
Date: Wed, 21 Nov 2007 12:45:03 +0000
From: Pavel Machek <pavel@....cz>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Andrey Borzenkov <arvidjaar@...l.ru>, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org,
Alexey Starikovskiy <astarikovskiy@...e.de>
Subject: Re: 2.6.24 regression: hibernation hangs on "Suspending console" in low-battery condition
Hi!
> > > > It works. Subjectively I have relatively long pause after first Suspending console
> > > > message (where it hangs otherwise), according to dmesg timestamp it is about
> > > > 1 second before next messages appear. Also last two times I tried it writeout
> > > > of suspend image was really slow; it was both with and without battery. Reading
> > > > on resume in really in order of magnitude faster.
> > > >
> > > > But manual STD so far works both on AC (with or without battery) or on battery.
> > > >
> > > > Of course it is possible that battery gets exhausted during STD, but system
> > > > is not switched off. Rather I would suspect something like ACPI notification
> > > > that comes during freeze ...
> > >
> > > Frankly, I'm suspecting a deadlock in the ACPI code.
> > >
> > > Please try to make kpowersave start hibernation a bit earlier and see what
> > > happens.
> > >
> > > What's your critical time now?
> > >
> > >
> >
> > it was set to 5%. Setting it to 10% makes it work, but it just confirms what I
> > said before - suspend-to-RAM in normal battery conditions (or without battery)
> > works.
>
> Yes.
I have something similar in suse bugzilla, but there the claim is 'it
always works if I trigger it manually'.
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 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/
Powered by blists - more mailing lists