public inbox for cygwin-developers@cygwin.com
 help / color / mirror / Atom feed
From: Mark Geisert <mark@maxrnd.com>
To: Cygwin-developers <cygwin-developers@cygwin.com>
Subject: Re: load average calculation failing
Date: Sun, 8 May 2022 00:01:22 -0700	[thread overview]
Message-ID: <3a3edd10-2617-0919-4eb0-7ca965b48963@maxrnd.com> (raw)
In-Reply-To: <Pine.BSF.4.63.2205051618470.42373@m0.truegem.net>

Mark Geisert wrote (on the main Cygwin mailing list):
> I've recently noticed that the 'xload' I routinely run shows zero load even with 
> compute-bound processes running.  This is on both Cygwin pre-3.4.0 as well as 
> 3.3.4.  A test program, shown below, indicates that getloadavg() is returning with 
> 0 status, i.e. not an error but no elems
> of the passed-in array updated.
> 
> Stepping with gdb through the test program seems weird within the 
> loadavginfo::load_init method.  Single-stepping at line loadavg.cc:68 goes to 
> strace.h:52 and then to _sigbe ?!
> 
> I had recently updated both Cygwin and Windows 10 to latest at the same time so I 
> cannot say when the failure started.  Last day or two at most.
> 
> ..mark
> 
> -------------------
> #define _GNU_SOURCE
> #include <stdio.h>
> #include <stdlib.h>
> 
> int
> main (int argc, char **argv)
> {
>      double loadavg[3];
> 
>      int res = getloadavg (loadavg, 3);
>      if (res == -1)
>          return 0xFF;
>      if (res > 0)
>          for (int i = 0; i < res; i++)
>              printf ("%f.2 ", loadavg[i]);
> 
>      return res;
> }

I've debugged a bit further..  Within Cygwin's loadavg.cc:load_init(), the 
PdhOpenQueryW() call returns successfully.  The subsequent PdhAddEnglishCounterW() 
call is unsuccessful.  It returns status 0x800007D0 == PDH_CSTATUS_NO_MACHINE. 
The code (at line 68 mentioned above) calls debug_printf() to conditionally 
display the error, which is what leads to the strace.h and _sigbe; that's fine.

The weird PDH_CSTATUS_NO_MACHINE is the problem.  I'll try running the example 
from an elevated shell.  Or rebooting the machine.  After that it's consulting 
some oracle TBD. :-(

..mark

       reply	other threads:[~2022-05-08  7:01 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 ` Mark Geisert [this message]
     [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
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=3a3edd10-2617-0919-4eb0-7ca965b48963@maxrnd.com \
    --to=mark@maxrnd.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).