Hi, I'm using the iwlwifi for my WP2 encrypted 135 Mb/s WiFi network connection. Uploading files on my NAS using SMB is quite depressing. The upload speed begins at around 4.5 MB/s (like on Windows 7 all the time) and then collapses to around 0.6 MB/s after some seconds (10 – 20 secs). I don't find any WiFi or Samba error message in the syslog, but something is definitely wrong. Best Regards, Ettore Atalan nm-tool output: - Device: wlan0 [-] ----------------------------------------------------------- Type: 802.11 WiFi Driver: iwlwifi State: connected Default: yes Capabilities: Speed: 135 Mb/s Wireless Properties WEP Encryption: yes WPA Encryption: yes WPA2 Encryption: yes IPv4 Settings: Address: 192.168.2.104 Prefix: 24 (255.255.255.0) Gateway: 192.168.2.1 DNS: 192.168.2.1
This bug is lacking tons of details: I need lspci (to know what device) *full* dmesg that will be just to start.
Created attachment 152501 [details] lspci output (In reply to Emmanuel Grumbach from comment #1) > This bug is lacking tons of details: This was clear to me. > I need lspci (to know what device) Please see the attachment.
Created attachment 152521 [details] full dmesg (In reply to Emmanuel Grumbach from comment #1) > *full* dmesg > > that will be just to start. Okay. Best Regards, Ettore Atalan
Created attachment 152531 [details] dmesg supplement after this problem has happened Please feel free to ask for further log files and/or details.
Please do the following when traffic doesn't go trough as root: echo 0xC0800000 > /sys/module/iwlwifi/parameters/debug as regular user: ping 192.168.1.1 -c25 then, let me know what you see in the ping window, and attach the dmesg to the bug. Thanks.
(In reply to Emmanuel Grumbach from comment #5) > Please do the following when traffic doesn't go trough Do you mean no traffic (resp. file upload) at all or when the problem appears while uploading a file to the NAS? > as regular user: > ping 192.168.1.1 -c25 BTW, I have no device with this IP address. Best Regards, Ettore Atalan
(In reply to Ettore Atalan from comment #6) > (In reply to Emmanuel Grumbach from comment #5) > > Please do the following when traffic doesn't go trough > > Do you mean no traffic (resp. file upload) at all or when the problem > appears while uploading a file to the NAS? when problem occurs. > > > > as regular user: > > ping 192.168.1.1 -c25 > > BTW, I have no device with this IP address. This seemed to be your gateway - but whatever is in your subnet. > > > Best Regards, > Ettore Atalan
Created attachment 152541 [details] current dmesg (In reply to Emmanuel Grumbach from comment #5) > Please do the following when traffic doesn't go trough > > as root: > echo 0xC0800000 > /sys/module/iwlwifi/parameters/debug Output (unfortunately not very helpful): echo 0xC0800000 > /sys/module/iwlwifi/parameters/debug: command not found > as regular user: > ping 192.168.1.1 -c25 > > then, let me know what you see in the ping window, … Output: PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=2.52 ms 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=3.08 ms 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=3.05 ms 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=4.98 ms 64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=3.07 ms 64 bytes from 192.168.2.1: icmp_seq=6 ttl=64 time=3.19 ms 64 bytes from 192.168.2.1: icmp_seq=7 ttl=64 time=1.99 ms 64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=4.38 ms 64 bytes from 192.168.2.1: icmp_seq=9 ttl=64 time=4.04 ms 64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=3.23 ms 64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=3.86 ms 64 bytes from 192.168.2.1: icmp_seq=12 ttl=64 time=3.96 ms 64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=2.85 ms 64 bytes from 192.168.2.1: icmp_seq=14 ttl=64 time=1.96 ms 64 bytes from 192.168.2.1: icmp_seq=15 ttl=64 time=3.18 ms 64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=1.76 ms 64 bytes from 192.168.2.1: icmp_seq=17 ttl=64 time=4.71 ms 64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=3.25 ms 64 bytes from 192.168.2.1: icmp_seq=19 ttl=64 time=4.92 ms 64 bytes from 192.168.2.1: icmp_seq=20 ttl=64 time=3.29 ms 64 bytes from 192.168.2.1: icmp_seq=21 ttl=64 time=2.83 ms 64 bytes from 192.168.2.1: icmp_seq=22 ttl=64 time=3.24 ms 64 bytes from 192.168.2.1: icmp_seq=23 ttl=64 time=1.89 ms 64 bytes from 192.168.2.1: icmp_seq=24 ttl=64 time=3.32 ms 64 bytes from 192.168.2.1: icmp_seq=25 ttl=64 time=3.14 ms --- 192.168.2.1 ping statistics --- 25 packets transmitted, 25 received, 0% packet loss, time 24033ms rtt min/avg/max/mdev = 1.766/3.271/4.980/0.874 ms > … and attach the dmesg to the bug. Okay. > Thanks. You're welcome. Best Regards, Ettore Atalan
your pings look very good... I don't seen any bug on the wifi side here...
Is it more likely a SMB/CIFS problem?
(In reply to Ettore Atalan from comment #10) > Is it more likely a SMB/CIFS problem? can't really tell - but you see that your ping response time is fine. I suggest you ping your gateway while you run your transfer - to see what happens. As long as the ping response time is fine, it means you don't have problems from the WiFi side.
Created attachment 152551 [details] ping output The ping is better after the upload speed has dropped.
makes sense your wifi is working perfectly. Closing the bug.
I have created a bug report for this in the samba bug tracker. URL: https://bugzilla.samba.org/show_bug.cgi?id=10856 Best Regards, Ettore Atalan
The FTP upload speed is now as slow as with SMB/CIFS after upgrading to Kubuntu 15.04 with Kernel 3.19. PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data. 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=3.21 ms 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=3.28 ms 64 bytes from 192.168.2.1: icmp_seq=3 ttl=64 time=3.12 ms 64 bytes from 192.168.2.1: icmp_seq=4 ttl=64 time=4.37 ms 64 bytes from 192.168.2.1: icmp_seq=5 ttl=64 time=3.31 ms 64 bytes from 192.168.2.1: icmp_seq=6 ttl=64 time=3.33 ms 64 bytes from 192.168.2.1: icmp_seq=7 ttl=64 time=12.0 ms (!) 64 bytes from 192.168.2.1: icmp_seq=8 ttl=64 time=3.30 ms 64 bytes from 192.168.2.1: icmp_seq=9 ttl=64 time=5.00 ms 64 bytes from 192.168.2.1: icmp_seq=10 ttl=64 time=3.27 ms 64 bytes from 192.168.2.1: icmp_seq=11 ttl=64 time=3.11 ms 64 bytes from 192.168.2.1: icmp_seq=12 ttl=64 time=3.27 ms 64 bytes from 192.168.2.1: icmp_seq=13 ttl=64 time=4.34 ms 64 bytes from 192.168.2.1: icmp_seq=14 ttl=64 time=3.30 ms 64 bytes from 192.168.2.1: icmp_seq=15 ttl=64 time=3.29 ms 64 bytes from 192.168.2.1: icmp_seq=16 ttl=64 time=5.54 ms 64 bytes from 192.168.2.1: icmp_seq=17 ttl=64 time=3.12 ms 64 bytes from 192.168.2.1: icmp_seq=18 ttl=64 time=5.17 ms 64 bytes from 192.168.2.1: icmp_seq=19 ttl=64 time=3.10 ms 64 bytes from 192.168.2.1: icmp_seq=20 ttl=64 time=3.33 ms 64 bytes from 192.168.2.1: icmp_seq=21 ttl=64 time=3.26 ms 64 bytes from 192.168.2.1: icmp_seq=22 ttl=64 time=2.73 ms 64 bytes from 192.168.2.1: icmp_seq=23 ttl=64 time=3.29 ms 64 bytes from 192.168.2.1: icmp_seq=24 ttl=64 time=3.33 ms 64 bytes from 192.168.2.1: icmp_seq=25 ttl=64 time=4.73 ms --- 192.168.2.1 ping statistics --- 25 packets transmitted, 25 received, 0% packet loss, time 24033ms rtt min/avg/max/mdev = 2.735/3.968/12.020/1.801 ms Best Regards, Ettore Atalan
I don't see any problem with the ping times. There is nothing I can do with this.
Another problem?
Your WiFi device behaves well. That's all I am accountable for. Instead of wasting my time, I'll remove myself from this bug.
(In reply to Emmanuel Grumbach from comment #18) > Your WiFi device behaves well. No, the upload rate of my WiFi device is much slower on Linux (~ 600 KB/s) than on Windows 7 (~ 4.5 MB/s). > That's all I am accountable for. Who is accountable for the upload rate?