Hi Dean, On Thu, Jul 09, 2015, Dean Jenkins wrote: > Please can you point to me to some details on how to use the l2cap-tester > tool so that I can attempt to look into this issue. First of all, please avoid top-posting on this list. Regarding l2cap-tester, there's really nothing special needed except for the hci_vhci module and running the tool as root. However, as I pointed out what was causing this you shouldn't even need l2cap-tester, but just create an L2CAP socket with any tool. The more important thing is to have the right config options in the kernel. I've got at least the following: CONFIG_LOCKDEP_SUPPORT=y CONFIG_DEBUG_SPINLOCK=y CONFIG_DEBUG_LOCK_ALLOC=y CONFIG_PROVE_LOCKING=y CONFIG_LOCKDEP=y CONFIG_DEBUG_MUTEXES=y I'd guess only the "LOCKDEP" ones are really needed, but not completely sure about it. I was kind of half expecting you to already be familiar with l2cap-tester since you were submitting patches to L2CAP, but I guess it's never too late :) Either way it'd be good if you could also look into adding new test cases to the tool that specifically exercise the code paths that you were fixing. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
