Leopold Palomo-Avellaneda wrote: > > Hi Leo, > > > > the messages in your syslog is written by the e1000 driver. > > the e1000 driver? the rte1000 driver not? I created a new kernel without > this > driver to not have any problem with rtnet.
I guess he is talking about the rt_e1000 driver (based on e1000 driver). > > > I compared the e1000 driver in SVN trunk with the one in 0.9.9. > > As the syslog show, I always have worked with 0.9.10 (trunk), :-) > well that what I have seen ... Are you sure? Because the SVN version of RTnet has this rt_e1000 patch already applied and it seems like you don't, so maybe you are not running rtnet SVN version. Better try a diff to be sure. > > One interesting difference is around line 316 in e1000_main.c. > > In 0.9.9 it is > > if ((err = rtdm_irq_request(&adapter->irq_handle, > adapter->pdev->irq, > > e1000_intr, RTDM_IRQTYPE_SHARED, > > netdev->name, netdev))) > > > > In trunk it is > > if ((err = rtdm_irq_request(&adapter->irq_handle, > adapter->pdev->irq, > > e1000_intr, flags, netdev->name, netdev))) > > If you have MSI enabled and if you have the PCIe e1000, the flags should > be > > zero. > > yes, I have MSI enabled > > > Could you try to set flags to RTDM_IRQTYPE_SHARED in any case before > > calling rtdm_irq_request? I have no idea if this helps, but perhaps it > is > > worth a try... > > Regards > > well, yes... > > I'm a bit saturated. I don't have any message of this kind today .... and > yesterday I got a nice routing table ..... and today not. > > I'm trying to understand rtcap and see what is happens with the pings. > What do > you think that is the best way to afford all the issues that I have? > - begin to make test to the RTDM_IRQTYPE_SHARED flags to see the > something? > - see the rtcap about the ping? > .... buy a flight to Mallorca island and walk in the beach and forget the > computers....? > You don't have to understand RTcap. Just enable it at rtnet configuration (make menuconfig) and load its module, enable its interface and let wireshark/tcpdump capture the traffic. The only thing you have to do then is to check the frames (which are sent, are they corrupt ... ) ... and last but not least ... send me one of those tickets ;) Karl > regards, > > Leo > > > > > Mathias > > > > > asking to Mathias: > > > > Hi, > > > > > > > > I never had this message even if I use two (sometimes three) e1000 > NICs > > > > > > in > > > > > > > my setup. However, I am currently running the released version set: > > > > > > Xenomai > > > > > > > 2.3.3, kernel 2.6.20, rtnet 0.9.9 on an Intel machine. > > > > When exactly does this message appears in dmesg? What did you do > > > > > > before? > > > > > > I attach the syslog of yesterday, with all the appears .. > > > > > > > > > Leo > > > > > > A Dijous 15 Novembre 2007, M. Koehrer va escriure: > > > > > > what does it means this message of the dmesg? > > > > > > it's important? > > > > > > > > > > > > e1000: rteth0: e1000_clean_tx_irq: Detected Tx Unit Hang > > > > > > Tx Queue <0> > > > > > > TDH <0> > > > > > > TDT <2> > > > > > > next_to_use <2> > > > > > > next_to_clean <0> > > > > > > buffer_info[next_to_clean] > > > > > > time_stamp <1003aa118> > > > > > > next_to_watch <0> > > > > > > jiffies <1003aa305> > > > > > > next_to_watch.status <0> > > > > > > > > > > Jan -- von Karl Reichert Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/rtnet-users
