From: Tejun Heo <tj@kernel.org>
To: Tony Luck <tony.luck@gmail.com>
Cc: Minchan Kim <minchan.kim@gmail.com>,
Jiri Slaby <jirislaby@gmail.com>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
mm-commits@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: WARNING: at kernel/workqueue.c [was: mmotm 2011-01-06-15-41 uploaded]
Date: Tue, 11 Jan 2011 15:32:44 +0100 [thread overview]
Message-ID: <20110111143244.GC30607@htj.dyndns.org> (raw)
In-Reply-To: <AANLkTimeUN9m-roDmsfaMaiD4wZw1wETYsf+dONjpmyj@mail.gmail.com>
On Mon, Jan 10, 2011 at 03:36:09PM -0800, Tony Luck wrote:
> > Here it is, too.
> > mmotm-01-06
>
> Also in today's linux-next (tag: next-20110110) on ia64:
>
>
> ------------[ cut here ]------------
> WARNING: at kernel/workqueue.c:1202 worker_enter_idle+0x3f0/0x4a0()
> Hardware name: server rx2620
> Modules linked in:
>
> Call Trace:
> [<a000000100014cb0>] show_stack+0x50/0xa0
> sp=e0000040600d7c30 bsp=e0000040600d0dd0
> [<a000000100bcaa20>] dump_stack+0x30/0x50
> sp=e0000040600d7e00 bsp=e0000040600d0db8
> [<a000000100082260>] warn_slowpath_common+0xc0/0x100
> sp=e0000040600d7e00 bsp=e0000040600d0d78
> [<a0000001000822e0>] warn_slowpath_null+0x40/0x60
> sp=e0000040600d7e00 bsp=e0000040600d0d50
> [<a0000001000b0830>] worker_enter_idle+0x3f0/0x4a0
> sp=e0000040600d7e00 bsp=e0000040600d0d28
> [<a0000001000b2c80>] worker_thread+0x8c0/0x980
> sp=e0000040600d7e00 bsp=e0000040600d0c28
> [<a0000001000c08c0>] kthread+0x120/0x160
> sp=e0000040600d7e00 bsp=e0000040600d0be8
> [<a000000100012ef0>] kernel_thread_helper+0x30/0x60
> sp=e0000040600d7e30 bsp=e0000040600d0bc0
> [<a00000010000a0c0>] start_kernel_thread+0x20/0x40
> sp=e0000040600d7e30 bsp=e0000040600d0bc0
> ---[ end trace 7e2fb881ec0622f8 ]---
Ah, of course, it's commit 21ec12364bb78b72ad36b94269c64b3ee31b038f
(workqueue: remove noop condition check in worker_clr_flags()). The
condition it removes is not a noop. Reverting it.
Thank you.
--
tejun
next prev parent reply other threads:[~2011-01-11 14:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 23:41 mmotm 2011-01-06-15-41 uploaded akpm
2011-01-07 17:18 ` mmotm 2011-01-06-15-41 uploaded (apple_bl) Randy Dunlap
2011-01-07 23:42 ` mmotm 2011-01-06-15-41 uploaded Stephen Rothwell
2011-01-10 18:04 ` [PATCH -mm] fix powerpc/sparc build Andrea Arcangeli
2011-01-10 10:19 ` WARNING: at kernel/workqueue.c [was: mmotm 2011-01-06-15-41 uploaded] Jiri Slaby
2011-01-10 16:31 ` Minchan Kim
2011-01-10 23:36 ` Tony Luck
2011-01-11 14:32 ` Tejun Heo [this message]
2011-01-12 1:34 ` Hillf Danton
2011-01-12 9:52 ` Tejun Heo
2011-01-10 14:37 ` qemu-kvm defunct due to THP " Jiri Slaby
2011-01-10 15:01 ` Andrea Arcangeli
2011-01-10 21:02 ` Jiri Slaby
2011-01-12 15:02 ` Andrea Arcangeli
2011-01-11 1:01 ` bnx2 card cannot be detected (WAS Re: mmotm 2011-01-06-15-41 uploaded) CAI Qian
2011-01-11 4:10 ` CAI Qian
2011-01-11 8:00 ` CAI Qian
2011-01-13 9:52 ` WARNING: at fs/dcache.c:1359 d_set_d_op [was: mmotm 2011-01-06-15-41 uploaded] Jiri Slaby
2011-01-13 9:57 ` Jiri Slaby
2011-01-13 10:54 ` Nick Piggin
2011-01-13 15:33 ` Valdis.Kletnieks
2011-01-13 15:40 ` Jiri Slaby
2011-01-14 8:20 ` [autofs] " Ian Kent
2011-01-16 11:32 ` Jiri Slaby
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=20110111143244.GC30607@htj.dyndns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=minchan.kim@gmail.com \
--cc=mm-commits@vger.kernel.org \
--cc=tony.luck@gmail.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
all inboxes | Powered by JetHome®