Re: [RTnet-users] Bad Comfiguration Master/Slave ??

[Teresa Noviello]

On 3/10/06, Jan Kiszka <[EMAIL PROTECTED]> wrote:

I'm picking a standard answer first: please check if there is no IRQ
conflict between the realtime NIC and some Linux device (see
/proc/interrupts). This can have ugly side effects, up to crashes/lock-ups.

In my /proc/interrupts AT BOOT TIME,
 I have:
-----------
"
        CPU0
0:     19287    XT-PIC timer
1:      110      XT-PIC  i8042
2:       0        XT-PIC  cascade
4:      6         XT-PIC  serial
15:    14206  XT-PIC   ide1
MMI:  0
ERR:  1
"

--------------

When then i insert the eth0' driver, which is "e100", i have another row in this file (for eth0):
-----------
"
        CPU0
0:     19287    XT-PIC timer
1:      110      XT-PIC  i8042
2:       0        XT-PIC  cascade
4:      6         XT-PIC  serial
11:    1601    XT-PIC  eth0
15:    14206  XT-PIC   ide1
MMI:  0
ERR:  1
"
--------------

Before starting with inserting RTAI' modules and doing 'rtnet start', i do

'rmmod e100'
and the row for eth0 isn't still present in /proc/interrupts.

Then, we have the same problem i told you.

When we do in the master host

"rtnet stop"

we have a Segmentation Fault but we do not have  Kernel oops.

Maybe we can try by hand with the command "rtcfg" with utilities described in

"http://www.rts.uni-hannover.de/rtnet/lxr/source/Documentation/RTcfg.spec?v=0.9.1"

line 359??


We have tested that the host ping internet with rtnet on (rtping).

Tery

--
Teresa Noviello
Chiedersi Sempre:"Avro' il tempo di rifarlo?"