From owner-freebsd-bugs@FreeBSD.ORG Sat Aug 27 14:50:18 2005 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB01C16A41F for ; Sat, 27 Aug 2005 14:50:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B68BE43D45 for ; Sat, 27 Aug 2005 14:50:18 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id j7REoIPk074513 for ; Sat, 27 Aug 2005 14:50:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id j7REoIbm074512; Sat, 27 Aug 2005 14:50:18 GMT (envelope-from gnats) Date: Sat, 27 Aug 2005 14:50:18 GMT Message-Id: <200508271450.j7REoIbm074512@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: "Julien Gabel" Cc: Subject: Re: kern/80005 : [if_re] re(4) network interface _very_ unpredictable working (RTL8169S/8110S Gigabit Ethernet). X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Julien Gabel List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Aug 2005 14:50:19 -0000 The following reply was made to PR kern/80005; it has been noted by GNATS. From: "Julien Gabel" To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/80005 : [if_re] re(4) network interface _very_ unpredictable working (RTL8169S/8110S Gigabit Ethernet). Date: Sat, 27 Aug 2005 16:49:09 +0200 (CEST) Just to note that the problem persist at this time, currently using RELENG_6 permanently. Others report were made, showing that this is not an isolated problem, even though it may not be widely seen. One report said that this may be corrected in -CURRENT, but i don't have the material to test it right now. But if that is right, and since this problem happeared before 5.2 release, it may be a good thing if someone may be test it, trying to MFC fixes before the 6.0 release if any (two years with this same problem seems very long). As asked by Bjoern A. Zeeb on current@[1], follow the PHY/miibus information for re(4): # grep rgephy /var/run/dmesg.boot rgephy0: on miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto -- -jpeg. [1] lists.freebsd.org/pipermail/freebsd-current/2005-August/054843.html