Leopold Palomo-Avellaneda wrote: > [...] > > > the _same_ card was working with rtnet (not xenomai but rtai) in a > > > configuration that I had in another box. > > > > That's what I mean, the card is not the problem. The problem is the > current > > setup, so as a result it is not working. But of course not the card is > the > > one to blame. ... > > are you working for intel? ;-) >
Also not the processor is the one to blame ;) > no, I'm joking. > > Sadly, I have tested the same configuration with a rtai kernel and I got > the > same hang :-( Also, the network card got the same irq in rtai ... > > Then, do you think that if I put two pcie network card this issue would be > solved? I can only guess. It could. Try out everything you can do without buying new hardware, as mentioned in xenomai FAQ. This includes switching cards into another PCI slot and using APIC. If the problem still remains, I would try out that PCI-express hint! Karl > > Regards, > > Leo > > > > > The reason is of course not the driver or sth similiar, but the IRQ > > > > conflict. So I would also suggest to buy this PCI-Express card, I > don't > > > > > > see > > > > > > > any reason why not. But in the end it's your decission, of course > ... > > > > > > I need three network cards: one gigalan non rt and two 100Mb (rt) and > I > > > have a > > > mobo with one pcie_16 (long, for graphics not used, vga incorporated) > two > > > pcie but the short slot and 4 pci. I have two old netword card intel > e100 > > > but > > > that worked with a rtnet. > > > Are you telling me that it's better that I buy two pcie short slot to > use > > > it? > > > or maybe it's better that I forget xenomai and returns to rtai and > test > > > it with rtnet? > > > > Depends on your requirements. I would at least give it a try, if > possible. > > Buying those e1000 for PCI-e could save your skin. If it's okay to > return > > to rtai, you can of course do this, too. Depends if you need xenomai or > > not. If RTAI works and you don't need any xenomai features, why not > using > > rtai .... > > > > > [....] > > > > > > > > > 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?!? > > > > > > > > I use a Core 2 Duo, APIC is disable and it works, too. So no need > for > > > > > > APIC > > > > > > > no matter if you are using dual core or not. > > > > > > yes, it seems .... > > > > > > maybe it's a question of the kernel no? or is the driver who negotiate > > > the irq > > > with the hw? > > > > > > Regards, > > > > > > Leo > > > > > > > > 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 > -- von Karl Reichert Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser ------------------------------------------------------------------------- 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
