RPI4 wifi unreliable when usb3 storage is attached
Bug #1861338 reported by
Paul Larson
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-raspi2 (Ubuntu) |
Invalid
|
High
|
Hui Wang | ||
Eoan |
Expired
|
Undecided
|
Unassigned |
Bug Description
On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage device to one of the 2x usb3 ports (the ones closest to the ethernet port), wifi will sudden stop working. If you unplug the usb stick while running a ping, it will usually start working again almost instantaneously.
Kernel version I have is: 5.3.0-1017-raspi2
and I've confirmed this happens on both armhf and arm64
The only thing I found in journalctl that looks suspicious is this, but it seems to have happened before plugging in the usb stick:
Jan 29 20:54:59 ubuntu wpa_supplicant[
I just did a test, could not reproduce this issue. Maybe your usb storage consumes too much power, could you please change other usb sticks to redo the test?
on the usb-serial console, my Wifi is enabled and ping a website: UP,LOOPBACK, RUNNING> mtu 65536
ubuntu@ubuntu:~$ uname -a
Linux ubuntu 5.3.0-1017-raspi2 #19+otg SMP Wed Jan 29 12:45:11 CST 2020 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@ubuntu:~$ ifconfig
lo: flags=73<
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 10 bytes 842 (842.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 10 bytes 842 (842.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163< UP,BROADCAST, RUNNING, MULTICAST> mtu 1500 32ff:fe0e: 9bc5 prefixlen 64 scopeid 0x20<link>
inet 192.168.2.104 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::dea6:
ether dc:a6:32:0e:9b:c5 txqueuelen 1000 (Ethernet)
RX packets 58 bytes 7614 (7.6 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 69 bytes 7950 (7.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ubuntu@ubuntu:~$ ping www.sohu.com
PING fbx.a.sohu.com (123.126.104.68) 56(84) bytes of data.
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=1 ttl=57 time=10.4 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=2 ttl=57 time=6.75 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=3 ttl=57 time=4.80 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=4 ttl=57 time=17.3 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=5 ttl=57 time=5.55 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=6 ttl=57 time=5.24 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=7 ttl=57 time=5.08 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=8 ttl=57 time=6.37 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=9 ttl=57 time=6.56 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=10 ttl=57 time=4.25 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=11 ttl=57 time=7.62 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=12 ttl=57 time=4.09 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=13 ttl=57 time=7.59 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=14 ttl=57 time=7.78 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=15 ttl=57 time=6.42 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=16 ttl=57 time=4.29 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=17 ttl=57 time=4.03 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=18 ttl=57 time=4.06 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=19 ttl=57 time=13.3 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=20 ttl=57 time=4.16 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=21 ttl=57 time=11.1 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=22 ttl=57 time=6.45 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=23 ttl=57 time=5.60 ms
64 bytes from 123.126.104.68 (123.126.104.68...