From: Willy Tarreau <willy@w.ods.org>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: lkml <linux-kernel@vger.kernel.org>, Mark Cooke <mpc@star.sr.bham.ac.uk>
Subject: Re: pre6 oddity (fwd)
Date: Sun, 20 Jul 2003 10:13:21 +0200 [thread overview]
Message-ID: <20030720081321.GC643@alpha.home.local> (raw)
In-Reply-To: <Pine.LNX.4.55L.0307191805200.11090@freak.distro.conectiva>
Hi Marcelo,
This was a procps bug. 2.0.11 I believe. There was something like a
printf("%ull", prio) with prio=-1, which prints 2^64-1 (the high number seen
here). Upgrading to 2.0.13 fixed the problem for me.
Cheers,
Willy
On Sat, Jul 19, 2003 at 06:07:42PM -0300, Marcelo Tosatti wrote:
>
> Bogus.
>
> ---------- Forwarded message ----------
> Date: 19 Jul 2003 08:54:55 +0100
> From: Mark Cooke <mpc@star.sr.bham.ac.uk>
> To: Marcelo Tosatti <marcelo@conectiva.com.br>
> Subject: pre6 oddity
>
> Hi Marcelo,
>
> On two of my machines running pre6, I am seeing top report very odd
> priorities for two kernel tasks:
>
> PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU
> COMMAND
>
> 8 root 18446744073709551615 -20 0 0 0 SW< 0.0
> 0.0 0:00 0 mdrecoveryd
> 16 root 18446744073709551615 -20 0 0 0 SW< 0.0
> 0.0 0:00 0 raid1d
>
>
> Something related to the scheduling changes going on ?
>
> (RedHat 9 base system)
>
> Mark
>
> --
> Mark Cooke <mpc@star.sr.bham.ac.uk>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-07-20 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-19 21:07 pre6 oddity (fwd) Marcelo Tosatti
2003-07-20 8:13 ` Willy Tarreau [this message]
2003-07-22 8:01 ` Mark Cooke
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=20030720081321.GC643@alpha.home.local \
--to=willy@w.ods.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=mpc@star.sr.bham.ac.uk \
/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