Re: How can process in STOP state consume 200% CPU?
Yuri wrote: > On 06/28/2011 17:24, Sergey Babkin wrote: > > Most probably the process is running in an endless loop in the > > kernel mode ... While it's in the kernel mode, you can't do > > anything to it other than use the kernel debugger. > > How is this normally possible to make program to loop in kernel > mode on -STABLE kernel? Doesn't this mean bug in kernel? In kernel code, but not necessarily in the -STABLE kernel itself -- there could be a problem in a kernel module. I haven't checked, but would not be surprised if VirtualBox included one. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Re: How can process in STOP state consume 200% CPU?
Jun 28, 2011 04:29:35 PM, jh...@dataix.net wrote: >> I got Vir= tualBox process in a strange state. It has the status STOP but >>= shows by top as consuming 200% CPU for a very long time. >> How i= s this possible and what does this mean? Process time stays at 0:00 >= ;> TIME. kill -9 doesn't kill it. > > >I would suppose= that because you stopped the clients frontend that the >backend has = not been notified and is doing its best to draw to the >screen causin= g a high CPU usage. (Sorry about quoting, it doesn't always work wel= l from the web client). Most probably the process is running in an endle= ss loop in the kernel mode. Where it got after entering the STOP state. = Remember, the signals are processed only after the process exits from th= e kernel mode to the user mode, and so are the scheduling states. While = it's in the kernel mode, you can't do anything to it other than use the = kernel debugger. -SB ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: How can process in STOP state consume 200% CPU?
On 06/28/2011 17:24, Sergey Babkin wrote: (Sorry about quoting, it doesn't always work well from the web client). Most probably the process is running in an endless loop in the kernel mode. Where it got after entering the STOP state. Remember, the signals are processed only after the process exits from the kernel mode to the user mode, and so are the scheduling states. While it's in the kernel mode, you can't do anything to it other than use the kernel debugger. How is this normally possible to make program to loop in kernel mode on -STABLE kernel? Doesn't this mean bug in kernel? Yuri ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: How can process in STOP state consume 200% CPU?
Yuri wrote: > kill -9 doesn't kill it. I think I've seen this before; it looks as if, since the process is STOPped, the "kill -9" remains pending rather than being acted upon. I _think_ you can make the process go away by doing a "kill -CONT" after the "kill -9". No idea how a STOPped process can continue to consume CPU, unless in an infinite loop at elevated interupt level (and in that case the "kill -CONT" may not work -- you may need to drop into kdb, try to do some debugging and/or get a dump, and then reboot). ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: How can process in STOP state consume 200% CPU?
On Tue, Jun 28, 2011 at 11:40:29AM -0700, Yuri wrote: > I got VirtualBox process in a strange state. It has the status STOP but > shows by top as consuming 200% CPU for a very long time. > How is this possible and what does this mean? Process time stays at 0:00 > TIME. kill -9 doesn't kill it. > kill -CONT >PID USERNAME THR PRI NICE SIZERES STATE C TIMECPU > COMMAND > 9390 yuri3 440 508M 246M STOP3 0:00 200.00% > VirtualBox > <...> > > 8.2-STABLE > I would suppose that because you stopped the clients frontend that the backend has not been notified and is doing its best to draw to the screen causing a high CPU usage. Though you have used -STOP on the process youll still have to -CONT after the -KILL for it to actually exit since the process is effectively stopped its not going to abide by any further signals until it recieves -CONT. Anyway now you know not to use -STOP on that process ;) Is it supposed to do anything with the stop signal ? has it been documented in VB ? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: How can process in STOP state consume 200% CPU?
On Tue, Jun 28, 2011 at 11:40 AM, Yuri wrote: > I got VirtualBox process in a strange state. It has the status STOP but > shows by top as consuming 200% CPU for a very long time. > How is this possible and what does this mean? Process time stays at 0:00 > TIME. kill -9 doesn't kill it. > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME CPU > COMMAND > 9390 yuri 3 44 0 508M 246M STOP 3 0:00 200.00% > VirtualBox Can you send the output of these various procstat commands: procstat -kk 9390 procstat -f 9390 procstat -t 9390 procstat -i 9390 | grep -vE -- '---$' procstat -j 9390 | grep -vE -- '--$' As well as ps output for the process: ps auwwx | grep -w 9390 Also ktrace'ing the process and sending a kdump (or part of it) could be useful. Thanks, Josh ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
How can process in STOP state consume 200% CPU?
I got VirtualBox process in a strange state. It has the status STOP but shows by top as consuming 200% CPU for a very long time. How is this possible and what does this mean? Process time stays at 0:00 TIME. kill -9 doesn't kill it. PID USERNAME THR PRI NICE SIZERES STATE C TIMECPU COMMAND 9390 yuri3 440 508M 246M STOP3 0:00 200.00% VirtualBox <...> 8.2-STABLE Yuri ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
