@seamoose Thanks. That's pretty much the config that I had. I've now setup an
external VM and created a wireguard tunnel from my Pi 3B+ but it still won't
fail running iperf3. Is there a specific payload that you're transferring?
Also, your IPv6 config, is that just the default or did you do some manual
configuration? On my Pi:
$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether b8:27:eb:3e:ab:fb brd ff:ff:ff:ff:ff:ff
inet 192.168.99.67/24 brd 192.168.99.255 scope global dynamic eth0
valid_lft 860949sec preferred_lft 860949sec
inet6 fe80::ba27:ebff:fe3e:abfb/64 scope link
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP
group default qlen 1000
link/ether b8:27:eb:6b:fe:ae brd ff:ff:ff:ff:ff:ff
inet 192.168.99.57/24 brd 192.168.99.255 scope global dynamic wlan0
valid_lft 860949sec preferred_lft 860949sec
inet6 fe80::ba27:ebff:fe6b:feae/64 scope link
valid_lft forever preferred_lft forever
4: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN
group default qlen 1000
link/none
inet 10.241.0.1/24 scope global wg0
valid_lft forever preferred_lft forever
** Also affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-raspi (Ubuntu Eoan)
** Changed in: linux-raspi (Ubuntu Focal)
Status: New => Confirmed
** No longer affects: linux-raspi2 (Ubuntu Focal)
** Changed in: linux-raspi (Ubuntu)
Status: New => Incomplete
--
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-raspi package in Ubuntu:
Incomplete
Status in linux-raspi2 package in Ubuntu:
Incomplete
Status in linux-raspi2 source package in Eoan:
Won't Fix
Status in linux-raspi source package in Focal:
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-raspi/+bug/1861936/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
