Skip site navigation (1)Skip section navigation (2)
Date:      07 Mar 1996 13:22:29 -0500
From:      Robert Sanders <rsanders@mindspring.com>
To:        freebsd-current@freebsd.org
Subject:   ps and u_map allocation problems with kernel supped Mar 7
Message-ID:  <kn68cgg3ve.fsf@xena.mindspring.com>

next in thread | raw e-mail | index | archive | help
$ date
Thu Mar  7 13:11:58 EST 1996

$ uptime
 1:12PM  up 25 mins, 11 users, load averages: 2.63, 1.42, 0.74

$ ps auxw
USER       PID %CPU %MEM   VSZ  RSS  TT  STAT STARTED       TIME COMMAND
root       589  4.0  2.0   216  600  p9  S+   14Nov63    0:00.03 cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -
root       190  4.6 16.4  3652 4968  ??  S    11Nov63    0:18.97 X -bpp 32 (XF86_S3)
root       588  1.0  1.0   452  304  p9  S+   14Nov63    0:00.01 /bin/sh -ec cc -c -O -W -Wreturn-type -Wcomment -Wredundant-decls 
root         3  0.0  0.1     0   12  ??  DL    9Nov63    0:02.79  (vmdaemon)
root         4  0.0  0.1     0   12  ??  DL    9Nov63    0:00.25  (update)
root        60  0.0  0.6   420  176  ??  Ss    9Nov63    0:03.53 ppp -auto c-themaxx-sync
root        76  0.0  0.3   184   96  ??  Ss   10Nov63    0:00.11 syslogd
root        84  0.0  0.6   420  160  ??  S<s  10Nov63    0:00.26 xntpd
daemon      88  0.0  0.0   176   24  ??  IWs  10Nov63    0:00.01 portmap
root        97  0.0  0.0   188   24  ??  IWs  10Nov63    0:00.04 inetd
root       104  0.0  0.4   236  120  ??  Ss   10Nov63    0:00.05 cron
root       106  0.0  0.0   192   20  ??  IWs  10Nov63    0:00.03 lpd
...

$ cat /proc/76/status
syslogd 76 1 76 76 -1,-1 sldr 826220915,531841 0,33902 0,73456 select 0 0 0,0

$ ctime.pl 826220915
Thu Mar  7 12:48:35 1996

dmesg output and config file are available at
  http://www.mindspring.com/~rsanders/freebsd/dmesg
  http://www.mindspring.com/~rsanders/freebsd/HROTHGAR

I've tried rebuilding libkvm and ps, but it didn't help.

Also, I got two or three "vm_fork: u_map allocation failed" panic
messages in the last two days.  My root partition doesn't have space
for a kernel built with config -g right now, so I can't give much
more information.

I've been tracking -current pretty closely on this machine, so both
problems must have appeared in the last week or so.

  -- Robert



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?kn68cgg3ve.fsf>