Cyril Wallois wrote: > Hi Jan, > > Is CONFIG_FRAME_POINTER set as well? The stack unwinder likely needs > this to tell data apart from return addresses.
[Argh, another one with a broken mail client setup...] > > CONFIG_FRAME_POINTER is set in autoconf.h of the kernel source : > > #define CONFIG_FRAME_POINTER 1 > CONFIG_KALLSYMS/_ALL=y? Otherwise, I'm clueless for now. > > To begin, I would like to understand the error : Inappropriate ioctl > for > > device > > > > This error is return in slave or master node by tdmacfg : > > > > MASTER : > > > > ./rtnet -v start > > ... > > usr/rtnet/sbin/tdmacfg rteth0 master > > 5000 > > ioctl: Inappropriate ioctl for > > device > > > > /usr/rtnet/sbin/tdmacfg rteth0 slot 0 > > 0 > > > > ioctl: Inappropriate ioctl for > > device > > > > /usr/rtnet/sbin/rtcfg rteth0 add 192.168.1.11 -stage1 > > - > > ifconfig: SIOCGIFFLAGS: No such device > > > > SLAVE : > > > > ./rtnet -v start > > ... > > /usr/rtnet/sbin/tdmacfg rteth0 > > slave > > > > ioctl: Inappropriate ioctl for device > > > > Is it a bad configuration of etc/rtnet.conf, or can it comes from the > driver > > ? > > > > Does the driver still oops? Then you don't need to look at management > tool errors. Start simple with a peer-to-peer configuration with out > RTmac or RTcfg (see README). > > > In this way, ioctl error appears when I try to configure the loopback : > > # ./rtifconfig -a > rtlo Medium: Local Loopback > LOOPBACK MTU: 1500 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > rteth0 Medium: Ethernet Hardware address: 00:1E:AC:00:00:14 > IP address: 192.168.1.11 Broadcast address: 192.168.1.255 > UP BROADCAST RUNNING MTU: 1500 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > # ./rtifconfig rtl0 up > ioctl: No such device "rtlo" - try copy&paste. ;) This implies that rt_loopback is loaded. > > And when I try to configure the route for the rteth0 interface : > > ./rtroute add 192.168.1.10 dev rteth0 > ioctl: Inappropriate ioctl for device > "rtlo" if you want to use the loopback. If it shall be rteth0, you need to configure&up that one as well. > > The oops happened when I load the standard driver before loading the rtnet > driver (then remove with rmmod before loading rtnet of course), . > In this case I'm able to send packet and material interrupt occurs (then > oops). > The sending "doesn't work" if the standard driver isn't load before > (ethereal doesn't show any transmitted packet). > > At first glance, there is a problem of initialization, maybe the irq ? Or you accidentally disabled/broke some hardware setup while porting. Jan
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev
_______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
