windows 10 client crash on a specific device removal

Submitted by heel on #1

I have a problem with a windows 10 client crashing (BSOD) whenever the usb device (national instruments USB-6009) is either physically unplugged from the Odroid-C2 server or released (stop-using) with the virtual-here client gui.
USB-6009 device is the only device having this problem
This problem is not present on Win7/64bit client against the same server.

Client is version 4.5.9,
server is the vhusbdarm64a53 optimized version (downloaded 2. sep. 2018 - not sure how to see which is the version).
server is Odroid-C2 with Ubuntu 18.04.1 LTS (GNU/Linux 3.16.57-25 aarch64).

Any suggestions how to debug such a problem.

Submitted by heel on Wed, 2018/10/03 - 07:38

#2

To supplement my findings:
In addition to the crash on device removal I see that it has a very slow transmission speed for this particular usb device (national instruments USB6009 daq device). Speed is down by a factor 20.

I tried to install the latest optimized server for arm64 and also the non optimized server both downloaded now from the web. This did not improve (or deteriorate) anything.

I tried to change the server platform from Odroid to Raspberry P3 (Raspbian) and installed the latest free non optimized version from the web for arm. This works!

This is of course a good news, but Rpi has a slow network speed (Ethernet is USB based so bottlenecks are to expect) so I'd rather stick with something of the format of Odroid.

I have attempted to update the kernel from (GNU/Linux 3.16.57-25 aarch64) to something more recent but this has failed.
So in conclusion - the problem is related to the Odroid server in some way.
Any suggestions on how to debug this or use another platform similar to Odroid which is known to work well? I need the small form factor and 4 USB.

Submitted by Michael on Wed, 2018/10/03 - 09:34

#3

I would recommend using the pi3 as it has a good kernel. Also the odroid xu4 has a very good kernel. However on the C2 the 3.16 kernel is very out of date and although they do patch some things i would recommend using the pi3. The USB-6009 is only a usb 1.1 device so the pi3 should easily be able to handle it.