From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <530A77F9.9040407@xenomai.org> Date: Sun, 23 Feb 2014 23:36:41 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <530A69FD.9060708@xenomai.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] RaspberryPi kernel 3.8 issue List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gregory Dymarek Cc: xenomai@xenomai.org On 02/23/2014 11:18 PM, Gregory Dymarek wrote: > Thank you for such quick response! > > Actually yes, this is a warning. Sorry. > > That's the content: > irqreturn_t handle_irq_event_percpu(struct irq_desc *desc, struct irqaction > *action) > ... > if (WARN_ONCE(!irqs_disabled(),"irq %u handler %pF enabled interrupts\n", > irq, action->handler)) > local_irq_disable(); > > > Should the IRQs be 'not disabled' at the first place? irqs_disabled() does not really test if irqs are disabled when running over I-pipe, it tests if the linux domain is "stalled", i.e. if irqs are disabled, but "virtually". Anyway, I believe the problem is that handle_IRQ is called, normally a call to ipipe_do_irq should be inserted, so, the normal interposition of the I-pipe seems missing. Could you try to disable stack unwinding to see if we have a different trace? -- Gilles.