From owner-freebsd-current@FreeBSD.ORG Thu Jun 17 18:43:43 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 834C516A4CE; Thu, 17 Jun 2004 18:43:43 +0000 (GMT) Received: from avscan2.sentex.ca (avscan2.sentex.ca [199.212.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C591943D41; Thu, 17 Jun 2004 18:43:42 +0000 (GMT) (envelope-from mike@sentex.net) Received: from localhost (localhost.sentex.ca [127.0.0.1]) by avscan2.sentex.ca (8.12.11/8.12.11) with ESMTP id i5HIh86l026797; Thu, 17 Jun 2004 14:43:09 -0400 (EDT) (envelope-from mike@sentex.net) Received: from avscan2.sentex.ca ([127.0.0.1]) by localhost (avscan2.sentex.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 26345-07; Thu, 17 Jun 2004 14:43:08 -0400 (EDT) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by avscan2.sentex.ca (8.12.11/8.12.11) with ESMTP id i5HIh8pg026742; Thu, 17 Jun 2004 14:43:08 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.11/8.12.11) with ESMTP id i5HIh06B023827; Thu, 17 Jun 2004 14:43:00 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.1.1.1.0.20040617130800.113cf920@64.7.153.2> X-Sender: mdtpop@64.7.153.2 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1 Date: Thu, 17 Jun 2004 14:45:18 -0400 To: Andreas Braukmann , freebsd-current@freebsd.org From: Mike Tancsa In-Reply-To: <17680000.1087489752@bitrot.bitlab.unixxinu.de> References: <17680000.1087489752@bitrot.bitlab.unixxinu.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at avscan2b 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 18:43:43 -0000 At 12:29 PM 17/06/2004, Andreas Braukmann wrote: >Hi there, > >I'm using a bunch of Portwell SBCs with five onboard Realtek >8139C+ NICs. Currently they're running 5.0 kernels from around >April, 2003 and the NICs are driven by rl(4). Since then the >8139C+ was moved to re(4). > >re(4) doesn't like the chips, though. > >pciconf -lv output: > >re0@pci0:9:0: class=0x020000 card=0x813910ec chip=0x813910ec rev=0x20 >hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RT8139 (A/B/C/813x/C+) Fast Ethernet Adapter' > class = network > subclass = ethernet Interesting. I have come across 2 motherboards now that have onboard Realteks of some sort, similar to what you see. In the PCI conf below, rl0 is the onboard and rl1 a PCI version. rl0@pci1:4:0: class=0x020000 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RT8139 (A/B/C/813x/C+) Fast Ethernet Adapter' class = network subclass = ethernet rl1@pci1:5:0: class=0x020000 card=0x813910ec chip=0x813910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RT8139 (A/B/C/813x/C+) Fast Ethernet Adapter' class = network subclass = ethernet Yet, one works as expected, the other half works in that the switch sees a lot of FCS errors as if there were a duplex mismatch, despite both sides being autoneg. (I tried various manual configs as well on both sides without change). This is on stable, but the same problem was happening on CURRENT when I tried to see if the re driver would see it, it did not. The only difference I see from your NIC and mine are the revs, yet the onboards on the 2 motherboards I have refuse to work without generating lots of errors. ---Mike