> I could not image a scenario that lead to 3 different values on the > same variable mutex->__data.__lock seen in 3 positions. Is there a common pattern to these 3 different values? - Do they look like memory bit-flips (if yes, then misbehaviour / misconfigured HW?) - Do they always contain the same pattern (if yes, then buffer-overflow? Add "guard-bytes" around the struct and attempt to reproduce the behaviour) Slightly tangential. Have you checked for any unpatched HW errata in CPU, cache controller, memory controller that can cause writes posted by the CPU to be lost in some rare scenarios? regards CVS
