X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=Auav
	acAIEugu7l2m3SxnxfM9z8axKdYAGSZvMXa0Rdq3n+mt7+3NMCQr1ik5fv63N2Ix
	ZJFSIQTBiUDvX8Dc3ejWAtBE1QvMj8iAmeZe/lF8dofA2OFdvbq3R8LM8BTvsbXi
	W9uIJA9nHC0phjvxZihO290t3b2imc9zq5IzScE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; s=default; bh=NWP2RA8YKG
	UaU/j2V0ZWHbt6FkE=; b=hFbGYLFmY0vzSwvJZofdCSyLpgpc+LtLh+MNHfOTCv
	ZgkbuPXTC006hgcfNJvvVq6OWZGPCT0EZFLa0W0MEgrEZkCxHFm+Uihm72zGLBel
	2xfNk0brhwkrtmXkzEZ9uix9Uh62h4puYb8YY9vTnrdNrcrheHn+Gji0qQr8CJ5/
	8=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=symptoms, render, sixteen, smoothly
X-HELO: mail-pf0-f175.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20161025;        h=x-gm-message-state:date:from:to:subject:message-id:references         :mime-version:content-disposition:in-reply-to:user-agent;        bh=BTtu/dyQn1YQ4tdri7OMw0T2DoytnjvyM8lH9/UHMsA=;        b=ougFNDgPR4zgxGp0iAIBBof6dq96ryDISGeyVLIHmezrmEjFUGUJUTP1Xp4QQ9K0Sy         S2ahJwGV+LHgsAbVHs8U2qlgDTod5V5J5YeUl+CcBals1bFKmZhzh3SacooE9DNuxb2X         drc62WiQivzrCc6at6tPXXNGhKoGaoIhWm0kKJxtXS3CnizZKLK8pvVyzPAk4wuPsMcK         kZMRPuMKc29qzmam6mokTDmdOV0vUBFfrU+3U/x7HNX7JlO1Vbz6oMxlHZI+HPSQ10eR         iIvUebchcP6oOrZX9RIzmzf0OsX6k2L2HIClvE497LG6liVFTV89IXecDNQ9PuSqM/Xs         huNA==
X-Gm-Message-State: AN3rC/5IC1uAVcjihQP7ld4/AxL1dfyBzqUNwKBEwHBor7BTemAlkvRi	qPs7hBycdhBm4d6JHDjq3g==
X-Received: by 10.99.128.72 with SMTP id j69mr11562634pgd.28.1494127670600;        Sat, 06 May 2017 20:27:50 -0700 (PDT)
Date: Sat, 6 May 2017 20:27:47 -0700
From: Noah Misch <noah AT leadboat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygserver - Postgres Multiple connection Load Testing - Inifinte Loop
Message-ID: <20170507032747.GA876495@rfd.leadboat.com>
References: <200408030333 DOT i733XEXn023894 AT mx3 DOT redhat DOT com> <20040803100612 DOT GP31522 AT cygbert DOT vinschen DOT de> <20170321025614 DOT GA2100214 AT tornado DOT leadboat DOT com> <20170324171101 DOT GI29995 AT calimero DOT vinschen DOT de> <20170328052652 DOT GA2351961 AT tornado DOT leadboat DOT com> <20170402023624 DOT GA2561924 AT tornado DOT leadboat DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170402023624.GA2561924@tornado.leadboat.com>
User-Agent: Mutt/1.5.24 (2015-08-30)

On Sat, Apr 01, 2017 at 10:36:24PM -0400, Noah Misch wrote:
> On Tue, Mar 28, 2017 at 01:26:52AM -0400, Noah Misch wrote:
> > On Fri, Mar 24, 2017 at 06:11:01PM +0100, Corinna Vinschen wrote:
> > > I pushed a patchset now, and uploaded new developer snapshots for
> > > testing to https://cygwin.com/snapshots/
> > 
> > > Please give it a try
> 
> > I call the cygwin-20170324 freezes "limited" because the symptoms differ from
> > the classic freeze I described upthread.  "strace /bin/true" and "cat
> > /proc/sysvipc/sem" do not hang, but every PostgreSQL backend process is stuck
> > waiting on a synchronization primitive.
> > 
> > I can distill another self-contained test case for the limited freeze seen in
> > cygwin-20170324, but that make take awhile.  I'm sending this early report so
> > you're aware of the possible regression in cygwin-20170324.
> 
> I'm attaching a new test program that demonstrates the regression.  My previous
> test program created sixteen processes that each picked a random semaphore to
> lock.  Now, each process picks two semaphores and locks them in order.  This
> proceeds smoothly on GNU/Linux and on cygwin-20170321.tar.xz "cygserver -r 40".
> It freezes within one second on cygwin-20170324.tar.xz "cygserver -r 40".

I suggest reverting the cygwin-20170324 cygserver changes for now.  Older
versions can be configured to have reliable sysv semaphores, but I think no
settings render sysv semaphores reliable in Cygwin 2.8.0.  What do you think?

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