Hi all, >From my tests, it doesn't seem like a problem related to ipv6, but with high load in 3B+ version. In my case its easy to reproduce if I use ipforward and connection state over 20.04 server pi image, more less from scratch, static ip, pihole, tun0 and no ipv6.
root@pin:/home/janzun# uname -a Linux pin 5.4.0-1008-raspi #8-Ubuntu SMP Wed Apr 8 11:13:06 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux # sysctl -p net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1 net.ipv4.ip_forward = 1|0 -> it depends First test: # echo 0 > /proc/sys/net/ipv4/ip_forward # iptables -F; iptables -X; iptables -P INPUT|FORWARD|OUTPUT ACCEPT # wget -O /dev/null https://*/10GB.bin ==> Some error in one of the attemps Second test (forget the purpose of the rules): # echo 1 > /proc/sys/net/ipv4/ip_forward # iptables -A INPUT -p tcp -m state --state ESTABLISHED,RELATED -j ACCEPT # wget -O /dev/null https://*/10GB.bin ==> Allways stopped at about 1.5GB and crash (same with -p udp). Kernel log: Apr 25 18:11:21 localhost kernel: [22872.242430] ------------[ cut here ]------------ Apr 25 18:11:21 localhost kernel: [22872.242515] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Apr 25 18:11:21 localhost kernel: [22872.242716] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330 Apr 25 18:11:21 localhost kernel: [22872.242733] Modules linked in: 8021q garp mrp stp llc xt_multiport xt_state xt_conntrack xt_tcpudp iptab Apr 25 18:11:21 localhost kernel: [22872.242956] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G C E 5.4.0-1008-raspi #8-Ubuntu Apr 25 18:11:21 localhost kernel: [22872.242962] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) Apr 25 18:11:21 localhost kernel: [22872.242972] pstate: 60400005 (nZCv daif +PAN -UAO) Apr 25 18:11:21 localhost kernel: [22872.242985] pc : dev_watchdog+0x324/0x330 Apr 25 18:11:21 localhost kernel: [22872.242995] lr : dev_watchdog+0x324/0x330 Apr 25 18:11:21 localhost kernel: [22872.243000] sp : ffff80001000bd60 Apr 25 18:11:21 localhost kernel: [22872.243005] x29: ffff80001000bd60 x28: 0000000000000140 Apr 25 18:11:21 localhost kernel: [22872.243014] x27: 00000000ffffffff x26: 0000000000000000 Apr 25 18:11:21 localhost kernel: [22872.243023] x25: ffff00002f650000 x24: ffffa8d07f545018 Apr 25 18:11:21 localhost kernel: [22872.243031] x23: 0000000000000000 x22: 0000000000000001 Apr 25 18:11:21 localhost kernel: [22872.243039] x21: ffff00002f650480 x20: ffffa8d07fa07000 Apr 25 18:11:21 localhost kernel: [22872.243047] x19: 0000000000000000 x18: 0000000000000000 Apr 25 18:11:21 localhost kernel: [22872.243055] x17: ffff800010876378 x16: 0000000000000000 Apr 25 18:11:21 localhost kernel: [22872.243063] x15: ffff000039234090 x14: ffffffffffffffff Apr 25 18:11:21 localhost kernel: [22872.243072] x13: 0000000000000000 x12: ffffa8d07fb3e000 Apr 25 18:11:21 localhost kernel: [22872.243081] x11: ffffa8d07fa2c000 x10: 0000000000000000 Apr 25 18:11:21 localhost kernel: [22872.243088] x9 : 0000000000000004 x8 : 00000000000001cb Apr 25 18:11:21 localhost kernel: [22872.243096] x7 : 0000000000000000 x6 : 0000000000000001 Apr 25 18:11:21 localhost kernel: [22872.243103] x5 : 0000000000000000 x4 : 0000000000000002 Apr 25 18:11:21 localhost kernel: [22872.243111] x3 : ffffa8d07ee15790 x2 : 0000000000000040 Apr 25 18:11:21 localhost kernel: [22872.243119] x1 : 3cb8609474fd0d00 x0 : 0000000000000000 Apr 25 18:11:21 localhost kernel: [22872.243128] Call trace: Apr 25 18:11:21 localhost kernel: [22872.243138] dev_watchdog+0x324/0x330 Apr 25 18:11:21 localhost kernel: [22872.243155] call_timer_fn+0x3c/0x178 Apr 25 18:11:21 localhost kernel: [22872.243168] __run_timers.part.0+0x204/0x330 Apr 25 18:11:21 localhost kernel: [22872.243177] run_timer_softirq+0x40/0x78 Apr 25 18:11:21 localhost kernel: [22872.243188] __do_softirq+0x168/0x384 Apr 25 18:11:21 localhost kernel: [22872.243199] irq_exit+0xb0/0xe8 Apr 25 18:11:21 localhost kernel: [22872.243213] __handle_domain_irq+0x70/0xc0 Apr 25 18:11:21 localhost kernel: [22872.243222] bcm2836_arm_irqchip_handle_irq+0x74/0xe0 Apr 25 18:11:21 localhost kernel: [22872.243230] el1_irq+0x108/0x200 Apr 25 18:11:21 localhost kernel: [22872.243242] arch_cpu_idle+0x3c/0x1c8 Apr 25 18:11:21 localhost kernel: [22872.243255] default_idle_call+0x24/0x48 Apr 25 18:11:21 localhost kernel: [22872.243269] do_idle+0x210/0x2a0 Apr 25 18:11:21 localhost kernel: [22872.243278] cpu_startup_entry+0x28/0x30 Apr 25 18:11:21 localhost kernel: [22872.243291] secondary_start_kernel+0x134/0x1b8 Apr 25 18:11:21 localhost kernel: [22872.243297] ---[ end trace d80fb39a4340a900 ]--- Workaround 1, reboot on kernel message: # cat /etc/rsyslog.d/60-lan7800-reboot.conf :msg, regex, "transmit queue 0 timed" ^/usr/sbin/reboot Workaround 2, better for me: # crontab -e * * * * * /scripts/7800-authorized.sh Mine is version 3B+ with the following usb table: # lsusb -t /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/3p, 480M |__ Port 1: Dev 6, If 0, Class=Vendor Specific Class, Driver=lan78xx, 480M |__ Port 3: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 3: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M So: # cat /scripts/7800-authorized.sh #!/bin/sh # The number of Ips and lines at your convenience, increasing the -c number has no sense. ping -c1 192.168.1.1 > /dev/null && exit 0 ping -c1 192.168.1.45 > /dev/null && exit 0 echo 0 > /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.1/authorized sleep 5 echo 1 > /sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1/1-1.1.1/authorized logger [Error] Rebooting network iface due to module fail... # eol You cannot do a mix (rsyslog and 0/1 authorized) because kernel message happends only first time, until reboot. Hope it helps you. -- 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/1861936 Title: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out) Status in linux-raspi2 package in Ubuntu: Incomplete Status in linux-raspi2 source package in Eoan: Confirmed Bug description: Desciption changed: Raspberry Pi 3 network partially dies (transmission doesn't work, reception still does) shortly after a burst of network load over IPv6, when IPv6 connectivity is provided by a tunnel from tunnelbroker.net. The triggering load is typically an HTTP(S) download, and replication can be done without actually saving the file (wget -O /dev/null ...). Problem happens within downloading ~10 GB, usually withinthe first 1 GB of traffic) Replication is 100% as long as _all_ of the following conditions are met - 6in4 tunnel to HE.net set up with netplan - ipv6 rules applied (netfilter-persistent) - ipv6 forwarding enabled (edit /etc/sysctl.conf) kern.log message that appears after a while: 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: 60400005 (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 : ffff00001001bd60 Feb 4 23:42:59 rpi3 kernel: [ 571.878817] x29: ffff00001001bd60 x28: 0000000000000140 Feb 4 23:42:59 rpi3 kernel: [ 571.878827] x27: 00000000ffffffff x26: 0000000000000000 Feb 4 23:42:59 rpi3 kernel: [ 571.878836] x25: ffff8ecbefa4e000 x24: ffff305e0f529018 Feb 4 23:42:59 rpi3 kernel: [ 571.878845] x23: 0000000000000000 x22: 0000000000000001 Feb 4 23:42:59 rpi3 kernel: [ 571.878853] x21: ffff8ecbefa4e480 x20: ffff305e0f807000 Feb 4 23:42:59 rpi3 kernel: [ 571.878862] x19: 0000000000000000 x18: 0000000000000000 Feb 4 23:42:59 rpi3 kernel: [ 571.878871] x17: ffff000010fd8218 x16: ffff305e0e30efb8 Feb 4 23:42:59 rpi3 kernel: [ 571.878879] x15: ffff8ecbf922a290 x14: ffffffffffffffff Feb 4 23:42:59 rpi3 kernel: [ 571.878888] x13: 0000000000000000 x12: ffff305e0f944000 Feb 4 23:42:59 rpi3 kernel: [ 571.878897] x11: ffff305e0f82d000 x10: 0000000000000000 Feb 4 23:42:59 rpi3 kernel: [ 571.878905] x9 : 0000000000000004 x8 : 000000000000017f Feb 4 23:42:59 rpi3 kernel: [ 571.878913] x7 : 0000000000000000 x6 : 0000000000000001 Feb 4 23:42:59 rpi3 kernel: [ 571.878921] x5 : 0000000000000000 x4 : 0000000000000008 Feb 4 23:42:59 rpi3 kernel: [ 571.878929] x3 : ffff305e0ee15750 x2 : 0000000000000004 Feb 4 23:42:59 rpi3 kernel: [ 571.878937] x1 : 6abb42c67c954600 x0 : 0000000000000000 Feb 4 23:42:59 rpi3 kernel: [ 571.878946] Call trace: Feb 4 23:42:59 rpi3 kernel: [ 571.878955] dev_watchdog+0x324/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878967] call_timer_fn+0x3c/0x178 Feb 4 23:42:59 rpi3 kernel: [ 571.878977] __run_timers.part.0+0x200/0x330 Feb 4 23:42:59 rpi3 kernel: [ 571.878985] run_timer_softirq+0x40/0x78 Feb 4 23:42:59 rpi3 kernel: [ 571.878995] __do_softirq+0x168/0x384 Feb 4 23:42:59 rpi3 kernel: [ 571.879007] irq_exit+0xb0/0xe8 Feb 4 23:42:59 rpi3 kernel: [ 571.879020] __handle_domain_irq+0x70/0xc0 Feb 4 23:42:59 rpi3 kernel: [ 571.879028] bcm2836_arm_irqchip_handle_irq+0x74/0xe0 Feb 4 23:42:59 rpi3 kernel: [ 571.879037] el1_irq+0x108/0x200 Feb 4 23:42:59 rpi3 kernel: [ 571.879050] arch_cpu_idle+0x3c/0x1c8 Feb 4 23:42:59 rpi3 kernel: [ 571.879069] default_idle_call+0x24/0x48 Feb 4 23:42:59 rpi3 kernel: [ 571.879081] do_idle+0x210/0x2a0 Feb 4 23:42:59 rpi3 kernel: [ 571.879091] cpu_startup_entry+0x28/0x30 Feb 4 23:42:59 rpi3 kernel: [ 571.879102] secondary_start_kernel+0x154/0x1c8 Feb 4 23:42:59 rpi3 kernel: [ 571.879108] ---[ end trace 349744d60a20e77a ]--- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1017-raspi2 5.3.0-1017.19 ProcVersionSignature: Ubuntu 5.3.0-1017.19-raspi2 5.3.13 Uname: Linux 5.3.0-1017-raspi2 aarch64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: arm64 Date: Tue Feb 4 23:49:19 2020 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+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
