Christophe Kumsta wrote:
>
> Hi Paolo,
>
> I'm now running rtai-0.2x with kernel 2.2.10.
> I've recompiled all my drivers and they work fine.
> Except (alway) my network-card driver .... which now
> print a (perhaps) more comprehensive message :
>
> "unexpected IRQ vector 209 on CPU#0!"
>
> I don't know at all what can be this IRQ vector 209 !!
> But now , at the ~3rd time , the system freeze totally,
> which is a great pb ...
> I'm going to take a care at my driver to know what's
> happening exactly during the send_message sequence ...
>
> Thanks for all.
>
> --
It seems to me that you are using the interrupt vector 0xF1 for IPIs
without installing any IPI handler. In the previous RTAI, 0.1, version
it was checked because we shared IPIs with Linux now we use our own and
let Linux show the message above for diagnose.
In fact it is RTAI_4_VECTOR, i.e. 0xF1 or 241. Linux diagnoses it as 209
because it subtracts 32 for the first 32 reserved irqs.
The rtai SMP scheduler uses it to send rescheduling messages. I do not
understand how you got there. There is a 1 Khz timer example that shows
how to use IPI messages without the scheduler to process timer
interrupts if you need just a periodic task that want to exploit all the
available CPUs for a lot of fp calculations, with fifos to communicate
to/from a Linux process that tries to write a fifo sent 5Mb/s directly
to disk.
Can I have a look at your code?
Ciao, Paolo.
--- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
----
For more information on Real-Time Linux see:
http://www.rtlinux.org/~rtlinux/
