Bug 202943
Summary: | Realtek 8192ee high ping only without load | ||
---|---|---|---|
Product: | Networking | Reporter: | aladjev.andrew (aladjev.andrew) |
Component: | Wireless | Assignee: | networking_wireless (networking_wireless) |
Status: | NEW --- | ||
Severity: | normal | CC: | aladjev.andrew, haritonovsb, lukas.redlinger |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 4.20.16 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
aladjev.andrew@gmail.com
2019-03-15 21:25:45 UTC
Hello! I'd like to report exactly the same situation. It's strange that the problem didn't get much of attention and support. ]$ lspci | grep Wireless 03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192EE PCIe Wireless Network Adapter on ad Tp-Link TL-WN881ND rev.2 PCIe x1 card. All available powersaving-related module options have been tested, it stays the same. Also tested master branch from https://github.com/lwfinger/rtlwifi_new, still no changes. ]$ uname -a Linux 5.2.6-arch1-1-ARCH #1 SMP PREEMPT Sun Aug 4 14:58:49 UTC 2019 x86_64 GNU/Linux ]$ lsmod | grep 8192 rtl8192ee 131072 0 btcoexist 217088 1 rtl8192ee rtl_pci 36864 1 rtl8192ee rtlwifi 126976 3 rtl_pci,btcoexist,rtl8192ee mac80211 999424 3 rtl_pci,rtlwifi,rtl8192ee ]$ ping 192.168.88.1 PING 192.168.88.1 (192.168.88.1) 56(84) bytes of data. 64 bytes from 192.168.88.1: icmp_seq=1 ttl=64 time=94.5 ms 64 bytes from 192.168.88.1: icmp_seq=2 ttl=64 time=14.5 ms 64 bytes from 192.168.88.1: icmp_seq=3 ttl=64 time=36.8 ms 64 bytes from 192.168.88.1: icmp_seq=4 ttl=64 time=58.9 ms 64 bytes from 192.168.88.1: icmp_seq=5 ttl=64 time=80.9 ms 64 bytes from 192.168.88.1: icmp_seq=6 ttl=64 time=104 ms 64 bytes from 192.168.88.1: icmp_seq=7 ttl=64 time=24.5 ms 64 bytes from 192.168.88.1: icmp_seq=8 ttl=64 time=46.9 ms 64 bytes from 192.168.88.1: icmp_seq=9 ttl=64 time=68.9 ms 64 bytes from 192.168.88.1: icmp_seq=10 ttl=64 time=90.9 ms 64 bytes from 192.168.88.1: icmp_seq=11 ttl=64 time=11.5 ms 64 bytes from 192.168.88.1: icmp_seq=12 ttl=64 time=33.8 ms 64 bytes from 192.168.88.1: icmp_seq=13 ttl=64 time=55.9 ms 64 bytes from 192.168.88.1: icmp_seq=14 ttl=64 time=77.9 ms 64 bytes from 192.168.88.1: icmp_seq=15 ttl=64 time=44.2 ms 64 bytes from 192.168.88.1: icmp_seq=16 ttl=64 time=21.2 ms 64 bytes from 192.168.88.1: icmp_seq=17 ttl=64 time=43.8 ms 64 bytes from 192.168.88.1: icmp_seq=18 ttl=64 time=65.9 ms 64 bytes from 192.168.88.1: icmp_seq=19 ttl=64 time=87.9 ms 64 bytes from 192.168.88.1: icmp_seq=20 ttl=64 time=8.51 ms ^C --- 192.168.88.1 ping statistics --- 20 packets transmitted, 20 received, 0% packet loss, time 49ms rtt min/avg/max/mdev = 8.506/53.563/103.894/28.854 ms then if I download an archlinux iso at ~70-80 Mbit/s in the background is looks like ]$ ping 192.168.88.1 PING 192.168.88.1 (192.168.88.1) 56(84) bytes of data. 64 bytes from 192.168.88.1: icmp_seq=1 ttl=64 time=1.40 ms 64 bytes from 192.168.88.1: icmp_seq=2 ttl=64 time=2.34 ms 64 bytes from 192.168.88.1: icmp_seq=3 ttl=64 time=1.29 ms 64 bytes from 192.168.88.1: icmp_seq=4 ttl=64 time=1.63 ms 64 bytes from 192.168.88.1: icmp_seq=5 ttl=64 time=1.55 ms 64 bytes from 192.168.88.1: icmp_seq=6 ttl=64 time=2.16 ms 64 bytes from 192.168.88.1: icmp_seq=7 ttl=64 time=4.64 ms 64 bytes from 192.168.88.1: icmp_seq=8 ttl=64 time=1.54 ms 64 bytes from 192.168.88.1: icmp_seq=9 ttl=64 time=2.01 ms 64 bytes from 192.168.88.1: icmp_seq=10 ttl=64 time=1.66 ms 64 bytes from 192.168.88.1: icmp_seq=11 ttl=64 time=1.85 ms 64 bytes from 192.168.88.1: icmp_seq=12 ttl=64 time=1.55 ms 64 bytes from 192.168.88.1: icmp_seq=13 ttl=64 time=1.58 ms 64 bytes from 192.168.88.1: icmp_seq=14 ttl=64 time=2.58 ms 64 bytes from 192.168.88.1: icmp_seq=15 ttl=64 time=2.30 ms 64 bytes from 192.168.88.1: icmp_seq=16 ttl=64 time=3.17 ms Update. I get these results ~]$ ping 192.168.88.1 PING 192.168.88.1 (192.168.88.1) 56(84) bytes of data. 64 bytes from 192.168.88.1: icmp_seq=1 ttl=64 time=0.746 ms 64 bytes from 192.168.88.1: icmp_seq=2 ttl=64 time=0.868 ms 64 bytes from 192.168.88.1: icmp_seq=3 ttl=64 time=0.853 ms 64 bytes from 192.168.88.1: icmp_seq=4 ttl=64 time=0.868 ms 64 bytes from 192.168.88.1: icmp_seq=5 ttl=64 time=0.818 ms 64 bytes from 192.168.88.1: icmp_seq=6 ttl=64 time=0.844 ms 64 bytes from 192.168.88.1: icmp_seq=7 ttl=64 time=0.841 ms 64 bytes from 192.168.88.1: icmp_seq=8 ttl=64 time=0.913 ms 64 bytes from 192.168.88.1: icmp_seq=9 ttl=64 time=0.844 ms 64 bytes from 192.168.88.1: icmp_seq=10 ttl=64 time=0.886 ms ^C --- 192.168.88.1 ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 387ms rtt min/avg/max/mdev = 0.746/0.848/0.913/0.044 ms with a driver from rtl8192ee_revised.tar.bz2 file in https://github.com/lwfinger/rtlwifi_new/tree/extended repository built against Linux 4.19.65-1-lts #1 SMP Wed Aug 7 21:48:46 UTC 2019 x86_64 GNU/Linux ArchLinux current LTS kernel. Connection speed and stability on a heavy load are also not affected. have you tried disabling power management this way? iw dev <devname> set power_save off Yes, I've tried this before. Still no luck. [user@host ~]$ ping 192.168.88.1 PING 192.168.88.1 (192.168.88.1) 56(84) bytes of data. 64 bytes from 192.168.88.1: icmp_seq=1 ttl=64 time=29.1 ms 64 bytes from 192.168.88.1: icmp_seq=2 ttl=64 time=18.5 ms 64 bytes from 192.168.88.1: icmp_seq=3 ttl=64 time=40.9 ms 64 bytes from 192.168.88.1: icmp_seq=4 ttl=64 time=63.9 ms 64 bytes from 192.168.88.1: icmp_seq=5 ttl=64 time=85.9 ms 64 bytes from 192.168.88.1: icmp_seq=6 ttl=64 time=5.46 ms 64 bytes from 192.168.88.1: icmp_seq=7 ttl=64 time=28.9 ms 64 bytes from 192.168.88.1: icmp_seq=8 ttl=64 time=51.8 ms 64 bytes from 192.168.88.1: icmp_seq=9 ttl=64 time=73.9 ms 64 bytes from 192.168.88.1: icmp_seq=10 ttl=64 time=32.8 ms 64 bytes from 192.168.88.1: icmp_seq=11 ttl=64 time=15.9 ms ^C --- 192.168.88.1 ping statistics --- 11 packets transmitted, 11 received, 0% packet loss, time 10015ms rtt min/avg/max/mdev = 5.460/40.630/85.857/24.278 ms [user@host ~]$ sudo iw dev wlp3s0 set power_save off [user@host ~]$ ping 192.168.88.1 PING 192.168.88.1 (192.168.88.1) 56(84) bytes of data. 64 bytes from 192.168.88.1: icmp_seq=1 ttl=64 time=35.3 ms 64 bytes from 192.168.88.1: icmp_seq=2 ttl=64 time=57.9 ms 64 bytes from 192.168.88.1: icmp_seq=3 ttl=64 time=80.8 ms 64 bytes from 192.168.88.1: icmp_seq=4 ttl=64 time=103 ms 64 bytes from 192.168.88.1: icmp_seq=5 ttl=64 time=23.5 ms 64 bytes from 192.168.88.1: icmp_seq=6 ttl=64 time=45.2 ms 64 bytes from 192.168.88.1: icmp_seq=7 ttl=64 time=68.5 ms 64 bytes from 192.168.88.1: icmp_seq=8 ttl=64 time=90.3 ms 64 bytes from 192.168.88.1: icmp_seq=9 ttl=64 time=10.5 ms 64 bytes from 192.168.88.1: icmp_seq=10 ttl=64 time=33.4 ms 64 bytes from 192.168.88.1: icmp_seq=11 ttl=64 time=56.5 ms 64 bytes from 192.168.88.1: icmp_seq=12 ttl=64 time=82.5 ms ^C --- 192.168.88.1 ping statistics --- 12 packets transmitted, 12 received, 0% packet loss, time 11016ms rtt min/avg/max/mdev = 10.487/57.270/102.931/27.413 ms On Mon, Sep 30, 2019 at 4:16 PM <bugzilla-daemon@bugzilla.kernel.org> wrote: > > https://bugzilla.kernel.org/show_bug.cgi?id=202943 > > lukas.redlinger@agilox.net changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |lukas.redlinger@agilox.net > > --- Comment #3 from lukas.redlinger@agilox.net --- > have you tried disabling power management this way? > > iw dev <devname> set power_save off > > -- > You are receiving this mail because: > You are on the CC list for the bug. |