When i boot Xenomai normally and look in /proc/interrupts, i get the list attached. Is this what can show IRQ conflicts? lsmod shows that e1000 is loaded at boot.Benjamin Biegel wrote:Thanks for your help. I now recompiled with the your suggestions. The config-file generated my gconfig is attached. The xenomai examples work. But when i do the local loopback test described in: http://www.xenomai.org/index.php/RTnet:Installation_%26_Testing the computer freezes after some time after the command './rtnet start'. It does not even show 'waiting for slaves'. If i do the ctrl + backslash quit after running './rtnet start' i can see with lsmod that rtmac rtcft rt_loopback rt_e1000 rtpacket rtipv4 rtnet are loaded. But even if i do this forced quit the PC freezes.I guess the freeze is finally triggered by rtifconfig rteth0 up. What is /proc/interrupts reporting when you loaded standard e1000 and enabled the interface under Linux (/me is looking for IRQ conflicts)?
Does the /proc/interrupts file show that serial-console/netconsole is the next step? Would it be easier to try and install Xenomai + RTnet on another computer? Or is it normal that an amount of problems have to be solved first?Is it possible it would not crash if there were actually slaves? Or do you have other suggestions?If the above reports no clashes for e1000's IRQ line, please attach a serial or netconsole and try to capture any potential oops via a second PC. See linux/Documentation/serial-console.txt or linux/Documentation/networking/netconsole.txt for details.
Jan