BUG: Sharing IRQ with COM1 Causes System to RebootLast reviewed: April 12, 1995Article ID: Q107697 |
The information in this article applies to:
SYMPTOMSWhen COM1 and another communications (COM) port are active and share the same IRQ using the Windows 3.1 COMM.DRV, the system hangs or reboots.
CAUSEWhen two or more COM ports share an IRQ, COMM.DRV creates a linked list of these ports using the NextDEB field of the ComDEB structure that the COMM.DRV maintains for each port. When an interrupt occurs that has been hooked by COMM.DRV, the COMM.DRV interrupt handler walks the list of COM ports that are sharing the IRQ. For each port in the list, the COMM.DRV interrupt handler checks for and services any interrupts that are pending from the port. The COMM.DRV interrupt handler knows when it has reached the end of the list of ports that are sharing an IRQ when it reaches a ComDEB structure in which the NextDEB field is zero. If another port is sharing an IRQ with COM1 and it is opened after COM1, the NextDEB field in the ComDEB structure for the other port will point to the ComDEB structure for COM1. However, in the COMM.DRV included with Windows 3.1, the offset to COM1's ComDEB structure happens to be zero. The list of COM ports sharing an IRQ with COM1 will appear to end with the port on the list before COM1. This will cause the COMM.DRV interrupt handler to skip the interrupt servicing for COM1, and its interrupt will never be cleared. If the interrupt is level-triggered and it is not cleared, the COMM.DRV interrupt handler will be immediately called again as soon as interrupts are reenabled. This will cause the machine to hang or reboot.
RESOLUTIONThe following are resolutions:
STATUSThis bug is fixed in version 3.11 of Windows for Workgroups.
|
Additional reference words: 3.10 buglist3.10
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |