Windows NT May Hang With DEC Pathworks Installed (132694)
The information in this article applies to:
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
This article was previously published under Q132694 SYMPTOMS
Windows NT servers with two or more CPUs and DEC Pathworks for Windows
NT, versions 4.1 or 4.1b installed, stop responding (hang). No STOP message
appears, and there no hardware or software errors are logged.
CAUSE
This problem occurs because DEC Pathworks for Windows NT acquires and
releases spinlocks in reverse order in the NetBIOS over DECNet code. This
causes the computer to hang when one CPU tries to acquire a lock still
held by another CPU. The following is a simplified description of how this
condition occurs:
- On Processor 0, a DEC Pathworks for Windows NT routine acquires Lock A
spinlock, and then, while holding Lock A, tries to acquire Lock B spinlock.
- On Processor 1, a DEC Pathworks for Windows NT routine acquires Lock B
spinlock, and then, while holding Lock B, tries to acquire Lock A spinlock.
STATUS
DEC Pathworks is currently testing a fix for this problem.
The products included here are manufactured by vendors independent of
Microsoft; we make no warranty, implied or otherwise, regarding these
products' performance or reliability.
| Modification Type: | Major | Last Reviewed: | 10/23/2003 |
|---|
| Keywords: | kb3rdparty kbnetwork KB132694 |
|---|
|