[Xenomai-core] Re: [Xenomai-help] Bad EIP kernel-Oops

2006-09-15 Thread Philippe Gerum
On Fri, 2006-09-15 at 00:12 +0200, Dmitry Adamushko wrote: [...] And it's not a good idea to get ipipe_catch_event() buzy spinning as (as I understand) ipipe_dispatch_event() may take, in general, an unbounded amount of time. Actually, this is not an issue, since there is no requirement

[Xenomai-core] Re: [Xenomai-help] Bad EIP kernel-Oops

2006-09-15 Thread Jan Kiszka
Philippe Gerum wrote: diff -uNrp 2.6.17-ipipe-1.3-10/kernel/ipipe/core.c 2.6.17-ipipe/kernel/ipipe/core.c --- 2.6.17-ipipe-1.3-10/kernel/ipipe/core.c 2006-09-15 10:13:15.0 +0200 +++ 2.6.17-ipipe/kernel/ipipe/core.c 2006-09-14 20:09:22.0 +0200 ... @@ -638,6 +642,7 @@ int

[Xenomai-core] Re: [Xenomai-help] Bad EIP kernel-Oops

2006-09-15 Thread Philippe Gerum
On Fri, 2006-09-15 at 10:33 +0200, Jan Kiszka wrote: Philippe Gerum wrote: diff -uNrp 2.6.17-ipipe-1.3-10/kernel/ipipe/core.c 2.6.17-ipipe/kernel/ipipe/core.c --- 2.6.17-ipipe-1.3-10/kernel/ipipe/core.c 2006-09-15 10:13:15.0 +0200 +++ 2.6.17-ipipe/kernel/ipipe/core.c

[Xenomai-core] Re: [Xenomai-help] Bad EIP kernel-Oops

2006-09-15 Thread Dmitry Adamushko
On 15/09/06, Philippe Gerum [EMAIL PROTECTED] wrote: On Fri, 2006-09-15 at 00:12 +0200, Dmitry Adamushko wrote:[...] And it's not a good idea to get ipipe_catch_event() buzy spinning as (as I understand) ipipe_dispatch_event() may take, in general, an unbounded amount of time.Actually, this is

[Xenomai-core] Re: [Xenomai-help] Bad EIP kernel-Oops

2006-09-14 Thread Dmitry Adamushko
On 13/09/06, Jan Kiszka [EMAIL PROTECTED] wrote: It's the indirect call to the event handler. 8b3: 8b 55 e4mov0xffe4(%ebp),%edx 8b6: 50push %eax- 8b7: ff 94 93 80 22 00 00call *0x2280(%ebx,%edx,4) 8be: 83 c4 0cadd$0xc,%esp 8c1: 85 c0 test %eax,%eaxIn my case the kernel tries to access the

[Xenomai-core] Re: [Xenomai-help] Bad EIP kernel-Oops

2006-09-14 Thread Dmitry Adamushko
The proper fix is to synchronize ipipe_catch_event(..., NULL) with theevent dispatcher, so that any caller could legitimately assume that no subsequent call to the former handler will happen on any CPU after thisservice has returned. Since ipipe_unregister_domain() may alreadylegitimately assume

[Xenomai-core] Re: [Xenomai-help] Bad EIP kernel-Oops

2006-09-12 Thread Dmitry Adamushko
On 12/09/06, Philippe Gerum [EMAIL PROTECTED] wrote: On Tue, 2006-09-12 at 15:24 +0200, Nils Kemper wrote: Hi, I want to use Xenomai, but I get (sometimes, but everytime the same) kernel-Oops just by running xeno-test: [..] Xenomai: stopping native API services. I-pipe: Domain Xenomai

[Xenomai-core] Re: [Xenomai-help] Bad EIP kernel-Oops

2006-09-12 Thread Jan Kiszka
Dmitry Adamushko wrote: On 12/09/06, Philippe Gerum [EMAIL PROTECTED] wrote: On Tue, 2006-09-12 at 15:24 +0200, Nils Kemper wrote: Hi, I want to use Xenomai, but I get (sometimes, but everytime the same) kernel-Oops just by running xeno-test: [..] Xenomai: stopping native API