All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rainer Fiebig <jrf@mailbox.org>
To: Matheus Fillipe <matheusfillipeag@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	"Johannes Weiner" <hannes@cmpxchg.org>,
	"Rodolfo García Peñas" <kix@kix.es>,
	"Oliver Winker" <oliverml1@oli1170.net>,
	"Jan Kara" <jack@suse.cz>,
	bugzilla-daemon@bugzilla.kernel.org, linux-mm@kvack.org,
	"Maxim Patlasov" <mpatlasov@parallels.com>,
	"Fengguang Wu" <fengguang.wu@intel.com>,
	"Tejun Heo" <tj@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	killian.de.volder@megasoft.be, atillakaraca72@hotmail.com
Subject: Re: [Bug 75101] New: [bisected] s2disk / hibernate blocks on "Saving 506031 image data pages () ..."
Date: Wed, 3 Apr 2019 10:23:46 +0200	[thread overview]
Message-ID: <8bfe1578-6ace-4bb2-5a31-295660f0f8a4@mailbox.org> (raw)
In-Reply-To: <CAFWuBvcAFhhPk4K-w7OLVBo8psWuDdUP4hJNLq3QeFUyg=_Mow@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 2021 bytes --]

Am 03.04.19 um 05:54 schrieb Matheus Fillipe:
> Wow! Here I am to revive this topic in 2019! I have exactly the same
> problem, on ubuntu 18.04.2 with basically all kernels since 4.15.0-42 up to
> 5, which was all I tested, currently on 4.18.0-17-generic... I guess this
> has nothing to do with the kernel anyway.
> 
> It was working fine before, even with proprietary nvidia drivers which
> would generally cause a bug on the resume and not while saving the ram
> snapshot. I've been trying to tell this to the ubuntu guys and you can see
> my whole story with this problem right here:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819915
> 
> Shortly, I tried with or without nvidia modules enabled (or intel or using
> nouveau), many different kernels, disabled i915, and this is all  get in
> all those different combinations:
> https://launchpadlibrarian.net/417327528/i915.jpg
> 
> The event is pretty random and seems to be more likely to happen after 2 or
> 4 gb of ram is ever used (I have 16 in total), and nothing changes if later
> I reduce the ram usage later. But is random, I successfully hibernated with
> 11gb in use yesterday, just resumed and hibernated 5 seconds later without
> doing nothing else  than running hibernate, and got freeze there.
> 
> This also happens randomly if there's just 3 or 2 gb in use, likely on the
> second attempt of after more than 5 minutes after the computer is on. What
> can be wrong here?
> 

The last time that I've encountered this issue was sometime in 2017
under conditions described in Comment 23. And that's true for
s2both/s2disk and the kernel-methods.

It seems that you are using the uswsusp package. In that case it might
be worth taking a look at the settings in /etc/suspend.conf. What works
here is:

#image size = 3500000
early writeout = n
#threads = y

If this doesn't help, you should try hard to figure out what has changed
from Ubuntu 18.04.1 to 18.04.2 as it worked with the former for you.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-04-03  8:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-05 23:33 [Bug 75101] New: [bisected] s2disk / hibernate blocks on "Saving 506031 image data pages () ..." Johannes Weiner
2014-05-05 23:45 ` Rafael J. Wysocki
2014-06-12 22:02   ` Johannes Weiner
2014-06-12 23:50     ` Rafael J. Wysocki
2014-06-13  4:55       ` Johannes Weiner
2014-06-16 16:29         ` Rafael J. Wysocki
2019-04-02 23:25           ` Andrew Morton
2019-04-03  3:54             ` Matheus Fillipe
2019-04-03  8:23               ` Rainer Fiebig [this message]
2019-04-03  8:34             ` Rainer Fiebig
2019-04-03  9:34             ` Jan Kara
2019-04-03 10:04               ` Rainer Fiebig
2019-04-03 16:59                 ` Matheus Fillipe
2019-04-03 17:55                   ` Rainer Fiebig
2019-04-03 19:08                     ` Matheus Fillipe
     [not found]                     ` <CAFWuBvfxS0S6me_pneXmNzKwObSRUOg08_7=YToAoBg53UtPKg@mail.gmail.com>
2019-04-04 10:48                       ` Rainer Fiebig
2019-04-04 16:04                         ` matheus
2019-04-03 21:43               ` Rafael J. Wysocki
     [not found] <bug-75101-27@https.bugzilla.kernel.org/>
2014-04-29 22:24 ` Andrew Morton
2014-05-05 15:35   ` Johannes Weiner
2014-05-05 16:10     ` Jan Kara
2014-05-05 21:00       ` Oliver Winker

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=8bfe1578-6ace-4bb2-5a31-295660f0f8a4@mailbox.org \
    --to=jrf@mailbox.org \
    --cc=akpm@linux-foundation.org \
    --cc=atillakaraca72@hotmail.com \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=fengguang.wu@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=jack@suse.cz \
    --cc=killian.de.volder@megasoft.be \
    --cc=kix@kix.es \
    --cc=linux-mm@kvack.org \
    --cc=matheusfillipeag@gmail.com \
    --cc=mpatlasov@parallels.com \
    --cc=oliverml1@oli1170.net \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=tj@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.