On 2013-02-15 16:26, Jan Kiszka wrote:
On 2013-02-15 16:15, Anders Blomdell wrote:
Hi,
I have a DX79SI that dies with "kernel BUG at
arch/x86/kernel/ipipe.c:589!" when running Xenomai. This is not very
surprising since when running the system with an ordinary kernel thera
are a few 'do_IRQ: X.Y No irq handler for vector (irq -1)' each day.
Question is if it would be possible to do something less fatal than
'BUG_ON(irq < 0);' in the code below:
This remains a bug that has to be understood.
int __ipipe_handle_irq(struct pt_regs *regs)
{
struct ipipe_percpu_data *p = __ipipe_this_cpu_ptr(&ipipe_percpu);
int irq, vector = regs->orig_ax, flags = 0;
struct pt_regs *tick_regs;
if (likely(vector < 0)) {
irq = __this_cpu_read(vector_irq[~vector]);
BUG_ON(irq < 0);
} else { /* Software-generated. */
irq = vector;
flags = IPIPE_IRQF_NOACK;
}
Kernel 3.5.7 with latest I-pipe?
Yes.
This is the second report of this kind,
see [1] for the discussion and suggestions. If you don't have KGDB and
that kind enabled, try Gilles' instrumentations.
After a running xenomai five and a half day on a DX58SO motherboard, the
system crashed, leaving a single 'do_IRQ: 2.166 No irq handler for
vector (irq -1)' on our logserver.
I'm planning to put in Gilles instrumentations and change the BUG_ON to
a WARN_ON/WARN, but what should I return after that (my guess is a
'return 1', but waiting a week to be proved wrong would be a waste of
time :-).
Jan
[1] http://thread.gmane.org/gmane.linux.real-time.xenomai.users/15936
Regards
Anders
--
Anders Blomdell Email: [email protected]
Department of Automatic Control
Lund University Phone: +46 46 222 4625
P.O. Box 118 Fax: +46 46 138118
SE-221 00 Lund, Sweden
_______________________________________________
Xenomai mailing list
[email protected]
http://www.xenomai.org/mailman/listinfo/xenomai
