Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-raspi (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned | ||
Focal |
Fix Committed
|
Undecided
|
Unassigned | ||
Groovy |
Fix Released
|
Undecided
|
Unassigned | ||
linux-raspi2 (Ubuntu) |
Incomplete
|
High
|
Hui Wang | ||
Eoan |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
[Impact]
A mix of incoming TCP traffic, forwarding packets and saturating the link results in lan78xx TX queue timeouts which brings the network interface down.
[Test Case]
Se comment #99 below.
[Where Problems Could Occur]
Probably lost or corrupted TCP packets. Most likely not worse than what we're currently seeing.
[Original 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-
- 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/
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_
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+
Feb 4 23:42:59 rpi3 kernel: [ 571.878807] lr : dev_watchdog+
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+
Feb 4 23:42:59 rpi3 kernel: [ 571.878967] call_timer_
Feb 4 23:42:59 rpi3 kernel: [ 571.878977] __run_timers.
Feb 4 23:42:59 rpi3 kernel: [ 571.878985] run_timer_
Feb 4 23:42:59 rpi3 kernel: [ 571.878995] __do_softirq+
Feb 4 23:42:59 rpi3 kernel: [ 571.879007] irq_exit+0xb0/0xe8
Feb 4 23:42:59 rpi3 kernel: [ 571.879020] __handle_
Feb 4 23:42:59 rpi3 kernel: [ 571.879028] bcm2836_
Feb 4 23:42:59 rpi3 kernel: [ 571.879037] el1_irq+0x108/0x200
Feb 4 23:42:59 rpi3 kernel: [ 571.879050] arch_cpu_
Feb 4 23:42:59 rpi3 kernel: [ 571.879069] default_
Feb 4 23:42:59 rpi3 kernel: [ 571.879081] do_idle+0x210/0x2a0
Feb 4 23:42:59 rpi3 kernel: [ 571.879091] cpu_startup_
Feb 4 23:42:59 rpi3 kernel: [ 571.879102] secondary_
Feb 4 23:42:59 rpi3 kernel: [ 571.879108] ---[ end trace 349744d60a20e77a ]---
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-
ProcVersionSign
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)
CVE References
description: | updated |
description: | updated |
Changed in linux-raspi2 (Ubuntu Eoan): | |
status: | New → Confirmed |
Changed in linux-raspi2 (Ubuntu Focal): | |
status: | New → Confirmed |
Changed in linux-raspi2 (Ubuntu Eoan): | |
status: | Confirmed → Won't Fix |
description: | updated |
Changed in linux-raspi (Ubuntu Focal): | |
status: | Confirmed → In Progress |
Changed in linux-raspi (Ubuntu Groovy): | |
status: | Confirmed → In Progress |
Changed in linux-raspi (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in linux-raspi (Ubuntu Groovy): | |
status: | In Progress → Fix Committed |
I will try to reproduce your issue first.
thx.