Jan Kiszka wrote:
> Beyer Philipp wrote:
>   
>> Jan Kiszka wrote:
>>     
>>> Beyer Philipp wrote:
>>>   
>>>       
>>>> ...
>>>> kontron_xenomai:~# rtifconfig rtlo up 127.0.0.1
>>>> kontron_xenomai:~# rtroute add 10.0.0.2 00:E0:4B:0E:3D:29 dev rteth1
>>>>     
>>>>         
>>> You could try rtroute solict as well, first from master to slave, then
>>> the other way around. This also indicates if there is any communication
>>> at all (one direction should work as we saw). Check /proc/xenomai/irq if
>>> something happens, and on which side. If you can resolve the conflict on
>>> IRQ #10 (e.g. by unloading the Linux driver for the competing device),
>>> you could also try rteth0.
>>>   
>>>       
>> The problem is I actually can't unload this other module, because it is
>> compiled into the kernel.
>> And I need it statically, because I boot from it via PXE -> kernel tftp
>> -> nfsrootfs. This device is the VIA RHINE I was speaking of. It is
>> eth0. If I try to rtifconfig rteth0 my system freezes! Thats because I
>> tried with rteth1 :D
>>     
>
> /me slowly starting to understand the scenario. Again, you can instruct
> rt_tulip to skip the first NIC so that rteth1 becomes rteth0.
>
>   
>> kontron_xenomai:~# rtroute solicit 10.0.0.2 dev rteth1
>> kontron_xenomai:~# rtroute
>> Host Routing Table
>> Hash    Destination     HW Address              Device
>> 00      0.0.0.0         00:00:00:00:00:00       rtlo
>> 01      10.0.0.1        00:00:00:00:00:00       rtlo
>> 01      127.0.0.1       00:00:00:00:00:00       rtlo
>> 3F      10.255.255.255  FF:FF:FF:FF:FF:FF       rteth1
>> kontron_xenomai:~# cat /proc/xenomai/irq
>> IRQ         CPU0
>>   0:       82322
>>  11:           2
>>  34:           3
>> -------------------------------------------------------------------------
>> kontron_xenomai:~# rtroute solicit 10.0.0.1 dev rteth1
>> kontron_xenomai:~# rtroute
>> Host Routing Table
>> Hash    Destination     HW Address              Device
>> 00      0.0.0.0         00:00:00:00:00:00       rtlo
>> 01      127.0.0.1       00:00:00:00:00:00       rtlo
>> 02      10.0.0.2        00:00:00:00:00:00       rtlo
>> 3F      10.255.255.255  FF:FF:FF:FF:FF:FF       rteth1
>> kontron_xenomai:~# cat /proc/xenomai/irq
>> IRQ         CPU0
>>   0:      104582
>>  11:           3
>>  34:           4
>>     
>
> irq count before and after the solicit would tell more. The should be
> one IRQ for packet tx and one for rx.
>   
You mean like this:

kontron_xenomai:~# cat /proc/xenomai/irq
IRQ         CPU0
  0:       45700
 11:          10
 34:          11
kontron_xenomai:~# rtping -c 3 10.0.0.1
Real-time PING 10.0.0.1 56(84) bytes of data.

--- 10.0.0.1 rtping statistics ---
3 packets transmitted, 0 received, 100% packet loss
worst case rtt = 0.0 us
kontron_xenomai:~# cat /proc/xenomai/irq
IRQ         CPU0
  0:       48866
 11:          13
 34:          14
kontron_xenomai:~#

With soilicit it is as you said.

^^
> Ok, then also compare the kernel output of the Linux driver in debug
> mode with that of rt_tulip in debug mode. Maybe the media type isn't
> negotiated correctly. I remember some issues - without further details
> unfortunately. I only remember that tulip was somehow fishy in this
> regard, fits to this comment [1].
>
> Do you have a crosslink cable in between? There is the "options" module
> parameter of rt_tulip, playing with it may be worthwhile (see [2] for
> the meanings).
>   
I tried
insmod /usr/local/rtnet/modules/rt_tulip.ko debug=6 options=11,11
what is in that case the default - and thats nothing special for 100
megabit ethernet.

and
insmod /usr/local/rtnet/modules/rt_tulip.ko debug=6 options=14,14
what these other values exactly mean - I have not really the perfect idea ;)

I also had a closer look at the linux tulip drivers with highest debug
level (6)
but nowhere was a clue what media is used. But I read about the default
value is 0 - that would be

/10baseT/


I could force the driver to the values I want. I am going to play with
it a bit more.

And yes I have a crosslink cable in between.


>
> [1]http://www.rts.uni-hannover.de/rtnet/lxr/source/drivers/tulip/tulip_core.c#L1644
> [2]http://www.rts.uni-hannover.de/rtnet/lxr/source/drivers/tulip/tulip_core.c#L58
>
>   


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Reply via email to