Re: arch_int_restore_interrupts

On 8/5/07, Ingo Weinhold <bonefish-CFLBMwTPW48UNGrzBIF7/[email protected]> wrote:
>
> That's hard to say. If the problem doesn't occur any longer, after you
> disable debug output, then it's pretty likely. In that case, if you mostly
> have interrupts enabled while calling dprintf() from your thread, you
> might
> indeed think about implementing the second dprintf() path, as it might
> improve the situation.


I haven't disabled debug output yet, and the problem has just occurred
again.
I realized the scheduler doesn't stop, as getting in and out of KDL gives me
a different
running thread (even if always the very same few). System though, does not
respond to
the mouse.

Note, that our current scheduler seems to have a problem with higher
> priority
> threads starving lower priority ones. Doing a lot (that includes debug
> output) in a high priority thread can quite likely cause system blocking
> as
> you describe it.



Thanks again for you help.

CU, Ingo


Salvo

-- 
Salvatore Benedetto (a.k.a. emitrax)
Student of Computer and Telecommunications Engineering
University of Messina (Italy)
www.messinalug.org

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

_______________________________________________
Open-beos-kernel-devel mailing list
Open-beos-kernel-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/open-beos-kernel-devel