That message is caused by tasks exiting with a nonzero preempt_count.
The preempt_count is basically a count of the number of spinlocks held,
so it should always be zero when a task exits. Since it is positive,
you don't have anything to worry about wrt "stability" but the system
may not be preempting at all, which would make the preempt-kernel patch
worthless.
I talked to Steve Lord and Eric Sandeen at SGI and they believe they
know the cause of the problem. Basically, XFS destroys some data
structures and doesn't unlock the associated lock, but just forgets
about it. This is not good for kernel preemption.
They think the newest XFS in CVS does not do this anymore, but it still
may in some places. Can you give it a try and let me know if you still
see the messages? Especially with the same regularity and value.
http://oss.sgi.com/projects/xfs/cvs_download.html
Thanks,
Robert Love
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/