Testing on the mainline v4.8-rc3 kernel, the first thing that happens is that the NIC dies before I can even use it. Browser just sits there, so I try to ping:
thor@thor-ideapad:~$ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. ping: sendmsg: No buffer space available ping: sendmsg: No buffer space available ^C --- 8.8.8.8 ping statistics --- 10 packets transmitted, 0 received, 100% packet loss, time 28251ms Then I unload the module to try to recover: thor@thor-ideapad:~$ sudo modprobe -r rtl8821ae thor@thor-ideapad:~$ sudo modprobe rtl8821ae The modprobe kind of sits there for several seconds trying to unload before it returns to the command line. Something isn't responding as it should I think, because usually, kernel modules unload almost instantly. So anyway, I now manage to stay connected, so I ping: thor@thor-ideapad:~$ ping 8.8.8.8 ... ... ... 64 bytes from 8.8.8.8: icmp_seq=16 ttl=55 time=8203 ms 64 bytes from 8.8.8.8: icmp_seq=17 ttl=55 time=7154 ms 64 bytes from 8.8.8.8: icmp_seq=18 ttl=55 time=6130 ms 64 bytes from 8.8.8.8: icmp_seq=19 ttl=55 time=5106 ms 64 bytes from 8.8.8.8: icmp_seq=20 ttl=55 time=4084 ms 64 bytes from 8.8.8.8: icmp_seq=21 ttl=55 time=3060 ms 64 bytes from 8.8.8.8: icmp_seq=22 ttl=55 time=2036 ms 64 bytes from 8.8.8.8: icmp_seq=23 ttl=55 time=12.7 ms 64 bytes from 8.8.8.8: icmp_seq=24 ttl=55 time=47.7 ms 64 bytes from 8.8.8.8: icmp_seq=25 ttl=55 time=12.1 ms 64 bytes from 8.8.8.8: icmp_seq=26 ttl=55 time=12.1 ms 64 bytes from 8.8.8.8: icmp_seq=27 ttl=55 time=11.5 ms 64 bytes from 8.8.8.8: icmp_seq=28 ttl=55 time=11.8 ms 64 bytes from 8.8.8.8: icmp_seq=29 ttl=55 time=11.7 ms 64 bytes from 8.8.8.8: icmp_seq=30 ttl=55 time=12.2 ms 64 bytes from 8.8.8.8: icmp_seq=31 ttl=55 time=11.4 ms 64 bytes from 8.8.8.8: icmp_seq=32 ttl=55 time=21.4 ms 64 bytes from 8.8.8.8: icmp_seq=33 ttl=55 time=13.4 ms 64 bytes from 8.8.8.8: icmp_seq=34 ttl=55 time=11.5 ms 64 bytes from 8.8.8.8: icmp_seq=35 ttl=55 time=12.5 ms 64 bytes from 8.8.8.8: icmp_seq=36 ttl=55 time=12.6 ms 64 bytes from 8.8.8.8: icmp_seq=37 ttl=55 time=11.5 ms 64 bytes from 8.8.8.8: icmp_seq=38 ttl=55 time=40.7 ms 64 bytes from 8.8.8.8: icmp_seq=39 ttl=55 time=69.3 ms 64 bytes from 8.8.8.8: icmp_seq=40 ttl=55 time=108 ms 64 bytes from 8.8.8.8: icmp_seq=41 ttl=55 time=194 ms 64 bytes from 8.8.8.8: icmp_seq=42 ttl=55 time=12.3 ms 64 bytes from 8.8.8.8: icmp_seq=43 ttl=55 time=192 ms 64 bytes from 8.8.8.8: icmp_seq=44 ttl=55 time=12.0 ms 64 bytes from 8.8.8.8: icmp_seq=45 ttl=55 time=191 ms 64 bytes from 8.8.8.8: icmp_seq=46 ttl=55 time=12.0 ms 64 bytes from 8.8.8.8: icmp_seq=47 ttl=55 time=137 ms 64 bytes from 8.8.8.8: icmp_seq=48 ttl=55 time=25.6 ms 64 bytes from 8.8.8.8: icmp_seq=49 ttl=55 time=3684 ms 64 bytes from 8.8.8.8: icmp_seq=50 ttl=55 time=2626 ms 64 bytes from 8.8.8.8: icmp_seq=51 ttl=55 time=1606 ms 64 bytes from 8.8.8.8: icmp_seq=52 ttl=55 time=585 ms 64 bytes from 8.8.8.8: icmp_seq=53 ttl=55 time=4381 ms ... ... ... It kind of does this weird cycle with the ping times. It's what I saw before with the distribution kernel, so there's no difference there. I noticed that this bug has been tagged with bios-outdated. Should I look into flashing a new BIOS on the machine? I won't touch a thing unless instructed to do so. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618267 Title: RTL8821AE abruptly halts all network traffic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
