COM port errors "No operations reported in timeout period"

[Comark Corp]

Hello,

Running the latest version of BIT I am getting a "No operations reported in timeout period" on random COM ports. It can happen on any of the 6 COM ports on this board. If I try to re-start BIT, it will report that the just failed COM port is in use. I have to re-boot the machine in order to test again.

System specifics:

IBT MI802N 1.6GHz Atom based motherboard.
Windows 7 embedded pro x32 SP1
4GB memory.

Any ideas come to mind?

Thanks.

[David (PassMark)]

Might be that the CPU is too slow, or overloaded. Or it might be the COM port device driver software has crashed.

[Comark Corp]

Might be that the CPU is too slow, or overloaded. Or it might be the COM port device driver software has crashed.

Thanks for the answer.

I tried just running the COM ports themselves at 100% duty cycle and it failed in 32 minutes.
Previously, I was running all the tests (2D, 3D, CPU, memory, disk drive, and Passmark CD) at 50%. The failure would take quite a while to manifest itself; anywhere between 15 to 25 hours or so. The COM port driver is the built-in Microsoft one. BIT version 5.3 (1036) also fails. I think I'll try running under XP and see if it fails as well. If it does, I think that would rule out a default driver issue.

[Comark Corp]

Thanks for the answer.

I tried just running the COM ports themselves at 100% duty cycle and it failed in 32 minutes.
Previously, I was running all the tests (2D, 3D, CPU, memory, disk drive, and Passmark CD) at 50%. The failure would take quite a while to manifest itself; anywhere between 15 to 25 hours or so. The COM port driver is the built-in Microsoft one. BIT version 5.3 (1036) also fails. I think I'll try running under XP and see if it fails as well. If it does, I think that would rule out a default driver issue.

As it turns out, Windows XP does not fail. Only Windows 7 and Windows 8 do. The problem turned out to be the default serial.sys driver that comes with the O/S. The board manufacturer supplied a patched serial.sys from Fintek that seems to correct the issue. I tested a few other boards we have for the bug, and it seems that only Fintek devices get the error. The following chips all seem to exhibit the problem:
F81866AD
F81216DG
F71869AD

[David (PassMark)]

Thanks for the follow up.
This will surely help others who have the same problem.

[Comark Corp]

Interesting that when I search for the word Fintek, this thread doesn't appear in the search results.

[David (PassMark)]

Should be OK now. The search index was out of date.

[mrudloff]

Hi Jay,
Where can I find the driver? I wasn't able to locate it on Fintek's web-site.

Thanks

[Comark Corp]

Hi Jay,
Where can I find the driver? I wasn't able to locate it on Fintek's web-site.

Thanks

Do you have access to Usenet binary groups? I could post it there and you could use
This search engine to find it:
http://www.binsearch.info/
Jay