From owner-freebsd-current@FreeBSD.ORG Thu Jun 17 20:53:41 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C78F16A4CE; Thu, 17 Jun 2004 20:53:41 +0000 (GMT) Received: from lithium.plan-ix.de (lithium.plan-ix.de [212.37.39.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA0A343D48; Thu, 17 Jun 2004 20:53:39 +0000 (GMT) (envelope-from braukmann@tse-online.de) Received: from localhost (lithium.plan-ix.de [212.37.39.35]) by lithium.plan-ix.de (Postfix) with ESMTP id 469D92EDE4F; Thu, 17 Jun 2004 20:52:16 +0000 (GMT) Received: from localhost.plan-ix.de ([212.37.39.35]) by localhost (lithium.plan-ix.de [212.37.39.35]) (amavisd-new, port 10025) with ESMTP id 97246-08; Thu, 17 Jun 2004 20:52:15 +0000 (GMT) Received: from [192.168.225.100] (p508247E0.dip0.t-ipconnect.de [80.130.71.224]) by lithium.plan-ix.de (Postfix) with ESMTP id AB2CD2EC66F; Thu, 17 Jun 2004 20:52:15 +0000 (GMT) Date: Thu, 17 Jun 2004 22:52:15 +0200 From: Andreas Braukmann To: Bill Paul Message-ID: <76590000.1087505535@cage.int.unixxinu.de> In-Reply-To: <20040617202559.1904C16A4CF@hub.freebsd.org> References: <20040617202559.1904C16A4CF@hub.freebsd.org> X-Mailer: Mulberry/3.1.0 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new at plan-ix.de cc: freebsd-current@freebsd.org Subject: Re: Realtek RT8139 (onboard) - failed to receive packet in loopback mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2004 20:53:41 -0000 On 06/17/04 20:25:59 +0000 Bill Paul wrote: >> re0: port 0xdc00-0xdcff mem 0xe3400000-0xe34000ff irq 11 at device 9.0 on pci0 >> re0: Ethernet address: 00:90:fb:04:1b:31 >> re0: diagnostic failed, failed to receive packet in loopback mode >> re0: attach aborted due to hardware diag failure >> device_attach: re0 attach returned 5 >> >> >> It seems that the 8169-specific hardware diagnostic (re_diag(sc)) >> should only carried out for chips being identified as 8169 based. > > No, it works with the 8139C+ too (though it's not strictly necessary: > the hardware bug that the re_diag() routine was meant to find is only > present on some 8169 boards, but running the DMA test on all boards > doesn't hurt). ok. > [...] > >> I see no ill effects so far. I didn't notice an additional problem at first sight: ifconfig doesn't show the media types. gate# ifconfig re0 re0: flags=8843 mtu 1500 options=1b inet 192.168.222.222 netmask 0xffffff00 broadcast 192.168.222.255 ether 00:90:fb:04:1b:31 media: Ethernet autoselect (none) The PHY is recognized as follows: rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > I discovered some problems with the diagnostic routine on the C+ > chip recently, but it only manifested on this one really old and > crufty P166 machine My systems are equipped with VIA C3/533 CPUs. > that I have (and then only intermittently). > It turns out that the link state has some effect on the behavior > of loopback mode (even though logically, it shouldn't). That is, > sometimes the test will fail if the network cable is unplugged. That might have been the cause in my case, too. The ports were not connected to the switch at probe time. I just double-checked this and the diagnostic fails with the port connected to the switch, too. > I made some changes to re_diag() to fix this, I would test the changes gladly. > which I can send you once I get home from the office. Thanks. -Andreas