Date: Sun, 8 Nov 1998 12:58:24 -0500 (EST) From: robert+freebsd@fledge.watson.org To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: kern/8604: Robert Watson <robert@fledge.watson.org> Message-ID: <199811081758.MAA01130@sleipnir.watson.org>
next in thread | raw e-mail | index | archive | help
>Number: 8604 >Category: kern >Synopsis: ps u gets confused about process start times >Confidential: yes >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Nov 8 10:00:01 PST 1998 >Last-Modified: >Originator: Robert Watson >Organization: >Release: FreeBSD 3.0-CURRENT i386 >Environment: FreeBSD 3.0 (several days old -current): the machine is a notebook and spends a fair amount of time suspended during travel and while I am asleep. :) I suspect that that is the valid context. The machine is also running Coda. >Description: ps aux gives confused output about process start time after waking up: USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 288 1.1 16.6 19448 7764 ?? S 28Oct98 150:23.97 /usr/X11R6/bin/X root 1 0.0 0.2 496 72 ?? Is 28Oct98 0:00.49 /sbin/init -- root 2 0.0 0.0 0 0 ?? DL 28Oct98 7:35.93 (pagedaemon) root 3 0.0 0.0 0 0 ?? DL 28Oct98 0:14.31 (vmdaemon) root 4 0.0 0.0 0 0 ?? DL 28Oct98 5:25.43 (syncer) root 91 0.0 0.4 804 172 ?? Ss 28Oct98 0:11.62 syslogd daemon 101 0.0 0.0 788 0 ?? IWs - 0:00.00 (portmap) root 114 0.0 0.0 532 0 ?? IWs - 0:00.00 (mountd) root 117 0.0 0.0 316 0 ?? IWs - 0:00.00 (nfsd) root 119 0.0 0.0 296 0 ?? IW - 0:00.00 (nfsd) root 120 0.0 0.0 296 0 ?? IW - 0:00.00 (nfsd) root 121 0.0 0.0 296 0 ?? IW - 0:00.00 (nfsd) .. robert 1075 0.0 2.0 1328 904 p2 Ds 12:51PM 0:00.12 -csh (tcsh) robert 1078 0.0 0.6 408 280 p2 R+ 12:53PM 0:00.00 ps -aux root 0 0.0 0.0 0 0 ?? DLs 28Oct98 0:02.06 (swapper) robert 1079 0.0 2.0 1328 904 p2 RV 12:53PM 0:00.00 -csh (tcsh) Some processes have a valid start time; others do not. There doesn't even seem to be a relationship between 'long running' and whether it happens or not. I have not seen this behavior before. cd'ing to /proc witnesses the same effect: % cd /proc/299 # dud process % more status sh 299 289 299 0 -1,-1 noflags -1,-1 0,9105 0,27317 wait 1000 1000 1000,1000,100 0,0,5,68,500,501,502,801,802,900,1004,1060 % cd /proc/309 # not a dud process % more status kwm 309 299 299 0 -1,-1 noflags 909631349,791520 178,939360 102,121346 select 10 00 1000 1000,1000,1000,0,5,68,500,501,502,801,802,900,1004,1060 % >How-To-Repeat: Not repeatable, or at least, I have not seen the behavior before. >Fix: No known fix -- just a symptom report to see if anyone else has seen this either. >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811081758.MAA01130>