"Martin J. Bligh" <email@example.com> wrote:
> OK, did that. your patches + debug up the wazoo. Bugger all output,
> and a hang that looks similar, but the culprit is hiding even more,
> as far as I can't see ;-(
yes, nobody's spinning on the /proc lock any more.
I don't understand why all the tasks in set_cpus_allowed() are showing up
as being in " R " state. Possibly the wait_for_completion() in there is
stack gunk and they're really spinning on the runqueue lock?
You haven't tried disabling sched_migrate_task() yet?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:27 EST