All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Алексей Герасёв" <alexey.gerasev@gmail.com>, xenomai@xenomai.org
Subject: Re: [Xenomai] Disabling shared IRQ line
Date: Tue, 1 Dec 2015 08:28:05 +0100	[thread overview]
Message-ID: <565D4C05.7000907@siemens.com> (raw)
In-Reply-To: <CAG7USP01084WJwhUF+24+BcGGyrvSkfs53U9xkOmxJ6-9=5n+A@mail.gmail.com>

On 2015-12-01 06:35, Алексей Герасёв wrote:
> Hello everyone!
> 
> I have x86_64 PC with CAN adapter served by PLX PCI driver on board. I've
> installed Xenomai 3.0.1 Cobalt on Linux kernel 3.16.7 with
> ipipe-core-3.16.7-x86-5 patch. My CAN adapter has two channels, and they're
> registered on one IRQ line (in my case it's 19). Shared interrupts were
> enabled. When one channel is up and other is down, I have strange error:
> when I sent 500 and received 500 frames through one channel interface, the
> IRQ line became disabled with message: '[Xenomai] xnintr_vec_handler: IRQ19
> not handled. Disabling IRQ line'. When both channels are up, there is no
> such error.
> 
> I've found in 'xnintr_vec_handler' in 'xenomai-3/kernel/cobalt/intr.c' file
> of xenomai source that if at least one handler on shared IRQ line returns
> 'XN_IRQ_NONE', then 'vec->unhandled' counter is incremented, and when it
> reaches 1000, the corresponding IRQ line is disabled. In my case the
> handler of the first channel, which is up, returns 'XN_IRQ_HANDLED' but the
> second one, which is down, returns 'XN_IRQ_NONE'.
> 
> The question is: is this behavior in 'xnintr_vec_handler' correct? Do I
> always need to enable both channels although I use only one of them?

No, this is a regression of aefaab5d03. I'll push a patch to fix this to
my upstream queue. Thanks for reporting!

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux


      reply	other threads:[~2015-12-01  7:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01  5:35 [Xenomai] Disabling shared IRQ line Алексей Герасёв
2015-12-01  7:28 ` Jan Kiszka [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=565D4C05.7000907@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=alexey.gerasev@gmail.com \
    --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.