Hi Paul, Could you give more explanation on your previous reply? Do you mean that I should release all locks before re-scheduling timer in the timeout handler?
[b]"Don't take a lock within your timeout function that's held across schedulng it. That can lead to precisely the sort of cycle you're experiencing...."[/b] In my 1 second timer handler, after job is done, it calls timeout( ) to re-schedule itself, so the qla_timer( ) can be called again at next second, but I did not release mutex before calling timeout( ). Is this the true origin of the deadlock? Tom This message posted from opensolaris.org _______________________________________________ networking-discuss mailing list [email protected]
