On Wed, 2011-04-27 at 12:50 -0500, James Bottomley wrote: > To test the theory, Chris asked me to try with data=ordered. > Unfortunately, the deadlock still shows up. This is what I get. As another data point: I'm trying the same kernel with CONFIG_PREEMPT enabled. This time the deadlock doesn't happen. Instead, kswapd0 gets pegged at 99% CPU for much of the untar, but it does eventually complete. James -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
