Re: Invisible process killing the CPU
Laszlo Nagy wrote: 75% user, 24.2% system, 0.0% idle. Despite those stats, I do not see what is eating up 100% cpu time. I already restarted the computer but it is the same. This problem started some hours ago. The CPU is hot, I can feel it on the air stream pouring out the computer case. There are more people that should work with this computer, but they can't. It is terribly slow. Please help me. The system is FreeBSD 6.1. Thanks, Laszlo snip Whats the output of systat -vmstat 1 ? Ta, Joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Invisible process killing the CPU
Whats the output of systat -vmstat 1 ? I have never used this command, so I do not know what it means. :-) 1 usersLoad 1.08 1.13 1.12 Feb 16 17:16 Mem:KBREALVIRTUAL VN PAGER SWAP PAGER Tot Share TotShareFree in out in out Act 132968 13828 43505616452 276648 count All 229824 2154024240645227628 pages Interrupts Proc:r p d s wCsw Trp Sys Int Sof Flt910 cow1014 total 1 62 1165 670221721 5154 6425 62152 wire1: atkb 61680 act 4: sio0 18.2%Sys 0.0%Intr 81.8%User 0.0%Nice 0.0%Idl 104784 inact 3 19: rl0 |||||||||| 2224 cache 20: ata = 274424 free 5 23: vr0 daefr 1006 cpu0: time Namei Name-cacheDir-cache4965 prcfr Calls hits% hits% react 6641059487 90 pdwake 4435 zfodpdpgs Disks ad4 ad6 18 ozfod intrn KB/t 0.00 0.00 %slo-z61456 buf tps 0 05546 tfree39 dirtybuf MB/s 0.00 0.00 35656 desiredvnodes % busy0 04901 numvnodes 1861 freevnodes ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Invisible process killing the CPU
Whats the output of systat -vmstat 1 ? 1 usersLoad 1.20 1.18 1.15 Feb 16 17:54 Mem:KBREALVIRTUAL VN PAGER SWAP PAGER Tot Share TotShareFree in out in out Act 133548 13636 43550416200 272372 count All 234084 2139224241081227768 pages Interrupts Proc:r p d s wCsw Trp Sys Int Sof Flt897 cow1229 total 1 63 1852 656022082 8353 6268 63496 wire1: atkb 62456 act 4: sio0 21.2%Sys 0.0%Intr 78.8%User 0.0%Nice 0.0%Idl 106940 inact 109 19: rl0 |||||||||| 2224 cache 20: ata === 270148 free112 23: vr0 daefr 1008 cpu0: time Namei Name-cacheDir-cache4960 prcfr Calls hits% hits% react 6357356922 90 pdwake 4324 zfodpdpgs Disks ad4 ad6 20 ozfod intrn KB/t 0.00 0.00 %slo-z61456 buf tps 0 05530 tfree44 dirtybuf MB/s 0.00 0.00 35656 desiredvnodes % busy0 05056 numvnodes 1944 freevnodes ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Invisible process killing the CPU
Laszlo Nagy wrote: 75% user, 24.2% system, 0.0% idle. Despite those stats, I do not see what is eating up 100% cpu time. I already restarted the computer but it is the same. This problem started some hours ago. The CPU is hot, I can feel it on the air stream pouring out the computer case. There are more people that should work with this computer, but they can't. It is terribly slow. Please help me. Probably it is not a problem with the kernel (it was working before) but I tried to upgrade to the latest 6.2 branch. make buildworld is so incredibly slow that I don't think it will finish within a week. :-( Compilation starts, but the C compiler only gets about 0.3% CPU time. The remaining 99.7% is lost somewhere. :-( Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Invisible process killing the CPU
Nagy László Zsolt wrote: Laszlo Nagy wrote: 75% user, 24.2% system, 0.0% idle. Despite those stats, I do not see what is eating up 100% cpu time. I already restarted the computer but it is the same. This problem started some hours ago. The CPU is hot, I can feel it on the air stream pouring out the computer case. There are more people that should work with this computer, but they can't. It is terribly slow. Please help me. Probably it is not a problem with the kernel (it was working before) but I tried to upgrade to the latest 6.2 branch. make buildworld is so incredibly slow that I don't think it will finish within a week. :-( Compilation starts, but the C compiler only gets about 0.3% CPU time. The remaining 99.7% is lost somewhere. :-( Laszlo Possible hardware problem perhaps? Are you able to run a burn-in test on the machine? Stabbing in the dark really. Ta, Joe ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Invisible process killing the CPU
Possible hardware problem perhaps? Are you able to run a burn-in test on the machine? What is that? How can I perform that? (Tomorrow the machine will be free, I can play with it.) I can imagine that the processor is overheated and so the frequency was reduced by the BIOS. But that does not explain why I cannot see the process using the CPU. An invisible process eating up CPU time cannot be a hardware problem, can it? Stabbing in the dark really. Mee too. :-( ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Invisible process killing the CPU
On Feb 16, 2007, at 10:54 AM, Nagy László Zsolt wrote: Possible hardware problem perhaps? Are you able to run a burn-in test on the machine? What is that? How can I perform that? (Tomorrow the machine will be free, I can play with it.) I can imagine that the processor is overheated and so the frequency was reduced by the BIOS. But that does not explain why I cannot see the process using the CPU. An invisible process eating up CPU time cannot be a hardware problem, can it? One possibility is that your CPU fan has failed, in which case newer machines would downclock itself extremely in order to avoid burning out-- that might be an explanation for why your performance has decreased so much. Otherwise, try using ps auxw to show all of the processes which are running and see whether there are surprising things, or perhaps try top -o time to sort by accumulated CPU time and look at what's consuming the most... -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Invisible process killing the CPU
Hello Nagy! Fri, Feb 16, 2007 at 05:54:18PM +0100 you wrote: [ systat -vmstat 1 ] Namei Name-cacheDir-cache 4960 prcfr Looks like processes on this system are forking at a rate of 5000/sec. The `last pid' in the top output should be incrementing like mad. The processes finish before top gets to see them for a long enough time, so you don't get to see a single process eating up all cpu. -- DoubleF No virus detected in this message. Ehrm, wait a minute... /kernel: pid 56921 (antivirus), uid 32000: exited on signal 9 Oh yes, no virus:) pgpHHUve85SeK.pgp Description: PGP signature
Re: Invisible process killing the CPU
One possibility is that your CPU fan has failed, in which case newer machines would downclock itself extremely in order to avoid burning out-- that might be an explanation for why your performance has decreased so much. The cpu fan is not failed. This was the first thing I checked before I wrote to this list. The fan is spinning. In my understanding, if the freq goes down then each program will use more of the total CPU time because of the less computing capacity. So, having two processes, instead of 10% + 10% (total 20%) it would be 50% + 50% (total 100%). But this is not the case. On this computer, everything is at 0% but the total CPU is at 100%. Otherwise, try using ps auxw to show all of the processes which are running and see whether there are surprising things, I do not know enough about FreeBSD to tell what is surprising. :-( Would it help to send the output here? or perhaps try top -o time to sort by accumulated CPU time and look at what's consuming the most... Most CPU time is for the ppp daemon: PID USERNAME THR PRI NICE SIZERES STATETIME WCPU COMMAND 244 root 1 960 3404K 2084K select 1:40 0.00% ppp but I don't think that ppp is causing the problem, since it is at WCPU 0%. Best, Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Invisible process killing the CPU
Hello Nagy! Fri, Feb 16, 2007 at 10:25:03PM +0300 I wrote: [ systat -vmstat 1 ] Namei Name-cacheDir-cache 4960 prcfr Looks like processes on this system are forking at a rate of 5000/sec. Ouch, that's pages freed by exiting processes, not process forks (gotta get some sleep). Anyway, if this is persistent, then some processes are exiting all the time, and they have to get created somehow, so the scenario is the same... -- DoubleF No virus detected in this message. Ehrm, wait a minute... /kernel: pid 56921 (antivirus), uid 32000: exited on signal 9 Oh yes, no virus:) pgpS17j1kaAjF.pgp Description: PGP signature
Re: Invisible process killing the CPU
Ouch, that's pages freed by exiting processes, not process forks (gotta get some sleep). Anyway, if this is persistent, then some processes are exiting all the time, and they have to get created somehow, so the scenario is the same... Yess! That was it! Thank you so much! :-) There was a program that forked another in a loop. The forked program was working for days, but now it is throwing an error. You were right. The parent process was starting the child process at an incredibly rate. And you were also right in that, since the child processes were running only for some msec, they where not recognized by top and so they were not shown. You are a genious! :-) Thank you! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Invisible process killing the CPU
[ systat -vmstat 1 ] Namei Name-cacheDir-cache 4960 prcfr Looks like processes on this system are forking at a rate of 5000/sec. Ouch, that's pages freed by exiting processes, not process forks (gotta get some sleep). Anyway, if this is persistent, then some processes are exiting all the time, and they have to get created somehow, so the scenario is the same... Now the CPU is almost idle. :-) However, the prcfr value is still between 400 and 500. Is that normal? Laszlo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
