Hello Ingo,
I had the very same problem and I found a "tricky" solution for it.
You should (must?) have not shared interrupts with the realtime NICs, in your case
there is a interrupt sharing between the aic7xxx and eth1.
With the kernel 2.4.22 I was using (ACPI enabled), the interrupts of the PCI adapters
are assigned by the linux kernel.
The algorithm for that can be found in linux/drivers/acpi/pci_link.c
One table defines the "penalty" for reusing a certain IRQ assignment.
I modified this table according to the following patch:
------ PATCH BEGIN -----------
--- linux-2.4.22-orig/drivers/acpi/pci_link.c Mon Aug 25 11:44:41 2003
+++ linux-2.4.22/drivers/acpi/pci_link.c Thu Oct 23 13:36:47 2003
@@ -399,11 +399,13 @@
* as 'best bets' for PCI use.
*/
+/* The list is adapted - we do not need the IRQs for
+ * COM, Floppy, LPT, Sound, Mouse, RTC */
static int acpi_irq_penalty[ACPI_MAX_IRQS] = {
- 1000000, 1000000, 1000000, 10000,
- 10000, 0, 10000, 10000,
- 10000, 0, 0, 0,
- 10000, 100000, 100000, 100000,
+ 1000000, 1000000, 1000000, 0,
+ 10, 0, 10, 10,
+ 0, 0, 0, 0,
+ 0, 15, 100000, 100000,
};
---------------- PATCH END ---------------
Doing this and disabling e.g. USB, audio etc. devices in the BIOS it works in a way
that at least two or three PCI NICs have a unique interrupt assigned.
However, I do have a UP machine, but the principle idea should be the same.
You can see the ACPI interrupt assignment during boot phase (or with dmesg).
I am just about the move to kernel 2.4.24 and rtai 3.0 and rtnet 0.6.
The interrupts assignement code in kernel 2.4.24 has been completely modified against
2.4.22 - I have to find a solution for that as well, but the principle idea should be
the same.
Hope that helps
Mathias
--
Mathias Koehrer
[EMAIL PROTECTED]
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
RTnet-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/rtnet-users
