From: Dave Young <hidave.darkstar@gmail.com>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: mmotm 2010-11-03-12-17 uploaded
Date: Thu, 4 Nov 2010 22:15:58 +0800 [thread overview]
Message-ID: <20101104141557.GA2472@darkstar> (raw)
In-Reply-To: <201011031919.oA3JJgkF008936@imap1.linux-foundation.org>
On Wed, Nov 03, 2010 at 12:18:16PM -0700, akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2010-11-03-12-17 has been uploaded to
>
> http://userweb.kernel.org/~akpm/mmotm/
>
> and will soon be available at
>
> git://zen-kernel.org/kernel/mmotm.git
>
> It contains the following patches against 2.6.36:
>
While booting I got:
[ 0.766899] =================================
[ 0.767135] [ INFO: inconsistent lock state ]
[ 0.767255] 2.6.36-mm1 #1
[ 0.767371] ---------------------------------
[ 0.767490] inconsistent {RECLAIM_FS-ON-W} -> {IN-RECLAIM_FS-W} usage.
[ 0.767613] kswapd0/544 [HC0[0]:SC0[0]:HE1:SE1] takes:
[ 0.767733] (cpu_hotplug.lock){+.+.?.}, at: [<ffffffff81041cbc>] get_online_cpus+0x3c/0x50
[ 0.768082] {RECLAIM_FS-ON-W} state was registered at:
[ 0.768203] [<ffffffff8106c865>] mark_held_locks+0x4d/0x6b
[ 0.768369] [<ffffffff8106c935>] lockdep_trace_alloc+0xb2/0xd7
[ 0.768534] [<ffffffff810f721e>] kmem_cache_alloc+0x2a/0x126
[ 0.768701] [<ffffffff81247ae9>] idr_pre_get+0x2d/0x75
[ 0.768867] [<ffffffff81247b42>] ida_pre_get+0x11/0x73
[ 0.769032] [<ffffffff81056344>] create_worker+0x4a/0x153
[ 0.769199] [<ffffffff814ecbd6>] workqueue_cpu_callback+0xb9/0x205
[ 0.769366] [<ffffffff8150c9bb>] notifier_call_chain+0x33/0x5b
[ 0.769532] [<ffffffff810603fb>] __raw_notifier_call_chain+0x9/0xb
[ 0.769697] [<ffffffff81503af6>] _cpu_up+0x75/0x11a
[ 0.769862] [<ffffffff81503bf0>] cpu_up+0x55/0x6a
[ 0.770008] [<ffffffff81ad1655>] kernel_init+0xc9/0x1e2
[ 0.770008] [<ffffffff81003a64>] kernel_thread_helper+0x4/0x10
[ 0.770008] irq event stamp: 27
[ 0.770008] hardirqs last enabled at (27): [<ffffffff8150923a>] _raw_spin_unlock_irqrestore+0x46/0x55
[ 0.770008] hardirqs last disabled at (26): [<ffffffff81508c8b>] _raw_spin_lock_irqsave+0x24/0x58
[ 0.770008] softirqs last enabled at (20): [<ffffffff8104d897>] del_timer_sync+0x50/0x8f
[ 0.770008] softirqs last disabled at (18): [<ffffffff8104d85f>] del_timer_sync+0x18/0x8f
[ 0.770008]
[ 0.770008] other info that might help us debug this:
[ 0.770008] no locks held by kswapd0/544.
[ 0.770008]
[ 0.770008] stack backtrace:
[ 0.770008] Pid: 544, comm: kswapd0 Not tainted 2.6.36-mm1 #1
[ 0.770008] Call Trace:
[ 0.770008] [<ffffffff8106c5a4>] valid_state+0x18b/0x19e
[ 0.770008] [<ffffffff8100deb3>] ? save_stack_trace+0x2a/0x48
[ 0.770008] [<ffffffff8106cf9d>] ? check_usage_forwards+0x0/0x7e
[ 0.770008] [<ffffffff8106c6bd>] mark_lock+0x106/0x261
[ 0.770008] [<ffffffff8100deb3>] ? save_stack_trace+0x2a/0x48
[ 0.770008] [<ffffffff8106da58>] __lock_acquire+0x3b0/0xe14
[ 0.770008] [<ffffffff8106e4ad>] ? __lock_acquire+0xe05/0xe14
[ 0.770008] [<ffffffff8106c5d9>] ? mark_lock+0x22/0x261
[ 0.770008] [<ffffffff8106e4ad>] ? __lock_acquire+0xe05/0xe14
[ 0.770008] [<ffffffff8106e4ad>] ? __lock_acquire+0xe05/0xe14
[ 0.770008] [<ffffffff8106e594>] lock_acquire+0xd8/0x104
[ 0.770008] [<ffffffff81041cbc>] ? get_online_cpus+0x3c/0x50
[ 0.770008] [<ffffffff81507a82>] __mutex_lock_common+0x48/0x34f
[ 0.770008] [<ffffffff81041cbc>] ? get_online_cpus+0x3c/0x50
[ 0.770008] [<ffffffff8104d46d>] ? try_to_del_timer_sync+0x6e/0x7c
[ 0.770008] [<ffffffff81041cbc>] ? get_online_cpus+0x3c/0x50
[ 0.770008] [<ffffffff8150923a>] ? _raw_spin_unlock_irqrestore+0x46/0x55
[ 0.770008] [<ffffffff810d61f1>] ? calculate_normal_threshold+0x0/0x47
[ 0.770008] [<ffffffff81507e38>] mutex_lock_nested+0x37/0x3c
[ 0.770008] [<ffffffff81041cbc>] get_online_cpus+0x3c/0x50
[ 0.770008] [<ffffffff810d6aa9>] set_pgdat_percpu_threshold+0x1f/0x97
[ 0.770008] [<ffffffff810cfb06>] kswapd+0x255/0x8cb
[ 0.770008] [<ffffffff81039c42>] ? finish_task_switch+0x44/0xeb
[ 0.770008] [<ffffffff815070a2>] ? schedule+0x68a/0x6d7
[ 0.770008] [<ffffffff8105bcb6>] ? autoremove_wake_function+0x0/0x38
[ 0.770008] [<ffffffff810cf8b1>] ? kswapd+0x0/0x8cb
[ 0.770008] [<ffffffff8105b81d>] kthread+0x9c/0xa4
[ 0.770008] [<ffffffff81003a64>] kernel_thread_helper+0x4/0x10
[ 0.770008] [<ffffffff81509650>] ? restore_args+0x0/0x30
[ 0.770008] [<ffffffff8105b781>] ? kthread+0x0/0xa4
[ 0.770008] [<ffffffff81003a60>] ? kernel_thread_helper+0x0/0x10
prev parent reply other threads:[~2010-11-04 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 19:18 mmotm 2010-11-03-12-17 uploaded akpm
2010-11-04 14:15 ` Dave Young [this message]
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=20101104141557.GA2472@darkstar \
--to=hidave.darkstar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox