John David Anglin wrote: >>> - mtsp(space, 3); >>> + load_context(space); >> I came to the similar conclusion and tried exactly this patch earlier >> today. It didn't fixed the problem (although I had the feeling that the >> bug didn't appeared as often then). > > Ok, then maybe load_context needs to be atomic. This is a bit tricky > because we may have to ensure that no tlb misses are triggered (relied > upon translation) during the update. I'll try tomorrow. What makes me wondering: a) the bug always triggers AFAICS with applications which uses threads (for the ruby1.9 problem it's always the miniruby process). Maybe the problem happens to something being wrong in the signal handler with threadened applications, e.g. arch/parisc/kernel/signal.c:648 ? b) maybe stupid question: In the case it's a generic processor problem, would e.g. changing the kernel to use sr4 instead of sr3 for userspace-accesses change something? What does HPUX uses? At least one could try...? Helge -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
