Am 27.02.2011 19:49, schrieb Vinzenz Bargsten:
Hi,Here is a syslog from loading the rt modules to several times where no packets are received any longer, rtping somehow fixes this each time -------------------------------------------------------------------------------------------------------- <loading rt modules, reload normal 8139too module for second nic> Feb 28 14:37:12 robot02 kernel: [ 2700.032927] Feb 28 14:37:12 robot02 kernel: [ 2700.032927] *** RTnet 0.9.12 - built on Nov 16 2010 17:58:50 *** Feb 28 14:37:12 robot02 kernel: [ 2700.032928] Feb 28 14:37:12 robot02 kernel: [ 2700.032930] RTnet: initialising real-time networking Feb 28 14:37:12 robot02 kernel: [ 2700.083904] initializing loopback... Feb 28 14:37:12 robot02 kernel: [ 2700.083910] RTnet: registered rtlo Feb 28 14:37:12 robot02 kernel: [ 2700.099315] rt_8139too Fast Ethernet driver 0.9.24-rt0.7 Feb 28 14:37:12 robot02 kernel: [ 2700.099343] rt_8139too 0000:03:00.0: PCI->APIC IRQ transform: INT A -> IRQ 16 Feb 28 14:37:12 robot02 kernel: [ 2700.099719] RTnet: registered rteth0 Feb 28 14:37:12 robot02 kernel: [ 2700.119140] RTcap: real-time capturing interface Feb 28 14:37:12 robot02 kernel: [ 2700.157079] 8139too: 8139too Fast Ethernet driver 0.9.28 Feb 28 14:37:12 robot02 kernel: [ 2700.157103] 8139too 0000:03:01.0: PCI->APIC IRQ transform: INT A -> IRQ 17 Feb 28 14:37:12 robot02 kernel: [ 2700.157987] 8139too 0000:03:01.0: eth0: RealTek RTL8139 at 0xe400, 00:50:fc:4b:ab:fb, IRQ 17 Feb 28 14:37:12 robot02 kernel: [ 2700.159954] eth0: link up, 100Mbps, full-duplex, lpa 0xC1E1 <starting wireshark> Feb 28 14:38:36 robot02 kernel: [ 2783.323474] device rteth0 entered promiscuous mode <switching on remote station, tg3 interface is also connected to it> Feb 28 14:41:41 robot02 kernel: [ 2968.349004] rteth0: Abnormal interrupt, status 00002020. Feb 28 14:41:42 robot02 kernel: [ 2969.335530] rteth0: Abnormal interrupt, status 00000020. Feb 28 14:41:44 robot02 kernel: [ 2971.016290] rteth0: Abnormal interrupt, status 00002020. Feb 28 14:41:47 robot02 kernel: [ 2974.027938] tg3 0000:02:00.0: eth1: Link is up at 1000 Mbps, full duplex Feb 28 14:41:47 robot02 kernel: [ 2974.027941] tg3 0000:02:00.0: eth1: Flow control is on for TX and on for RX Feb 28 14:41:47 robot02 kernel: [ 2974.028230] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Feb 28 14:42:03 robot02 kernel: [ 2989.989823] tg3 0000:02:00.0: eth1: Link is down Feb 28 14:42:06 robot02 kernel: [ 2992.982582] tg3 0000:02:00.0: eth1: Link is up at 1000 Mbps, full duplex Feb 28 14:42:06 robot02 kernel: [ 2992.982585] tg3 0000:02:00.0: eth1: Flow control is on for TX and on for RX <nothing is received anymore after ca 30000 packets> Feb 28 14:42:33 robot02 kernel: [ 3020.354780] rteth0: Abnormal interrupt, status 00000020. Feb 28 14:42:35 robot02 kernel: [ 3022.008621] rteth0: Abnormal interrupt, status 00002020. Feb 28 14:42:36 robot02 kernel: [ 3022.892454] rteth0: Abnormal interrupt, status 00000020. Feb 28 14:42:38 robot02 kernel: [ 3024.937412] rteth0: Abnormal interrupt, status 00002020. <running rtping works and packets are received again; clearing wireshark capture> Feb 28 14:50:44 robot02 kernel: [ 3510.100933] device rteth0 left promiscuous mode Feb 28 14:50:44 robot02 kernel: [ 3510.403421] device rteth0 entered promiscuous mode Feb 28 14:52:30 robot02 kernel: [ 3616.258851] device rteth0 left promiscuous mode Feb 28 14:52:31 robot02 kernel: [ 3616.449625] device rteth0 entered promiscuous mode <nothing is received anymore after >100000 packets> <resetting wireshark> Feb 28 15:02:09 robot02 kernel: [ 4193.923103] device rteth0 left promiscuous mode Feb 28 15:02:10 robot02 kernel: [ 4194.306697] device rteth0 entered promiscuous mode <still no more packets received, running rtping> <no "Abnormal interrupt message this time; wireshark shows an old package and ARP requests and ping communication> <resetting wireshark> <nothing is received anymore after ca 64000 packets> <running rtping> <no "Abnormal interrupt message this time; wireshark shows an old package and ARP requests and ping communication> <resetting wireshark> <nothing is received anymore after ca 372000 packets> <running rtping> <no "Abnormal interrupt message this time; wireshark shows an old package and ARP requests and ping communication> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Anyone has an idea, where the problem might be?uname --all Linux robot02 2.6.35.7-xeno #1 SMP Sat Nov 13 15:21:22 CET 2010 x86_64 GNU/Linux last commit to rtnet git repository I used to compile RTNet was: ------------------------------------------------------------------------------------ commit d84fca3830f142b199473af1364955c035b70f4b Author: Jan Kiszka <jan.kis...@siemens.com> Date: Thu Nov 11 19:37:32 2010 +0100 rt_igb: Enable MSI/MSI-X support Signed-off-by: Jan Kiszka <jan.kis...@siemens.com> -----------------------------------------------------------------------------------
|
------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
