site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com <http://developer.apple.com/documentation/DeviceDrivers/Conceptual/WritingDeviceDriver/DebuggingDrivers/chapter_8_section_4.html> S+E -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... At 22:27 +0200 10/9/07, Phil Regnauld wrote: Any idea on how to debug this ? My guess is that you've run into some sort of kernel bug that's causing it to leave a dangling mutex. To debug this, you need to know what mutex is casing the problem. And the best way do that, at least on currently released systems, is to fire up the kernel debugger and get a "showallstacks" log. This will let you figure out which locks the various threads in question are blocked waiting for. Also, if you have access to Leopard seeds, you should try to reproduce the problem on Leopard. This email sent to site_archiver@lists.apple.com