From: Alexander Beregalov <a.beregalov@gmail.com>
To: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: next-20090202: task kmemleak:763 blocked for more than 120 seconds.
Date: Mon, 2 Feb 2009 14:27:28 +0300 [thread overview]
Message-ID: <a4423d670902020327x61a1d9dehb1642b25ec7f82f1@mail.gmail.com> (raw)
Hi
It seems it is blocked forever.
[ 1704.619898] INFO: task kmemleak:763 blocked for more than 120 seconds.
[ 1704.697951] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[ 1704.791613] kmemleak D 0000000000000001 6008 763 2
[ 1704.862460] ffff88007d497e60 0000000000000046 ffff88007d497da0
ffff88007d6a4000
[ 1704.951037] ffff88007d6a4000 0000000000004000 0000000000000002
ffff88007d6a4000
[ 1705.039609] ffff88007d80a000 ffff88007d6a4398 0000000200000000
00000001000758b5
[ 1705.128202] Call Trace:
[ 1705.157383] [<ffffffff806379f2>] ? _spin_unlock_irqrestore+0x42/0x80
[ 1705.234396] [<ffffffff80634c86>] ? schedule_timeout+0x66/0xe0
[ 1705.304137] [<ffffffff80634a43>] schedule+0x13/0x40
[ 1705.363483] [<ffffffff80634c86>] schedule_timeout+0x66/0xe0
[ 1705.431145] [<ffffffff8024c7c0>] ? process_timeout+0x0/0x10
[ 1705.498918] [<ffffffff80634c81>] ? schedule_timeout+0x61/0xe0
[ 1705.568663] [<ffffffff80634d19>] schedule_timeout_uninterruptible+0x19/0x20
[ 1705.652987] [<ffffffff802c3830>] kmemleak_scan_thread+0x120/0x170
[ 1705.726889] [<ffffffff802c3710>] ? kmemleak_scan_thread+0x0/0x170
[ 1705.800784] [<ffffffff80258d66>] kthread+0x56/0x90
[ 1705.859088] [<ffffffff8020ce9a>] child_rip+0xa/0x20
[ 1705.918441] [<ffffffff80235489>] ? finish_task_switch+0x89/0x110
[ 1705.991303] [<ffffffff80637986>] ? _spin_unlock_irq+0x36/0x60
[ 1706.061041] [<ffffffff8020c880>] ? restore_args+0x0/0x30
[ 1706.125584] [<ffffffff80258d10>] ? kthread+0x0/0x90
[ 1706.184917] [<ffffffff8020ce90>] ? child_rip+0x0/0x20
[ 1706.246334] no locks held by kmemleak/763.
next reply other threads:[~2009-02-02 11:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 11:27 Alexander Beregalov [this message]
2009-02-02 14:53 ` Catalin Marinas
2009-02-02 15:14 ` Frédéric Weisbecker
2009-02-02 15:15 ` Frédéric Weisbecker
2009-02-02 21:57 ` Mandeep Singh Baines
2009-02-03 0:41 ` Frederic Weisbecker
2009-02-03 12:48 ` Catalin Marinas
2009-02-03 20:52 ` Frederic Weisbecker
2009-02-06 16:02 ` next-20090202: task kmemleak:763 blocked for more than 120seconds Catalin Marinas
2009-02-03 12:31 ` next-20090202: task kmemleak:763 blocked for more than 120 seconds Catalin Marinas
2009-02-03 11:57 ` Alexander Beregalov
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=a4423d670902020327x61a1d9dehb1642b25ec7f82f1@mail.gmail.com \
--to=a.beregalov@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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
all inboxes | Powered by JetHome®