From mboxrd@z Thu Jan 1 00:00:00 1970 From: Philippe Gerum In-Reply-To: <200905041539.35371.smolorz@domain.hid> References: <200905041409.01179.smolorz@domain.hid> <200905041539.35371.smolorz@domain.hid> Content-Type: text/plain Date: Mon, 04 May 2009 15:44:13 +0200 Message-Id: <1241444653.26544.323.camel@domain.hid> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] Kernel lockup when shared IRQ is enabled List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Sebastian Smolorz Cc: xenomai@xenomai.org On Mon, 2009-05-04 at 15:39 +0200, Sebastian Smolorz wrote: > Steven Kauffmann wrote: > > 2009/5/4 Sebastian Smolorz : > > > 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.