Hi,<br><br>Thanks for the reply.<br>So the BUG_ON means that it is known prior that a could raise in this codelines.<br>Correct me if am wrong. In that case, there would a patch to fix this, guessing.<br><br>--Sri<br><br><div class="gmail_quote">
On Wed, May 25, 2011 at 11:15 PM, Mulyadi Santosa <span dir="ltr"><<a href="mailto:mulyadi.santosa@gmail.com">mulyadi.santosa@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi...<br>
<div class="im"><br>
On Wed, May 25, 2011 at 16:32, sri <<a href="mailto:bskmohan@gmail.com">bskmohan@gmail.com</a>> wrote:<br>
> kernel BUG at kernel/workqueue.c:113!<br>
<br>
</div>from <a href="http://lxr.linux.no/#linux+v2.6.18/kernel/workqueue.c" target="_blank">http://lxr.linux.no/#linux+v2.6.18/kernel/workqueue.c</a>, lines around 113:<br>
int fastcall queue_work(struct workqueue_struct *wq, struct work_struct *work)<br>
107{<br>
108 int ret = 0, cpu = get_cpu();<br>
109<br>
110 if (!test_and_set_bit(0, &work->pending)) {<br>
111 if (unlikely(is_single_threaded(wq)))<br>
112 cpu = singlethread_cpu;<br>
113 BUG_ON(!list_empty(&work->entry));<br>
114 __queue_work(per_cpu_ptr(wq->cpu_wq, cpu), work);<br>
115 ret = 1;<br>
116 }<br>
117 put_cpu();<br>
118 return ret;<br>
119}<br>
<br>
So, if I interpret it correctly, that BUG_ON line means that if<br>
work->entry is not empty or null, then it is a bug.<br>
<br>
Not sure what causes that, but it could be simply due to failure of<br>
"work" initialization (as work_struct) somewhere...<br>
<font color="#888888"><br>
<br>
--<br>
regards,<br>
<br>
Mulyadi Santosa<br>
Freelance Linux trainer and consultant<br>
<br>
blog: <a href="http://the-hydra.blogspot.com" target="_blank">the-hydra.blogspot.com</a><br>
training: <a href="http://mulyaditraining.blogspot.com" target="_blank">mulyaditraining.blogspot.com</a><br>
</font></blockquote></div><br><br clear="all"><br>-- <br>--<br> Krishna Mohan B<br>