All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: purpose of WARN_ON in kernel/workqueue.c:worker_enter_idle()
Date: Thu, 21 Jul 2011 13:13:58 +0200	[thread overview]
Message-ID: <20110721111357.GA17725@aepfle.de> (raw)
In-Reply-To: <20110721073828.GY3455@htj.dyndns.org>

On Thu, Jul 21, Tejun Heo wrote:

> On Mon, Jul 18, 2011 at 06:15:18PM +0200, Olaf Hering wrote:
> > whats the purpose of "WARNING: at kernel/workqueue.c:1217 worker_enter_idle()"?
> > I put some debug in the function, cpu is always 1, nr_workers is either
> > 2 or 3, current_work is NULL.
> > Is there some real bug lurking thats worth to track down?
> 
> Oh yeah, that means workqueue worker accounting went out of sync which
> may lead to workqueue hang which usually means dead system.  Can you
> please print out what goes out of sync?  ie. print gcwq->nr_workers,
> nr_idle and get_gcwq_nr_running(gcwq->cpu)?

Whit my silly debug patch below I got this output, which is also in the
posted dmesg output:

[   43.376143] worker_enter_idle: c 1 3           (null)
[  821.936288] worker_enter_idle: c 1 2           (null)
[ 1068.816239] worker_enter_idle: c 1 2           (null)
[ 1167.136160] worker_enter_idle: c 1 3           (null)
[ 1220.896745] worker_enter_idle: c 1 3           (null)
[ 1280.176207] worker_enter_idle: c 1 3           (null)
[ 1304.820106] worker_enter_idle: c 1 3           (null)
[ 2091.140542] worker_enter_idle: c 1 3           (null)
[ 2275.856762] worker_enter_idle: c 1 3           (null)
[ 2382.976445] worker_enter_idle: c 1 2           (null)
[ 2387.696067] worker_enter_idle: c 1 2           (null)


> Also, it would be helpful to enable and record workqueue events (grep
> workqueue /sys/kernel/debug/tracing/available_events).  It should
> allow us what led to the condition.

I will enable these options and report back.


---
 kernel/workqueue.c |   16 ++++++++++++++++
 1 file changed, 16 insertions(+)

Index: linux-2.6/kernel/workqueue.c
===================================================================
--- linux-2.6.orig/kernel/workqueue.c
+++ linux-2.6/kernel/workqueue.c
@@ -1192,6 +1192,7 @@ EXPORT_SYMBOL_GPL(queue_delayed_work_on)
 static void worker_enter_idle(struct worker *worker)
 {
 	struct global_cwq *gcwq = worker->gcwq;
+	int cpu;
 
 	BUG_ON(worker->flags & WORKER_IDLE);
 	BUG_ON(!list_empty(&worker->entry) &&
@@ -1213,8 +1214,23 @@ static void worker_enter_idle(struct wor
 		wake_up_all(&gcwq->trustee_wait);
 
 	/* sanity check nr_running */
+#if 0
 	WARN_ON_ONCE(gcwq->nr_workers == gcwq->nr_idle &&
 		     atomic_read(get_gcwq_nr_running(gcwq->cpu)));
+#else
+	cpu = atomic_read(get_gcwq_nr_running(gcwq->cpu));
+	if (gcwq->nr_workers == gcwq->nr_idle && cpu) {
+		void *func;
+		struct work_struct *cw = worker->current_work;
+		func = cw ? cw->func : NULL;
+		printk("%s: c %x %x %p", __func__, cpu, gcwq->nr_workers, func);
+		if (func)
+			print_symbol("%s\n",(unsigned long)func);
+		else
+			printk("\n");
+		WARN_ON_ONCE(1);
+	}
+#endif
 }
 
 /**

      reply	other threads:[~2011-07-21 11:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 16:15 purpose of WARN_ON in kernel/workqueue.c:worker_enter_idle() Olaf Hering
2011-07-21  7:38 ` Tejun Heo
2011-07-21 11:13   ` Olaf Hering [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=20110721111357.GA17725@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.