Bug 85601 - iwlwifi: dvm: Wireless-N 100 Samba upload speed collapses after some seconds
Summary: iwlwifi: dvm: Wireless-N 100 Samba upload speed collapses after some seconds
Status: REOPENED
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL: https://bugzilla.samba.org/show_bug.c...
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-04 21:08 UTC by Ettore Atalan
Modified: 2015-05-07 15:20 UTC (History)
0 users

See Also:
Kernel Version: 3.16
Tree: Mainline
Regression: No


Attachments
lspci output (1.38 KB, text/plain)
2014-10-05 19:20 UTC, Ettore Atalan
Details
full dmesg (53.25 KB, text/plain)
2014-10-05 19:59 UTC, Ettore Atalan
Details
dmesg supplement after this problem has happened (1.05 KB, text/plain)
2014-10-05 20:34 UTC, Ettore Atalan
Details
current dmesg (50.67 KB, text/plain)
2014-10-06 12:25 UTC, Ettore Atalan
Details
ping output (6.01 KB, text/plain)
2014-10-06 12:48 UTC, Ettore Atalan
Details

Description Ettore Atalan 2014-10-04 21:08:45 UTC
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
Comment 1 Emmanuel Grumbach 2014-10-05 05:38:12 UTC
This bug is lacking tons of details:

I need lspci (to know what device)
*full* dmesg

that will be just to start.
Comment 2 Ettore Atalan 2014-10-05 19:20:26 UTC
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.
Comment 3 Ettore Atalan 2014-10-05 19:59:57 UTC
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
Comment 4 Ettore Atalan 2014-10-05 20:34:30 UTC
Created attachment 152531 [details]
dmesg supplement after this problem has happened

Please feel free to ask for further log files and/or details.
Comment 5 Emmanuel Grumbach 2014-10-06 07:09:23 UTC
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.
Comment 6 Ettore Atalan 2014-10-06 11:32:32 UTC
(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
Comment 7 Emmanuel Grumbach 2014-10-06 11:34:36 UTC
(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
Comment 8 Ettore Atalan 2014-10-06 12:25:02 UTC
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
Comment 9 Emmanuel Grumbach 2014-10-06 12:27:09 UTC
your pings look very good...

I don't seen any bug on the wifi side here...
Comment 10 Ettore Atalan 2014-10-06 12:29:43 UTC
Is it more likely a SMB/CIFS problem?
Comment 11 Emmanuel Grumbach 2014-10-06 12:33:38 UTC
(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.
Comment 12 Ettore Atalan 2014-10-06 12:48:24 UTC
Created attachment 152551 [details]
ping output

The ping is better after the upload speed has dropped.
Comment 13 Emmanuel Grumbach 2014-10-06 12:52:53 UTC
makes sense
your wifi is working perfectly.

Closing the bug.
Comment 14 Ettore Atalan 2014-10-06 14:04:22 UTC
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
Comment 15 Ettore Atalan 2015-05-07 13:34:51 UTC
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
Comment 16 Emmanuel Grumbach 2015-05-07 13:37:44 UTC
I don't see any problem with the ping times.

There is nothing I can do with this.
Comment 17 Ettore Atalan 2015-05-07 13:56:08 UTC
Another problem?
Comment 18 Emmanuel Grumbach 2015-05-07 14:41:53 UTC
Your WiFi device behaves well. That's all I am accountable for.
Instead of wasting my time, I'll remove myself from this bug.
Comment 19 Ettore Atalan 2015-05-07 15:20:27 UTC
(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?

Note You need to log in before you can comment on or make changes to this bug.