linux-um archives
 help / color / mirror / Atom feed
From: "Christopher S. Aker" <caker@theshore.net>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] 2.6.10-um, /proc/stat is missing information
Date: Thu, 13 Jan 2005 19:09:50 -0600	[thread overview]
Message-ID: <001401c4f9d5$c03c3ce0$0201a8c0@hawk> (raw)
In-Reply-To: 200501140150.08487.blaisorblade@yahoo.it

> 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).

# cat /proc/stat 
cpu  93 0 0 0 0 4129 0
cpu0 93 0 0 0 0 4129 0
intr 17406 6535 0 90 0 10414 309 0 0 0 0 1 57 0 0
ctxt 20120
btime 1105664741
processes 1564
procs_running 1
procs_blocked 0

Looks like that was the fix.  And I see it went in with 2.6.10-mm1.

Thanks BB,
-Chris


-------------------------------------------------------
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

  reply	other threads:[~2005-01-14  1:08 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
2005-01-14  1:09   ` Christopher S. Aker [this message]
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='001401c4f9d5$c03c3ce0$0201a8c0@hawk' \
    --to=caker@theshore.net \
    --cc=blaisorblade@yahoo.it \
    --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