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:
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<UP,LOOPBACK,RUNNING> mtu 65536
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
inet 192.168.2.104 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::dea6:32ff:fe0e:9bc5 prefixlen 64 scopeid 0x20<link>
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): icmp_seq=24 ttl=57 time=3.86 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=25 ttl=57 time=5.81 ms
64 bytes from 123.126.104.68 (123.126.104.68): icmp_seq=26 ttl=57 time=6.88 ms
,,,,
On a console via ssh, we can see a usb stick is plugged into the usb3 and mount
it to /mnt/
[ 142.964958] usb 1-1.2: new high-speed USB device number 3 using xhci_hcd
[ 143.065593] usb 1-1.2: New USB device found, idVendor=0781, idProduct=5575,
bcdDevice= 1.27
[ 143.065609] usb 1-1.2: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 143.065620] usb 1-1.2: Product: Cruzer Glide
[ 143.065631] usb 1-1.2: Manufacturer: SanDisk
[ 143.065640] usb 1-1.2: SerialNumber: 20043109300EAD30F6EF
[ 143.117186] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[ 143.119025] scsi host0: usb-storage 1-1.2:1.0
[ 143.119391] usbcore: registered new interface driver usb-storage
[ 143.124401] usbcore: registered new interface driver uas
[ 144.130229] scsi 0:0:0:0: Direct-Access SanDisk Cruzer Glide 1.27
PQ: 0 ANSI: 6
[ 144.131441] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 144.132701] sd 0:0:0:0: [sda] 15223808 512-byte logical blocks: (7.79
GB/7.26 GiB)
[ 144.134146] sd 0:0:0:0: [sda] Write Protect is off
[ 144.134161] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
[ 144.134745] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled,
doesn't support DPO or FUA
[ 144.152487] sda: sda1
[ 144.156442] sd 0:0:0:0: [sda] Attached SCSI removable disk
^C
ubuntu@ubuntu:~$ sudo mount /dev/sda
sda sda1
ubuntu@ubuntu:~$ sudo mount /dev/sda1 /mnt/
ubuntu@ubuntu:~$ ls /mnt/
'1 Unit 1.mp3' 2.nsh EFIFlash.efi Fpt.efi
M.nsh SKL_DT_AIO_RVP_KSC_v01_04.bin
'System Volume Information' fparts.txt
1.nsh BOOTEX.LOG FCNTRL.BIN
KBL_DT_RVP8_DSTEP_Prod_SATA_NOPTT_CONS_IFWI_BIOS_33_3_ME_1040_Ext.bin R.nsh
STARTUP.NSH eeupdate64e.efi map
** Changed in: linux-raspi2 (Ubuntu)
Status: New => Triaged
** Changed in: linux-raspi2 (Ubuntu)
Importance: Undecided => High
** Changed in: linux-raspi2 (Ubuntu)
Assignee: (unassigned) => Hui Wang (hui.wang)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1861338
Title:
RPI4 wifi unreliable when usb3 storage is attached
Status in linux-raspi2 package in Ubuntu:
Triaged
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[1129]: random: Cannot read from
/dev/random: Resource temporarily unavailable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861338/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
