On Tuesday 14 April 2009 08:39:42 Avi Kivity wrote:
Nothing goes away. This happens without CONFIG_PROVE_LOCKING active in the kernel. Given
that one CPU is running at 100% I suspect that a spinlock is stuck...
Ed
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html