Hi I have done the tests previously suggested and here are the results.. Hope this meamn something
On Tue, 18 May 2004, Jan Kiszka wrote: > >>>... > >>>My other computer that runs as a Master uses the epro100 driver and never > >>>showed any error. However it seems to be doing a inifinite loop printing > >>>out the "unknown layer-3 protocol" line > >>> > >> > >>You are no longer able to use some console of that system? What is the > >>rate of that message, one per second or much more? Is it regular? > >> > > > > > > no i can't open any others because I am not using a GUI interface. When > > the "rtnet start" is in proccess I can't even "Alt+F2" to other consoles > > > > Then this is actually a crash. What happens if you don't connect the > master to the network? Does your system also hang? > I unplugged the cable to the network and ran "rtnet start" the computer stil froze. I don't think the computer crashed since beefore when it was connected to the network... it was still outputing printk to the screen.. You previously suggested me in manually insmod rtnet.o and loopback-rt.o to test whether the core is doing fine. I configured as such like you advised. rtifconfig rtlo up 127.0.0.1 insmod examples/frag-ip/frag-ip.o start_timer=1 the screen continuously output something i could hardly catch up .. but presumabily they are what is written for transmit packet and receive packets... One odd thing i have manage to find out is that my key-board "Num Lock" light kept on blinking and not responding my control. Also i coudln't not ALT+F* to any other consoles. From this response I guess the hard real-time task is taking most of the CPU which is probably the reason why the Linux process is at halt or seem crashed... I went and open what the frag-ip.c file is doing... One thing i wondered is in the if(timer_start) that start_rt_timer has an argument of "0" in the module initialising function... I am not sure what start_rt_timer(0) actually will do.. but a tick of 0 i guess mean absolutely fast ? I noticed that rt_task_make_periodic_relative_ns() is called .. which has the CYCLE set to 1s ... so wondered how the loop went so fast? > > The rate of the message if irregular.. sometime it outputs 2 at a time and > > sometimes none till few secs. > > > > So, these messages are likely triggered only by the non-real-time > traffic in your university networks (broadcasts...). > > >>RTcap is just a service layer which creates a read-only linux network > >>device to be used with standard sniffers like tcpdump or Ethereal. > > > > > > So it won't be in any use if I can't get two machines communicating ? > > Because currently RTcap is like doing a "rtnet start" outputing "unknown > > layer-3 protocol" > > > > RTcap will report ANY packet directed to and sent by the host (if in > promisc mode: any packet on the wire). But, as it depends on standard > sniffers, it will not work if the Linux part of your system crashes... > > >> > >>Did you already verified with some RTAI example if that part is running > >>without problems? > > > > > > I am not sure what RTAI example you are referring to? > > > > Latency tests or any example from the showroom (RTAI 3.x, earlier > version already come with that examples). See RTAI docs. > Yes I have tried those tests provide by RTAI3.x and all worked.. In fact I have also written a little something as real-time tasks and also worked. As I guess RTAI3.x is not the cause of the problem > > > > Ok I will try just doing a loopback. How do you transmit and receive data > > remotely without having RTmac and RTcfg ? a rt Ethernet driver or a > > normal one? > > > > RTmac is just an optional layer between the real-time driver and the > protocol stack. If you leave it out, you will still be able to transmit > and receive data with your real-time applications using the same > infrastructure, but you will loose the determinism due to potential > collisions and congestions on the network. > > RTcfg is used to setup RTmac/TDMA automatically, it is not involved in > user data exchange. > > > I have checked out what that "unknown layer-3 protocol" mean.. But I am > > not sure how this error can still occur if in the manager it store all the > > possible protocl in a stack (or is it a queue?) Is this response normal > > under network is not set up between >=2 stations? > > > > It's "normal" as long as you do not use a dedicated network without any > disturbing non-RTnet traffic. You are always free to switch this warning > of in the source code, it is just intended to help creating a clean setup. > > Jan > Thanks Bret ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ RTnet-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/rtnet-users
