X-Spam-Check-By: sourceware.org
Date: Thu, 13 Jul 2006 08:53:09 -0700
From: Yitzchak Scott-Thoennes <sthoenna AT efn DOT org>
To: cygwin AT cygwin DOT com
Subject: Re: Perl failure
Message-ID: <20060713155309.GA1648@efn.org>
References: <B7392353E4C4DE4ABC4EC255DB4CA0400347168A AT EXCHVS1 DOT spimageworks DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <B7392353E4C4DE4ABC4EC255DB4CA0400347168A@EXCHVS1.spimageworks.com>
User-Agent: Mutt/1.4.2.1i
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Wed, Jul 12, 2006 at 05:08:43PM -0700, Bruce Dobrin wrote:
> Hi,
> 
> I have a server that has been doing back end maintenance using perl on
> cygwin for 6 years now.  I recently upgraded from win2k and cyg1.5.9 to
> XP sp3 and cyg1.5.19 (to be fare,  I also cleaned up the perl code a
> bit).  The script checks versioning and build info on about 600+ windows
> systems.  Since the upgrade,  it gets thru about 500 of them ( almost
> exactly 2 hours)  and then:
> 
> panic: MUTEX_LOCK (45) [util.c:2266] at
> /c/dist_and_install_files/source/dist2/spUpdate2d.pl line 24, <HOSTFILE>
> line 277.
> panic: MUTEX_LOCK (45) [op.c:354], <HOSTFILE> line 277.

This indicates EDEADLK being returned from posix_mutex_lock.
 
> It hits a slightly different time and position in the list each time,
> but always after approximately 2 hours.  I found a few old mails
> suggesting rebaseall,  which I ran to no effect.  The system pretty much
> runs nothing but this. I've been running a version of this script since
> cyg1.3.9 and never had a problem like this one.
> 
> Any suggestions?

Can you revert one or more of the many things you changed, and see if 
it makes a difference?

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/