[okl4-developer] KD# exception delivery error

Geoffrey Lee glee at ok-labs.com
Tue Jul 31 01:16:47 EST 2007


On Sun, Jul 29, 2007 at 08:46:00PM -0400, Jorge Torres wrote:
> Hi okl4.org,
> 
> 
> I get this problem while trying to change the wombat threads scheduler
> register (not for L_Timer and L_syscall), but for (L_1, L_2,
> L_n.................)  threads,  but when I do so i get  "KD# exception
> delivery error" message before jumping into KDB,  what I'm doing is that
> I've replaced the eas_create_thread  and L4_Set_Priority on
> linux/kernel/arch/l4/kernel/process.c with two new functions
> mpsched_eas_create_thread and mpsched_set_priority, the
> mpsched_eas_create_thread is the same as the original eas_create_thread but
> it has a default fixed value for the  scheduler  parameter,  and what the
> mpsched_set_priority does is to send an IPC to a the NEW scheduler (say
> NEWSCHED) thread specifing target TID and priority. after receiving it(the
> NEWSCHED)  simply performs an L4_Set_Priority based on that information. (it
> works=it changes threads priority), but as system runs a tiny bit more, it
> simply drops into such error message, here is the output:
> .
> .

Hi Jorge

There is a hack that uses the scheduler for exceptions as well.  

See pistachio/arch/ia32/src/exception.cc:send_exception_ipc().  I am
guessing that it could not send the exception message, most probably
a syscall, hence it gave this error.


> 
> Anyways does somebudy knows why (where) is this exception delivery error
> happening?
> 
> Oh by the way, I dont know, why is it that every time I change some code on
> which linux kernel code depends on (arch/l4 code), forexample iguana's eas
> code,  i get:
> 
> make[1]: *** [vmlinux] Error 1
> make: *** [_all] Error 2
> 

I am not an expert on the build system, but probably the Linux 
build system does not know code outside of it has changed so
it was not able to build things properly as it got a bit
confused about what needs to be built and what does not.

> so I have to remove the build directory and when I rebuild (no changes made
> on code) things go fine!!.
> 
> Thank you very much for your help,
> 
> 
> Jorge

	- gl


> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer




More information about the Developer mailing list