linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sasha.levin@oracle.com>
To: Vlastimil Babka <vbabka@suse.cz>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
	Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
	Hugh Dickins <hughd@google.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: lru_add_drain_all hangs
Date: Fri, 27 Mar 2015 17:36:12 -0400	[thread overview]
Message-ID: <5515CD4C.1050806@oracle.com> (raw)
In-Reply-To: <55152BED.9050500@suse.cz>

On 03/27/2015 06:07 AM, Vlastimil Babka wrote:
>> [ 3614.918852] trinity-c7      D ffff8802f4487b58 26976 16252   9410 0x10000000
>> > [ 3614.919580]  ffff8802f4487b58 ffff8802f6b98ca8 0000000000000000 0000000000000000
>> > [ 3614.920435]  ffff88017d3e0558 ffff88017d3e0530 ffff8802f6b98008 ffff88016bad0000
>> > [ 3614.921219]  ffff8802f6b98000 ffff8802f4487b38 ffff8802f4480000 ffffed005e890002
>> > [ 3614.922069] Call Trace:
>> > [ 3614.922346] schedule (./arch/x86/include/asm/bitops.h:311 (discriminator 1) kernel/sched/core.c:2827 (discriminator 1))
>> > [ 3614.923023] schedule_preempt_disabled (kernel/sched/core.c:2859)
>> > [ 3614.923707] mutex_lock_nested (kernel/locking/mutex.c:585 kernel/locking/mutex.c:623)
>> > [ 3614.924486] ? lru_add_drain_all (mm/swap.c:867)
>> > [ 3614.925211] ? trace_hardirqs_on_caller (kernel/locking/lockdep.c:2580 kernel/locking/lockdep.c:2622)
>> > [ 3614.925970] ? lru_add_drain_all (mm/swap.c:867)
>> > [ 3614.926692] ? mutex_trylock (kernel/locking/mutex.c:621)
>> > [ 3614.927464] ? mpol_new (mm/mempolicy.c:285)
>> > [ 3614.928044] lru_add_drain_all (mm/swap.c:867)
>> > [ 3614.928608] migrate_prep (mm/migrate.c:64)
>> > [ 3614.929092] SYSC_mbind (mm/mempolicy.c:1188 mm/mempolicy.c:1319)
>> > [ 3614.929619] ? rcu_eqs_exit_common (kernel/rcu/tree.c:735 (discriminator 8))
>> > [ 3614.930318] ? __mpol_equal (mm/mempolicy.c:1304)
>> > [ 3614.930877] ? trace_hardirqs_on (kernel/locking/lockdep.c:2630)
>> > [ 3614.931485] ? syscall_trace_enter_phase2 (arch/x86/kernel/ptrace.c:1592)
>> > [ 3614.932184] SyS_mbind (mm/mempolicy.c:1301)
> That looks like trinity-c7 is waiting ot in too, but later on (after some more
> listings like this for trinity-c7, probably threads?) we have:
> 

It keeps changing constantly, even in this trace the process is blocking on the mutex
rather than doing something useful, and in the next trace it's a different process.


Thanks,
Sasha

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2015-03-27 21:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-27  3:32 Sasha Levin
2015-03-27 10:07 ` Vlastimil Babka
2015-03-27 21:36   ` Sasha Levin [this message]
2015-03-28 12:41     ` Vlastimil Babka

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=5515CD4C.1050806@oracle.com \
    --to=sasha.levin@oracle.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=riel@redhat.com \
    --cc=vbabka@suse.cz \
    /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