A Dimecres 07 Novembre 2007, M. Koehrer va escriure: > Hi Leo, > > your PC seems to use PCI-Express. One very good choice is to use > Intel Gigabit Ethernet adapters with PCI express connector (instead of the > eepro100). The adapter and rtnet support MSI which means that they will > have an exclusive IRQ. They are supported by rtnet (Driver rt_e1000).
Hi Mathias, yes it's a nice gigabit mobo with pci-e and gigabit integrated network. I choose that mobo because has 4 pci that we need for our sensor cards, netword cards, and capture cards. I prefer to use the pci intel card because they works with rtnet and the election of the hardware is very important with linux/xenomai/rtnet. I don't want to use the gigabit network card for rtnet because it's connected to a gigalan. This box will work as controller. > This means an invest in hardware but this should help you here... I did it ;-) > One thing, I do not understand: You have a multi CPU (or dual core) > machine, but APIC disabled? How can this work... I thought, that APIC is > required for multi CPU systems?!? yes it's a dual core amd64: processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 67 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 5400+ stepping : 3 cpu MHz : 2812.844 cache size : 512 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy bogomips : 5629.23 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc this messages repeated for: processor : 1 vendor_id : AuthenticAMD cpu family : 15 ..... the boot parameters that I have in the grub are: kernel /boot/vmlinuz-2.6.22-xenomai-2.4-rc5 root=/dev/sda2 ro noapic because are the _only_ one that I can use to boot, if not the sata controller doesn't works. And as you can see it's no required for dual core systems. Now, to me the main question is why I choose some assignment of irqs in the bios and the rtnet driver doesn't use it and chose another one.... Regards, Leo > > > A Dimarts 06 Novembre 2007, Karl Reichert va escriure: > > > Leopold Palomo-Avellaneda wrote: > > > > Ok, but how I can avoid it? > > > > > > Please have a look at http://www.xenomai.org/index.php/FAQs, section > > > > 'What > > > > > can I do if Xenomai and Linux devices share the same IRQ?' > > > > ok, done > > > > > > > Thus, try to plugin PCI boards into different slots, try the APIC > > > > > > > > interrupt > > > > > > > > > controller in kernel, etc... > > > > > > > > I can try to assign a irq in the bios to an specific slot. Also, I'm > > > > running > > > > the xenomai kernel with noapic in the kernel because if not I got a > > > > hang > > > > > > when > > > > booting. > > > > > > So that would be an easy solution: Assign different IRQs, if your BIOS > > > allows you to do so. > > > > ok, but rtnet doesn't take my bios settings. I have configure in bios > > that > > > > the network one use irq7 and network 2 irq15 and I got: > > > > RTnet: initialising real-time networking > > initializing loopback... > > RTnet: registered rtlo > > rteth0: 0000:01:06.0, 00:A0:C9:1D:52:B9, IRQ 11. > > *** Receiver lock-up bug detected *** > > Your device may not work reliably! > > RTnet: registered rteth0 > > rteth1: 0000:01:07.0, 00:90:27:13:A5:19, IRQ 10. > > *** Receiver lock-up bug detected *** > > Your device may not work reliably! > > RTnet: registered rteth1 > > > > > > any ideas? > > > > Leo ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users