All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] spurious interrupt with latest release
Date: Thu, 04 Sep 2008 17:51:54 +0200	[thread overview]
Message-ID: <48C0041A.5020001@domain.hid> (raw)
In-Reply-To: <op.ugyoorx2nuwxn3@domain.hid>

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.



      reply	other threads:[~2008-09-04 15:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02 13:28 [Xenomai-help] spurious interrupt with latest release stephane ancelot
2008-09-04  7:56 ` stephane ancelot
2008-09-04  9:05   ` Gilles Chanteperdrix
2008-09-04 14:47     ` stephane ancelot
2008-09-04 15:51       ` Gilles Chanteperdrix [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48C0041A.5020001@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.