Hi Ian,
I was using the stock Windows serial port drivers in Win2k and WinXP. I tried installing the Intel chipset INF update utility for the E7520 + 6300ESB chipset on the Win2K machine and no change in error behavior (I don't think it has any Intel specific serial port driver in the INF update).
The error almost always occurs on one of the com ports at the beginning of the test, but not always on the same com port. The error does occur again once in a while on each port as the test continues.
No other Passmark tests are running and no other software other than the Windows OS tasks that run after a basic Windows install and boot.
Can you tell me if the 'send data to com port' routine depends upon a receiving a transmitter-empty interrupt? There is an Intel errata about the transmitter empty interrupt on the 6300ESB but Intel considers it minor enough that they didn't see a need to change it. I guess they figure it shouldn't cause a problem for well-behaved drivers.
Thoughts? Could this also be related to the drop in throughput when multiple com ports are tested at the same time?
I was using the stock Windows serial port drivers in Win2k and WinXP. I tried installing the Intel chipset INF update utility for the E7520 + 6300ESB chipset on the Win2K machine and no change in error behavior (I don't think it has any Intel specific serial port driver in the INF update).
The error almost always occurs on one of the com ports at the beginning of the test, but not always on the same com port. The error does occur again once in a while on each port as the test continues.
No other Passmark tests are running and no other software other than the Windows OS tasks that run after a basic Windows install and boot.
Can you tell me if the 'send data to com port' routine depends upon a receiving a transmitter-empty interrupt? There is an Intel errata about the transmitter empty interrupt on the 6300ESB but Intel considers it minor enough that they didn't see a need to change it. I guess they figure it shouldn't cause a problem for well-behaved drivers.
Thoughts? Could this also be related to the drop in throughput when multiple com ports are tested at the same time?
Comment