linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric B Munson <emunson@akamai.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Commit 35ce7f29a breaks hibernation for XPS 13
Date: Fri, 24 Oct 2014 12:36:12 -0400	[thread overview]
Message-ID: <20141024163612.GA2256@akamai.com> (raw)
In-Reply-To: <20141024161634.GR4977@linux.vnet.ibm.com>

On Fri, 24 Oct 2014, Paul E. McKenney wrote:

> On Fri, Oct 24, 2014 at 12:08:15PM -0400, Eric B Munson wrote:
> > Paul,
> > 
> > As of 3.18-rc1 I can no longer hibernate my Dell XPS-13.  Bisect points
> > the finger at 35ce7f29a.  A revert of that commit confirms, I can once
> > again hibernate my machine without it.
> > 
> > When the hibernation fails I see this in dmesg:
> > [   37.953313] PM: Syncing filesystems ... done.
> > [   37.963694] Freezing user space processes ... (elapsed 0.001 seconds) done.
> > [   37.965297] PM: Marking nosave pages: [mem 0x00000000-0x00000fff]
> > [   37.965299] PM: Marking nosave pages: [mem 0x00058000-0x00058fff]
> > [   37.965301] PM: Marking nosave pages: [mem 0x0009d000-0x000fffff]
> > [   37.965304] PM: Marking nosave pages: [mem 0xc496a000-0xc4b6bfff]
> > [   37.965315] PM: Marking nosave pages: [mem 0xdadb7000-0xdcffefff]
> > [   37.965479] PM: Marking nosave pages: [mem 0xdd000000-0xffffffff]
> > [   37.966000] PM: Basic memory bitmaps created
> > [   37.966046] PM: Preallocating image memory... done (allocated 181989 pages)
> > [   38.141524] PM: Allocated 727956 kbytes in 0.17 seconds (4282.09 MB/s)
> > [   38.141525] Freezing remaining freezable tasks ... 
> > [   58.151863] Freezing of tasks failed after 20.004 seconds (0 tasks refusing to freeze, wq_busy=1):
> > [   58.151894] 
> > [   58.151896] Restarting kernel threads ... done.
> > [   58.181915] PM: Basic memory bitmaps freed
> > [   58.181917] Restarting tasks ... done.
> > 
> > 
> > I am not sure what else I can provide that might be useful, but I did
> > see the thread on net-dev about this same commit.  Please CC me on any
> > fixes and I will be happy to test.
> 
> Thank you for the bug report!
> 
> Does the following patch help?
> 
> 							Thanx, Paul

Paul,

This patch does not help.  I see the same dmesg output and failure to
hibernate.

Eric

> 
> ------------------------------------------------------------------------
> 
> rcu: More on deadlock between CPU hotplug and expedited grace periods
> 
> Commit dd56af42bd82 (rcu: Eliminate deadlock between CPU hotplug and
> expedited grace periods) was incomplete.  Although it did eliminate
> deadlocks involving synchronize_sched_expedited()'s acquisition of
> cpu_hotplug.lock via get_online_cpus(), it did nothing about the similar
> deadlock involving acquisition of this same lock via put_online_cpus().
> This deadlock became apparent with testing involving hibernation.
> 
> This commit therefore changes put_online_cpus() acquisition of this lock
> to be conditional, and increments a new cpu_hotplug.puts_pending field
> in case of acquisition failure.  Then cpu_hotplug_begin() checks for this
> new field being non-zero, and applies any changes to cpu_hotplug.refcount.
> 
> Reported-by: Jiri Kosina <jkosina@suse.cz>
> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Tested-by: Jiri Kosina <jkosina@suse.cz>
> Tested-by: Borislav Petkov <bp@suse.de>
> 
> diff --git a/kernel/cpu.c b/kernel/cpu.c
> index 356450f09c1f..90a3d017b90c 100644
> --- a/kernel/cpu.c
> +++ b/kernel/cpu.c
> @@ -64,6 +64,8 @@ static struct {
>  	 * an ongoing cpu hotplug operation.
>  	 */
>  	int refcount;
> +	/* And allows lockless put_online_cpus(). */
> +	atomic_t puts_pending;
>  
>  #ifdef CONFIG_DEBUG_LOCK_ALLOC
>  	struct lockdep_map dep_map;
> @@ -113,7 +115,11 @@ void put_online_cpus(void)
>  {
>  	if (cpu_hotplug.active_writer == current)
>  		return;
> -	mutex_lock(&cpu_hotplug.lock);
> +	if (!mutex_trylock(&cpu_hotplug.lock)) {
> +		atomic_inc(&cpu_hotplug.puts_pending);
> +		cpuhp_lock_release();
> +		return;
> +	}
>  
>  	if (WARN_ON(!cpu_hotplug.refcount))
>  		cpu_hotplug.refcount++; /* try to fix things up */
> @@ -155,6 +161,12 @@ void cpu_hotplug_begin(void)
>  	cpuhp_lock_acquire();
>  	for (;;) {
>  		mutex_lock(&cpu_hotplug.lock);
> +		if (atomic_read(&cpu_hotplug.puts_pending)) {
> +			int delta;
> +
> +			delta = atomic_xchg(&cpu_hotplug.puts_pending, 0);
> +			cpu_hotplug.refcount -= delta;
> +		}
>  		if (likely(!cpu_hotplug.refcount))
>  			break;
>  		__set_current_state(TASK_UNINTERRUPTIBLE);
> 

  reply	other threads:[~2014-10-24 16:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 16:08 Commit 35ce7f29a breaks hibernation for XPS 13 Eric B Munson
2014-10-24 16:16 ` Paul E. McKenney
2014-10-24 16:36   ` Eric B Munson [this message]
2014-10-24 17:18     ` Paul E. McKenney
2014-10-24 18:40       ` Eric B Munson
2014-10-24 20:31         ` Paul E. McKenney
2014-10-27 13:47           ` Eric B Munson
2014-10-27 15:10             ` Paul E. McKenney
2014-10-27 17:40               ` Paul E. McKenney
2014-10-27 18:03                 ` Eric B Munson
2014-10-27 18:14                   ` Paul E. McKenney

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=20141024163612.GA2256@akamai.com \
    --to=emunson@akamai.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    /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).