Re: [Xenomai-core] [Xenomai-help] comedi rtdm_interface.c build fails
On Mon, 2009-06-29 at 17:16 +0200, Stefan Kisdaroczi wrote: Hi, comedi rtdm_interface.c build fails (typo), patch attached. breaking commit: Fri, 12 Jun 2009 08:03:39 + (10:03 +0200) e20bd3f2613a052b93c1a4ecada6623a5332f54c Made conditional inclusion of owner field in struct proc_dir_entry due to changes in 2.6.30. Error: CC [M] drivers/xenomai/comedi/rtdm_interface.o drivers/xenomai/comedi/rtdm_interface.c: In function comedi_init_proc: drivers/xenomai/comedi/rtdm_interface.c:81: error: enrty undeclared (first use in this function) drivers/xenomai/comedi/rtdm_interface.c:81: error: (Each undeclared identifier is reported only once drivers/xenomai/comedi/rtdm_interface.c:81: error: for each function it appears in.) Thanks for the feedback. Please Cc: Alex for Comedi/RTDM related issues, and probably xenomai-core instead of -help as well. TIA, plain text document attachment (xeno_comedi_rtdm.patch) diff --git a/ksrc/drivers/comedi/rtdm_interface.c b/ksrc/drivers/comedi/rtdm_interface.c index d4ea5ac..73687b6 100644 --- a/ksrc/drivers/comedi/rtdm_interface.c +++ b/ksrc/drivers/comedi/rtdm_interface.c @@ -78,7 +78,7 @@ int comedi_init_proc(void) entry-data = NULL; entry-write_proc = NULL; entry-read_proc = comedi_rdproc_devs; - wrap_proc_dir_entry_owner(enrty); + wrap_proc_dir_entry_owner(entry); /* Creates the drivers related file */ entry = create_proc_entry(drivers, 0444, comedi_proc_root); @@ -93,7 +93,7 @@ int comedi_init_proc(void) entry-data = NULL; entry-write_proc = NULL; entry-read_proc = comedi_rdproc_drvs; - wrap_proc_dir_entry_owner(enrty); + wrap_proc_dir_entry_owner(entry); return 0; ___ Xenomai-help mailing list xenomai-h...@gna.org https://mail.gna.org/listinfo/xenomai-help -- Philippe. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
[Xenomai-core] x86: Endless minor faults
Hi all, seen such loops before? This particular trace is from a 2.6.29.3 kernel with ipipe-2.3-01 (SMP/PREEMPT_VOLUNTARY), but the same happens with 2.6.29.5/2.3-03: :| +func-6530.084 __ipipe_handle_exception+0x11 (page_fault+0x26) :| +func-6530.096 ipipe_check_context+0xd (__ipipe_handle_exception+0x71) :| #end 0x8000 -6530.069 do_page_fault+0x33 (__ipipe_handle_exception+0x1ff) :#func-6530.078 __ipipe_unstall_root+0x9 (do_page_fault+0x3cb) :| #begin 0x8000 -6530.068 __ipipe_unstall_root+0x34 (do_page_fault+0x3cb) :| +end 0x8000 -6530.069 __ipipe_unstall_root+0x59 (do_page_fault+0x3cb) :+func-6530.060 down_read_trylock+0x4 (do_page_fault+0x424) :+func-6530.068 _spin_lock_irqsave+0x9 (__down_read_trylock+0x16) :+func-6530.108 ipipe_check_context+0xd (_spin_lock_irqsave+0x1d) :#func-6520.066 _spin_unlock_irqrestore+0x4 (__down_read_trylock+0x3f) :#func-6520.069 __ipipe_restore_root+0x4 (_spin_unlock_irqrestore+0x21) :#func-6520.074 __ipipe_unstall_root+0x9 (__ipipe_restore_root+0x2c) :| #begin 0x8000 -6520.066 __ipipe_unstall_root+0x34 (__ipipe_restore_root+0x2c) :| +end 0x8000 -6520.069 __ipipe_unstall_root+0x59 (__ipipe_restore_root+0x2c) :+func-6520.096 find_vma+0x4 (do_page_fault+0x465) :+func-6520.150 ltt_run_filter_default+0x4 (_ltt_specialized_trace+0xc1) :+func-6520.098 handle_mm_fault+0x11 (do_page_fault+0x537) :+func-6520.090 _spin_lock+0x4 (handle_mm_fault+0x680) :+func-6520.063 ptep_set_access_flags+0x9 (handle_mm_fault+0x6d1) :+func-6520.282 flush_tlb_page+0xd (handle_mm_fault+0x6e7) :+func-6510.162 ltt_run_filter_default+0x4 (_ltt_specialized_trace+0xc1) :+func-6510.062 up_read+0x4 (do_page_fault+0x5a9) :+func-6510.072 _spin_lock_irqsave+0x9 (__up_read+0x1c) :+func-6510.117 ipipe_check_context+0xd (_spin_lock_irqsave+0x1d) :#func-6510.074 _spin_unlock_irqrestore+0x4 (__up_read+0x92) :#func-6510.069 __ipipe_restore_root+0x4 (_spin_unlock_irqrestore+0x21) :#func-6510.060 __ipipe_unstall_root+0x9 (__ipipe_restore_root+0x2c) :| #begin 0x8000 -6510.056 __ipipe_unstall_root+0x34 (__ipipe_restore_root+0x2c) :| +end 0x8000 -6510.420 __ipipe_unstall_root+0x59 (__ipipe_restore_root+0x2c) :| +func-6500.084 __ipipe_handle_exception+0x11 (page_fault+0x26) and again and again... We are looping over a minor fault here (according to /proc/PID/stat), the context is a Xenomai task in secondary mode. As the task no longer processes signals in this state, the whole system is more or less broken. Tomorrow I will try to find out the faulting address with an instrumented kernel, but maybe you already have some ideas. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Problem running klatency test
Shashank Bhatia schrieb:
[...]
open(/proc/xenomai/registry/native/pipes/klat_pipe): No such file or
directory
modprobe klat_mod or try the -P option?
the module ist called xeno_klat. patch attached.
diff --git a/src/testsuite/klatency/klatency.c
b/src/testsuite/klatency/klatency.c
index a22cd59..c419402 100644
--- a/src/testsuite/klatency/klatency.c
+++ b/src/testsuite/klatency/klatency.c
@@ -187,7 +187,7 @@ int main(int argc, char **argv)
if (benchdev == -1) {
perror(open(/proc/xenomai/registry/native/pipes/klat_pipe));
fprintf(stderr,
- modprobe klat_mod or try the -P option?\n);
+ modprobe xeno_klat or try the -P option?\n);
exit(EXIT_FAILURE);
}
} else {
signature.asc
Description: OpenPGP digital signature
___
Xenomai-core mailing list
Xenomai-core@gna.org
https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] x86: Endless minor faults
On Mon, 2009-06-29 at 19:35 +0200, Jan Kiszka wrote: Hi all, seen such loops before? This particular trace is from a 2.6.29.3 kernel with ipipe-2.3-01 (SMP/PREEMPT_VOLUNTARY), but the same happens with 2.6.29.5/2.3-03: Do you mean 2.6.29.5/2.4-03? -- Philippe. ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] x86: Endless minor faults
Philippe Gerum wrote: On Mon, 2009-06-29 at 19:35 +0200, Jan Kiszka wrote: Hi all, seen such loops before? This particular trace is from a 2.6.29.3 kernel with ipipe-2.3-01 (SMP/PREEMPT_VOLUNTARY), but the same happens with 2.6.29.5/2.3-03: Do you mean 2.6.29.5/2.4-03? No, in fact I meant 2.4-01 (the one of rc2). Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
