linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: axel@hh59.org
To: Andrew Morton <akpm@digeo.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	riel@conectiva.com.br
Subject: Re: 2.5.36-mm1
Date: Thu, 19 Sep 2002 17:09:59 +0200	[thread overview]
Message-ID: <20020919150959.GA1887@prester.hh59.org> (raw)
In-Reply-To: <3D8839B5.B37DF31C@digeo.com>

Hi Andrew!

On Wed, 18 Sep 2002, Andrew Morton wrote:

> A reminder that this changes /proc files.  Updated top(1) and
> vmstat(1) source is available at http://surriel.com/procps/

Well. I have retrieved procps from CVS and built it. But then vmstat gets an
segmentation fault. It looks like this..

prester:/root# vmstat
   procs                      memory      swap          io     system
cpu
 r  b  w   swpd   free   buff  cache   si   so    bi    bo   in    cs us sy
id
Segmentation fault
Exit 139

And with strace it looks like this...

...
getdents64(0x5, 0x804d038, 0x400, 0)    = 0
close(5)                                = 0
open("/proc/meminfo", O_RDONLY)         = 5
lseek(5, 0, SEEK_SET)                   = 0
read(5, "MemTotal:       191112 kB\nMemFre"..., 1023) = 543
open("/proc/stat", O_RDONLY)            = 6
read(6, "cpu  35477 2 4565 80407 9871\ncpu"..., 8191) = 815
close(6)                                = 0
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++

Don't know what I have done wrong. Or is the procps package for mm-series a
special one differing from the regular procps by Rik?

Best regards,
Axel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  parent reply	other threads:[~2002-09-19 15:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18  8:30 2.5.36-mm1 Andrew Morton
2002-09-19  8:10 ` 2.5.36-mm1 Robert Love
2002-09-19 15:09 ` axel [this message]
2002-09-19 15:13   ` 2.5.36-mm1 Rik van Riel

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=20020919150959.GA1887@prester.hh59.org \
    --to=axel@hh59.org \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    /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