From: Pavel Machek <pavel@ucw.cz>
To: Ingo Molnar <mingo@kernel.org>
Cc: Michal Hocko <mhocko@kernel.org>, Oleg Nesterov <oleg@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Chanho Min <chanho.min@lge.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] Revert "exec: make de_thread() freezable (was: Re: Linux 4.20-rc4)
Date: Tue, 4 Dec 2018 20:29:26 +0100 [thread overview]
Message-ID: <20181204192926.GA28651@amd> (raw)
In-Reply-To: <20181204090228.GC73770@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]
Hi!
> * Michal Hocko <mhocko@kernel.org> wrote:
>
> > > Do we actually have reports of this happening for people outside
> > > Android?
> >
> > Not that I am aware of.
>
> I'd say outside of Android 99% of the use of hibernation is the fail-safe
> that distributions offer on laptops with very low battery levels: the
> emergency hibernation when there's almost no power left anymore.
Android does not use hibernation AFAICT. Just s2ram.
> Do these hibernation failure messages typically make it to persistent
> logs before the system uses power?
I'd say so. If you have enough energy left for hibernation, you also
have enough energy left to write the logs and sync.
> In practice if that is buggy the kernel won't hibernate and the laptop
> will run out of power and the user will conclude "ugh, I shouldn't have
> left my laptop turned on" - without looking into the logs and reporting,
> as they'll perceive it as a user failure not a system failure.
>
> I certainly saw random Linux laptops fail to hibernate over the years and
> didn't report it, so if the distribution doesn't do the reporting
> automatically then chances are we'll never see it.
There are many reasons while hibernation can fail. Buggy drivers,
tasks in D state... And there are some when hibernation can fail "by
design". If you swap does not have enough space to store the data, for
example.
Hibernation was designed to be non-intrusive, and reliable as in "if
it hibernates it will also resume ok", but not reliable as in "it will
always hibernate".
I see that is problematic for "hibernate on battery low".
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-12-04 19:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 23:02 Linux 4.20-rc4 Linus Torvalds
2018-12-03 7:47 ` [PATCH] Revert "exec: make de_thread() freezable (was: Re: Linux 4.20-rc4) Ingo Molnar
2018-12-03 8:39 ` Michal Hocko
2018-12-03 12:03 ` Rafael J. Wysocki
2018-12-03 12:31 ` Oleg Nesterov
2018-12-03 12:38 ` Michal Hocko
2018-12-03 13:10 ` Pavel Machek
2018-12-03 13:53 ` Michal Hocko
2018-12-03 14:14 ` Pavel Machek
2018-12-03 14:17 ` Michal Hocko
2018-12-03 14:45 ` Pavel Machek
2018-12-03 17:06 ` Linus Torvalds
2018-12-03 17:18 ` Michal Hocko
2018-12-03 18:55 ` Pavel Machek
2018-12-04 9:02 ` Ingo Molnar
2018-12-04 9:10 ` Michal Hocko
2018-12-04 9:33 ` Ingo Molnar
2018-12-04 9:58 ` Michal Hocko
2018-12-04 17:31 ` Linus Torvalds
2018-12-04 18:17 ` Michal Hocko
2018-12-04 19:33 ` Linus Torvalds
2018-12-04 19:49 ` Linus Torvalds
2018-12-04 20:05 ` Linus Torvalds
2018-12-04 19:55 ` Pavel Machek
2018-12-04 19:42 ` Pavel Machek
2018-12-04 19:29 ` Pavel Machek [this message]
2018-12-03 13:40 ` Oleg Nesterov
2018-12-03 11:56 ` Oleg Nesterov
2018-12-04 9:17 ` Ingo Molnar
2018-12-05 14:36 ` Oleg Nesterov
2018-12-06 8:54 ` Chanho Min
2018-12-06 8:57 ` Pavel Machek
2018-12-06 9:07 ` Chanho Min
2018-12-03 12:00 ` Rafael J. Wysocki
2018-12-04 8:42 ` Ingo Molnar
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=20181204192926.GA28651@amd \
--to=pavel@ucw.cz \
--cc=a.p.zijlstra@chello.nl \
--cc=chanho.min@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=rafael.j.wysocki@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).