Here it is:
kd> !locks
**** DUMP OF ALL RESOURCE OBJECTS ****
KD: Scanning for held
locks…
Resource @ 0x85629564 Shared 2 owning threads
Contention Count = 16
Threads: 86ed5798-01<*> 95e58878-01<*>
Resource @ 0x8562959c Shared 1 owning threads
Threads: 86ed5a70-01<*>
KD: Scanning for held locks.
Resource @ 0x87fb296c Shared 1 owning threads
Contention Count = 85
Threads: 86ed5020-01<*>
KD: Scanning for held locks.
Resource @ 0x8ead488c Shared 17 owning threads
Contention Count = 9415
NumberOfSharedWaiters = 12
NumberOfExclusiveWaiters = 12
Threads: 86ed5d48-01<*> 878bed48-01<*> 91bf88f8-01<*> 86ed6798-01<*>
95da1020-01<*> 919fed48-01<*> 86ed8020-01<*> 86ed6d48-01<*>
86ed6a70-01<*> 95da4d48-01<*> 91b7daf8-01<*> 86ed64c0-01<*>
95da25c0-01<*> 8eaec570-01<*> 91893c78-01<*> 95c02918-01<*>
91a88810-01<*> 91a3fd48-01 86ed5798-01 86ed5a70-01
86ed5020-01 86ed54c0-01 8e82b758-01 87804d48-01
87fc83a8-01 95dfb8a8-01 878884d8-01 86ed9328-01
8eb2dd48-01
Threads Waiting On Exclusive Access:
91babd48 87981430 87fc3ca0 877f5d48
8793b718 95c03918 87942508 95db3030
95e3cd48 8e938d48 878af730 8e88ab40
KD: Scanning for held
locks…
Resource @ 0x91b8664c Shared 1 owning threads
Contention Count = 4
NumberOfExclusiveWaiters = 1
Threads: 86ed54c0-01<*>
Threads Waiting On Exclusive Access:
95e58878
KD: Scanning for held
locks…
Resource @ 0x95c0708c Shared 1 owning threads
Threads: 86ed5d48-01<*>
KD: Scanning for held locks…
Resource @ 0x87f03d90 Exclusively owned
Threads: 95db3030-01<*>
KD: Scanning for held locks.
Resource @ 0x95d8b500 Exclusively owned
Contention Count = 2
NumberOfExclusiveWaiters = 2
Threads: 95db3030-01<*>
Threads Waiting On Exclusive Access:
8e947a70 8792ad48
KD: Scanning for held
locks…
Resource @ 0x8782fa88 Exclusively owned
Threads: 86ed5020-01<*>
Resource @ 0x87840728 Exclusively owned
Threads: 86ed54c0-01<*>
KD: Scanning for held locks.
Resource @ 0x878eeca0 Exclusively owned
Threads: 86ed5a70-01<*>
Resource @ 0x80df993c Exclusively owned
Threads: 86ed5798-01<*>
KD: Scanning for held locks.
14373 total locks, 12 locks currently held
On Thu, Mar 31, 2011 at 7:36 PM, Scott Noone wrote:
> I want to see all threads on the system(information grouped as in
>> !exqueue).
>>
>
> !exqueue just shows the system worker queue threads. If you want to see all
> threads in the system that is:
>
> !process 0 7
>
> You can also use:
>
> !stacks
>
> Or:
>
> !stacks 2
>
> If you want a clean summary view.
>
>
> How can I see which thread has a lock? With !locks I can see waiting
>> threads.
>>
>
> !locks shows information about all of the ERESOURCEs in the system and the
> output includes both threads waiting for the lock and the threads that own
> the lock. In the output, an asterisk next to the thread address indicates
> that the thread owns the lock, if there isn’t an asterisk the thread is
> waiting for the lock.
>
> Note however that !locks doesn’t show ALL types of locks in the system,
> just ERESOURCEs. If you post the output of !locks (without the -v) I can
> tell you if the hang is related to ERESOURCEs at all.
>
>
> -scott
>
> –
> Scott Noone
> Consulting Associate and Chief System Problem Analyst
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
> “Neagoe Gabriel” wrote in message news:xxxxx@windbg.
> …
>
> !threads works only with sos extension for managed threads. (my mistake) 
>
> I want to see all threads on the system(information grouped as in
> !exqueue).
>
> I`m using !locks -v. All threads are waiting for some synchronization
> objects, including worker threads.
>
> How can I see which thread has a lock? With !locks I can see waiting
> threads.
>
> Only the mouse is working, everything else is in “hang state” 
-new
> windows state.
>
> Thank you,
>
> kd> !exqueue
> Dumping ExWorkerQueue: 82C00F00
>
> Critical WorkQueue( current = 0 maximum = 1 )
> THREAD 86ed5020 Cid 0004.0018 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 86ed5d48 Cid 0004.001c Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 86ed5a70 Cid 0004.0020 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 86ed5798 Cid 0004.0024 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 86ed54c0 Cid 0004.0028 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 878e9778 Cid 0004.089c Teb: 00000000 Win32Thread: 00000000 WAIT
>
> Delayed WorkQueue( current = 0 maximum = 1 )
> THREAD 86ed6020 Cid 0004.002c Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 86ed6d48 Cid 0004.0030 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 86ed6a70 Cid 0004.0034 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 86ed6798 Cid 0004.0038 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 86ed64c0 Cid 0004.003c Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 86ed8020 Cid 0004.0040 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 86ed8d48 Cid 0004.0044 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 91a88810 Cid 0004.020c Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 87f09b50 Cid 0004.021c Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 91bf88f8 Cid 0004.0220 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 91a3fd48 Cid 0004.0234 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 919fed48 Cid 0004.0248 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 95c02918 Cid 0004.026c Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 95c03918 Cid 0004.0274 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 91893c78 Cid 0004.0368 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 91b7daf8 Cid 0004.0370 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 8eaec570 Cid 0004.0374 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 95da1020 Cid 0004.03c8 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 95da25c0 Cid 0004.03d8 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 95da4d48 Cid 0004.03e4 Teb: 00000000 Win32Thread: 00000000 WAIT
> THREAD 878bed48 Cid 0004.0a5c Teb: 00000000 Win32Thread: 00000000 WAIT
>
> HyperCritical WorkQueue( current = 0 maximum = 1 )
> THREAD 86ed8a70 Cid 0004.0048 Teb: 00000000 Win32Thread: 00000000 WAIT
>
>
>
> On Thu, Mar 31, 2011 at 5:49 PM, Scott Noone wrote:
> I never use this command so I hadn’t realized it was broken…Looks like
> this hasn’t been updated to reflect changes to the ERESOURCE structure:
>
> 0: kd> .show_sym_failures /s /t
> Show symbol lookup failures: yes
> Show type lookup failures: yes
> 0: kd> !analyze -hang
>
>***************************************************************************
> * *
> * Bugcheck Analysis *
> * *
>
> *******************************************************************************
>
> Use !analyze -v to get detailed debugging information.
>
> BugCheck D5, {a56aee00, 0, 84e68eea, 0}
>
>
> Scanning for threads blocked on locks …
> type lookup ‘nt!_ERESOURCE’ failure, field ‘OwnerThreads’ not found.
> Cannot get _ERESOURCE type
>
> And it looks like that field of the ERESOURCE disappeared as of Vista or
> so.
>
> If you believe that you have an ERESOURCE deadlock you can use !locks -v
> instead, which has been updated to reflect the new ERESOURCE structure.
>
> As for !threads, that’s a new one to me. It appears to be undocumented and
> not work, so I’d stay away from that What info were you trying to get
> from that command?
>
> -scott
>
> –
> Scott Noone
> Consulting Associate and Chief System Problem Analyst
> OSR Open Systems Resources, Inc.
> http://www.osronline.com
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
>
> —
> WINDBG is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>