> If this is a memory ordering problem (and that seems quite plausible) > then a liberal sprinkling of "ia64_mf()" calls throughout the spinlock > routines would probably make it go away. I think I take this back ... if it were a memory ordering problem, then it could show up any time - not just at wrap-around. -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html