Hi Gilles,
I am running xenomai (svn 22.02.2007) with adeos-ipipe-2.6.19-arm-1.6-02.patch
on our AT91RM9200 board. (# CONFIG_PREEMPT is not set)
When starting latency with 100µs period I get
~ # latency
== Sampling period: 100 us
== Test mode: periodic user-mode task
== All results in
Steven Scholz wrote:
Hi Gilles,
I am running xenomai (svn 22.02.2007) with adeos-ipipe-2.6.19-arm-1.6-02.patch
on our AT91RM9200 board. (# CONFIG_PREEMPT is not set)
When starting latency with 100µs period I get
~ # latency
== Sampling period: 100 us
== Test mode: periodic user-mode
Steven Scholz wrote:
Hi Gilles,
I am running xenomai (svn 22.02.2007) with adeos-ipipe-2.6.19-arm-1.6-02.patch
on our AT91RM9200 board. (# CONFIG_PREEMPT is not set)
When starting latency with 100µs period I get
~ # latency
== Sampling period: 100 us
== Test mode: periodic user-mode
Gilles,
When starting latency with 100µs period I get
~ # latency
== Sampling period: 100 us
== Test mode: periodic user-mode task
== All results in microseconds
warming up...
BUG: soft lockup detected on CPU#0!
...
Ideas? How can I help with debugging this?
100us is too small, as I
Hi,
i pick up this issue again.
I am running 2.6.19 + adeos-ipipe-2.6.19-arm-1.6-02.patch +
xenomai-svn-2007-02-22
on an AT91RM9200 (160MHz/80MHz).
When starting latency -p 200 it runs for a while printing
RTT| 00:05:37 (periodic user-mode task, 200 us period, priority 99)
RTH|-lat
Hi Philippe,
this is what I get running Stephan slightly modified test with latest
2.6.20 / SVN trunk:
[ 3317.323825] Xenomai: starting native API services.
[ 3318.125915]c125ea70 3082 007c8af8 0003 cd6f4830 d0861f6c
d084f9ca
[ 3318.134339]d08466ff 00300188
Jan Kiszka wrote:
Hi Philippe,
this is what I get running Stephan slightly modified test with latest
2.6.20 / SVN trunk:
[ 3317.323825] Xenomai: starting native API services.
[ 3318.125915]c125ea70 3082 007c8af8 0003 cd6f4830 d0861f6c
d084f9ca
[ 3318.134339]
Steven Scholz wrote:
Hi,
i pick up this issue again.
I am running 2.6.19 + adeos-ipipe-2.6.19-arm-1.6-02.patch +
xenomai-svn-2007-02-22
on an AT91RM9200 (160MHz/80MHz).
When starting latency -p 200 it runs for a while printing
RTT| 00:05:37 (periodic user-mode task, 200 us
Hello,
I've write a little rtdm driver to r/w RealTimeClock on rtc146818
chipset.
I also use this driver to write kernel message from user-space
(printk).
In attachment you can find an archive with the driver and an example of
use (just code).
to compil, you must change kernel sources
On Fri, 2007-02-23 at 12:27 +0100, Steven Scholz wrote:
#ifdef CONFIG_IPIPE
if (unlikely(!ipipe_root_domain_p))
return;
#endif /* CONFIG_IPIPE */
When stepping trough I only see him getting into schedule() but leaving
it in the above lines and in
On Fri, 2007-02-23 at 14:16 +0100, Gilles Chanteperdrix wrote:
I do not think to remember that there are cases where calling schedule
from a real-time context is done by Xenomai, so maybe you can call panic
in schedule instead of returning. I will try and trig a tracer freeze
and dump the
On Fri, 2007-02-23 at 13:32 +0100, Jan Kiszka wrote:
Hi Philippe,
this is what I get running Stephan slightly modified test with latest
2.6.20 / SVN trunk:
[ 3317.323825] Xenomai: starting native API services.
[ 3318.125915]c125ea70 3082 007c8af8 0003 cd6f4830 d0861f6c
Philippe Gerum wrote:
On Fri, 2007-02-23 at 13:32 +0100, Jan Kiszka wrote:
Hi Philippe,
this is what I get running Stephan slightly modified test with latest
2.6.20 / SVN trunk:
[ 3317.323825] Xenomai: starting native API services.
[ 3318.125915]c125ea70 3082 007c8af8 0003
On Fri, 2007-02-23 at 14:34 +0100, Jan Kiszka wrote:
Attached with 3000 points (to play safe).
Great, thanks.
Hmm, I'm seeing prio values of
257 there. Normal, bug, or broken output?
Normal. IRQ thread priority.
--
Philippe.
___
Steven Scholz wrote:
Hi,
i pick up this issue again.
I am running 2.6.19 + adeos-ipipe-2.6.19-arm-1.6-02.patch +
xenomai-svn-2007-02-22
on an AT91RM9200 (160MHz/80MHz).
When starting latency -p 200 it runs for a while printing
RTT| 00:05:37 (periodic user-mode task, 200 us
Gilles,
I am running 2.6.19 + adeos-ipipe-2.6.19-arm-1.6-02.patch +
xenomai-svn-2007-02-22
on an AT91RM9200 (160MHz/80MHz).
When starting latency -p 200 it runs for a while printing
RTT| 00:05:37 (periodic user-mode task, 200 us period, priority 99)
RTH|-lat min|-lat
Philippe Gerum wrote:
On Fri, 2007-02-23 at 14:34 +0100, Jan Kiszka wrote:
Attached with 3000 points (to play safe).
Great, thanks.
Hmm, I'm seeing prio values of
257 there. Normal, bug, or broken output?
Normal. IRQ thread priority.
Ah, oh, the native skin. OK.
signature.asc
Philippe Gerum wrote:
On Fri, 2007-02-23 at 14:34 +0100, Jan Kiszka wrote:
Attached with 3000 points (to play safe).
Great, thanks.
FYI: Switching prio-coupling off doesn't let it trigger anymore. Which
/may/ mean that it's related to this feature, but which may also mean
that this
Steven Scholz wrote:
Gilles,
I am running 2.6.19 + adeos-ipipe-2.6.19-arm-1.6-02.patch +
xenomai-svn-2007-02-22
on an AT91RM9200 (160MHz/80MHz).
When starting latency -p 200 it runs for a while printing
RTT| 00:05:37 (periodic user-mode task, 200 us period, priority 99)
RTH|-lat
Gilles,
Sure but I would still not expect the system to hang!
As I said missing a deadline is bad but ok.
But hanging the whole system is not quite ok.
I want this bug solved too, especially since I am not sure that we will
only see it with too short periods.
Makes us two! ;-)
I would
Philippe,
But I don't get the output of __backtrace()!
Before calling your backtrace helper, try adding:
ipipe_set_printk_sync(ipipe_current_domain);
And then use printk() instead of my_printk()?
Yes, switching this on is a brute force attempt to bypass any
bufferization and allow
Jan Kiszka [EMAIL PROTECTED] 23.02 14:47
Nicolas BLANCHARD wrote:
Hello,
I've write a little rtdm driver to r/w RealTimeClock on rtc146818
chipset.
/me not having done much with rtc (hmm, a lot of years back on PCs, I
think): can this chip be found in normal PC hardware? Or is it only
on
Steven Scholz wrote:
Hi,
schedule. Anyway, I think the tracer will give better results than a
simple backtrace.
Ok. Thanks.
So what exactly shell I do? I have never worked with the tracer.
Just enabled
CONFIG_IPIPE_DEBUG=y
CONFIG_IPIPE_TRACE=y
CONFIG_IPIPE_TRACE_ENABLE=y
Steven Scholz wrote:
Jan,
So what exactly shell I do? I have never worked with the tracer.
Start here: http://www.xenomai.org/index.php/I-pipe:Tracer
I haven't followed all details (while hacking on other bugs :)), but you
have two options to catch a trace: the one described on that page
Hi all,
I am running 2.6.19 + adeos-ipipe-2.6.19-arm-1.6-02.patch +
xenomai-svn-2007-02-22
on an AT91RM9200 (160MHz/80MHz).
When starting latency -p 200 it runs for a while printing
RTT| 00:05:37 (periodic user-mode task, 200 us period, priority 99)
RTH|-lat min|-lat
Steven Scholz wrote:
Hi all,
I am running 2.6.19 + adeos-ipipe-2.6.19-arm-1.6-02.patch +
xenomai-svn-2007-02-22
on an AT91RM9200 (160MHz/80MHz).
When starting latency -p 200 it runs for a while printing
RTT| 00:05:37 (periodic user-mode task, 200 us period, priority 99)
RTH|-lat
On Wed, 2007-01-31 at 01:58 +0100, Philippe Gerum wrote:
Ok, no more distant rumblings about x86_64: a Xenomai port to this
architecture has officially started. A preliminary version of the I-pipe
for x86_64 is now available, which I'm going to use to port the Xenomai
core.
Here we are. The
On Fri, 2007-02-23 at 10:41 +1100, Andrew Dennison wrote:
The RTAI function rt_task_make_periodic() takes absolute ticks as the
start_time argument, however this was being compared to ns in the RTAI
emulation layer.
This patch fixes this, and also removes '+ period' as this seems wrong
with
On Tue, 2007-02-20 at 21:12 +0100, Jan Kiszka wrote:
This patch renames DECLARE_*XNLOCK to DEFINE_*XNLOCK, defines real
DECLARE_XNLOCK +
DECLARE_EXTERN_XNLOCK and applies it on several users.
Merged, thanks.
--
Philippe.
___
Xenomai-core
Philippe Gerum wrote:
On Wed, 2007-01-31 at 01:58 +0100, Philippe Gerum wrote:
Ok, no more distant rumblings about x86_64: a Xenomai port to this
architecture has officially started. A preliminary version of the I-pipe
for x86_64 is now available, which I'm going to use to port the
On Fri, 2007-02-23 at 19:57 +0100, Philippe Gerum wrote:
On Tue, 2007-02-20 at 22:23 +0100, Jan Kiszka wrote:
As long as there is obviously a conflict, catch it during kernel
configuration and urge the user to disable CONFIG_HPET_TIMER.
Applied, thanks.
Reverted from the trunk/
Philippe Gerum wrote:
On Fri, 2007-02-23 at 19:57 +0100, Philippe Gerum wrote:
On Tue, 2007-02-20 at 22:23 +0100, Jan Kiszka wrote:
As long as there is obviously a conflict, catch it during kernel
configuration and urge the user to disable CONFIG_HPET_TIMER.
Applied, thanks.
Reverted
Hi Jan
On Friday 23 February 2007 23:30, Jan Kiszka wrote:
recent development on Xenomai and the underlying I-pipe patch [1]
reached a point where real experiments on yet another architecture for
RTnet are starting to make sense.
In fact, RTnet has been enabled to build over x86_64 already
33 matches
Mail list logo
