Re: [stunnel-users] stunnel 5.18 may keep high CPU usage
Hello Michal, Same problem with 5.19b4 and nothing special in the logs. Now I know how to reproduce the problem instantly, I just have to put my computer in StanBy mode and Awake it. Using Process Explorer from Sysinternals I see that stunnel produce a permanent "Other I/O" flow when problem appear. I/O Other : "The rate at which the process is issuing bytes to I/O operations that do not involve data such as control operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os." OtherI/O is confirmed by Process Monitor that trace no File nor Registry nor Network activity. But as stunnel still respond correctly to a Quit menu or any other menus and SSL requests I assumed that it may be some Thread going crazy so I compared running thread between normal stunnel behavior with the 25% CPU behavior and found that in fact there is a thread that do no terminate correctly. Here is the Thread's stack : MSVCR90.dll!_endThread+0x7d ntoskrnl.exe!memset+0x61a ntoskrnl.exe!KeWaitForMultipleObjects+0xd52 ntoskrnl.exe!KeWaitForSingleObject+0x19f ntoskrnl.exe!PoStartNextPowerIrp+0xba4 ntoskrnl.exe!PoStartNextPowerIrp+0x1821 ntoskrnl.exe!PoStartNextPowerIrp+0x1a97 ntoskrnl.exe!KeReleaseInStackQueuedSpinLock+0x5a afd.sys+0x61c1c afd.sys+0x51d3b ntoskrnl.exe!NtMapViewOfSection+0x15b7 ntoskrnl.exe!NtDeviceIoControlFile+0x56 ntoskrnl.exe!KeSynchronizeExecution+0x3a23 wow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0 wow64cpu.dll!TurboDispatchJumpAddressEnd+0x1fb wow64.dll!Wow64SystemServiceEx+0x1ce wow64.dll!Wow64LdrpInitialize+0x42a ntdll.dll!RtlIsDosDeviceName_U+0x1f5c4 ntdll.dll!LdrInitializeThunk+0xe ntdll.dll!NtDeviceIoControlFile+0x15 WS2_32.dll!select+0x9f stunnel.exe!OPENSSL_Applink+0xd3ec stunnel.exe!OPENSSL_Applink+0x961 Hope it help... regards. MT> Please try stunnel 5.19b4: MT> https://www.stunnel.org/downloads.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 15.06.2015 22:38, Dod wrote:
Here is the Thread's stack :
MSVCR90.dll!_endThread+0x7d ntoskrnl.exe!memset+0x61a ntoskrnl.exe!KeWaitForMultipleObjects+0xd52 ntoskrnl.exe!KeWaitForSingleObject+0x19f ntoskrnl.exe!PoStartNextPowerIrp+0xba4 ntoskrnl.exe!PoStartNextPowerIrp+0x1821 ntoskrnl.exe!PoStartNextPowerIrp+0x1a97 ntoskrnl.exe!KeReleaseInStackQueuedSpinLock+0x5a afd.sys+0x61c1c afd.sys+0x51d3b ntoskrnl.exe!NtMapViewOfSection+0x15b7 ntoskrnl.exe!NtDeviceIoControlFile+0x56 ntoskrnl.exe!KeSynchronizeExecution+0x3a23 wow64cpu.dll!TurboDispatchJumpAddressEnd+0x6c0 wow64cpu.dll!TurboDispatchJumpAddressEnd+0x1fb wow64.dll!Wow64SystemServiceEx+0x1ce wow64.dll!Wow64LdrpInitialize+0x42a ntdll.dll!RtlIsDosDeviceName_U+0x1f5c4 ntdll.dll!LdrInitializeThunk+0xe ntdll.dll!NtDeviceIoControlFile+0x15 WS2_32.dll!select+0x9f stunnel.exe!OPENSSL_Applink+0xd3ec stunnel.exe!OPENSSL_Applink+0x961
I'm not a Windows kernel expert, but it looks to me like a Windows kernel synchronization problem (possibly a deadlock) in the power management code. Please correct me if I'm reading it wrong. Googling for PoStartNextPowerIrp returns numerous other (seemingly random) cases of spinning threads. I'm still looking for a solution. BTW: Why don't you have symbols for afd.sys? Could it be a malware infection? Best regards, Mike -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJVf2BLAAoJEC78f/DUFuAUudQQAIuj6D8WqP3uqLcK6v2pWMNN wOumt92B3GoqQUUdDippmLtJCcHqTrKYdTv3oMfZpr+6aL7LSFQEkmF/N3J99Oo/ tc0aV2Ifn9b3FQfUss0Yiq6GUg4ZWiCr/vvrKO8zBfLInh8MzdhUq20oXC/QJWJy mKJ/QRLSgoTHvTenqDXO4Q6ufQ7mxHH0XyedhadCxfOPNl3bRCpiWwwFhTz77h3U VD5e3SYrRP6/fi91fASwrRCAxnxiXq+9PES9+/ciStQTjeoRolIQ9df2pXjHDTTp 7HyOdy1wBic1s9404ZgT12pMdKgE/xltFerup8BRKUeBQsYzwu+ul5rbsLqe+zxG rK4aNg05V6Qz+gky9RNbSm8OLmv0UCIkXCcFghRXRC0e5BJsgx4nPS78/6vqZ1vf hG6SD+jd+bWgjl61cM8Jy9+jal9ZZzEg9/1OHOpbrzCNTIHhvpNzaTwYZkps2f/g N032wJmmi2FBVtL+/Ibx1vjnTcMNaeygFwj82fJt3wqNisRH75CLVNF5legI44qD S5bYSTLEEc0s7HArkgnXTAMT+yK9caoz+l8zxOghWTzwdt0Ihik6Es1s6/zGI4ge 2EBPsjbXkGhsEGmEbym8L9tg4GZw76Cq+m3mH9rrjnaXX9lGwn2gNVEl++/4PdYI zi7rrGl9H2wL9T88lSsq =Xnwv -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Users, In case anyone else experienced the same error, a fix is available for testing in stunnel 5.20b7: https://www.stunnel.org/downloads.html Any subsequent releases will obviously also include the fix. 8-) Mike -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJViDedAAoJEC78f/DUFuAUCogQAJ3PK9tRPJbvu3tLeijuCYGc Q0JwY7qz5aY3ZITqDju7kOAi6naNN/qIcojchJEleazMQ86mnkapmJ545mrPcAKk AMda6HM6Haqhbv7modhs2ebwk7PshoeGdNySFHanzs9UxZeH0YsLM7n8KTfS3088 DX+344Rr92ycPvYvxCACSPRWf+aznT2+LM2kDPx3tiUnZXDvFVhVXq/bCKlvM38u ZfDjyOh8T/BGZ9hE4WVgMTmGhPMI3NPmKwThRjY8nuiHY5E0dWCMwbU38Bn7bZJK YxpEQztuLfUIp19pQ95bNIWuZXDzaveJ4ne/p6pSKYzc+Rm/pWEROnKkzf1O8aDp JnOqAPRFspIwCoZbaicWGezC/hh2/P5sLR6bH1z2DWKq2uu0WPsrt+IE1aOGwAc3 kkwOZ5BYL5WBSwPfKF49KHsWbiZIgMuN1vh5opHcy5/bLa7mXkQ+uC3ymBx2q6x5 boQcwZmJu75YM5Gd+bxW3VeY4XQubEYzi9TbdrRuLDgz4kbAWATPzaSqXWlhXwyM e4OmDeVOM0Cdz2dYwcvLga/klz2RukyTzgwVpvTioeLGo8ccGCSA0D+z8k8vaP4K cIxDCtFeHxe1NHuqS6QOhhZE7T4tbG9LbmBRAu2rLS+KbOuK9n2iP5NqyxZXgDV/ pLn3QD1WDacHstD75NP0 =mCrt -----END PGP SIGNATURE-----
participants (2)
-
Dod -
Michal Trojnara