From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 121374 invoked by alias); 14 Jun 2017 23:32:29 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 121358 invoked by uid 89); 14 Jun 2017 23:32:28 -0000 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,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=humble, European, awhile, smoothly X-HELO: mail-qt0-f174.google.com Received: from mail-qt0-f174.google.com (HELO mail-qt0-f174.google.com) (209.85.216.174) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 14 Jun 2017 23:32:27 +0000 Received: by mail-qt0-f174.google.com with SMTP id w1so20260843qtg.2 for ; Wed, 14 Jun 2017 16:32:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=Ey9X4byvuLfHFXuVGRmPeM5KHEFESi+5gb93Kl0yYUU=; b=tb/zu9P0nGCWE0SfkU9sXmBpWb5mq5UGdkhEERO1LNEXVnQzvx9lAPyIEQz2N6GlxH 8fLKEEMZnR6/qv+oxy3gIDpZNH9qAfz0fp+mti+sO0WQCmAyRelHF/eU95XqXCfgPhhm TEbCB3MMQhPSGqbY+Q+jNIsmBCFefHqHAKVResXxgDSPx+9YpO5T6pm2EcKrXabyzC3W ujjhala929mhL6XXXzELWrsg29OMRdHitHG2FthiWpOHdc8QIdph1Pejb6DeIT4yiLl/ idJaDvLXJh0ppBHUCYgPZcrIwV0Rsjo0AmKALpXy3N9WR6Itd5Zw/ikB/fSiRT20g0e2 JA9w== X-Gm-Message-State: AKS2vOwEkwY6TASDerb8sZzZPa/w7sTX3rOvu0tkzdqjtfBbauwmoa36 MX7x3x6JO6dx/0p5oGA= X-Received: by 10.200.40.251 with SMTP id j56mr3407944qtj.186.1497483149949; Wed, 14 Jun 2017 16:32:29 -0700 (PDT) Received: from [192.168.106.37] (static-64-222-175-129.myfairpoint.net. [64.222.175.129]) by smtp.googlemail.com with ESMTPSA id t35sm1063785qte.38.2017.06.14.16.32.25 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Jun 2017 16:32:29 -0700 (PDT) Subject: Re: cygserver - Postgres Multiple connection Load Testing - Inifinte Loop To: cygwin@cygwin.com References: <200408030333.i733XEXn023894@mx3.redhat.com> <20040803100612.GP31522@cygbert.vinschen.de> <20170321025614.GA2100214@tornado.leadboat.com> <20170324171101.GI29995@calimero.vinschen.de> <20170328052652.GA2351961@tornado.leadboat.com> <20170402023624.GA2561924@tornado.leadboat.com> <20170507032747.GA876495@rfd.leadboat.com> <590E98DD.9000805@cygwin.com> From: Marco Atzeri Message-ID: Date: Wed, 14 Jun 2017 23:32:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 MIME-Version: 1.0 In-Reply-To: <590E98DD.9000805@cygwin.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2017-06/txt/msg00155.txt.bz2 On 07/05/2017 05:47, Larry Hall (Cygwin) wrote: > On 05/06/2017 11:27 PM, Noah Misch wrote: >> 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? > > Just FYI, Corinna is away for a bit (in European time, "a bit" = until > June ;-) ) so don't be surprised if her response is delayed. > as she is back, we can humble rise her attention to the matter. Regards Marco -- 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