From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-developers@cygwin.com
Subject: Re: load average calculation failing -- fixed by Windows update
Date: Thu, 12 May 2022 10:43:29 +0200 [thread overview]
Message-ID: <YnzIsZmKOOIVrlyE@calimero.vinschen.de> (raw)
In-Reply-To: <77d75d10-cdcb-c041-5abe-f022fc6ec46b@maxrnd.com>
On May 12 01:24, Mark Geisert wrote:
> Corinna Vinschen wrote:
> > On May 11 16:40, Mark Geisert wrote:
> > > Jon Turney wrote:
> > > > On 10/05/2022 09:34, Mark Geisert wrote:
> > > > > Corinna Vinschen wrote:
> > > > > > [redirect back to cygwin-developers]
> > > >
> > > > > >
> > > > > > > > 0x800007D0 == PDH_CSTATUS_NO_MACHINE. The code (at line 68 mentioned
> > > > > >
> > > > > > This is a weird error.
> > > > > >
> > > > > > "The path did not contain a computer name and the function was unable
> > > > > > to retrieve the local computer name."
> > > > > >
> > > > > > Yeah, sure.
> > > > > >
> > > > > > Mark, did you try to add the computer name to the path by calling
> > > > > > GetComputerName() in load_init?
> > > >
> > > > As we've seen before, this error also seems to be also used for "not
> > > > authorized" problems.
> > > >
> > > > https://sourceware.org/git/?p=newlib-cygwin.git;a=commitdiff;h=de7f13aa9acec022ad1e4b3f929d4dc982ddf60b
> > >
> > > Sheesh. This all seems entirely too complicated.
> > >
> > > But thankfully, after installing latest Windows patches (from yesterday's MS
> > > Patch Tuesday) I find myself on W10 21H2 Build 19044.1706. Xload, uptime,
> > > and Jon's initial PoC code now show good load averages. I had previously
> > > been on Build 19044.1645.
> > >
> > > The first counter read now gets error 0xC0000BC6 == PDH_INVALID_DATA, but no
> > > errors on subsequent counter reads. This sounds like it now matches what
> > > Corinna reported for W11. I wonder if she's running build 1706 already.
> > >
> > > It seems to me MS broke PDH or its interfacing for one build, 1645, and
> > > fixed it for the next, 1706. That's all I can surmise from the data we
> > > have.
> > >
> > > I think my work and/or damage here (on this topic) is done.
> >
> > You're the luck one then. It still doesn't work for me on W10 21H1
> > and W11.
>
> What Windows build(s) are you running? The 'ver' command inside a Command
> Prompt window is the easiest way to determine.
>
> Also, both my machines were running build 1645 but it was a Windows Home
> machine that had the issue; the Windows Pro machine was fine. So many
> variables....
Both domain member machine, Windows 10 version 10.0.19043.1706 and
Windows 11 version 10.0.22000.675. Both Enterprise editions.
Corinna
next prev parent reply other threads:[~2022-05-12 8:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.BSF.4.63.2205051618470.42373@m0.truegem.net>
2022-05-08 7:01 ` load average calculation failing Mark Geisert
[not found] ` <223aa826-7bf9-281a-aed8-e16349de5b96@dronecode.org.uk>
2022-05-09 8:45 ` Corinna Vinschen
2022-05-09 8:53 ` Corinna Vinschen
2022-05-10 8:34 ` Mark Geisert
2022-05-10 13:37 ` Jon Turney
2022-05-11 23:40 ` load average calculation failing -- fixed by Windows update Mark Geisert
2022-05-12 8:17 ` Corinna Vinschen
2022-05-12 8:24 ` Mark Geisert
2022-05-12 8:43 ` Corinna Vinschen [this message]
2022-05-12 9:48 ` Corinna Vinschen
2022-05-13 10:34 ` Jon Turney
2022-05-13 11:04 ` Corinna Vinschen
2022-05-13 11:05 ` Corinna Vinschen
2022-05-16 5:25 ` load average calculation imperfections Mark Geisert
2022-05-16 16:49 ` Jon Turney
2022-05-17 5:39 ` Mark Geisert
2022-05-17 14:48 ` load average calculation failing -- fixed by Windows update Jon Turney
2022-05-17 19:48 ` Mark Geisert
2022-05-09 11:29 ` load average calculation failing Jon Turney
2022-05-10 8:21 ` Mark Geisert
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=YnzIsZmKOOIVrlyE@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-developers@cygwin.com \
/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).