Hans Dingemans wrote:
> Anything else I can do?
>>Try 1.9 release. If it happens again, submit debug trace with 'DEBUG=3D=
> IO_DEBUG=3D1 EVENT_DEBUG=3D1 USB_DEBUG=3D1' (normally a
After compiling with debug, load module with 'insmod ./ndiswrapper.ko
debug=3D0'; when 'scheduling while atomic' errors start (you can see disk
activity due to system log messages), enable debug with 'echo 6 >
/proc/net/ndiswrapper/debug' and submit a few thousand lines of log. In t=
case, the log messages should point to the cause, even if debug was not o=
when it first happens, since this seems to happen in a loop.