From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) by sourceware.org (Postfix) with ESMTPS id C01A3396E866 for ; Thu, 20 May 2021 16:02:34 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org C01A3396E866 Received: by mail-qt1-x82d.google.com with SMTP id 1so13171944qtb.0 for ; Thu, 20 May 2021 09:02:34 -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:from:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=Q7/lU9r0kswXjd60sqS4He8VJe18zsRYj6Oo7ERGdS4=; b=SyZYZvZ/roxjWWrQkSCk/WWd1w9kJD7Asgeta/+/J5FVqh9XiJCfoMEnj7uLL7VO6o +ptcEG6uOyxRhf3wpc34q360l9MIjQkZDiMoJ+Sm9iMa2NzcBm9JLFaFv4fL4MiKBo2J pFf9IUwMOTeyF8MeXphLWHOYDraa4Ghi85+tHmRWtKadohCmU43SvTK8CJICs1dHk7fS 15o2nxAjLuHH7zf9F88/m3T1OdxCna2OBvsk4K582oez5EbXq3zof9g7d2gMA6AHBfI6 6g9VKGvyxaoJP5hGIhfsj794Nmy20vCtQOuQqkQZ7K4snM0tS/pxRRyPxMpaNJRqA2eO 8CZQ== X-Gm-Message-State: AOAM5320bpYG/wJQPrUjQ1w/Nbku8Ty3HHcbEhFuwAx8OlKNM/ewK0dA 6bBqd5gKw8rb3NppS8yjfXAxJEDfyj0= X-Google-Smtp-Source: ABdhPJyYooqG8+JLwBNeuvrs9d1ngux8KQ7hCWvi+uKBeJxr4NcTS1XVI1PEwxQooAnrNKmgJYdC9Q== X-Received: by 2002:ac8:5981:: with SMTP id e1mr5904996qte.310.1621526553771; Thu, 20 May 2021 09:02:33 -0700 (PDT) Received: from [192.168.1.19] (pool-108-27-17-105.nycmny.fios.verizon.net. [108.27.17.105]) by smtp.gmail.com with ESMTPSA id x9sm2223150qtf.76.2021.05.20.09.02.32 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 20 May 2021 09:02:32 -0700 (PDT) Subject: Re: sshd high cpu load From: "A. Doggy" To: cygwin@cygwin.com References: Message-ID: <7bd9875a-691e-95fe-77ea-4c8ccd98a46d@gmail.com> Date: Thu, 20 May 2021 12:02:32 -0400 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 May 2021 16:02:35 -0000 Anyone? On 5/19/2021 12:48 AM, A. Doggy wrote: > To Cygwin, > > > I am running cygwin openssh as a windows service. I have been doing so > for many years with out issue. Recently, I have been running into an > issue where it maxes out my cpu on any version newer than 8.4p1-1. The > solution is to downgrade to 8.4p1-1. My server machine is a dell t330 > running windows 10. I am not a business despite using business grade > hardware.I have tried both 20h2 and 21h1 but no luck. There are no > users signed in when the issues occur and occurs within minutes of > booting up. The only change from the default config is I have it > running on a nonstandard port. Any advice is welcome as I really would > like to upgrade to a newer version. Thanks >