RX packet drops on Raspberry Pi 5 not reflected in ethtool or softnet_stat
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c, linux, raspberry-pi
- Domain
- embedded-iot, networking, operating-systems
Research direction
No source file or test is named. Start by reproducing sustained traffic while comparing ip -s link show eth0, ethtool -S eth0, /proc/net/softnet_stat, and /proc/interrupts, then inspect the macb driver and RP1 IRQ/DMA path. Done means identifying where the drops are counted and establishing whether a kernel or firmware change is required.
Written by the indexing model from the issue text.
Description
Describe the bug
RX dropped packets on Raspberry Pi 5 (RP1 Ethernet) not accounted for by ethtool or softnet_stat
Summary
Using a Raspberry Pi 5 (Model B Rev 1.0) with Raspberry Pi OS and the onboard RP1 Ethernet (driver: macb), I'm experiencing a consistent increase in RX packet drops as reported by ip -s link show eth0. However, these drops are not reflected in ethtool -S eth0 or /proc/net/softnet_stat.
This strongly suggests the packet loss is occurring between the NIC and the kernel network stack, likely due to RP1 driver (or DMA/IRQ handling) issues.
Symptoms
-
RX drops seen with
ip -s link show eth0:RX: bytes packets errors dropped missed mcast 4972630 27502 0 617 0 4248 -
No drops shown with
ethtool -S eth0:q0_rx_dropped: 0 rx_resource_errors: 0 rx_overruns: 0 -
No softnet backlog congestion:
grep . /proc/net/softnet_stat # all second columns (softnet drops) are 0 -
IRQs are handled only by CPU0 by default:
cat /proc/interrupts | grep eth 104: 44535 0 0 0 rp1_irq_chip 6 Level eth0 -
Installing and enabling
irqbalancedoes not stop the RX drops. -
Behavior persists even using USB 3.0 Ethernet adapters (tested with AX88179).
Diagnosis
- The kernel is counting dropped RX packets.
- The NIC driver (
macb) and DMA interface do not acknowledge drops. - The loss appears to happen in the path between NIC → driver → netdev → socket.
- The issue could be related to the RP1 integration or IRQ/DMA handling.
- Affects onboard Ethernet on Pi 5, not specific to cables or switch.
Request
Please advise on:
- Whether this is a known issue with the RP1 or the
macbdriver - Any recommended kernel module parameters or overlays
- Whether there are upcoming fixes in
rpi-firmwareor kernel updates - How to help trace or test this further
Happy to provide more debug logs if needed.
Steps to reproduce the behaviour
Reproducing the issue
- Boot Raspberry Pi 5 with default Raspberry Pi OS.
- Connect to gigabit network.
- Run any kind of sustained traffic (ping, DNS, iperf3).
- Monitor
ip -s link show eth0and observedroppedincreasing. - Check
ethtool -S eth0and/proc/net/softnet_stat: no errors reported.
Device (s)
Raspberry Pi 5
System
- Model: Raspberry Pi 5 Model B Rev 1.0
- OS: Raspberry Pi OS (64-bit, aarch64)
- Kernel:
uname -a Linux pihole6 6.12.25+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30) aarch64 GNU/Linux - Ethernet driver:
ethtool -i eth0 driver: macb version: 6.12.25+rpt-rpi-2712
The issue is not related to physical network components. The following were tested and ruled out:
- Multiple high-quality Ethernet cables (Cat6 and Cat7)
- Different switch ports and switches (1 Gbps)
- Direct connection to a known-good Asus ET12 router
- USB 3.0 Ethernet adapters (with AX88179 chipset)
- The problem persists regardless of the physical interface used
This confirms that the RX packet drops are not caused by link instability, faulty cables, or external hardware.
- Dominant language
- C
- Stars
- 13.2k
- Forks
- 5.5k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 21
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/linux
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7415 · 2 comments · 1 reaction ·
-
rp1-cfe doesn't forward V4L2_EVENT_SOURCE_CHANGE event from csi-2 sensor driver to userspace app Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raspberrypi/linux#7399 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
raspberrypi/linux#7357 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7054 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
raspberrypi/linux#7634 · 8 comments · 1 reaction ·
All issues in raspberrypi/linux
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#15320 ·
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarbourMasters/Shipwright#7229 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
riscv-software-src/riscv-isa-sim#2435 · 1 comment ·