Pavel Machek wrote:
> 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'.
ehh ... did not I say exactly the same thing?
P.S. may I ask you to reply to all - at least to the person who initiated
this thread ...
-
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]
