From: Andrey Repin <anrdaemon@yandex.ru>
To: "Christoph Lüders" <lueders@cfos.de>, cygwin@cygwin.com
Subject: Re: SSHD causes 100% CPU load
Date: Tue, 4 May 2021 18:14:52 +0300 [thread overview]
Message-ID: <854495804.20210504181452@yandex.ru> (raw)
In-Reply-To: <282781730.20210428091007@cfos.de>
Greetings, Christoph Lüders!
This list is in "no top posting, please" mode.
> Wednesday, April 28, 2021, 06:23:02, "Andrey Repin" wrote:
>> Greetings, Christoph Lüders!
>>> I run cygwin 32-bit on Windows 10 Pro Build 19042. Cygwin is 3.2.0-1,
>>> openssh is 8.5p1-1.
>>> I use sshd to access the machine from afar. I notice (often multiple)
>>> processes of sshd.exe with 100% CPU load.
>> https://cygwin.com/pipermail/cygwin/2021-April/248299.html
>> https://cygwin.com/pipermail/cygwin/2021-April/248309.html
> thanks for the link. Am I mistaken or was there no solution
> mentioned? Do you have any advice how to fix this problem?
No, you are not. There were multiple reports (I only listed recent ones), but
no solution yet.
>>> A stack shown with procexp has function names like
>>> "cygwin1.dll!acl_get_perm" and "cygwin1.dll!_assert".
>>> Can anyone give me some advice how to proceed further? I have updated
>>> to the latest cygwin multiple times; reboot doesn't help either.
--
With best regards,
Andrey Repin
Tuesday, May 4, 2021 18:13:40
Sorry for my terrible english...
next prev parent reply other threads:[~2021-05-04 15:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 10:42 Christoph Lüders
2021-04-28 4:23 ` Andrey Repin
2021-04-28 7:10 ` Christoph Lüders
2021-05-04 15:14 ` Andrey Repin [this message]
2021-05-04 21:56 ` Brian Inglis
2021-08-05 10:12 ` Takashi Yano
2021-08-05 15:07 ` Corinna Vinschen
2021-08-05 16:43 ` Takashi Yano
2021-08-06 1:55 ` Takashi Yano
2021-08-06 9:11 ` Corinna Vinschen
2021-08-06 11:14 ` Takashi Yano
2021-08-06 13:59 ` Corinna Vinschen
2021-08-06 11:30 ` Takashi Yano
2021-08-06 12:35 ` Takashi Yano
2021-08-06 13:57 ` Corinna Vinschen
2021-08-06 14:16 ` ASSI
2021-08-06 14:27 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=854495804.20210504181452@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=lueders@cfos.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).