>> OK, well backing out dcache_lock-vs-tasklist_lock-take-3.patch does
>> indeed seem to fix the problem. It's done 5.5 whole cycles now, and
>> still going strong.
>
> Well that patch fixed a real bug. It abviously added or exposed another
> one though.
Yeah, wasn't suggesting actually removing it - was just trying to
narrow it down some more.
> I continue to wonder if that task_struct is scrogged. There seem to be no
> other processes holding the lock.
>
> Might be interesting to give the below patch a run with memory debug
> enabled.
>
> Also spinlock debugging enabled. It would be nice to run with preempt and
> sleep-in-spinlock debugging enabled too, but I think preempt is broken on
> NUMA?
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 ;-(
File too big. zipped, attatched. sorry. I'll make a better attempt at it
tommorow, and I'll try to put some effort into it for once ;-)
M.
-
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/
This archive was generated by hypermail 2b29 : Sun Jun 15 2003 - 22:00:27 EST