All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Terje Frøysa" <Terje.Froysa@sintef.no>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] IRQ155 not handled. Disabling IRQ line
Date: Tue, 2 Dec 2014 10:33:46 +0100	[thread overview]
Message-ID: <20141202093346.GE2076@hermes> (raw)
In-Reply-To: <314E5ECDAA86314791309FA670550F89C9C51961@SINTEFEXMBX05.sintef.no>

On Tue, Dec 02, 2014 at 09:28:37AM +0000, Terje Frøysa wrote:
> Dear forum,
> 
> Question:
> If a driver is deemed buggy and the IRQ disabled, why is it still serving the interrupts?
> 
> Running Debian 3.8.13-bone67 and Xenomai 2.6.4
> 
> At opening call, my GPIO RTDM IRQ driver enables a GPIO line w/irq.
> My user-space program issues read-requests to receive a time-stamp for each irq.
> The irq handler is very compact. It only reads the system time, rises a semaphore if not already up and returns RT_INTR_HANDLED.
> 
> When starting (open + loop w/reads),  the dmesg log-message appears:  "IRQ155 not handled. Disabling IRQ line".
> It appears only once in the start.
> Never-the-less, the interrupts are still handled and keep coming.

Well, probably because the code re-enables the irq line ?

-- 
					    Gilles.


  reply	other threads:[~2014-12-02  9:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02  9:28 [Xenomai] IRQ155 not handled. Disabling IRQ line Terje Frøysa
2014-12-02  9:33 ` Gilles Chanteperdrix [this message]
2014-12-02  9:51   ` Terje Frøysa
2014-12-02  9:57     ` Gilles Chanteperdrix
2014-12-02 10:20       ` Terje Frøysa
2014-12-02 10:53         ` Gilles Chanteperdrix
2014-12-02 12:07           ` Terje Frøysa
2014-12-02 12:13             ` Gilles Chanteperdrix
2014-12-02 12:16               ` Terje Frøysa
2014-12-02 12:17                 ` Gilles Chanteperdrix

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=20141202093346.GE2076@hermes \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=Terje.Froysa@sintef.no \
    --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.