Key creation problem with 2.1.16
Carola Grunwald
caro at nymph.paranoici.org
Sun Jan 29 14:28:37 CET 2017
Hello,
on Sun, 29 Jan 2017 03:29:54 +0000 (UTC), I wrote:
>on Thu, 8 Dec 2016 03:27:07 +0000 (UTC), I wrote:
>
>>And there's a probably different problem with a likely broken IPC, where
>>I get 259/$103 in return for the current and all following commands
>>until another agent instance appears in the Task Manager after about 2
>>minutes.
>
>These 2 minutes were my gpg.exe call timeout interval.
>
>The cause of the frozen gpg-agent.exe instance may be a mutex deadlock,
>possibly a problem within the Windows nPth implementation. With a frozen
>agent the call stack dump always looks the same as shown below. Here it
>usually takes less than 2 hours to get such a glitch with 5+ broken
>gpg-agent.exe processes added to the task list overnight, resulting in
>periodical server failures.
>
>GnuPG 2.1.17, libgcrypt 1.7.5, Windows 7 (32 and 64 bit)
>
>
>Normal idle situation:
>
>Stack for thread gpg-agent.exe+0x14e0
>-------------------------------------------------
>ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
>ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x7d2
>ntoskrnl.exe!KeWaitForMutexObject+0x19f
>ntoskrnl.exe!PsIsSystemProcess+0x94
>ntoskrnl.exe!KeStackAttachProcess+0x11c1
>ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x9dd
>ntoskrnl.exe!KeWaitForMultipleObjects+0x26b
>ntoskrnl.exe!MmCreateSection+0xe23
>ntoskrnl.exe!NtOpenResourceManager+0x599
>ntoskrnl.exe!KeSynchronizeExecution+0x3a43
>wow64cpu.dll!TurboDispatchJumpAddressEnd+0x690
>wow64cpu.dll!TurboDispatchJumpAddressEnd+0xe3
>wow64.dll!Wow64SystemServiceEx+0x1ce
>wow64.dll!Wow64LdrpInitialize+0x429
>ntdll.dll!RtlResetRtlTranslations+0x1b08
>ntdll.dll!RtlResetRtlTranslations+0xc63
>ntdll.dll!LdrInitializeThunk+0xe
>ntdll.dll!NtWaitForMultipleObjects+0x15
>kernel32.dll!WaitForMultipleObjectsEx+0x8e
>kernel32.dll!WaitForMultipleObjects+0x18
>ntdll.dll!RtlQueryInformationActivationContext+0x12d
>gpg-agent.exe+0x375b
>
>TCP/IP
>Protocol Local Address Remote Address State
>-------------------------------------------------
>TCP mypc:49237 mypc:0 LISTENING
>TCP mypc:49238 mypc:0 LISTENING
>TCP mypc:49239 mypc:0 LISTENING
>TCP mypc:49240 mypc:0 LISTENING
>
>
>Frozen agent:
>
>Stack for thread gpg-agent.exe+0x14e0
>-------------------------------------------------
>ntoskrnl.exe!SeAccessCheckWithHint+0xb4a
>ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x7d2
>ntoskrnl.exe!KeWaitForMutexObject+0x19f
>ntoskrnl.exe!PsIsSystemProcess+0x94
>ntoskrnl.exe!KeStackAttachProcess+0x11c1
>ntoskrnl.exe!KeAcquireSpinLockAtDpcLevel+0x9dd
>ntoskrnl.exe!KeWaitForMutexObject+0x19f
>ntoskrnl.exe!NtWaitForSingleObject+0xb2
>ntoskrnl.exe!KeSynchronizeExecution+0x3a43
>wow64cpu.dll!TurboDispatchJumpAddressEnd+0x690
>wow64cpu.dll!TurboDispatchJumpAddressEnd+0x484
>wow64.dll!Wow64SystemServiceEx+0x1ce
>wow64.dll!Wow64LdrpInitialize+0x429
>ntdll.dll!RtlResetRtlTranslations+0x1b08
>ntdll.dll!RtlResetRtlTranslations+0xc63
>ntdll.dll!LdrInitializeThunk+0xe
>ntdll.dll!NtWaitForSingleObject+0x15
>ntdll.dll!RtlIntegerToUnicodeString+0x20b
>libnpth-0.dll!npth_clock_gettime+0x18f
>libnpth-0.dll!npth_eselect+0x485
>gpg-agent.exe+0x375b
with two additional (dead) gpg agent threads listed:
TID Start Address
----------------------------------------
4528 gpg-agent.exe+0x14e0
...
5240 libnpth-0.dll!npth_setname_np+0x59
4924 libnpth-0.dll!npth_setname_np+0x59
>
>TCP/IP
>Protocol Local Address Remote Address State
>-------------------------------------------------
>TCP mypc:49237 mypc:0 LISTENING
>TCP mypc:49237 mypc:49854 ESTABLISHED
>TCP mypc:49237 mypc:50065 ESTABLISHED (-> gpg.exe)
>TCP mypc:49238 mypc:0 LISTENING
>TCP mypc:49239 mypc:0 LISTENING
>TCP mypc:49240 mypc:0 LISTENING
>TCP mypc:49854 mypc:49237 ESTABLISHED
Kind regards
Caro
More information about the Gnupg-devel
mailing list