2014-02-26 10:26 GMT+01:00 Philippe Gerum :
> On 02/25/2014 08:03 PM, Kim De Mey wrote:
>>
>> 2014-02-25 17:07 GMT+01:00 Philippe Gerum :
>>>
>>> On 02/25/2014 10:07 AM, Kim De Mey wrote:
Hello all,
I noticed that when enabling the registry in Xenomai-forge (mercury
co
Right,
here is updated trace:
http://pastebin.com/FW6i2Gds
there is unstall root call on line 39
followed by read_current_timer at line 88
if I understand this well read_current_timer fails with bad_irq?
On 26 February 2014 21:49, Gilles Chanteperdrix <
gilles.chanteperd...@xenomai.org> wrote:
On 02/26/2014 11:00 AM, Gregory Dymarek wrote:
> I will have a look later on. However this makes me question, why to spend
> time fixing old kernel if there are already ipipe patches for 3.10.
> Shouldn't we try to do this for the more recent kernel 3.10 so this can be
> eventually incorporated int
Here is one more ipipe trace with less garbage:
http://pastebin.com/WG80f6cx
This happened when i plug usb device after boot is complete
On 26 February 2014 19:59, Gregory Dymarek wrote:
>
> Gilles
> here is the ipipe trace (see line 112)
> http://pastebin.com/EcLn0MxJ
>
> that corresponds to
Gilles
here is the ipipe trace (see line 112)
http://pastebin.com/EcLn0MxJ
that corresponds to
http://pastebin.com/vjLJVDGS
I do not see any call to enable irq, but there are plenty calls for debug.
Could you also explain in a few words the previous patch please.
What was wrong with local_fiq_d
> I will have a look later on. However this makes me question, why to spend
> time fixing old kernel if there are already ipipe patches for 3.10.
> Shouldn't we try to do this for the more recent kernel 3.10 so this can be
> eventually incorporated into Xenomai? or this not that straight forward?
On 2/15/14, Gilles Chanteperdrix wrote:
> On 02/15/2014 04:30 PM, ali hagigat wrote:
>> My system:
>> Fedora 13
>> x86, 32 bits
>> xenomai-2.6.3
>> kernel-3.5.7
>>
>> I executed examp13 and then examp12, computer froze, GNOME stopped,
>> only mouse could move but it could not point at the icons or
On Wednesday 26 February 2014, Gregory Dymarek wrote:
> I guess this also might be down to the kernel configuration. I'm now
> running with a full debug, don't know if this can affect the result.
Can you guys email me your .config files - I'll take a look at them,
compare to the minimal config I
I will have a look later on. However this makes me question, why to spend
time fixing old kernel if there are already ipipe patches for 3.10.
Shouldn't we try to do this for the more recent kernel 3.10 so this can be
eventually incorporated into Xenomai? or this not that straight forward?
On 26
On 02/25/2014 07:11 PM, Gilles Chanteperdrix wrote:
The API documentation already lives in a per-version directory on the
server. README.INSTALL, TROUBLESHOOTING and manual pages link directly
to 2.6 documentation.
There will be significant differences, and I'd rather split the entire
docume
On 02/25/2014 08:03 PM, Kim De Mey wrote:
2014-02-25 17:07 GMT+01:00 Philippe Gerum :
On 02/25/2014 10:07 AM, Kim De Mey wrote:
Hello all,
I noticed that when enabling the registry in Xenomai-forge (mercury
core), that the SIGCHLD gets set to ignore (SIG_IGN) in the
spawn_daemon() call.
I gue
2014-02-25 17:07 GMT+01:00 Philippe Gerum :
> On 02/25/2014 10:07 AM, Kim De Mey wrote:
>>
>> Hello all,
>>
>> I noticed that when enabling the registry in Xenomai-forge (mercury
>> core), that the SIGCHLD gets set to ignore (SIG_IGN) in the
>> spawn_daemon() call.
>> I guess this choice was made t
2014-02-10 12:23 GMT+01:00 Kim De Mey :
> 2014-02-09 17:57 GMT+01:00 Philippe Gerum :
>> On 02/06/2014 02:36 PM, Kim De Mey wrote:
>>>
>>> Hi,
>>>
>>> I believe there is a problem in Xenomai-forge when doing a pSOS
>>> t_suspend() call right after a t_start() call.
>>> It looks like the task does n
13 matches
Mail list logo
