Yes. The issue is fairly reproducible and takes not more than 10-15mins to
occur.
--
Thanks,
Nilesh
Sent via CanvasHD
"Dr. Stephen Henson" wrote:
On Wed, Jan 15, 2014, Tayade, Nilesh wrote:
>
> Thanks. I have already captured the lock details in an array. Please see
> below. The leftmost di
On Wed, Jan 15, 2014, Tayade, Nilesh wrote:
>
> Thanks. I have already captured the lock details in an array. Please see
> below. The leftmost digit is lock number index.
> Lock 19 was taken by same thread and it was released (lock_present = 0). And
> this is causing confusion for me.
>
> 18 {
> -Original Message-
> From: owner-openssl-us...@openssl.org [mailto:owner-openssl-
> us...@openssl.org] On Behalf Of Dr. Stephen Henson
> Sent: Wednesday, January 15, 2014 6:30 PM
> To: openssl-users@openssl.org
> Subject: Re: Deadlock in openssl1.0.1e.
>
> On W
On Wed, Jan 15, 2014, Tayade, Nilesh wrote:
>
>
> Thanks for your suggestions. I did try capturing the debug information and
> below is how the state of the locks is. The array per lock stores information
> of the owner, file and lock_present i.e. lock is held or not.
> I see that the lock # 1
> -Original Message-
> From: owner-openssl-us...@openssl.org [mailto:owner-openssl-
> us...@openssl.org] On Behalf Of Dr. Stephen Henson
> Sent: Wednesday, January 15, 2014 1:56 AM
> To: openssl-users@openssl.org
> Subject: Re: Deadlock in openssl1.0.1e.
>
> On T
On Tue, Jan 14, 2014, Tayade, Nilesh wrote:
> Hi,
>
> I am not able to understand what???s going wrong, below is the latest stack
> trace I got. Thread 19 is killed by a watchdog, and it was waiting on a lock.
> Other threads do not show any lock being held.
>
>
I'd suggest you modify your lo
...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Lee Dilkie
Sent: Tuesday, January 14, 2014 7:25 PM
To: openssl-users@openssl.org
Subject: Re: Deadlock in openssl1.0.1e.
and what are all the other threads doing? some other thread must already own
this lock and is waiting on
and what are all the other threads doing? some other thread must already
own this lock and is waiting on something else.
-lee
On 2014-01-10 13:11, Tayade, Nilesh wrote:
> Hi,
>
> I am facing a deadlock issue on openssl1.0.1e. Please see the stack below.
> Could anyone please advise if this is a
Hi,
I am facing a deadlock issue on openssl1.0.1e. Please see the stack below.
Could anyone please advise if this is a known bug? Is there any workaround/fix?
FIPS is disabled on my system.
(gdb) bt full
#0 __lll_lock_wait () at
../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:136
No loc
