[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Well, I only managed to replicate it on Ubuntu, and it requires many conditions to be met: - 6in4 tunnel to HE.net - ipv6 rules applied - ipv6 forwarding enabled Removing/replacing any one of these made downloading (wget -O /dev/null) reliable for at least 3 repeats of a large (~1GB+) downloads. I recreated the setup on Raspbian, and so far haven't had the issue. ** Summary changed: - Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) + Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Never mind the LAN7515 heatsink. The issue was avoided by some combination of other missing configuration (I have since managed to trigger the issue): - iptables-rules not loaded - dnsmasq not running Sometimes (in the full HE.net tunnel + v6 gateway configuration), the problem is triggered by an IPv4 download, even. I'll keep tracking this down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Huh... even downloading over HE.net's tunnel doesn't kill it (within the 3 attempts I've tried) now. I have previously added a passive cooler to the USB/NIC chip as the RPi3 was down for this test. I'll keep the RPi3 up as a caching DNS + IPv6 gateway (ie. as before, minus DHCPv4), point DNS queries to it, and see how it behaves for the next week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
I made a pair of scripts - one sets up the tunnel, addresses on dummy interfaces, and routing. The other one cleans up. Testing with iperf does NOT replicate the issue, however. Maybe someone else can find a test case that reliably triggers the bug. I have some ideas which I'll try soon. https://gist.github.com/myxal/7a191e8a62a45f9187ae56cbe3c862b2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Sorry for the delayed response. I moved my network back to RPi1 so I can do experiments on the affected RPi3. I'm thinking, if this is indeed caused by the usage of a 6in4 tunnel, and you're unable to set up one with HE.net because of unavailability/ISP restrictions, it should be possible to set up a 6in4 tunnel within your own network (obviously, another host would be needed for this). I'll try to provide a config/script/whatever that would do this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
OK, I will continue studying how to setup ipv6. And could you please find some easy ways to reproduce this problem (like without ipv6), if you could, it will be easier to debug and we could report this issue to raspberry.org too. thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Oh, I had the URL wrong (archive.ubuntu instead of ports...). Installed .1019 kernel, headers, etc... issue persists with the new kernel - dmesg attached. ** Attachment added: "dmesg-1019.txt" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5330924/+files/dmesg-1019.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
So far, I couldn't set up the ipv6 on my rpi3B+ board, I need to do more study. And I checked the eoan-proposed, the 1019 kernel is already there. If there is no this file in the folder /etc/apt/sources.list.d/ on your board, you could put this file to that folder and run sudo apt-get update Then you could install 1019 kernel to do the test. sudo apt install linux-image-(press tab), it will list 1019 kernel. ** Attachment added: "proposed.list" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5330815/+files/proposed.list -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
re: dnsmasq - whoops, private repo. Here's another link: https://paste.ubuntu.com/p/TCwQBkg9vS/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
@hui.wang: Only the RPi is acting as the IPv6 gateway for the network (it sends router advertisements to internal LAN on br0, issued by dnsmasq - the relevant dnsmasq config is here: https://github.com/myxal/DigitalHome/blob/master/configurations/dnsmasq/dnsmasq.d/Echolife6.conf The mac is unaware of the tunnel, it autoconfigures itself according to the router advertisements, and RPi forwards the packets according to normal forwaring rules. But we're getting off-topic here. Regarding your config - the internal (br0) and external (he-ipv6) should have addresses from different prefixes. I'm not sure which of the settings is wrong, but seeing as you are setting the gateway to what looks like a correct address, I'm guessing your internal address is wrong. On tunnelbroker, this is listed as: "Client IPv6 address" - this is the external address, and must be set exactly as indicated by tunnelbroker "Server IPv6 address" - this is the gateway - seems correctly entered in the config "Routed /64" - this is the prefix from which you'll pick an address for the internal (br0) interface. I picked ...::1 because it's easy to enter and remember. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
So both your RPI3B+ and your host mac machine setup the IPv6 tunnel, and they share the same tunnel from tunnelbroker.net. And this is my example configs and my two yamls: https://pastebin.ubuntu.com/p/TDCDMrtzCb/ anything is wrong? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Not quite. - for downloads, as the issue happens when using IPv6 tunnel, so I'd use wget -6 ... - for youtube - this is playing on another machine (Mac running Chromium browser). I mentioned it because it's significant amount of traffic which, in presence of IPv6 connectivity, will (mostly) go through the tunnel. Your IPv6 addresses look misconfigured, as both he-ipv6 and br0 have addresses from the same /64 prefix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
I changed the ip in the two yaml and put them to $rpi3B+/etc/netplan/, reboot, but the ipv6 doesn't work, only ipv4 works. BTW, you said you run wget and play youtube all on the rpi3B+, right? This is the log on my rpi3B+: ubuntu@ubuntu:~$ ifconfig br0: flags=4163 mtu 1500 inet 192.168.2.4 netmask 255.255.255.0 broadcast 192.168.2.255 inet6 fe80::7c3a:7cff:fe69:3425 prefixlen 64 scopeid 0x20 inet6 2001:470:35:3b1::2 prefixlen 64 scopeid 0x0 ether 7e:3a:7c:69:34:25 txqueuelen 1000 (Ethernet) RX packets 305 bytes 78562 (78.5 KB) RX errors 0 dropped 8 overruns 0 frame 0 TX packets 137 bytes 14821 (14.8 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163 mtu 1500 ether b8:27:eb:ce:ca:4c txqueuelen 1000 (Ethernet) RX packets 318 bytes 83612 (83.6 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 137 bytes 14821 (14.8 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 he-ipv6: flags=209 mtu 1480 inet6 fe80::c0a8:204 prefixlen 64 scopeid 0x20 inet6 2001:470:35:3b1::1 prefixlen 64 scopeid 0x0 sit txqueuelen 1000 (IPv6-in-IPv4) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 77 bytes 7128 (7.1 KB) TX errors 22 dropped 0 overruns 0 carrier 22 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 807 bytes 61288 (61.2 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 807 bytes 61288 (61.2 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ubuntu@ubuntu:~$ wget http://ftp.antik.sk/ubuntu-releases/eoan/ubuntu-19.10-live-server-amd64.iso --2020-02-24 09:38:24-- http://ftp.antik.sk/ubuntu-releases/eoan/ubuntu-19.10-live-server-amd64.iso Resolving ftp.antik.sk (ftp.antik.sk)... 2a02:130:9900:30::12, 88.212.10.12 Connecting to ftp.antik.sk (ftp.antik.sk)|2a02:130:9900:30::12|:80... failed: Connection timed out. Connecting to ftp.antik.sk (ftp.antik.sk)|88.212.10.12|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 883949568 (843M) [application/x-iso9660-image] Saving to: ��‘ubuntu-19.10-live-server-amd64.iso��’ 9.10-live-server-am 0%[] 2.51K --.-KB/seta 262d ^C -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
How to set up bridge - is github gist link OK? https://gist.github.com/myxal/6554bd370658a11621a30cd2e6e7d7a8 Testing without IPv6 tunnel - I'm not sure what you mean. If eth0 is the WAN side, and only wlan0 is for the LAN side, then there's no bridge needed... This would introduce another NAT (currently IPv4 NAT is already performed at the ISP router, and I can't change that), compared to the current setup - see the gist linked above. I have tried (previously, with kernel 1017 I think) just disabling the IPv6 part altogether (the tunnel interface was not created, static addresses not assigned, etc. wlan and eth0 still in bridge), and the issue was not reproduced. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Since the Apple usb NIC doesn't have this issue, it is a problem on the driver lan78xx.c Do you mean even without ipv6 tunnel, only setup a bridge on rpi3 to let eth0 connect WAN and let wlan0 play a role of AP, this issue could be reproduced? Could you please share the detailed steps on how to setup a bridge on the rpi3 to reproduce this issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Sorry, got kinda stuck trying to test with a USB NIC: https://askubuntu.com/q/1212529/325336 After disabling systemd-resolved (+ putting a public DNS IPv4 address in resolv.conf), v6 download over the external USB NIC (Apple USB Ethernet, 05ac:1402) works fine. After switching the cable back to the built-in NIC, the error appeared almost immediately, didn't even get to try the v6 download. [ 2452.471188] br0: port 3(eth1) entered disabled state [ 3030.723594] br0: received packet on wlan0 with own address as source address (addr:b8:27:eb:3a:ba:a2, vlan:0) [ 3030.860954] br0: received packet on wlan0 with own address as source address (addr:b8:27:eb:3a:ba:a2, vlan:0) [ 3037.463785] br0: received packet on wlan0 with own address as source address (addr:b8:27:eb:3a:ba:a2, vlan:0) [ 3228.800706] asix 1-1.3:1.0 eth1: link up, 100Mbps, full-duplex, lpa 0xCDE1 [ 3228.804385] br0: port 3(eth1) entered blocking state [ 3228.804417] br0: port 3(eth1) entered forwarding state [ 3293.930873] [ cut here ] [ 3293.930958] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out [ 3293.931102] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330 [ 3293.931109] Modules linked in: asix sit tunnel4 ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic bcm2835_v4l2(CE) ecc bcm2835_mmal_vchiq(CE) vc_sm_cma(CE) brcmfmac v4l2_common videobuf2_vmalloc brcmutil videobuf2_memops videobuf2_v4l2 cfg80211 videobuf2_common input_leds videodev mc spidev raspberrypi_hwmon uio_pdrv_genirq uio sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 3293.931334] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C E 5.3.0-1018-raspi2 #20-Ubuntu [ 3293.931339] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) [ 3293.931348] pstate: 6045 (nZCv daif +PAN -UAO) [ 3293.931356] pc : dev_watchdog+0x324/0x330 [ 3293.931363] lr : dev_watchdog+0x324/0x330 [ 3293.931366] sp : 1001bd60 [ 3293.931371] x29: 1001bd60 x28: 0140 [ 3293.931380] x27: x26: [ 3293.931388] x25: f2fb79363000 x24: 4f7cab129018 [ 3293.931396] x23: x22: 0001 [ 3293.931404] x21: f2fb79363480 x20: 4f7cab407000 [ 3293.931412] x19: x18: [ 3293.931420] x17: 10fd8218 x16: 4f7ca9f0f060 [ 3293.931428] x15: f2fb79228510 x14: [ 3293.931437] x13: x12: 4f7cab54 [ 3293.931445] x11: 4f7cab42d000 x10: [ 3293.931453] x9 : 0004 x8 : 0192 [ 3293.931461] x7 : x6 : 0001 [ 3293.931468] x5 : x4 : 0008 [ 3293.931476] x3 : 4f7caaa15750 x2 : 0004 [ 3293.931484] x1 : 59c84c96ab783c00 x0 : [ 3293.931492] Call trace: [ 3293.931500] dev_watchdog+0x324/0x330 [ 3293.931515] call_timer_fn+0x3c/0x178 [ 3293.931525] __run_timers.part.0+0x200/0x330 [ 3293.931533] run_timer_softirq+0x40/0x78 [ 3293.931544] __do_softirq+0x168/0x384 [ 3293.931554] irq_exit+0xb0/0xe8 [ 3293.931564] __handle_domain_irq+0x70/0xc0 [ 3293.931572] bcm2836_arm_irqchip_handle_irq+0x74/0xe0 [ 3293.931579] el1_irq+0x108/0x200 [ 3293.931590] arch_cpu_idle+0x3c/0x1c8 [ 3293.931603] default_idle_call+0x24/0x48 [ 3293.931615] do_idle+0x210/0x2a0 [ 3293.931623] cpu_startup_entry+0x2c/0x30 [ 3293.931636] secondary_start_kernel+0x154/0x1c8 [ 3293.931641] ---[ end trace 356cf2f8b780723e ]--- [ 3734.263219] br0: port 3(eth1) entered disabled state [ 3737.505916] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped [ 3737.523763] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped [ 3737.541622] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped [ 3737.559099] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped [ 3737.576635] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped [ 3737.593932] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped [ 3737.611136] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped [ 3737.628048] lan78xx 1-1.1.1:1.0 eth0: kevent 0 may have been dropped ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
-1019 kernel should be in the eoan-proposed channel. And I tried to setup the 6in4 on my host laptop, it didn't work, maybe the ISP block the packets because of GFW of china. And since the dwc2 also has this problem, it looks this issue has nothing to do with usb host driver, could you plug a different usb->ethernet (different brand from lan78xx) and test with this usb->ethernet, let us see if you could still reproduce the problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
> Looks like to setup a 6in4 tunnel, I need a static public IP first I don't think that static IP is needed to make it work at least temporarily, I don't have a static one either, just public. You only need to have public IP on the device you can manage - e.g. router at home, and make sure that raspberry has a static internal address. Then, in the router's firewall/forwarding settings, either set raspberry as the DMZ host, or set forward anything from the remote tunnel IP to raspberry. That being said, if are behind a carrier NAT which you can't manage, you won't be able to set up the tunnel. I've just tried the switch to dwc2 driver, it didn't help. (still on ~1018 kernel). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Where can I find the ~1019 kernel? The repositories are still at ~1018. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Hi. The USB ports still work fine - I use a USB keyboard to correctly reboot the machine when it gets stuck. My most recent replication was with ~1017 kernel, will try the newer ones. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Looks like to setup a 6in4 tunnel, I need a static public IP first, but I don't have that IP. And you could do a test, let us change the usb host driver, if the problem can't be reproduced anymore, it proves it is a problem on usb host driver. To change the usb host driver: add dtoverlay=dwc2 in the config.txt for RPI3B+ board. to check if usb host driver is changed: lsusb -t (it will show dwc2 instead of dwc_otg). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Hi mlx, >From the calltrace, it looks like the transmit doesn't work when problem happens, it is probably a problem of the driver lan78xx.c or a problem of the usb host driver. So when problem happens, does the other usb ports still work? and the latest kernel -1019 version integrated a couple of patches to lan78xx.c, you could do a test with -1019 kernel. And looks like other people also met the similar problem (at least similar calltrace): https://www.raspberrypi.org/forums/search.php?keywords=lan78xx+transmit+queue+0+timed+out&sid=54addf297812dfe931b66a621bcae444 And I am still trying to reproduce this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
@mlx, I will try to reproduce the bug according to your steps this weekend. thx. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
@hui.wang Is there anything else needed from me? The issue still happens (intermittently under my normal use as an IPv6 gateway). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
** Attachment added: "10rpi3-bridge-static.yaml" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326547/+files/10rpi3-bridge-static.yaml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
** Attachment added: "99-ipv6-home.conf" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326537/+files/99-ipv6-home.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
** Attachment added: "rules.v4" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326548/+files/rules.v4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
** Attachment added: "rules.v6" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326549/+files/rules.v6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
(This is still with full setup, ie, jool and iptunnel, traffic using the tunnel): The first time I tried I also managed to download gparted without issues, but next time the issue appeared again. No jool and no tunnel: wget 2x 900MB (ubuntu iso), no issue. scp the same iso from local machine to RPi, also no issue. No jool, 6in4 tunnel + ip6tables: Replicated on 3rd attempt with wget. I think what may be contributing is that the machine is acting as an IPv6 gateway for my network, and there are some background bursts of load on the tunnel (Youtube playing on the desktop). The wget download itself is also going through the tunnel: $ wget http://ftp.antik.sk/ubuntu-releases/eoan/ubuntu-19.10-live-server-amd64.iso --2020-02-08 21:51:00-- http://ftp.antik.sk/ubuntu-releases/eoan/ubuntu-19.10-live-server-amd64.iso Resolving ftp.antik.sk (ftp.antik.sk)... 2a02:130:9900:30::12, 88.212.10.12 Connecting to ftp.antik.sk (ftp.antik.sk)|2a02:130:9900:30::12|:80... connected. Can you retry with a 6in4 tunnel? Im using the free offering from tunnelbroker.net Or perhaps suggest a way to collect more logs. I'll upload a set of relevant config files for: - netplan - netfilter-persistent - sysctl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
** Attachment added: "15rpi3-HEnet-Prague.yaml" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5326546/+files/15rpi3-HEnet-Prague.yaml -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Hmm, will look into this again. I'm using a feature-rich networking setup (6in4 tunnel, jool NAT64, LAN + WLAN bridge, ip(6)tables), maybe some of it is also required). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
The only difference between kernel 5.3.0-1017-raspi2 #19+otg and 5.3.0-1017-raspi2 #19-Ubuntu is: CONFIG_USB_DWC2_HOST=y and CONFIG_USB_DWC2_DUAL_ROLE is not set in the #19-Ubuntu CONFIG_USB_DWC2_DUAL_ROLE=y and CONFIG_USB_DWC2_HOST is not set in the #19-otg The difference will not affect this bug. And I built the #19+otg kernel for this bug: #1861070 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Oh, 192.168.2.103 is the wifi's IP on the RPI3B+, I redo the test with lan's ip (192.168.2.107), can't reproduce the bug too. log on the host: hwang4@hwang4-Vostro-5390:~/Downloads$ scp dell-bto-bionic-beaver-osp1-shireen-X44-20200103-22.iso ubuntu@192.168.2.107:~/lan/ The authenticity of host '192.168.2.107 (192.168.2.107)' can't be established. ECDSA key fingerprint is SHA256:HbfQtMzTnE9Bl6sg20Y95s6Ruf21ybTJ6T7npMl0Ex4. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.2.107' (ECDSA) to the list of known hosts. ubuntu@192.168.2.107's password: dell-bto-bionic-beaver-osp1-shireen-X44-20200103-22.iso 100% 3389MB 7.0MB/s 08:06 log on the RPI3B+: ubuntu@ubuntu:~/lan$ dmesg [0.00] Booting Linux on physical CPU 0x00 [0x410fd034] [0.00] Linux version 5.3.0-1017-raspi2 (root@zaku) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #19+otg SMP Wed Jan 29 12:45:11 CST 2020 (Ubuntu 5.3.0-1017.19+otg-raspi2 5.3.13) [0.00] Machine model: Raspberry Pi 3 Model B Plus Rev 1.3 [0.00] efi: Getting EFI parameters from FDT: ... [ 113.962890] audit: type=1400 audit(1581076329.560:38): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.lxd.lxd" pid=1686 comm="apparmor_parser" [ 114.104891] audit: type=1400 audit(1581076329.700:39): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.lxd.migrate" pid=1687 comm="apparmor_parser" [ 6029.845036] lan78xx 1-1.1.1:1.0 eth0: No phy led trigger registered for speed(-1) [ 6029.853021] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready ubuntu@ubuntu:~/lan$ ifconfig eth0: flags=4163 mtu 1500 inet 192.168.2.107 netmask 255.255.255.0 broadcast 192.168.2.255 inet6 fe80::ba27:ebff:fece:ca4c prefixlen 64 scopeid 0x20 ether b8:27:eb:ce:ca:4c txqueuelen 1000 (Ethernet) RX packets 2470290 bytes 3725719810 (3.7 GB) RX errors 0 dropped 14 overruns 0 frame 0 TX packets 1074945 bytes 72518896 (72.5 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ubuntu@ubuntu:~/lan$ ls -la total 3470028 drwxrwxr-x 2 ubuntu ubuntu 4096 Feb 7 13:32 . drwxr-xr-x 8 ubuntu ubuntu 4096 Feb 7 13:32 .. -rw-rw-r-- 1 ubuntu ubuntu 3553296384 Feb 7 13:40 dell-bto-bionic-beaver-osp1-shireen-X44-20200103-22.iso -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
Hi Hui, There seems to be some (small?) difference between your kernel (5.3.0-1017-raspi2 #19+otg) and the reporter's kernel (original 5.3.0-1017-raspi2 #19-Ubuntu) ? I realize you're of course aware of the changes introduced in this '+otg' custom build you're running, but just wanted to mention that to confirm those are unrelated to the symptoms seen in this bug. cheers, Mauricio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
set it to incomplete first. ** Changed in: linux-raspi2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
I did the test on the rpi3B+ board, scp a 3.3G size file from host machine to the rpi3B+ board (mmc card), there is no any errors, and there is no calltrace in the dmesg of the rpi3B+ board. log on the host machine: hwang4@hwang4-Vostro-5390:~/Downloads$ scp dell-bto-bionic-beaver-osp1-shireen-X44-20200103-22.iso ubuntu@192.168.2.103:~/test/ The authenticity of host '192.168.2.103 (192.168.2.103)' can't be established. ECDSA key fingerprint is SHA256:HbfQtMzTnE9Bl6sg20Y95s6Ruf21ybTJ6T7npMl0Ex4. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '192.168.2.103' (ECDSA) to the list of known hosts. ubuntu@192.168.2.103's password: dell-bto-bionic-beaver-osp1-shireen-X44-20200103-22.iso 100% 3389MB 641.5KB/s 1:30:09 log on the rpi3B+ board: ubuntu@ubuntu:~/test$ 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:~/test$ ls -la total 3470028 drwxrwxr-x 2 ubuntu ubuntu 4096 Feb 7 11:53 . drwxr-xr-x 7 ubuntu ubuntu 4096 Feb 7 11:51 .. -rw-rw-r-- 1 ubuntu ubuntu 3553296384 Feb 7 13:23 dell-bto-bionic-beaver-osp1-shireen-X44-20200103-22.iso dmesg: [ 22.099395] audit: type=1400 audit(1581076194.463:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=1132 comm="apparmor_parser" [ 22.114632] audit: type=1400 audit(1581076194.479:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1131 comm="apparmor_parser" [ 27.603378] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 112.486200] kauditd_printk_skb: 18 callbacks suppressed [ 112.486207] audit: type=1400 audit(1581076328.080:30): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.lxd.activate" pid=1678 comm="apparmor_parser" [ 112.507068] audit: type=1400 audit(1581076328.104:31): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.lxd.buginfo" pid=1680 comm="apparmor_parser" [ 112.543622] audit: type=1400 audit(1581076328.140:32): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.lxd.benchmark" pid=1679 comm="apparmor_parser" [ 112.684646] audit: type=1400 audit(1581076328.280:33): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.lxd.check-kernel" pid=1681 comm="apparmor_parser" [ 113.298782] audit: type=1400 audit(1581076328.896:34): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.lxd.hook.install" pid=1684 comm="apparmor_parser" [ 113.474537] audit: type=1400 audit(1581076329.072:35): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.lxd.lxc" pid=1685 comm="apparmor_parser" [ 113.522045] audit: type=1400 audit(1581076329.116:36): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.lxd.hook.configure" pid=1683 comm="apparmor_parser" [ 113.551776] audit: type=1400 audit(1581076329.148:37): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.lxd.daemon" pid=1682 comm="apparmor_parser" [ 113.962890] audit: type=1400 audit(1581076329.560:38): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.lxd.lxd" pid=1686 comm="apparmor_parser" [ 114.104891] audit: type=1400 audit(1581076329.700:39): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.lxd.migrate" pid=1687 comm="apparmor_parser" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
I will try to reproduce your issue first. thx. ** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of SD card IO and network load ((lan78xx): transmit queue 0 timed out)
** Description changed: - Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and network load. Happened a few times when I tried to download a gparted zip release (~350 MiB) directly to the SD card, and then finally when I tried to scp the finished download from a desktop onto RPi's card. - Didn't collect information when it happened, but kept a copy of kernel.log. Here's the relevant part: + Raspberry Pi 3 network dies shortly after a burst of SD card IO (writes) and network load. Happened a few times (every time) when I tried to download a gparted zip release (~350 MiB) directly to the SD card, and then finally when I tried to scp the finished download from a desktop onto RPi's card. + Didn't collect information when it happened, but kept a copy of kern.log. Here's the relevant part: Feb 4 23:42:59 rpi3 kernel: [ 571.878359] [ cut here ] Feb 4 23:42:59 rpi3 kernel: [ 571.878420] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Feb 4 23:42:59 rpi3 kernel: [ 571.878550] WARNING: CPU: 3 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878557] Modules linked in: sit tunnel4 ip_tunnel bridge stp llc ip6table_filter ip6_tables xt_tcpudp xt_conntrack nf_conntrack iptable_filter bpfilter nls_ascii dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) input_leds vc_sm_cma(CE) v4l2_common videobuf2_vmalloc spidev videobuf2_memops videobuf2_v4l2 raspberrypi_hwmon videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel jool(OE) jool_common(OE) nf_defrag_ipv6 nf_defrag_ipv4 ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid crct10dif_ce sdhci_iproc phy_generic fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 Feb 4 23:42:59 rpi3 kernel: [ 571.878774] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G C OE 5.3.0-1017-raspi2 #19-Ubuntu Feb 4 23:42:59 rpi3 kernel: [ 571.878781] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) Feb 4 23:42:59 rpi3 kernel: [ 571.878789] pstate: 6045 (nZCv daif +PAN -UAO) Feb 4 23:42:59 rpi3 kernel: [ 571.878800] pc : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878807] lr : dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878812] sp : 1001bd60 - Feb 4 23:42:59 rpi3 kernel: [ 571.878817] x29: 1001bd60 x28: 0140 - Feb 4 23:42:59 rpi3 kernel: [ 571.878827] x27: x26: - Feb 4 23:42:59 rpi3 kernel: [ 571.878836] x25: 8ecbefa4e000 x24: 305e0f529018 - Feb 4 23:42:59 rpi3 kernel: [ 571.878845] x23: x22: 0001 - Feb 4 23:42:59 rpi3 kernel: [ 571.878853] x21: 8ecbefa4e480 x20: 305e0f807000 - Feb 4 23:42:59 rpi3 kernel: [ 571.878862] x19: x18: - Feb 4 23:42:59 rpi3 kernel: [ 571.878871] x17: 10fd8218 x16: 305e0e30efb8 - Feb 4 23:42:59 rpi3 kernel: [ 571.878879] x15: 8ecbf922a290 x14: - Feb 4 23:42:59 rpi3 kernel: [ 571.87] x13: x12: 305e0f944000 - Feb 4 23:42:59 rpi3 kernel: [ 571.878897] x11: 305e0f82d000 x10: - Feb 4 23:42:59 rpi3 kernel: [ 571.878905] x9 : 0004 x8 : 017f - Feb 4 23:42:59 rpi3 kernel: [ 571.878913] x7 : x6 : 0001 - Feb 4 23:42:59 rpi3 kernel: [ 571.878921] x5 : x4 : 0008 - Feb 4 23:42:59 rpi3 kernel: [ 571.878929] x3 : 305e0ee15750 x2 : 0004 - Feb 4 23:42:59 rpi3 kernel: [ 571.878937] x1 : 6abb42c67c954600 x0 : + Feb 4 23:42:59 rpi3 kernel: [ 571.878817] x29: 1001bd60 x28: 0140 + Feb 4 23:42:59 rpi3 kernel: [ 571.878827] x27: x26: + Feb 4 23:42:59 rpi3 kernel: [ 571.878836] x25: 8ecbefa4e000 x24: 305e0f529018 + Feb 4 23:42:59 rpi3 kernel: [ 571.878845] x23: x22: 0001 + Feb 4 23:42:59 rpi3 kernel: [ 571.878853] x21: 8ecbefa4e480 x20: 305e0f807000 + Feb 4 23:42:59 rpi3 kernel: [ 571.878862] x19: x18: + Feb 4 23:42:59 rpi3 kernel: [ 571.878871] x17: 10fd8218 x16: 305e0e30efb8 + Feb 4 23:42:59 rpi3 kernel: [ 571.878879] x15: 8ecbf922a290 x14: + Feb 4 23:42:59 rpi3 kernel: [ 571.87] x13: x12: 305e0f944000 + Feb 4 23:42:59 rpi3 kernel: [ 571.878897] x11: 305e0f82d000 x10: + Feb 4 23:42:59 rpi3 kernel: [ 571.878905] x9 : 0004 x8 : 017f + Feb 4 23:42:59 rpi3 kernel: [ 571.
