From: Gerhard H. <Ger...@pe...> - 2009-10-08 15:25:44
|
Hello Musti, thanks a lot for your response. I just started another test 7) on my XM4 (netmicroSD-vx + console-vx) buffering to ramdisk. 7.1) last ifconfig before eth0 breakdown: eth0 Link encap:Ethernet HWaddr 46:D1:8F:50:9F:D0 inet addr:192.168.0.18 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12381 errors:0 dropped:0 overruns:0 frame:0 TX packets:274 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:15343241 (14.6 MiB) TX bytes:30406 (29.6 KiB) Interrupt:131 DMA chan:ff wlan0 Link encap:Ethernet HWaddr 00:0B:6B:0D:BA:DB inet addr:192.168.9.20 Bcast:192.168.9.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6258 errors:0 dropped:0 overruns:0 frame:0 TX packets:12173 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:252960 (247.0 KiB) TX bytes:15590719 (14.8 MiB) Interrupt:128 7.2) ifconfig after eth0 breakdown: eth0 Link encap:Ethernet HWaddr 46:D1:8F:50:9F:D0 inet addr:192.168.0.18 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14608 errors:0 dropped:0 overruns:0 frame:0 TX packets:275 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:18156965 (17.3 MiB) TX bytes:30448 (29.7 KiB) Interrupt:131 DMA chan:ff wlan0 Link encap:Ethernet HWaddr 00:0B:6B:0D:BA:DB inet addr:192.168.9.20 Bcast:192.168.9.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7376 errors:0 dropped:0 overruns:0 frame:0 TX packets:14368 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:297881 (290.8 KiB) TX bytes:18461463 (17.6 MiB) Interrupt:128 > Do you observe the increasing error count too? As you can see there are no errors at all in my case - neither after nor before breakdown. But this time I could transfer quite a lot data (around 17MB) as you can see above. What I have seen again during this test was the kernel message: NETDEV WATCHDOG: eth0: transmit timed out eth0: link down after some time (around 2 Minutes ... and after restarting the test it came after 15 Min). So it seems that the timeout is coming always, but only sometimes quite late. But it is always the same, that I can ping the gumstix over wlan, but offcourse not over eth0 any more. So wlan is still alive Musti, did you also use an adhoc or the managed mode for your wlan connection? Maybe I am going to the same things transfering the data over my wlan router and trying the managed mode next ... By the way my iwconfig output on wlan0 is the following: wlan0 MRVL-CF8385 ESSID:"myNet" Nickname:"" Mode:Ad-Hoc Frequency:2.437 GHz Cell: 02:22:D2:D1:32:D1 Bit Rate:48 Mb/s Tx-Power=13 dBm Retry limit:8 RTS thr=2347 B Fragment thr=2346 B Encryption key:off Power Management:off Link Quality:0/10 Signal level:-38 dBm Noise level:-97 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:532573 Tx excessive retries:73 Invalid misc:314 Missed beacon:0 Does anybody have an idea where else I could look at, or whatelse I could try? thanks again in advance Gerhard |