Serial port adapter occasionally does not flush buffered characters

USB Cables PL2303-DB9
21

Hi Lecherng - Thanks for posting!

Driver version 3.4.36.247 has not shown any of the above issues over the last few months, with our adapter (http://plugable.com/products/pl2303-db9/ – uses a Prolific PL2303HX Rev D chipset).

Are you using a Plugable brand adapter?

22

Hi Bernie

I’m not quite sure which Plugable brand adapter is it, as we had used it for quite some time…
However, i did manage to check the chipset version
‘This is a PL-2303 XA /HXA chip’

Could you advise?

23

Hi Lecherng - Plugable brand adapters have always used Rev D. Can you way what logo is showing on the adapter, and serial number info from the back? Here’s ours:
http://plugable.com/products/pl2303-db9

Thanks!
Bernie

24

I just had 7 back to back BSOD instances due to this issue. My system is running WIndows 7 Enterprise, and I’m using the latest driver from your site (v1.7.0). I’'m not sure if I have your “brand” serial cable, but it is the PL2303 XA / HXA chip (as reported by the Check-PL chip utility that comes with the driver). Since I don’t have a direct line to Prolific, I hope you can pass this info on.

My setup is using putty 0.62 (IT install). I am running on whatever com port the usb serial comes up as in device manager (it tends to roam), 115200n8. I am connected to a server to debug bios configuration output, so I am getting a steady stream of data. I have been able to replicate this lockup on a test system at home running Windows7 Home Professional 64bit connected to a pandaboard (pandaboard.org for more info) booting Ubuntu Linux with serial console enabled.

The cables work fine when running on a Linux host doing the same thing, so not a hardware issue. It also works when I run a Linux OS in Virtualbox and have it take over the usb-serial cable.

If I could, I would ditch Windows in a heartbeat, but other tools we need don’t run on Linux or in a Windows VM (which is more stressfull on a laptop than running Linux in a VM).

I hope this info helps you to reproduce this issue. If you need more, let me know.

Tobin Davis
tbdavisx intel.com

25

Hi Tobin,

Sorry to hear about the bug checks, I’ll be happy to help however I can. Our Plugable cables are HXD chips and the blue screens have been resolved with the latest drive. I can’t really speak to the results with the HXA chipset, however if you’d like to contact me at support@pluable.com I’ll be happy to see what I can do.

Thanks,
Jerome.

Plugable Technologies

26

Actually I’m still having blue screens on all sorts of 64bit machines (XP, 7, 8), but not 32bit ones. This is using the latest Microsoft signed driver 3.4.48.272 (05/02/2013).

WinDbg shows a dump of:

STACK_TEXT:
fffff880’1bf13280 fffff880’1a5c0d86 : fffffa80’1fadc610 fffffa80’16b062d0 fffffa80’16b06358 fffffa80’1fadc7a0 : ser2pl64+0xded7
fffff880’1bf13300 fffff880’1a5b649a : 00000000’00000001 fffff880’1bf135d0 00000000’00000000 fffffa80’1fadc7a0 : ser2pl64+0xcd86
fffff880’1bf13360 fffff880’0103ff88 : fffffa80’1fadc610 fffffa80’1fadc610 fffff880’1bf135d0 00000000’00000070 : ser2pl64+0x249a
fffff880’1bf13590 fffff880’0103f42f : fffffa80’1fdb5600 fffffa80’00000004 fffffa80’1fdb56b0 fffffa80’16b06228 : Wdf01000!FxIoQueue::DispatchRequestToDriver+0x488
fffff880’1bf13610 fffff880’0104afbb : fffffa80’1d1f4010 fffffa80’1fadc600 00000000’00000000 fffffa80’1fadc610 : Wdf01000!FxIoQueue::DispatchEvents+0x66f
fffff880’1bf13690 fffff880’0104430a : fffffa80’1d1f4000 fffffa80’1fadc610 fffffa80’1c45c010 fffff880’1bf13770 : Wdf01000!FxIoQueue::QueueRequest+0x2ab
fffff880’1bf13700 fffff880’010439da : fffffa80’1fadc610 00000000’0000002a fffffa80’1c45c500 fffffa80’1c45c010 : Wdf01000!FxPkgIo::Dispatch+0x4da
fffff880’1bf13770 fffff880’01043aa6 : fffffa80’1c45c010 fffffa80’1c45c500 fffffa80’16b06980 00000000’00000001 : Wdf01000!FxDevice::Dispatch+0x19a
fffff880’1bf137b0 fffff880’1a5e4a56 : fffffa80’1c45c010 fffffa80’1c45c500 00000000’00000000 00000000’00000001 : Wdf01000!FxDevice::DispatchWithLock+0xa6
fffff880’1bf137f0 fffff880’1a5e47f4 : fffffa80’1c45c010 fffffa80’1c45c518 00000000’00000000 fffff880’00000000 : serenum!Serenum_DispatchPassThrough+0x86
fffff880’1bf13830 fffff801’6867735f : fffffa80’1c45c010 fffff880’1bf13b80 fffffa80’1c45c010 fffff880’00000000 : serenum!Serenum_IoCtl+0x90
fffff880’1bf13890 fffff801’68677ce6 : 00000000’00000000 fffffa80’080ab620 00000000’00000001 00000000’00000000 : nt!IopXxxControlFile+0x7dd
fffff880’1bf13a20 fffff801’6828c053 : fffffa80’1d4f3080 00000000’0072e548 fffff880’1bf13aa8 00000000’00000000 : nt!NtDeviceIoControlFile+0x56
fffff880’1bf13a90 00000000’77cc2ad2 : 00000000’00000000 00000000’00000000 00000000’00000000 00000000’00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000’0072ee58 00000000’00000000 : 00000000’00000000 00000000’00000000 00000000’00000000 00000000’00000000 : 0x77cc2ad2

FOLLOWUP_IP:
ser2pl64+ded7
fffff880’1a5c1ed7 832100 and dword ptr [rcx],0

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: ser2pl64+ded7

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: ser2pl64

IMAGE_NAME: ser2pl64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 51106b4e

STACK_COMMAND: .cxr 0xfffff8801bf12880 ; kb

FAILURE_BUCKET_ID: 0x3B_ser2pl64+ded7

BUCKET_ID: 0x3B_ser2pl64+ded7

27

Hi Justin,

Thanks for posting here. Please reply to us at support@plugable.com with your Amazon order id and a link to this thread and we’ll figure out the next steps.

Thanks,
Jerome.

Plugable Technologies

28

Sure - I’ll send that and the full dump later today. Tested with others on Windows 8 and this seems a unique problem to the prolific drivers.

Repro by your team/prolific will be tricky though as this is uses specific equipment on the end of the serial port.