mersenneforum.org Utterly surreal OS bug
 Register FAQ Search Today's Posts Mark Forums Read

 2011-01-19, 00:03 #1 fivemack (loop (#_fork))     Feb 2006 Cambridge, England 33·239 Posts Utterly surreal OS bug Code: nfsslave2@cow:/home/nfsworld/2+956/linalg$ps -L 11743 PID LWP TTY STAT TIME COMMAND 11743 11743 ? Rl 9645:56 ../../msieve-svn/trunk/msieve-td130 -v -nc -t 4 11743 21509 ? Rl 8653:20 ../../msieve-svn/trunk/msieve-td130 -v -nc -t 4 11743 21510 ? Rl 9014:08 ../../msieve-svn/trunk/msieve-td130 -v -nc -t 4 11743 21515 ? Rl 9043:40 ../../msieve-svn/trunk/msieve-td130 -v -nc -t 4 nfsslave2@cow:/home/nfsworld/2+956/linalg$ ps 11743 PID TTY STAT TIME COMMAND 11743 ? Rl 24260266:53 ../../msieve-svn/trunk/msieve-td130 -v -nc -t 4 (and whilst the times reported by -L go up at a rate of about one minute per minute, the one reported by 'ps' on its own stays at that ridiculous value) I don't think I need to do anything about this, but it's most peculiar. Process 11743 also doesn't appear in 'top'.
2011-01-19, 07:42   #2
xilman
Bamboozled!

"𒉺𒌌𒇷𒆷𒀭"
May 2003
Down not across

2·3·7·271 Posts

Quote:
 Originally Posted by fivemack Code: nfsslave2@cow:/home/nfsworld/2+956/linalg$ps -L 11743 PID LWP TTY STAT TIME COMMAND 11743 11743 ? Rl 9645:56 ../../msieve-svn/trunk/msieve-td130 -v -nc -t 4 11743 21509 ? Rl 8653:20 ../../msieve-svn/trunk/msieve-td130 -v -nc -t 4 11743 21510 ? Rl 9014:08 ../../msieve-svn/trunk/msieve-td130 -v -nc -t 4 11743 21515 ? Rl 9043:40 ../../msieve-svn/trunk/msieve-td130 -v -nc -t 4 nfsslave2@cow:/home/nfsworld/2+956/linalg$ ps 11743 PID TTY STAT TIME COMMAND 11743 ? Rl 24260266:53 ../../msieve-svn/trunk/msieve-td130 -v -nc -t 4 (and whilst the times reported by -L go up at a rate of about one minute per minute, the one reported by 'ps' on its own stays at that ridiculous value) I don't think I need to do anything about this, but it's most peculiar. Process 11743 also doesn't appear in 'top'.
I saw exactly the same thing when doing the LA for a c178 recently. I believe that the author of top(1) didn't expect a single process to clock up so much time and a variable overflowed. I'm almost, but not quite, tempted to check the source of top(1) to find out. The underlying bug is, presumably, in the code that implements the /proc/*/stat interface.

Paul

Last fiddled with by xilman on 2011-01-19 at 07:45

All times are UTC. The time now is 02:40.

Sun Jul 3 02:40:37 UTC 2022 up 80 days, 41 mins, 0 users, load averages: 1.33, 1.24, 1.21