I'm not sure if this is related, but running trinity here, I noticed it was stuck at 100% system time on every CPU. perf report tells me we are spending all of our time in spin_lock under the sync system call.
I think it's coming from contention in the bdi_queue_work() call from inside sync_inodes_sb, which is spin_lock_bh(). I wonder if we're just spinning so hard on this one bh lock that we're starving the watchdog? Dave, do you have spinlock debugging on? -chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
