> Trond Myklebust wrote:
>>
>> ... I have the same problem on my setup. To me, it looks like
>> the loop in spawn_ksoftirqd() is suffering from some sort of
>> atomicity problem.
> Does a `set_current_state(TASK_RUNNING);' in spawn_ksoftirqd()
> fix it? If so we have a rogue initcall...
Nope. The same thing happens as before.
A couple of debugging statements show that ksoftirqd_CPU0 gets created
fine, and that ksoftirqd_task(0) is indeed getting set correctly
before we loop in spawn_ksoftirqd().
After this the second call to kernel_thread() succeeds, but
ksoftirqd() itself never gets called before the hang occurs.
Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/