Announcement

Collapse
No announcement yet.

COM port overruns

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • COM port overruns

    Hello,

    We have are having a problem in one of our configs where the serial ports fail with an overrun error. The failure only occurs with Windows server 2003 standard edition, and can take anywhere from several minutes to several hour to manifest themselves. Windows XP and 2000 do not get the error. We've tried changing the FIFO settings, as well as lowering the baud rate, duty cycle, and timeout settings but the problem persists. We've also tried doing all the usual things such as updating all the drivers, etc. but have had no success. The CD-ROM drive is in DMA mode, and the graphics card has acceleration enabled. The MB is a Commell FS-97GME http://www.commell.com.tw/Product/SBC/FS-97C.HTM
    with a core 2 duo T7400 and 1GB of ram. We have a VIA VT6421A chipset mini-PCI raid card running in RAID1 mode. We are using BIT version 5.3 (1026). There is no other hardware in the system. If we just run the serial port tests, they pass. A failure can be forced to happen sooner if we plug in a USB thumb drive or attemt to copy files from the passmark CD-ROM disc during testing. Is there something about Windows 2003 server that might be causing these types of errors? Or, perhaps there may be a workaround with BurninTest?

    Thanks!

    Last edited by Comark Corp; 09-03-2008, 12:45 PM. Reason: clarification
    Jay W.
    Diagnostic Engineer
    Comark Corporation
    93 West St.
    Medfield, MA 02052
    http://www.comarkcorp.com

  • #2
    Jay,

    You have already tried what I would normally suggest and I am not aware of any W2003 specific issues.

    I would first assume that it is related to the systems inability for the CPU to service the COM port interrupts fast enough, maybe due to blocking by the other devices. Hence, I would check the IRQ settings (levels, sharing and conflicts) and compare them with another OS that does not have this behavior.

    You might try uninstalling and re-installing the COM port driver just for the sake of trying it.

    I would also ask the Motherboard vendor if they are aware of such behavior.

    Regards,
    Ian

    Comment


    • #3
      Ugh, there was one driver I overlooked. Turns out that it was the Via RAID driver. Updating to version 5.80a solved the problem.

      Thanks.
      Jay W.
      Diagnostic Engineer
      Comark Corporation
      93 West St.
      Medfield, MA 02052
      http://www.comarkcorp.com

      Comment


      • #4
        Jay,

        Thanks for the feedback on the solution. Always appreciated.

        Regards,
        Ian

        Comment

        Working...
        X