From: Tejun Heo <tj@kernel.org>
To: CAI Qian <caiqian@redhat.com>
Cc: kexec <kexec@lists.infradead.org>,
linux-next@vger.kernel.org, torvalds@linux-foundation.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: kdump regression compared to v2.6.35
Date: Mon, 30 Aug 2010 16:55:49 +0200 [thread overview]
Message-ID: <4C7BC675.8050506@kernel.org> (raw)
In-Reply-To: <1706089082.1537331283179884183.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
On 08/30/2010 04:51 PM, CAI Qian wrote:
> kintegrityd R running task 0 13 2 0x00000008
> ffffffffffffff10 ffffffff81078e25 0000000000000010 0000000000000206
> ffff88046dcf1e40 0000000000000018 ffff88046dc9a440 ffff88046dc9a440
> ffff88088e231f00 ffff88088e239300 ffff88046dcf1ee0 ffffffff810796e8
> Call Trace:
> [<ffffffff81078e25>] ? worker_maybe_bind_and_lock+0x55/0xf0
> [<ffffffff810796e8>] ? rescuer_thread+0x108/0x1d0
> [<ffffffff810795e0>] ? rescuer_thread+0x0/0x1d0
> [<ffffffff810795e0>] ? rescuer_thread+0x0/0x1d0
> [<ffffffff8107fc06>] ? kthread+0x96/0xa0
> [<ffffffff8100be84>] ? kernel_thread_helper+0x4/0x10
> [<ffffffff8107fb70>] ? kthread+0x0/0xa0
> [<ffffffff8100be80>] ? kernel_thread_helper+0x0/0x10
...
> runnable tasks:
> task PID tree-key switches prio exec-runtime sum-exec sum-sleep
> ----------------------------------------------------------------------------------------------------------
> swapper 1 296.512617 23 120 296.512617 282.090606 0.046441 /
> sync_supers 11 293.512617 2 120 293.512617 0.002502 5354.887736 /
> R kintegrityd 13 2382.377879 1 100 2382.377879 180846.751167 0.001076 /
Looks like kintegrityd went bonkers. Maybe it has some busy wait
which doesn't quite work well with how cmwq schedules works. I'll
look into it. Can you please attach your .config?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-08-30 14:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <123671462.1479561283081998014.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-29 11:41 ` kdump regression compared to v2.6.35 caiqian
2010-08-29 11:56 ` CAI Qian
2010-08-29 11:52 ` Tejun Heo
2010-08-29 12:03 ` CAI Qian
2010-08-29 12:36 ` Tejun Heo
2010-08-30 3:42 ` CAI Qian
2010-08-30 8:29 ` Tejun Heo
2010-08-30 10:24 ` CAI Qian
2010-08-30 12:50 ` Tejun Heo
2010-08-30 14:02 ` CAI Qian
2010-08-30 14:21 ` Tejun Heo
2010-08-30 14:47 ` CAI Qian
2010-08-30 14:51 ` CAI Qian
2010-08-30 14:55 ` Tejun Heo [this message]
[not found] <71887879.1606161283215975799.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-31 0:53 ` caiqian
2010-08-31 9:22 ` Tejun Heo
[not found] <373987879.1541191283181021800.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-30 15:10 ` caiqian
2010-08-30 16:38 ` Tejun Heo
2010-08-30 17:31 ` Tejun Heo
[not found] <2142316909.1477341283065016062.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-29 7:01 ` caiqian
2010-08-29 8:57 ` Tejun Heo
2010-08-29 11:24 ` CAI Qian
2010-08-29 11:21 ` Tejun Heo
[not found] <229468156.1475641283020469212.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-28 18:36 ` caiqian
[not found] <2082161789.1474781283008521258.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2010-08-28 15:19 ` caiqian
2010-08-27 12:35 CAI Qian
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=4C7BC675.8050506@kernel.org \
--to=tj@kernel.org \
--cc=caiqian@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).