NetBSD Problem Report #59765

From www@netbsd.org  Sun Nov 16 14:17:24 2025
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits)
	 client-signature RSA-PSS (2048 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id D0FC01A9239
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 16 Nov 2025 14:17:24 +0000 (UTC)
Message-Id: <20251116141723.934451A923A@mollari.NetBSD.org>
Date: Sun, 16 Nov 2025 14:17:23 +0000 (UTC)
From: cryintothebluesky@gmail.com
Reply-To: cryintothebluesky@gmail.com
To: gnats-bugs@NetBSD.org
Subject: ure(4) seems to be quite broken on Raspberry Pi 3
X-Send-Pr-Version: www-1.0

>Number:         59765
>Category:       port-evbarm
>Synopsis:       ure(4) seems to be quite broken on Raspberry Pi 3
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-evbarm-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Nov 16 14:20:00 +0000 2025
>Originator:     Sad Clouds
>Release:        10.1
>Organization:
>Environment:
$ uname -a
NetBSD rp3 10.1 NetBSD 10.1 (GENERIC64) #0: Mon Dec 16 13:08:11 UTC 2024  mkrepro@mkrepro.NetBSD.org:/usr/src/sys/arch/evbarm/compile/GENERIC64 evbarm
>Description:
The following USB ethernet device is detected on boot. Relevant lines from dmesg:

[     3.901533] ure0 at uhub2 port 2
[     3.901533] ure0: Lenovo (0x0bda) Thinkpad USB LAN (0x8153), rev 2.10/31.20, addr 4
[     3.911535] ure0: RTL8153 unknown ver 6010
[     3.981539] rgephy0 at ure0 phy 0: RTL8251 1000BASE-T media interface, rev. 0
[     3.991541] rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto
[     4.001541] ure0: Ethernet address 3c:18:a0:25:79:72

However pinging this device from a Linux machine results in very erratic behaviour, as this ethernet device is constantly dropping packets:

$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=255 time=0.749 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=255 time=0.545 ms
From 192.168.1.2 icmp_seq=9 Destination Host Unreachable
From 192.168.1.2 icmp_seq=10 Destination Host Unreachable
From 192.168.1.2 icmp_seq=11 Destination Host Unreachable
From 192.168.1.2 icmp_seq=12 Destination Host Unreachable
From 192.168.1.2 icmp_seq=13 Destination Host Unreachable
From 192.168.1.2 icmp_seq=14 Destination Host Unreachable
From 192.168.1.2 icmp_seq=15 Destination Host Unreachable
From 192.168.1.2 icmp_seq=16 Destination Host Unreachable
From 192.168.1.2 icmp_seq=17 Destination Host Unreachable
From 192.168.1.2 icmp_seq=18 Destination Host Unreachable
From 192.168.1.2 icmp_seq=19 Destination Host Unreachable
From 192.168.1.2 icmp_seq=20 Destination Host Unreachable
From 192.168.1.2 icmp_seq=21 Destination Host Unreachable
From 192.168.1.2 icmp_seq=22 Destination Host Unreachable
From 192.168.1.2 icmp_seq=23 Destination Host Unreachable
From 192.168.1.2 icmp_seq=24 Destination Host Unreachable
From 192.168.1.2 icmp_seq=25 Destination Host Unreachable
From 192.168.1.2 icmp_seq=26 Destination Host Unreachable
From 192.168.1.2 icmp_seq=37 Destination Host Unreachable
From 192.168.1.2 icmp_seq=38 Destination Host Unreachable
From 192.168.1.2 icmp_seq=39 Destination Host Unreachable
From 192.168.1.2 icmp_seq=51 Destination Host Unreachable
From 192.168.1.2 icmp_seq=52 Destination Host Unreachable
From 192.168.1.2 icmp_seq=53 Destination Host Unreachable
From 192.168.1.2 icmp_seq=54 Destination Host Unreachable
From 192.168.1.2 icmp_seq=55 Destination Host Unreachable
From 192.168.1.2 icmp_seq=56 Destination Host Unreachable
From 192.168.1.2 icmp_seq=57 Destination Host Unreachable
From 192.168.1.2 icmp_seq=58 Destination Host Unreachable
From 192.168.1.2 icmp_seq=59 Destination Host Unreachable
64 bytes from 192.168.1.1: icmp_seq=3 ttl=255 time=58369 ms
64 bytes from 192.168.1.1: icmp_seq=60 ttl=255 time=1025 ms
64 bytes from 192.168.1.1: icmp_seq=61 ttl=255 time=0.676 ms
64 bytes from 192.168.1.1: icmp_seq=62 ttl=255 time=0.454 ms
64 bytes from 192.168.1.1: icmp_seq=63 ttl=255 time=0.447 ms
64 bytes from 192.168.1.1: icmp_seq=64 ttl=255 time=0.465 ms
64 bytes from 192.168.1.1: icmp_seq=65 ttl=255 time=0.455 ms
64 bytes from 192.168.1.1: icmp_seq=66 ttl=255 time=0.375 ms
64 bytes from 192.168.1.1: icmp_seq=67 ttl=255 time=0.383 ms

However:

Same device seems to work OK on NetBSD x86 VM.
Same device seems to work OK on FreeBSD Raspberry Pi 4 (not tested it with FreeBSD on Pi 3)

There seems to be something broken with NetBSD ure(4) driver and Raspberry Pi 3.









>How-To-Repeat:

>Fix:

Home	PR Database Search