Hello,
Setup:
client - win7, vh 3.2.4
server - rpi2, vh 2.6.0, Wifi dongle EW-7822 (note: USB3.0)
Usually all works well.
Once in 2-3 days of extensive usage, I reach a case where dongle stops working:
- On Win7 WiFi dialog, no networks are visible
- both Win7 and VH display the device, as usual. Then after restarting VH client, the device no longer displayed neither on VH or on Win7.
This is the System Messages output of VH client:
13:19:48 INFO :VirtualHere Client 3.2.4 starting (Compiled: Nov 13 2015 12:36:09)
13:19:48 INFO :Using config at C:\Users\Administrator\AppData\Roaming\vhui.ini
13:19:48 INFO :IPC available at \\.\pipe\vhclient
21:30:51 INFO :Drivers are up-to-date
07:10:42 INFO :Connection 1 remotely disconnected gracefully (rx)
07:10:52 INFO :Server ping timeout, shutting down connection 1...
09:08:29 INFO :Connection 1 receiving msg size didnt complete due to error 10054,
09:08:39 INFO :Server ping timeout, shutting down connection 1...
23:35:13 INFO :In file ../src/msw/window.cpp at line 577: 'SetFocus' failed with error 0x00000057 (the parameter is incorrect.).
I would appreciate any help on how to debug this, please?
Thank you.
Edit: the WiFi dongle is
Edit: the WiFi dongle is connected through a HUB (Dlink DUB-H7) to the Rpi2
rebooting windows DOES NOT resolve the issue
Notes:
- rebooting windows does not resolve the issue.
- killing and relaunching the vh server on the pi2, also does not resolve the issue.
-> rebooting the rpi2 resolves the issue, and the WiFi appears correctly on the Win7 client afterwords.
Issue will occur again, during next couple of days, so I would appreciate notes on how to debug it. Thank you.
Can you send me the /var/log
Can you send me the /var/log/syslog to mail [at] virtualhere.com (mail[at]virtualhere[dot]com) when you get the disconnect. That will (hopefully) describe kernel issues in raspbian that occur at that time or errors in virutalhere. At this point my i suspect a kernel bug in raspbian because only rebooting rpi fixes it (rather than just restarting virtualhere) I would like to know also what raspbian version you are using?
Edit: I forgot to add that err 10054 is the pi shutting down the tcp connection and the client then detecting this...
Edit Again: Also, if its not too much trouble could you plug one of the pis into the ethernet cable and see if that works past 3 days. If so then we can isolate the problem to the wifi dongle driver
pis are also always connected
pis are also always connected via eth0, and I confirm that once issue occurs access using Ethernet cable works. will send syslog via email.
Thank you.
Ok if the eth0 is still
Ok if the eth0 is still working the usb subsystem is up because the network shares the usb port, i'll take a look at your logs..