[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
NB: Have been informed that this will trickle down from upstream into the 5.10 kernels for Raspberry Pi OS as well. -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
The upstream fix "b160c28548bc tcp: do not mess with cloned skbs in tcp_add_backlog()" has been applied to focal/linux as part of the fixes for bug 1915195 (Focal update: v5.4.93 upstream stable release). It will be included for the next focal/linux-raspi, however this bug report will not be closed automatically. -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Mentioned to Raspberry Pi people at: https://github.com/raspberrypi/linux/issues/3850 If anyone knows of a more current bug report for this issue, let me know. ** Bug watch added: github.com/raspberrypi/linux/issues #3850 https://github.com/raspberrypi/linux/issues/3850 -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
** Changed in: linux-raspi (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux-raspi (Ubuntu Groovy) Status: In Progress => Fix Committed -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
** Changed in: linux-raspi (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux-raspi (Ubuntu Groovy) Status: Confirmed => In Progress -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
** Description changed: + [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 + 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: 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.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
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
+1 -- I'm stuck on an ancient version of the Pi OS because of 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 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Nice :) Does anyone know if this is getting into Raspberry Pi OS? -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Upstream fix: https://lore.kernel.org/netdev/20210119164900.766957-1-eric.duma...@gmail.com/ ** Also affects: linux-raspi2 (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** No longer affects: linux-raspi2 (Ubuntu Groovy) ** Changed in: linux-raspi (Ubuntu Groovy) Status: New => Confirmed -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I finally managed to reproduce this problem consistently and within 30 secs. Bisecting the kernel points at [1] to be problematic. Whether that commit introduces a real regression or merely exposes a different underlying issue is unclear at the moment. I wasn't able to reproduce the problem with a Realtek USB NIC attached to the Pi 3B+ so that points more towards a lan78xx driver/HW issue. Reverting commit [1] plus two follow-on fixes makes the problem go away. This looks similar to [2]. [1] https://github.com/torvalds/linux/commit/4f693b55c3d2d2239b8a0094b518a1e533cf75d5 [2] https://lore.kernel.org/netdev/80adc922-f667-a1ab-35a6-02bf1acfd...@gmail.com/ -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Thanks for the added information. I'll take another crack at trying to 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 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I can deterministically reproduce this crash with Wireguard on the RPI3 running 20.10 and hence using the lan78xx driver on eth0. A few minutes of browsing public web sites on a client connected through Wireguard to the RPI3 crashes the RPI. Changing nothing except for running Wireguard's forwarding through wlan0 rather than eth0 does not result in any crashes. So certainly seems to indicate that the wired ethernet's lan78xx driver shipping today with 20.10 is the culprit causing these crashes. -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I found a way to trigger the problem fast (within one minute). On Raspberry Pi 3 B+: * Enable IPv4 forwarding: sysctl net.ipv4.ip_forward=1 * Enable masquerading: iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE * Start a netcat listening process: sudo nc -l -p 1234 > /dev/null On another machine: * Configure IPv4 address manually setting Raspberry Pi as gateway * Open browser and load some web pages to test routing * Send data to Raspberry Pi: nc RASPI_IP 1234 < /dev/zero * Parallel browsing now leads to network crash on Raspberry Pi. A few seconds later the kernel warining appears: NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Both machines are connected via ethernet to a 100MBit router. I tested the following hardware: * Raspberry Pi 2 Model B v1.1: no crash * Raspberry Pi 3 Model B+: crash * Raspberry Pi 4 Model B (4 GB): no crash $ uname -a Linux ubuntu 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:19:55 UTC 2020 armv7l armv7l armv7l GNU/Linux -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I was finally able to reproduce the problem by pushing data through the Pi, i.e. sender -> Pi -> wireguard tunnel -> receiver. Takes about 1.5 hrs to trigger the timeout. -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Well, it took more than 24 hours for my Pi to crash again, but it did happen. I wasn't able to capture much of what triggered it as i wasn't home at the time. -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Ok yup this is almost certainly the issue (when the tunnel is pi is tunnelling traffic for something other than itself) My tunnel has been up for 12 hours, no crashes at all. -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Ahhh. I do have 3 tunnels up as well. Good find! -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@juergh I may have (somewhat) found the trigger. As previously noted, my internal clients have a static route to the remote wireguard networks via my raspberry pi. This is defined in my internal router (Unifi) ie: client > router > static route (10.241.0.0/24) to pi eth0 IP > pi > tunnel > VPS If have disabled this route, so now none of my clients can send data over the tunnel. Only the Pi which is running the tunnel itself is able to communicate over said tunnel. No crashes at all. So, with this in mind, setup an internal client with a static route to your wireguard network and start sending traffic to the remote site. This should (hopefully) trigger the 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 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
RE IPv6, there is some manual config. I have each vlan/network assigned a /64. On my pi's they get an address in that /64 (different networks for eth0 and wlan0) but they do have a static assignment as well (should have included that earlier: interface eth0 metric 300 static ip6_address=2403:::XXX0::11/64 static ip6_routers=2403:::XXX0::1 static ip_address=192.168.200.11/24 static routers=192.168.200.1 interface wlan0 metric 400 static ip6_address=2403:::XXX3::11/64 static ip6_routers=2403:::XXX3::1 static ip_address=192.168.209.11/24 static routers=192.168.209.1 -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
So exactly what type of payload triggers the issues, that i cant work out. I know the traffic profile, vast majority of it is monitoring related as my VPS is running grafana/influx and my internal clients are sending data over this tunnel using telegraf. There is also a fair bit of ICMP etc traffic, so all "monitoring" related. For a bit of clarity, my Pi essentially acts as an internal router to link to my VPS. So clients send traffic originating from 192.168.x.x to 192.168.200.11 (internal static routes) to reach the 10.241.0.x network. Will ping you offline to see if I can provide a level of access to troubleshoot in real time. -- 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@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: 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: 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: 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: 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 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-raspi/+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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
And the most recent crash: Oct 22 11:44:51 dns1 kernel: [ 3096.793118] [ cut here ] Oct 22 11:44:51 dns1 kernel: [ 3096.793183] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Oct 22 11:44:51 dns1 kernel: [ 3096.793282] WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x370/0x378 Oct 22 11:44:51 dns1 kernel: [ 3096.793288] Modules linked in: sctp wireguard ip6_udp_tunnel udp_tunnel 8021q garp mrp stp llc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 bcm2835_v4l2(CE) bcm2835_isp(CE) bcm2835_codec(CE) v4l2_mem2mem bcm2835_mmal_vchiq(CE) videobuf2_vmalloc videobuf2_dma_contig videobuf2_memops snd_bcm2835(CE) videobuf2_v4l2 videobuf2_common snd_pcm raspberrypi_hwmon videodev snd_timer snd mc vc_sm_cma(CE) rpi_poe_fan uio_pdrv_genirq uio sch_fq_codel drm 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 crct10dif_ce spidev phy_generic aes_neon_bs aes_neon_blk crypto_simd cryptd Oct 22 11:44:51 dns1 kernel: [ 3096.793477] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G C E 5.4.0-1022-raspi #25-Ubuntu Oct 22 11:44:51 dns1 kernel: [ 3096.793482] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) Oct 22 11:44:51 dns1 kernel: [ 3096.793491] pstate: 6045 (nZCv daif +PAN -UAO) Oct 22 11:44:51 dns1 kernel: [ 3096.793499] pc : dev_watchdog+0x370/0x378 Oct 22 11:44:51 dns1 kernel: [ 3096.793507] lr : dev_watchdog+0x370/0x378 Oct 22 11:44:51 dns1 kernel: [ 3096.793512] sp : 800010013d80 Oct 22 11:44:51 dns1 kernel: [ 3096.793517] x29: 800010013d80 x28: 363c2380 Oct 22 11:44:51 dns1 kernel: [ 3096.793527] x27: x26: 2bf81280 Oct 22 11:44:51 dns1 kernel: [ 3096.793536] x25: a28a3750a018 x24: 2bf81340 Oct 22 11:44:51 dns1 kernel: [ 3096.793546] x23: 3535245c x22: 35352000 Oct 22 11:44:51 dns1 kernel: [ 3096.793555] x21: 35352480 x20: a28a37807000 Oct 22 11:44:51 dns1 kernel: [ 3096.793564] x19: x18: Oct 22 11:44:51 dns1 kernel: [ 3096.793573] x17: x16: Oct 22 11:44:51 dns1 kernel: [ 3096.793582] x15: 35a340b0 x14: Oct 22 11:44:51 dns1 kernel: [ 3096.793591] x13: x12: a28a3793f000 Oct 22 11:44:51 dns1 kernel: [ 3096.793600] x11: a28a3782c000 x10: a28a3793fa80 Oct 22 11:44:51 dns1 kernel: [ 3096.793609] x9 : x8 : 0004 Oct 22 11:44:51 dns1 kernel: [ 3096.793617] x7 : x6 : Oct 22 11:44:51 dns1 kernel: [ 3096.793626] x5 : x4 : 0004 Oct 22 11:44:51 dns1 kernel: [ 3096.793634] x3 : a28a36e15798 x2 : 0040 Oct 22 11:44:51 dns1 kernel: [ 3096.793643] x1 : x0 : Oct 22 11:44:51 dns1 kernel: [ 3096.793652] Call trace: Oct 22 11:44:51 dns1 kernel: [ 3096.793661] dev_watchdog+0x370/0x378 Oct 22 11:44:51 dns1 kernel: [ 3096.793674] call_timer_fn+0x40/0x1e8 Oct 22 11:44:51 dns1 kernel: [ 3096.793684] run_timer_softirq+0x1d4/0x590 Oct 22 11:44:51 dns1 kernel: [ 3096.793694] __do_softirq+0x170/0x424 Oct 22 11:44:51 dns1 kernel: [ 3096.793704] irq_exit+0xb4/0xe8 Oct 22 11:44:51 dns1 kernel: [ 3096.793716] __handle_domain_irq+0x74/0xc8 Oct 22 11:44:51 dns1 kernel: [ 3096.793724] bcm2836_arm_irqchip_handle_irq+0x78/0xf0 Oct 22 11:44:51 dns1 kernel: [ 3096.793731] el1_irq+0x108/0x200 Oct 22 11:44:51 dns1 kernel: [ 3096.793742] arch_cpu_idle+0x40/0x238 Oct 22 11:44:51 dns1 kernel: [ 3096.793754] default_idle_call+0x28/0x6c Oct 22 11:44:51 dns1 kernel: [ 3096.793765] do_idle+0x214/0x2a0 Oct 22 11:44:51 dns1 kernel: [ 3096.793775] cpu_startup_entry+0x30/0x78 Oct 22 11:44:51 dns1 kernel: [ 3096.793789] secondary_start_kernel+0x18c/0x1c8 Oct 22 11:44:51 dns1 kernel: [ 3096.793796] ---[ end trace 2e28df1507856d1f ]--- -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Forgot to include: Raspberry PI: ubuntu@dns1:~$ uname -a Linux dns1 5.4.0-1022-raspi #25-Ubuntu SMP PREEMPT Thu Oct 15 13:31:49 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux ubuntu@dns1:~$ VPS: root@m21:~# uname -a Linux m21 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@m21:~# -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Absolutely! -- My Raspberry Pi sits inside my home network, its config: eth0: IP: 192.168.200.11 GW: 192.168.200.1 IPv6: enabled (prefix delegation from ISP) Metric: 300 wlan0: IP: 192.168.209.11 GW: 192.168.209.1 IPv6: enabled (prefix delegation from ISP) Metric: 400 wg0: flags=209 mtu 1420 inet 10.241.0.1 netmask 255.255.255.0 destination 10.241.0.1 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 37100 bytes 44690744 (44.6 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 17505 bytes 4748492 (4.7 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Wireguard config: root@dns1:~# cat /etc/wireguard/wg0.conf [Interface] ## This Desktop/client's private key ## PrivateKey = ## Client ip address ## Address = 10.241.0.1/24 [Peer] ## Ubuntu 20.04 server public key ## PublicKey = ## set ACL ## AllowedIPs = 10.241.0.0/24 ## Your Ubuntu 20.04 LTS server's public IPv4/IPv6 address and port ## Endpoint = :51820 ## Key connection alive ## PersistentKeepalive = 15 ubuntu@dns1:~$ sudo wg interface: wg0 public key: private key: (hidden) listening port: 53514 peer: endpoint: :51820 allowed ips: 10.241.0.0/24 latest handshake: 33 seconds ago transfer: 42.68 MiB received, 4.79 MiB sent persistent keepalive: every 15 seconds ubuntu@dns1:~$ -- My VPS hosted externally: eth0: DHCP from VPS provider with IPv4/6(public IP, ie not NAT) wg0: flags=209 mtu 1420 inet 10.241.0.3 netmask 255.255.255.0 destination 10.241.0.3 unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 16739 bytes 4405736 (4.4 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 36539 bytes 44736120 (44.7 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@m21:~# cat /etc/wireguard/wg0.conf [Interface] Address = 10.241.0.3/24 SaveConfig = true ListenPort = 51820 FwMark = 0xca6c PrivateKey = [Peer] PublicKey = AllowedIPs = 10.241.0.1/32, 192.168.200.0/24, 192.168.209.0/24, 192.168.210.0/24, 192.168.211.0/24, 192.168.212.0/24 Endpoint = :33962 root@m21:~# root@m21:~$ sudo wg interface: wg0 public key: private key: (hidden) listening port: 51820 fwmark: 0xca6c peer: endpoint: :53514 allowed ips: 10.241.0.1/32, 192.168.200.0/24, 192.168.209.0/24, 192.168.210.0/24, 192.168.211.0/24, 192.168.212.0/24 latest handshake: 1 minute, 36 seconds ago transfer: 5.33 MiB received, 42.91 MiB sent root@m21:~$ -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@seamoose So you're just setting up a wireguard tunnel and push data through it to make it fail? That's what I did but in my case between two Pis on the same network. Works just fine for me. Can you share some of your relevant (non-standard) configs? -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I am also on a 3B+ ubuntu@dns1:~$ cat /proc/device-tree/model Raspberry Pi 3 Model B Plus Rev 1.3 I dont believe you need anything fancy with IPv6, im not tunneling any v6 and its occurring with me. I do have IPv6 enabled on the interface used for tuneling. Hui Wang, im happy to provide a shell with remote access for you replicate and troubleshoot if 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 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I only have the 3B+ board - the issue was encountered, and is still reproducible on that board. OS has always been Ubuntu. I'll try to reduce the repro steps/conditions when I have time; my setup is the v6 tunnel +v6 router + ip6tables + bridge reproduces the issue immediately, so hopefully determining what contributes to the issue and what doesn't should be too hard. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Oh, the board I have is also a 3B+, maybe that is the reason I can't reproduce the issue. the silkscreen on my board is: Raspberry Pi 3 Model B+ @ Raspberry Pi 2017. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I'm unable to reproduce this issue. I have not fiddled with IPv6 yet due to my lack of knowledge and (IMO) unclear instructions in previous comments. I've pushed data through a wireguard tunnel while loading the Pi (because this sounds similar: https://github.com/raspberrypi/linux/issues/3782 but I've just realized, that that issue is filed against 3B and not 3B+, duh!). I've also tried the instructions from comment #43 but my test completes multiple times just fine. I'm afraid there's not much I can do without *clear* instructions on how to reproduce this in an *isolated* environment using an *Ubuntu* image. ** Bug watch added: github.com/raspberrypi/linux/issues #3782 https://github.com/raspberrypi/linux/issues/3782 -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I want to add that in my case it's not related to WLAN. I'm not using WLAN on the Pi and also totally disabled it in the config ( I was hoping that helped, but it didn't ). So the issue is related to the ETH0 -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@mlx -- dunno. What I do know is reverting to prior firmware solves the issue for me and at least @Tim. I had the same issue in May as there was another release. I reverted and it became stable. This summer, I tried to sudo apt upgrade and hit the problem again. So I reverted and am stable. Would like to get back to the tip for sure, but instability is instability. And it seems it's a shared problem across ETH0 and WLAN1 based on this thread. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@Chrostopher: if it's a driver problem, wouldn't your issue with WLAN be distinct from mine, where I'm seeing the wired Ethernet break? -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@Juerg: My config for my network setup, which is an AP via wlan0, not bridged and station via USB Wifi dongle: - #!/bin/bash # Error management set -o pipefail set -o nounset set -x apt install -y hostapd dnsmasq systemctl unmask hostapd systemctl enable hostapd systemctl stop hostapd systemctl stop dnsmasq echo -e "interface wlan0\n\tstatic ip_address=192.168.10.1/24\n\tnohook wpa_supplicant\n" >> /etc/dhcpcd.conf systemctl restart dhcpcd cp /home/pi/hostapd.conf /etc/hostapd/ sed -i 's/^#DAEMON_CONF=.*$/DAEMON_CONF="\/etc\/hostapd\/hostapd.conf"/' /etc/default/hostapd mv /etc/dnsmasq.conf /etc/dnsmasq.conf.orig cp /home/pi/dnsmasq.conf /etc/ systemctl unmask hostapd systemctl enable hostapd systemctl start hostapd service dnsmasq start - Unlike the top post, I'm not using IPV6 so that is not a factor. However, the kernel log --- CUT HERE --- ... NETDEV WATCHDOG occurs for me. As I state above in my original post: - When I do connect, I am sending a lot of data. Hard to pin what actions are triggering the NETDEV WATCHDOG backtrace, but it leaves wlan1 in a state where it cannot come up again: SIOCSIFFLAGS: No such device ip address shows wlan1: mtu 1500 qdisc mq state DOWN group default qlen 1000 vcgencmd shows: Aug 6 2020 16:24:09 version af3...d5b337 (clean) (release) (start) --- Seems to me a driver issue when there is a flood of traffic. The older version of firmware I posted above solves 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 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Ok, I'm utterly confused about the reported issue. Simple steps to reproduce, please? -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
FWIW, I tried the dwc2 overlay again with kernel 5.4.0-1021-raspi - as before in #21 this changes nothing - network still dies during first major (>100MB) download, while other USB ports continue working. On the plus side, the Pi can now actually boot with an external NIC plugged in. I'm not sure if the issue I had (boot getting stuck with external USB Ethernet adapter) got fixed or a hardware change I made (Apple USB Ethernet adapter -> generic RTL8153-based adapter) is responsible. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Have you tried the new overlay (dwc2)? It worked really well for me, thread and instructions here: https://github.com/raspberrypi/linux/issues/3843 ** Bug watch added: github.com/raspberrypi/linux/issues #3843 https://github.com/raspberrypi/linux/issues/3843 -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I'm having the exact same issue on my RPi 3. I've been using the Pi for a very long time now and never had an issue. But since last week I updated the OS to the latest Raspberry OS and the Pi is now running as a K3s master node. Since then the Pi keeps crashing like this. I've having a lot of network traffic, way more than it had before it was used as a k3s master node. About 2 days ago I tried the rpi-update which Christopher provided, and since then the Pi is running without any crashes (yet). Almost 48 hours already, where before it wasn't able to run 24 hours straight. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Bummers. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Cancel that. As expected, issue still present. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I *may* be jumping the gun here, but having just installed 5.4.0-1019-raspi this morning, things appear to be good! Did an upgrade ~ 30 minutes ago (usually i find the issue is triggered after around 10 minutes or so). Will update if/when it crashes. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
No idea. I didn't march forward on the commits until it breaks, and I don't know when the bug occurs or I'd scream about it. What I do know is this old version is stable and I've had demonstrably no problems with it. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@Christopher, It is devicetree, kernel and bootloader binary update, do you know what change on source code level fix 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 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
4.19.75, https://github.com/Hexxeh/rpi- firmware/commit/86b202d127ca3d413d0779d870cce2169afaacd7 Ancient. And functional. ;) -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@scubachristopher what kernel version did that put you on? -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Also happens on Linux 5.4 on Raspbian 10. Okay, I'll keep that in mind. At the moment I'm trying a different overlay (driver) for the USB chip to see if that helps (not sure yet, though it hasn't helped with the HDD). -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@hamishbm -- I solved this by reverting to a prior fw release: sudo rpi-update 86b202d127ca3d413d0779d870cce2169afaacd7 Zero issues since. JFYI -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I'm having this issue as well, but on Raspbian 10. Symptoms seems the same, generally occurs with high load. However, I don't seem to need IPv6 packets to cause this - my network is IPv4 only. I thought I had a power problem because I am also using an external HDD (it's also working as a NAS), but with the powered hub things aren't any better. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
NB: On Linux 4.9. I'll post here again if it happens on the new kernel (5.4). -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
RPI 3B+. My configuration is as follows: Raspian (buster) 5.4.51-v7+#1333 SMP Mon Aug 10 16:45:19 BST 2020 wlan0 AP, no bridge, fixed IP. wlan1 USB Wifi adapter ppp0 Hologram Nova Modem My application is in the field, so Wifi HotSpots can be unreliable (I can get an IP but can't connect). So I watch to see if I can get to the internet through wlan1 and if I cannot, I switch to cellular. Once on cellular, I look to see if I can get to the Internet via wlan1 (cheaper / faster) by ifconfig wlan1 up. When I do connect, I am sending a lot of data. Hard to pin what actions are triggering the NETDEV WATCHDOG backtrace, but it leaves wlan1 in a state where it cannot come up again: SIOCSIFFLAGS: No such device ip address shows wlan1: mtu 1500 qdisc mq state DOWN group default qlen 1000 vcgencmd shows: Aug 6 2020 16:24:09 version af3...d5b337 (clean) (release) (start) Not clear this is the same issue, but I thought I'd report as a use case. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@Matt I didn't find any special way to easily select between kernels on raspberry - installing the linux-{headers,image}--raspi2 would overwrite whatever was on the FAT partition, making it the kernel loaded on next boot. To revert to previous kernel, its package would need to be reinstalled (apt install --reinstall ). I did run into a problem where a tested kernel wouldn't boot, so I'd recommend making a backup of the FAT partition in advance so you can recover it outside of the Raspberry's OS session. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@mlx I'm running eth0 in bridge, and also using a tunnel broker ipv6 tunnel like the original poster. How would I go about running the testing 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 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
The Eoan Ermine has reached end of life, so this bug will not be fixed for that release ** Changed in: linux-raspi2 (Ubuntu Eoan) Status: Confirmed => Won't Fix -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
This has probably already been noticed, but in an attempt to simply get my PI working somewhat the way i wanted, i changed my tunnel to run over wlan0 instead of eth0 (they both connect back to the same network so doesn't make a huge difference). Tunnel and interfaces have been up for days, no issues reported. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Thanks. I hope the installation worked - I only have Focal now, and the headers package in that folder was asking for a dependency from Eoan which I don't have. Still, I managed to boot the system, and unfortunately the behaviour is the same. Aug 1 12:04:56 rpi3 kernel: [ 117.985005] [ cut here ] Aug 1 12:04:56 rpi3 kernel: [ 117.985053] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Aug 1 12:04:56 rpi3 kernel: [ 117.985163] WARNING: CPU: 1 PID: 0 at /home/hwang4/work/mainline/build/eoan-rpi/ubuntu-eoan/net/sched/sch_generic.c:448 dev_watchdog+0x370/0x378 Aug 1 12:04:56 rpi3 kernel: [ 117.985168] Modules linked in: 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 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 input_leds bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) raspberrypi_hwmon vc_sm_cma(CE) raspberrypi_cpufreq v4l2_common videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev mc uio_pdrv_genirq uio sch_fq_codel drm 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 sdhci_iproc spidev phy_generic crct10dif_ce fixed aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 Aug 1 12:04:56 rpi3 kernel: [ 117.985309] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G C E 5.3.0-1030-raspi2 #32+testpreempt Aug 1 12:04:56 rpi3 kernel: [ 117.985311] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) Aug 1 12:04:56 rpi3 kernel: [ 117.985316] pstate: 8045 (Nzcv daif +PAN -UAO) Aug 1 12:04:56 rpi3 kernel: [ 117.985320] pc : dev_watchdog+0x370/0x378 Aug 1 12:04:56 rpi3 kernel: [ 117.985324] lr : dev_watchdog+0x370/0x378 Aug 1 12:04:56 rpi3 kernel: [ 117.985326] sp : 1000bd90 Aug 1 12:04:56 rpi3 kernel: [ 117.985329] x29: 1000bd90 x28: 567789c1abf0 Aug 1 12:04:56 rpi3 kernel: [ 117.985334] x27: eeb8788d4480 x26: Aug 1 12:04:56 rpi3 kernel: [ 117.985338] x25: 0140 x24: eeb86f5c8480 Aug 1 12:04:56 rpi3 kernel: [ 117.985342] x23: 56778a807000 x22: eeb8788d445c Aug 1 12:04:56 rpi3 kernel: [ 117.985346] x21: eeb8788d4000 x20: eeb8788d4480 Aug 1 12:04:56 rpi3 kernel: [ 117.985351] x19: x18: Aug 1 12:04:56 rpi3 kernel: [ 117.985355] x17: x16: Aug 1 12:04:56 rpi3 kernel: [ 117.985359] x15: 56778a809708 x14: 56778a9418e0 Aug 1 12:04:56 rpi3 kernel: [ 117.985363] x13: 56778a941533 x12: 56778a82e000 Aug 1 12:04:56 rpi3 kernel: [ 117.985367] x11: x10: 56778a94 Aug 1 12:04:56 rpi3 kernel: [ 117.985372] x9 : x8 : 56778a94b8ab Aug 1 12:04:56 rpi3 kernel: [ 117.985376] x7 : x6 : 0002 Aug 1 12:04:56 rpi3 kernel: [ 117.985379] x5 : x4 : 0002 Aug 1 12:04:56 rpi3 kernel: [ 117.985385] x3 : x2 : 0004 Aug 1 12:04:56 rpi3 kernel: [ 117.985389] x1 : 2668adad17146c00 x0 : Aug 1 12:04:56 rpi3 kernel: [ 117.985394] Call trace: Aug 1 12:04:56 rpi3 kernel: [ 117.985400] dev_watchdog+0x370/0x378 Aug 1 12:04:56 rpi3 kernel: [ 117.985407] call_timer_fn+0x38/0x1e8 Aug 1 12:04:56 rpi3 kernel: [ 117.985412] run_timer_softirq+0x518/0x550 Aug 1 12:04:56 rpi3 kernel: [ 117.985417] __do_softirq+0x178/0x428 Aug 1 12:04:56 rpi3 kernel: [ 117.985422] irq_exit+0xf4/0x100 Aug 1 12:04:56 rpi3 kernel: [ 117.985429] __handle_domain_irq+0x90/0xf8 Aug 1 12:04:56 rpi3 kernel: [ 117.985433] bcm2836_arm_irqchip_handle_irq+0x68/0xd0 Aug 1 12:04:56 rpi3 kernel: [ 117.985436] el1_irq+0x108/0x200 Aug 1 12:04:56 rpi3 kernel: [ 117.985443] arch_cpu_idle+0x30/0x228 Aug 1 12:04:56 rpi3 kernel: [ 117.985453] default_idle_call+0x28/0x4c Aug 1 12:04:56 rpi3 kernel: [ 117.985458] do_idle+0x1e0/0x2c8 Aug 1 12:04:56 rpi3 kernel: [ 117.985464] cpu_startup_entry+0x28/0x30 Aug 1 12:04:56 rpi3 kernel: [ 117.985473] secondary_start_kernel+0x184/0x250 Aug 1 12:04:56 rpi3 kernel: [ 117.985476] ---[ end trace 6bb7d08c2e67083a ]--- -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Please test this kernel, I enabled the preempt in the testing kernel. https://people.canonical.com/~hwang4/rpi-preempt/ -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@Hui, is there a guide/checklist how to test the Pi OS kernel on Ubuntu? I trie replacing the contents of the FAT partition, and the kernel did boot, but that's still missing the modules, possibly something else..? -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Recently we found the CONFIG_PREEMPT is not enabled in the ubuntu kernel, but it is enabled in the Pi OS's kernel. We plan to enable the CONFIG_PREEMPT in the ubuntu kernel too. So please wait for that kernel and then test a kernel with PREEMPT enabled. Or you could test Pi OS's kernel first. Looks like there is 5.4 Pi OS's kernel. 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 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
** Attachment added: "kernel_5.4.0-1015.log" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5397093/+files/kernel_5.4.0-1015.log -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I got myself the Ruideng TC66 USB tester and played a bit with it - it appears that after the network dies on Raspberry, the system's stable power consumption ends up higher than when it's functional and idling. Some stray endless loop, perhaps? ** Attachment added: "RPi3B+ power consumption during bug" https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861936/+attachment/5397091/+files/Screenshot%202020-07-30%20at%2001.16.47.png -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I can confirm I am also seeing a very similar set of circumstances: -Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) -5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:34:24 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux -The "tunnel" in my case is using Wireguard to a server hosted externally. -Wireless continues to work -eth0 drops (can get arp but not packets) -Reboot is the only fix -Happens randomly, haven't been able to pinpoint the actual cause in my case -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Forgot to include: Jul 28 18:18:25 dns1 kernel: [ 1289.970276] [ cut here ] Jul 28 18:18:25 dns1 kernel: [ 1289.970354] NETDEV WATCHDOG: eth0 (lan78xx): transmit queue 0 timed out Jul 28 18:18:25 dns1 kernel: [ 1289.970463] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x324/0x330 Jul 28 18:18:25 dns1 kernel: [ 1289.970467] Modules linked in: wireguard ip6_udp_tunnel udp_tunnel 8021q garp mrp stp llc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 bcm2835_v4l2(CE) bcm2835_codec(CE) bcm2835_isp(CE) bcm2835_mmal_vchiq(CE) snd_bcm2835(CE) v4l2_mem2mem videobuf2_vmalloc videobuf2_dma_contig snd_pcm videobuf2_memops videobuf2_v4l2 snd_timer videobuf2_common raspberrypi_hwmon snd videodev mc vc_sm_cma(CE) rpi_poe_fan uio_pdrv_genirq uio sch_fq_codel drm 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 crct10dif_ce spidev phy_generic aes_neon_bs aes_neon_blk crypto_simd cryptd Jul 28 18:18:25 dns1 kernel: [ 1289.970634] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G C E 5.4.0-1015-raspi #15-Ubuntu Jul 28 18:18:25 dns1 kernel: [ 1289.970639] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) Jul 28 18:18:25 dns1 kernel: [ 1289.970646] pstate: 6045 (nZCv daif +PAN -UAO) Jul 28 18:18:25 dns1 kernel: [ 1289.970655] pc : dev_watchdog+0x324/0x330 Jul 28 18:18:25 dns1 kernel: [ 1289.970662] lr : dev_watchdog+0x324/0x330 Jul 28 18:18:25 dns1 kernel: [ 1289.970666] sp : 80001000bd60 Jul 28 18:18:25 dns1 kernel: [ 1289.970669] x29: 80001000bd60 x28: 0140 Jul 28 18:18:25 dns1 kernel: [ 1289.970677] x27: x26: Jul 28 18:18:25 dns1 kernel: [ 1289.970684] x25: 34891000 x24: a6c7d8749018 Jul 28 18:18:25 dns1 kernel: [ 1289.970691] x23: x22: 0001 Jul 28 18:18:25 dns1 kernel: [ 1289.970698] x21: 34891480 x20: a6c7d8c07000 Jul 28 18:18:25 dns1 kernel: [ 1289.970704] x19: x18: Jul 28 18:18:25 dns1 kernel: [ 1289.970711] x17: x16: Jul 28 18:18:25 dns1 kernel: [ 1289.970726] x15: 35a35e50 x14: Jul 28 18:18:25 dns1 kernel: [ 1289.970733] x13: x12: a6c7d8d3f000 Jul 28 18:18:25 dns1 kernel: [ 1289.970740] x11: a6c7d8c2c000 x10: Jul 28 18:18:25 dns1 kernel: [ 1289.970746] x9 : 0004 x8 : 01b9 Jul 28 18:18:25 dns1 kernel: [ 1289.970752] x7 : x6 : 0001 Jul 28 18:18:25 dns1 kernel: [ 1289.970759] x5 : x4 : 0002 Jul 28 18:18:25 dns1 kernel: [ 1289.970765] x3 : a6c7d8015790 x2 : 0040 Jul 28 18:18:25 dns1 kernel: [ 1289.970772] x1 : ba6e3f480831e100 x0 : Jul 28 18:18:25 dns1 kernel: [ 1289.970779] Call trace: Jul 28 18:18:25 dns1 kernel: [ 1289.970787] dev_watchdog+0x324/0x330 Jul 28 18:18:25 dns1 kernel: [ 1289.970800] call_timer_fn+0x3c/0x178 Jul 28 18:18:25 dns1 kernel: [ 1289.970810] __run_timers.part.0+0x204/0x330 Jul 28 18:18:25 dns1 kernel: [ 1289.970817] run_timer_softirq+0x40/0x78 Jul 28 18:18:25 dns1 kernel: [ 1289.970828] __do_softirq+0x168/0x384 Jul 28 18:18:25 dns1 kernel: [ 1289.970836] irq_exit+0xb0/0xe8 Jul 28 18:18:25 dns1 kernel: [ 1289.970846] __handle_domain_irq+0x70/0xc0 Jul 28 18:18:25 dns1 kernel: [ 1289.970853] bcm2836_arm_irqchip_handle_irq+0x74/0xe0 Jul 28 18:18:25 dns1 kernel: [ 1289.970859] el1_irq+0x108/0x200 Jul 28 18:18:25 dns1 kernel: [ 1289.970869] arch_cpu_idle+0x3c/0x1c8 Jul 28 18:18:25 dns1 kernel: [ 1289.970879] default_idle_call+0x24/0x48 Jul 28 18:18:25 dns1 kernel: [ 1289.970890] do_idle+0x210/0x2a0 Jul 28 18:18:25 dns1 kernel: [ 1289.970898] cpu_startup_entry+0x28/0x30 Jul 28 18:18:25 dns1 kernel: [ 1289.970910] secondary_start_kernel+0x134/0x1b8 Jul 28 18:18:25 dns1 kernel: [ 1289.970915] ---[ end trace 919e51f0c16f2046 ]--- -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
FWIW, i actually thought this was a bug with the latest raspbian image and decided to move forward with using 20.04 on my raspberry pi's, turns out that wasn't the case. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@hui.wang - yes, I have seen this a few times in Focal since upgrading about a month ago. I didn't look at the logs closely, but the message that appears repeatedly after the interface fails is "eth0: kevent 0 may have been dropped" I think, and bug #1647397 may be related/identical. User from that bug ascribes the cause to the use of bridge, and this is my case. @Matt, are you also running the interface in a bridge? -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@mlx and Matt, We have ubuntu-5.4 kernel for raspi (20.04), could you please test if this issue still happen with 5.4 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 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi2 (Ubuntu Focal) Status: New => Confirmed -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
I can confirm having the same issue, including on multiple raspberry pi 3s, one with an IPv6 tunnel from tunnelbroker.net, and one without. It can be triggered by a lot of IPv4 traffic for me as well. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Still observed with 5.3.0-1023 on eoan. Will be switching to focal, seeing as it should now boot. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
** Also affects: linux-raspi2 (Ubuntu Focal) Importance: Undecided Status: New -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
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: 6045 (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 : 80001000bd60 Apr 25 18:11:21 localhost kernel: [22872.243005] x29: 80001000bd60 x28: 0140 Apr 25 18:11:21 localhost kernel: [22872.243014] x27: x26: Apr 25 18:11:21 localhost kernel: [22872.243023] x25: 2f65 x24: a8d07f545018 Apr 25 18:11:21 localhost kernel: [22872.243031] x23: x22: 0001 Apr 25 18:11:21 localhost kernel: [22872.243039] x21: 2f650480 x20: a8d07fa07000 Apr 25 18:11:21 localhost kernel: [22872.243047] x19: x18: Apr 25 18:11:21 localhost kernel: [22872.243055] x17: 800010876378 x16: Apr 25 18:11:21 localhost kernel: [22872.243063] x15: 39234090 x14: Apr 25 18:11:21 localhost kernel: [22872.243072] x13: x12: a8d07fb3e000 Apr 25 18:11:21 localhost kernel: [22872.243081] x11: a8d07fa2c000 x10: Apr 25 18:11:21 localhost kernel: [22872.243088] x9 : 0004 x8 : 01cb Apr 25 18:11:21 localhost kernel: [22872.243096] x7 : x6 : 0001 Apr 25 18:11:21 localhost kernel: [22872.243103] x5 : x4 : 0002 Apr 25 18:11:21 localhost kernel: [22872.243111] x3 : a8d07ee15790 x2 : 0040 Apr 25 18:11:21 localhost kernel: [22872.243119] x1 : 3cb8609474fd0d00 x0 : 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
[Bug 1861936] Re: Raspberry Pi 3 network dies shortly after a burst of IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi2 (Ubuntu Eoan) Status: New => Confirmed -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Minor update - tried to check what's going on with 5.4 kernel by listening on the UART - there's no output. Setting standard priority on the focal-proposed repo, and reinstalling the linux-raspi2 package (along with its dependencies) from focal-proposed makes no difference. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
** Also affects: linux-raspi2 (Ubuntu Eoan) Importance: Undecided Status: New -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
For reference, recovered the installation with: cd <1st partition, FAT> for FILE in *.bak ;do mv -i ${FILE%%.bak} ${FILE%%.bak}.broken; mv -i ${FILE} ${FILE%%.bak}; done So yeah, kernel 5.4.0.1004.4 is unbootable. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
@juergh - I'm using origin/priority/pinning, so I installed that kernel with apt install linux-raspi2=5.4.0.1004.4 linux-image-raspi2=5.4.0.1004.4 linux-headers=5.4.0.1004.4 # (or something like that) Now my RPi is stuck at the color palette screen. As there is no grub2 AFAICT, what do I need to do to switch back to the older kernel? (I'm pretty sure the kernel was not uninstalled. -- 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 IPv6 tunnel network load ((lan78xx): transmit queue 0 timed out)
Can you try the Focal 5.4 kernel to see if the problem still exists there as well? Add the following line to /etc/apt/sources.list and run (I believe) 'apt install linux-raspi2': deb http://ports.ubuntu.com/ubuntu-ports focal-proposed universe -- 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 IPv6 tunnel 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 (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: + 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: 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.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+0x