Re: How can process in STOP state consume 200% CPU?

2011-06-28 Thread perryh
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 l

Re: Re: How can process in STOP state consume 200% CPU?

2011-06-28 Thread Sergey Babkin
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.

Re: How can process in STOP state consume 200% CPU?

2011-06-28 Thread Yuri
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 e

Re: How can process in STOP state consume 200% CPU?

2011-06-28 Thread perryh
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 c

Re: How can process in STOP state consume 200% CPU?

2011-06-28 Thread jhell
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.

Re: How can process in STOP state consume 200% CPU?

2011-06-28 Thread Josh Carroll
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 US