[Xenomai-help] spurious interrupt with latest release

[Xenomai-help] spurious interrupt with latest release

[stephane ancelot]

Hi,

I do not manage to run something stable using latest 2.4.5 branch and  
kernel 2.6.26


for unknown reasons , I got spurious interrupts in my realtime interrupt  
rtdm driver.

The IRQ is not shared , this happens with LAPIC enabled. I tried without  
it, but some other problem have happened.


and after a while the computer manages to crash ..

Best Regards
s.ancelot

Re: [Xenomai-help] spurious interrupt with latest release

[stephane ancelot]

[-- Attachment #1: Type: text/plain, Size: 1253 bytes --]

Hi,
Finally since I did not understand why this happened and to inhibit any  
driver writing related problems,I made the following architecture :

a single 5ms task triggs a PLX 9050 INTCSR software register to activate  
INTA  (level irq)

the rtdm interupt handler checks if IT comes from the PLX, disable PLX IT,  
resets the software register , reenable PLX it,
and ack irq rtdm

However at random time , I have always spurious interrupt in this handler.  
The time it occurs is random .

attached my kernel config.gz

Best Regards
S.Ancelot




Le Tue, 02 Sep 2008 15:28:59 +0200, stephane ancelot <sancelot@domain.hid> a  
écrit:

> Hi,
>
> I do not manage to run something stable using latest 2.4.5 branch and
> kernel 2.6.26
>
>
> for unknown reasons , I got spurious interrupts in my realtime interrupt
> rtdm driver.
>
> The IRQ is not shared , this happens with LAPIC enabled. I tried without
> it, but some other problem have happened.
>
>
> and after a while the computer manages to crash ..
>
> Best Regards
> s.ancelot
>
>
>
>
>
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help
>
>


[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 8927 bytes --]

Re: [Xenomai-help] spurious interrupt with latest release

[Gilles Chanteperdrix]

stephane ancelot wrote:
> Hi,
> Finally since I did not understand why this happened and to inhibit any  
> driver writing related problems,I made the following architecture :
> 
> a single 5ms task triggs a PLX 9050 INTCSR software register to activate  
> INTA  (level irq)
> 
> the rtdm interupt handler checks if IT comes from the PLX, disable PLX IT,  
> resets the software register , reenable PLX it,
> and ack irq rtdm
> 
> However at random time , I have always spurious interrupt in this handler.  
> The time it occurs is random .
> 
> attached my kernel config.gz

Hi,

Did you check the differences in masking/acking/unmasking interrupts for
the interrupt controller you use between the I-pipe patch that works and
the I-pipe patch that does not work ?

Regards.

-- 
                                                 Gilles.

Re: [Xenomai-help] spurious interrupt with latest release

[stephane ancelot]

Le Thu, 04 Sep 2008 11:05:05 +0200, Gilles Chanteperdrix  
<gilles.chanteperdrix@xenomai.org> a écrit:

> stephane ancelot wrote:
>> Hi,
>> Finally since I did not understand why this happened and to inhibit any
>> driver writing related problems,I made the following architecture :
>>
>> a single 5ms task triggs a PLX 9050 INTCSR software register to activate
>> INTA  (level irq)
>>
>> the rtdm interupt handler checks if IT comes from the PLX, disable PLX  
>> IT,
>> resets the software register , reenable PLX it,
>> and ack irq rtdm
>>
>> However at random time , I have always spurious interrupt in this  
>> handler.
>> The time it occurs is random .
>>
>> attached my kernel config.gz
>
> Hi,
>
> Did you check the differences in masking/acking/unmasking interrupts for
> the interrupt controller you use between the I-pipe patch that works and
> the I-pipe patch that does not work ?
>

I know that it rocks with
kernel 2.6.24.2 and  adeos-ipipe-2.6.24-x86-2.0-03.patch

it does not with :
kernel 2.6.26.2 and adeos-ipipe-2.6.26-x86-2.0-09.patch

Having a look at the patch I did not manage to find big differencies only  
in entry_32.S sysenter for enabling hw it, but I am not sure if this part  
of code may be related to my problem

The routed IRQ number is 18d

enabling ipipe and kernel debugging options does not help.


It would be useful , if I could reproduce the problem using a standard  
component of the PC to trig an IT like the PLX soft register, in order  
produce a regression test and some people being able to reproduce  
it.Supposing the same problem should appear :-)



Best Regards
Steph


> Regards.
>

Re: [Xenomai-help] spurious interrupt with latest release

[Gilles Chanteperdrix]

stephane ancelot wrote:
> Le Thu, 04 Sep 2008 11:05:05 +0200, Gilles Chanteperdrix  
> <gilles.chanteperdrix@xenomai.org> a écrit:
> 
>> stephane ancelot wrote:
>>> Hi,
>>> Finally since I did not understand why this happened and to inhibit any
>>> driver writing related problems,I made the following architecture :
>>>
>>> a single 5ms task triggs a PLX 9050 INTCSR software register to activate
>>> INTA  (level irq)
>>>
>>> the rtdm interupt handler checks if IT comes from the PLX, disable PLX  
>>> IT,
>>> resets the software register , reenable PLX it,
>>> and ack irq rtdm
>>>
>>> However at random time , I have always spurious interrupt in this  
>>> handler.
>>> The time it occurs is random .
>>>
>>> attached my kernel config.gz
>> Hi,
>>
>> Did you check the differences in masking/acking/unmasking interrupts for
>> the interrupt controller you use between the I-pipe patch that works and
>> the I-pipe patch that does not work ?
>>
> 
> I know that it rocks with
> kernel 2.6.24.2 and  adeos-ipipe-2.6.24-x86-2.0-03.patch
> 
> it does not with :
> kernel 2.6.26.2 and adeos-ipipe-2.6.26-x86-2.0-09.patch

Well, it would be nice to try 2.6.25.

> Having a look at the patch I did not manage to find big differencies only  
> in entry_32.S sysenter for enabling hw it, but I am not sure if this part  
> of code may be related to my problem
> 
> The routed IRQ number is 18d
> 
> enabling ipipe and kernel debugging options does not help.
> 
> 
> It would be useful , if I could reproduce the problem using a standard  
> component of the PC to trig an IT like the PLX soft register, in order  
> produce a regression test and some people being able to reproduce  
> it.Supposing the same problem should appear :-)

And if you run cat /proc/interrupts on the two kernels, do you observe
any difference, as for instance, irqs changing from edge to level, or
from local-apic to IO-apic or to fasteoi, or whatever ?

-- 
                                                 Gilles.