[Xenomai-core] [Website] API documentation

2006-04-07 Thread Bruno Rouchouse
Hello, FYI, API documentation update has been fixed on our web server. Documentation section should now provide an up to date information as far as API documentation is concerned and particularly on v2.0.x, v2.1.x versions and also on svn repository i.e. trunk section. >From now on, the doc shall

[Xenomai-core] nkpod->watchdog_trigger per CPU?

2006-04-07 Thread Jan Kiszka
Hi, analysing the watchdog characteristics in our scenarios, I just wondered if it is SMP-aware (we have no SMP in use, it's a pure analytical concern). The watchdog timeout is stored system-wide in nkpod->watchdog_trigger, but it is based on a per-CPU clock (TSC). Is the tick IRQ bound to a spec

Re: [Xenomai-core] [Xenoscope] GDB error

2006-04-07 Thread Philippe Gerum
Bruno Rouchouse wrote: Hi, someone using xenoscope for running simulation ? I'm getting a "GDB error: No symbol "mvm_bp" in current context." while launching my simulation under the xenoscope. Other information: I'm using GNU gdb 6.3-debian and simulation process works fine directly under g

Re: [Xenomai-core] nkpod->watchdog_trigger per CPU?

2006-04-07 Thread Philippe Gerum
Jan Kiszka wrote: Hi, analysing the watchdog characteristics in our scenarios, I just wondered if it is SMP-aware (we have no SMP in use, it's a pure analytical concern). The watchdog timeout is stored system-wide in nkpod->watchdog_trigger, but it is based on a per-CPU clock (TSC). Is the tick

Re: [Xenomai-core] Frozen timer IRQ

2006-04-07 Thread Jan Kiszka
Philippe Gerum wrote: > Jan Kiszka wrote: >> Philippe Gerum wrote: >> >>> Jan Kiszka wrote: >>> Philippe Gerum wrote: > Jan Kiszka wrote: > > >> Attached is an ipipe-freeze of the frozen system. It's taken at the >> time >> the main thread of the terminating a

Re: [Xenomai-core] Frozen timer IRQ

2006-04-07 Thread Jan Kiszka
Philippe Gerum wrote: > Jan Kiszka wrote: >> Philippe Gerum wrote: >>> ... >>> It seems that the pipeline log is not synced by >>> __ipipe_unstall_iret_root. >>> We need to know why. Question: is the root stage stalled or unstalled by >>> this >>> routine during the latest call before the box freez

Re: [Xenomai-core] nkpod->watchdog_trigger per CPU?

2006-04-07 Thread Gilles Chanteperdrix
Philippe Gerum wrote: > Jan Kiszka wrote: > > Hi, > > > > analysing the watchdog characteristics in our scenarios, I just wondered > > if it is SMP-aware (we have no SMP in use, it's a pure analytical concern). > > > > The watchdog timeout is stored system-wide in nkpod->watchdog_trigger,

[Xenomai-core] [draft PATCH] nested enable/disable irq calls

2006-04-07 Thread Dmitry Adamushko
Hi, yep, this is yet another draft patch which aims at supporting the nested irq disable/enable calls for the primary domain. o no changes on the adeos-ipipe layer, hence it's much cleaner and smaller that the one I have posted last time; o eliminates the need for XN_ISR_NOENABLE flag; o but

Re: [Xenomai-core] [draft PATCH] nested enable/disable irq calls

2006-04-07 Thread Philippe Gerum
Dmitry Adamushko wrote: Hi, yep, this is yet another draft patch which aims at supporting the nested irq disable/enable calls for the primary domain. o no changes on the adeos-ipipe layer, hence it's much cleaner and smaller that the one I have posted last time; o eliminates the need for XN_

Re: [Xenomai-core] Frozen timer IRQ

2006-04-07 Thread Philippe Gerum
Jan Kiszka wrote: BTW, that trace hacking reminds me that we should really think about making a kernel debugger run. I recently noticed that latest kgdb applied with a single failing hunk on top of ipipe (2.6.15, x86). Maybe it is just about making kgdb's irq-locks ipipe-aware and bypassing the

Re: [Xenomai-core] Frozen timer IRQ

2006-04-07 Thread Philippe Gerum
Philippe Gerum wrote: Jan Kiszka wrote: BTW, that trace hacking reminds me that we should really think about making a kernel debugger run. I recently noticed that latest kgdb applied with a single failing hunk on top of ipipe (2.6.15, x86). Maybe it is just about making kgdb's irq-locks ipipe-

Re: [Xenomai-core] Frozen timer IRQ - now traced with kgdb :)

2006-04-07 Thread Jan Kiszka
Philippe Gerum wrote: > Philippe Gerum wrote: >> Jan Kiszka wrote: >> >>> >>> BTW, that trace hacking reminds me that we should really think about >>> making a kernel debugger run. I recently noticed that latest kgdb >>> applied with a single failing hunk on top of ipipe (2.6.15, x86). Maybe >>> it

[Xenomai-core] bad/slow TSC hw detected by 2.6.17-rc1-mm1

2006-04-07 Thread Jim Cromie
FYI, Ive just built 17-rc1-mm1, and noted that the new time-keeping-system http://lwn.net/Articles/176837/ can now detect the buggy TSC on my GEODE-sc1100 cpu, and also that its apparently fixable by adding 'idle=poll' to kernel-boot-line. Apr 7 11:42:01 truck kernel: [ 19.160016] Kernel c

[Xenomai-core] Xenosim 2.1 Compile Fixes

2006-04-07 Thread Bernhard Walle
Hello, following fixes were necessary to compile Xenosim 2.1 together with Xenomai 2.1 on SUSE 10.0 with gcc 4.0.2. I hope it can be applied to SVN. (If generated files are in SVN, autoreconf must be run.) Thanks. Regards, Bernhard diff -Nur xenosim-2.1.0.orig/acinclude.m4 xenosim-2.1.0/acin