On 09/19/06 18:46, Chad Mynhier wrote:
> As for kernel stacks waiting for locks: Here are the functions the > threads are sitting in: > > 1 disp_getwork+0xa4() > 1 intr_thread+0xa4() > 2 cv_wait_sig+0x180() > 3 cv_wait_sig_swap+0x194() > 1 do_scrub_ecache_line+0x8c() > 1 sema_p+0x138() > 1 current_thread+0x44() > 1 cpu_pause+0x7c() > 2 cv_timedwait+0x98() > 1 putnext+0x1cc() > 1 prom_rtt() > 1 prom_enter_mon+0x38() > 63 cv_wait+0x38() The lack of console response you mention elsewhere *may* be explained by that putnext() thread. You may simply have caught a perfectly healthy thread midway through putnext(), but if it is blocked in there and has been for a while that could explain some lack of response. > Is there some way to > look at t_disp_time on a Solaris 8 server other than dumping memory > starting at the kthread_t pointer and knowing the offset within the > structure? Does ::print kthread_t t_disp_time not work on Solaris 8? My memory of that release is fading. Cheers Gavin
