Re: [Libusb-win32-devel] Disconnect detection in libusb

[<IC-...@t-...>]

Hello,

>From: "Dan Ellis" <Dan...@ne...>
>
>kosel wrote:
>> Hello,
>> 
>>> From: IC-...@t-... (kosel)
>>> 
>>>> From: "Dan Ellis" <Dan...@ne...> The problems you
>>>> are describing sound very much like ones I encountered when keeping
>>>> a handle open to the device and putting a laptop into standby (and
>>>> got fixed).
>>> 
>>> it seems to be connected with your solved problem.
>>> 
>>> I commented out the
>>> usb_close(udev);
>>> which was executed after usb_bulk_read failed and before the loop to
>>> research for the device is reentered.
>> 
>> ups,
>> I forgot to wrote, that commenting out the call of usb_close _seems_
>> to solve the problem for S1 suspend. 
>> After resume from S1 everything seem to work fine.
>> 
>> But after resume from S3 suspend, there is still no wake up for the
>> USB. (Not only my libusb device.) 

Concerning this point: it doesn't depend on the kind of suspend.
It depend on the call of usb_close.

>
>I think you may need a kernel debugger to get much further. Try
>debugview from sysinternals (free).
>
>You can update the driver (with any additional debug you put in) by just
>putting the new build into WINDOWS\system32\drivers and replugging your
>device.

I have added 
usb_message("usb_os_close\n");
in the beginning of usb_os_close. While enabling libusb debug output
and running debugview, the problem does not occur, because debugview
takes a lot of CPU time for debugoutput.
But without debugview running, the problem occurs.
Also without my usb_message but with debuview running.
So there must be some kind of race condition.


Greetings
	Juergen