From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net,
Jeff Dike <jdike@addtoit.com>
Cc: "Christopher S. Aker" <caker@theshore.net>
Subject: Re: [uml-devel] 2.6.10-um, /proc/stat is missing information
Date: Fri, 14 Jan 2005 01:50:08 +0100 [thread overview]
Message-ID: <200501140150.08487.blaisorblade@yahoo.it> (raw)
In-Reply-To: <001901c4f9ca$f72825d0$0201a8c0@hawk>
On Friday 14 January 2005 00:52, Christopher S. Aker wrote:
> I just verified this on a Debian install and an FC2 install.
>
> Moving from 2.6.9-bb4 to 2.6.10-um vanilla, top reports either 100% user,
> or 100% idle.
>
> [2.6.10] # cat /proc/stat
> cpu 645 1 0 0 0 0 0
> cpu0 645 1 0 0 0 0 0
> intr 63462 54820 0 174 10 8270 93 0 0 0 0 1 94 0 0
> ctxt 108849
> btime 1105659428
> processes 1542
> procs_running 2
> procs_blocked 0
>
> [2.6.9-bb4] # cat /proc/stat
> cpu 407 0 1989 7536 252 28 1
> cpu0 407 0 1989 7536 252 28 1
> intr 15430 10185 0 48 1 5035 134 0 0 0 0 0 27 0 0
> ctxt 10966
> btime 1105660071
> processes 1501
> procs_running 1
> procs_blocked 0
>
> Looks like some information is missing from /proc/stat in 2.6.10.
>
> -Chris
Try retesting after applying update-process-times.patch (the one for the crash
you were seeing): that patch was not merged by maintainers in mainline,
though IIRC it was sent in the right time frame (maybe because they weren't
marked as urgent, or because they were a lot of patches, which is also
possible).
About this, we should try for the future (even if this one was a special case,
having to merge tens of invasive patches for security purposes is not nice)
to merge big things only before -rc1 and -rc2, since after those releases
things must calm down. This recommendation must be updated with changes in
the release cycle followed by Linus, obviously.
Bye
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-01-14 0:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 23:52 [uml-devel] 2.6.10-um, /proc/stat is missing information Christopher S. Aker
2005-01-14 0:50 ` Blaisorblade [this message]
2005-01-14 1:09 ` Christopher S. Aker
2005-01-14 0:52 ` Blaisorblade
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=200501140150.08487.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=caker@theshore.net \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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