04/03/2012 8:47 PM
post92433
|
Stopping ham by executing the command hamctrl -stop makes few running threads inherits the ham priority and make the
system appear non-responsive. It appears that one of the thread which can occupy the entire cpu time, if allowed, is
inheriting the ham priority and not allowing any other threads a chance to run.
Any thoughts on how a thread can inherit the ham priority when the ham is stopped?
|
|
|