On Sun, 9 Oct 2011, Friedrich Schick wrote: > Hello, Resending the same message over and over does not make people more repsonsive - quite the contrary it might promote you on the ignore list easily. > I am running a 3.0.3 rt11 on an FPGA embedded PowerPC 440. Everything > runs fine so far. > > Currently, I am trying to get an UIO driver working with interrupts > (the kernel Oops after a short while, see below). I guess, its > something with the connected hardware, that fires too fast. That guess is very wrong and guessing in the context of kernel oopses is never a good idea. > How can I set the UIO kernel driver to a higher priority than my > rt-userspace threads? Since I need the rt-threads to be scheduled > before TCP priorities, my userspace priorities are 51 and up. chrt > By the way, what is meant by "Kernel panic - not syncing: Fatal > exception in interrupt"? A fatal exception happend in interrupt context. The kernel can not recover from that. The only resolution is PANIC. > NIP [c02f2030] rt_spin_lock_slowlock+0x98/0x260 > LR [c02f1fe8] rt_spin_lock_slowlock+0x50/0x260 > Call Trace: > [c9ff3ef0] [c02f1fe8] rt_spin_lock_slowlock+0x50/0x260 (unreliable) > [c9ff3f50] [c0029a70] __wake_up+0x24/0x58 This looks very wrong. Seems you requested the interrupt with IRQF_NO_THREAD which cannot work with UIO. > [c9ff3f70] [c02548f8] uio_event_notify+0x3c/0x64 > [c9ff3f80] [c0254970] uio_interrupt+0x50/0x68 > [c9ff3f90] [c006a6cc] handle_irq_event_percpu+0x68/0x174 > [c9ff3fd0] [c006a82c] handle_irq_event+0x54/0x8c > [c9ff3fe0] [c006cf30] handle_edge_irq+0xa8/0x1a8 > [c9ff3ff0] [c000b5e4] call_handle_irq+0x18/0x28 > [c90c1980] [c000360c] do_IRQ+0xf0/0x14c > [c90c19b0] [c000caf8] ret_from_except+0x0/0x18 Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
