From: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>
To: linux-nfs@vger.kernel.org
Subject: Broken suspend since 3.18.9
Date: Wed, 11 Mar 2015 11:50:02 +0000 (UTC) [thread overview]
Message-ID: <pan.2015.03.11.11.50.02@googlemail.com> (raw)
Since 3.18.9 suspend no longer works reliably (only ~10% of the time), unlike 3.18.8;
the suspend sequence starts, but after a few seconds the machine just returns to
wakeup state.
The following log spew points the finger at NFS-related changes:
Mar 11 00:54:45 ragnarok kernel: PM: Syncing filesystems ... done.
Mar 11 00:55:05 ragnarok kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Mar 11 00:55:05 ragnarok kernel: Freezing remaining freezable tasks ...
Mar 11 00:55:05 ragnarok kernel: nfsv4.1-svc D ffff88061f411740 0 22942 2 0x00000000
Mar 11 00:55:05 ragnarok kernel: ffff8800d63cfd98 0000000000000046 ffff8800d63cfc78 0000000000009000
Mar 11 00:55:05 ragnarok kernel: ffff88059b582ca0 ffff8800d63cffd8 ffff88059b583020 01ffffffa07c0798
Mar 11 00:55:05 ragnarok kernel: 0000000000011740 ffffffff81816500 ffff88061f411740 ffff88055cc48ee0
Mar 11 00:55:05 ragnarok kernel: Call Trace:
Mar 11 00:55:05 ragnarok kernel: [<ffffffffa07c57e4>] ? rpc_release_resources_task+0x34/0x40 [sunrpc]
Mar 11 00:55:05 ragnarok kernel: [<ffffffffa07c64de>] ? __rpc_execute+0x18e/0x360 [sunrpc]
Mar 11 00:55:05 ragnarok kernel: [<ffffffff8108ad4b>] ? lock_timer_base.isra.36+0x2b/0x50
Mar 11 00:55:05 ragnarok kernel: [<ffffffff8108ae1f>] ? try_to_del_timer_sync+0x4f/0x70
Mar 11 00:55:05 ragnarok kernel: [<ffffffff81535c02>] schedule_timeout+0x102/0x1f0
Mar 11 00:55:05 ragnarok kernel: [<ffffffffa07c67b0>] ? rpc_do_put_task+0x80/0x90 [sunrpc]
Mar 11 00:55:05 ragnarok kernel: [<ffffffff8108a7b0>] ? migrate_timer_list+0xb0/0xb0
Mar 11 00:55:05 ragnarok kernel: [<ffffffffa03c1f7a>] nfs41_callback_svc+0x16a/0x180 [nfsv4]
Mar 11 00:55:05 ragnarok kernel: [<ffffffff81074710>] ? __wake_up_sync+0x20/0x20
Mar 11 00:55:05 ragnarok kernel: [<ffffffffa03c1e10>] ? nfs4_callback_svc+0x60/0x60 [nfsv4]
Mar 11 00:55:05 ragnarok kernel: [<ffffffff81067c2b>] kthread+0xdb/0x100
Mar 11 00:55:05 ragnarok kernel: [<ffffffff81067b50>] ? kthread_create_on_node+0x180/0x180
Mar 11 00:55:05 ragnarok kernel: [<ffffffff81536d2c>] ret_from_fork+0x7c/0xb0
Mar 11 00:55:05 ragnarok kernel: [<ffffffff81067b50>] ? kthread_create_on_node+0x180/0x180
Mar 11 00:55:05 ragnarok kernel:
Mar 11 00:55:05 ragnarok kernel: Restarting kernel threads ... done.
Mar 11 00:55:05 ragnarok kernel: Restarting tasks ... done.
I found that shutting down the automount service (thus killing all NFS mounts)
makes things work immediately. The same symptom can be seen in 3.19.1, which
- as far as I can tell - got the same commits recently.
Any ideas? I can gladly test patches.
Thanks!
Holger
reply other threads:[~2015-03-11 11:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=pan.2015.03.11.11.50.02@googlemail.com \
--to=holger.hoffstaette@googlemail.com \
--cc=linux-nfs@vger.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.