Deadlock in TCP/IP on Multiprocessor ComputersLast reviewed: July 23, 1997Article ID: Q171181 |
The information in this article applies to:
SYMPTOMSUnder stressful conditions in Windows NT 4.0, TCP/IP may cause a deadlock on a multiprocessor computer, putting the computer into a non-usable state.
CAUSEThis problem happens because the thread on one processor has already allocated a tcb_lock and then the calling function tries to lock the TCBTableLock. Then, on the second processor the thread has a lock on the TCBTableLock and the calling function tries to get a tcb_lock.
STATUSMicrosoft has confirmed this to be a problem in Windows NT version 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information. |
Keywords : kbbug4.00 kbfix4.00 NTSrvWkst ntstop nttcp kbbuglist kbfixlist
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |