From: Tomas Racek <tracek@redhat.com>
To: Mel Gorman <mgorman@suse.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Jan Kara <jack@suse.cz>, Dave Hansen <dave@linux.vnet.ibm.com>,
George Spelvin <linux@horizon.com>,
riel@redhat.com
Subject: Re: 3.7-rc6 soft lockup in kswapd0
Date: Fri, 23 Nov 2012 11:13:17 +0100 [thread overview]
Message-ID: <20121123101316.GA10295@luke.redhat.com> (raw)
Hi Mel,
I've encoutered the same problem as George yesterday running xfstests in qemu with latest git sources:
BUG: soft lockup - CPU#0 stuck for 23s! [kswapd0:31]
irq event stamp: 9740956
hardirqs last enabled at (9740955): [<ffffffff8166c273>] restore_args+0x0/0x30
hardirqs last disabled at (9740956): [<ffffffff8166d9ad>] apic_timer_interrupt+0x6d/0x80
softirqs last enabled at (9740954): [<ffffffff8105c887>] __do_softirq+0x167/0x3d0
softirqs last disabled at (9740949): [<ffffffff8166e0fc>] call_softirq+0x1c/0x30
CPU 0
Pid: 31, comm: kswapd0 Not tainted 3.7.0-rc6+ #232 Bochs Bochs
Process kswapd0 (pid: 31, threadinfo ffff88003d2cc000, task ffff88003d2d8000)
Call Trace:
[<ffffffff8113bb81>] zone_watermark_ok_safe+0x71/0x100
[<ffffffff8113baff>] ? zone_watermark_ok+0x1f/0x30
[<ffffffff8114bd6e>] kswapd+0x2fe/0xd70
[<ffffffff8114ba70>] ? try_to_free_pages+0x830/0x830
[<ffffffff8107f9bd>] kthread+0xed/0x100
[<ffffffff8107f8d0>] ? insert_kthread_work+0x80/0x80
[<ffffffff8166cdac>] ret_from_fork+0x7c/0xb0
[<ffffffff8107f8d0>] ? insert_kthread_work+0x80/0x80
Code: 4c 2b 8f 00 01 00 00 48 d1 fa 49 39 d1 7e 30 31 c9 eb 20 0f 1f 80 00 00 00 00 48 8b 87 58 01 00 00 48 d1 fa 48 83 c7 58 48 d3 e0 <49> 29 c1 49 39 d1 7e 0f 83 c1 01 39 f1 75 e0 b8 01 00 00 00 5d
Git bisect pointed me to:
c654345924f mm: remove __GFP_NO_KSWAPD
[adding Rik to Cc:]
Prior to this commit I wasn't able to reproduce it.
(BTW: I hope I managed to send this mail with proper Reply-To:, strangely your mail and those from Honza were not delivered to my mailbox.)
Tom
--
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>
next reply other threads:[~2012-11-23 12:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 10:13 Tomas Racek [this message]
[not found] <20121122175824.19604.qmail@science.horizon.com>
2012-11-22 22:06 ` 3.7-rc6 soft lockup in kswapd0 Jan Kara
2012-11-22 22:36 ` Jan Kara
2012-11-23 8:51 ` Mel Gorman
2012-11-23 10:02 ` George Spelvin
2012-11-24 7:52 ` George Spelvin
2012-11-26 3:58 ` George Spelvin
2012-11-26 10:01 ` Mel Gorman
2012-11-26 13:05 ` George Spelvin
2012-11-26 18:32 ` Johannes Weiner
2012-11-26 18:53 ` George Spelvin
2012-11-26 19:09 ` Mel Gorman
2012-11-27 21:25 ` George Spelvin
2012-11-28 11:39 ` Mel Gorman
2012-11-29 14:54 ` George Spelvin
2012-11-29 15:20 ` Mel Gorman
2012-11-29 17:08 ` Johannes Weiner
2012-12-03 18:28 ` George Spelvin
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=20121123101316.GA10295@luke.redhat.com \
--to=tracek@redhat.com \
--cc=20121123085137.GA646@suse.de \
--cc=dave@linux.vnet.ibm.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@horizon.com \
--cc=mgorman@suse.de \
--cc=riel@redhat.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).