From: Philippe Gerum <rpm@xenomai.org>
To: Sebastian Smolorz <smolorz@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Kernel lockup when shared IRQ is enabled
Date: Mon, 04 May 2009 15:44:13 +0200 [thread overview]
Message-ID: <1241444653.26544.323.camel@domain.hid> (raw)
In-Reply-To: <200905041539.35371.smolorz@domain.hid>
On Mon, 2009-05-04 at 15:39 +0200, Sebastian Smolorz wrote:
> Steven Kauffmann wrote:
> > 2009/5/4 Sebastian Smolorz <smolorz@domain.hid>:
> > > Steven Kauffmann wrote:
> > >> Hi all,
> > >>
> > >> As some other people on this mailing list, we also have system lockups
> > >> with the latest 2.4 branch. For some people the problems seems to be
> > >> solved when using the adeos-ipipe-2.6.28.9-x86-2.2-07.patch. So we
> > >> tried that but the system still freezes. The console output on another
> > >> machine reports nothing when the system freezes but at computer
> > >> startup we found this line:
> > >>
> > >> Xenomai: xnintr_shirq_handler: IRQ11 not handled. Disabling IRQ line.
> > >>
> > >> lspci shows us that the peak CAN card and the ethernet controller use
> > >> the same IRQ.
> > >
> > > Generally, it is problematic to share IRQs between RT and NRT devices.
> > > You better try to decouple these two devices WRT IRQ sharing.
> > >
> > >> Every time we try to bring up the ethernet device the system freezes.
> > >> Is this related with the above kernel log message and that both cards
> > >> use the same IRQ?
> > >
> > > Are you sure that the system freezes? Do you happen to be logged in over
> > > the net?
> >
> > Yes I'm sure. I cannot ping to the system anymore ...
>
> That is not a sign of a freezed system. The ping does not get replied because
> the ethernet IRQ is not handled any more. I bet the system continues to work.
> You can check this by using a serial console or a local keyboard.
Maybe an interrupt storm kills the board as soon as interrupts are
enabled again in case the ethernet IRQ is level sensitive, since the
last event was not handled.
--
Philippe.
next prev parent reply other threads:[~2009-05-04 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 11:59 [Xenomai-help] Kernel lockup when shared IRQ is enabled Steven Kauffmann
2009-05-04 12:08 ` Sebastian Smolorz
2009-05-04 13:30 ` Steven Kauffmann
2009-05-04 13:39 ` Sebastian Smolorz
2009-05-04 13:44 ` Philippe Gerum [this message]
2009-05-05 7:41 ` Steven Kauffmann
2009-05-05 7:48 ` Gilles Chanteperdrix
2009-05-05 12:04 ` Steven Kauffmann
2009-05-05 12:26 ` Gilles Chanteperdrix
2009-05-05 17:32 ` Martin Shepherd
2009-05-06 14:54 ` Steven Kauffmann
2009-05-04 13:29 ` Philippe Gerum
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=1241444653.26544.323.camel@domain.hid \
--to=rpm@xenomai.org \
--cc=smolorz@domain.hid \
--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.