Bill Huey (hui) wrote: > > Patch here: > > http://mmlinux.sourceforge.net/public/patch-2.6.20-rc2-rt2.2.lock_stat.p atch > > bill
This version is much better and ran stablely. If I'm reading the output correctly, the locks are listed by their initialization point (function, file and line # that a lock is initialized). That's good information to identify the lock. However, it will be more useful if there is information about where the locking was initiated from and who was trying to obtain the lock. Tim - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
