From: Andrey Borzenkov <arvidjaar@mail.ru>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
Alexey Starikovskiy <astarikovskiy@suse.de>
Subject: Re: 2.6.24 regression: hibernation hangs on "Suspending console" in low-battery condition
Date: Sun, 11 Nov 2007 21:48:18 +0300 [thread overview]
Message-ID: <200711112148.23133.arvidjaar@mail.ru> (raw)
In-Reply-To: <200711111927.26540.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 1880 bytes --]
On Sunday 11 November 2007, Rafael J. Wysocki wrote:
> On Sunday, 11 of November 2007, Andrey Borzenkov wrote:
> > On Monday 05 November 2007, Andrey Borzenkov wrote:
> > > Notice "hung" not "hangs". This happened so far only once - when low battery
> > > condition triggered suspend to disk. I was not able to reproduce it after
> > > this running on AC.
> > >
> > > Just in case it rings the bell for someone. This is not suspend regression
> > > reported earlier by Jens - I do not even have SATA nor is using libata
> > > drivers.
> > >
> >
> > This happened second time, now with 2.6.24-rc2. I have kpowersave configured
> > to initiate suspend-to-disk on low battery. Suspend-to-disk is initiated,
> > but system stops after Suspending console line. Suspend image is not created.
> >
> > This did work before although I do not name exact version.
> >
> > I am rather at loss how to proceed further ... any idea? dmesg and config
> > attached just in case. The problem is that hibernation works when I initiate
> > it manually ...
>
> Have you tried it with the battery removed?
>
>
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 ...
If someone can advice which options to enable I could try netconsole. But likely
not before next weekend.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-11-11 18:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-05 19:01 2.6.24-rc1: hibernation hung on "Suspending console" Andrey Borzenkov
2007-11-11 10:30 ` 2.6.24 regression: hibernation hangs on "Suspending console" in low-battery condition Andrey Borzenkov
2007-11-11 18:27 ` Rafael J. Wysocki
2007-11-11 18:48 ` Andrey Borzenkov [this message]
2007-11-11 19:10 ` Rafael J. Wysocki
2007-11-16 21:01 ` Andrey Borzenkov
2007-11-16 21:33 ` Rafael J. Wysocki
2007-11-16 21:55 ` Rafael J. Wysocki
2007-11-21 12:45 ` Pavel Machek
2007-11-21 17:06 ` Andrey Borzenkov
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=200711112148.23133.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=astarikovskiy@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox