From owner-freebsd-stable@FreeBSD.ORG Thu May 29 15:56:05 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A0AF106566C for ; Thu, 29 May 2008 15:56:05 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from qsrv01sl.mx.bigpond.com (qsrv01sl.mx.bigpond.com [144.140.92.181]) by mx1.freebsd.org (Postfix) with ESMTP id 73D2B8FC1E for ; Thu, 29 May 2008 15:56:04 +0000 (UTC) (envelope-from dewayne.geraghty@heuristicsystems.com.au) Received: from nschwotgx03p.mx.bigpond.com ([58.172.113.127]) by nschwmtas02p.mx.bigpond.com with ESMTP id <20080529130307.VHJQ23069.nschwmtas02p.mx.bigpond.com@nschwotgx03p.mx.bigpond.com>; Thu, 29 May 2008 13:03:07 +0000 Received: from mail.heuristicsystems.com.au ([58.172.113.127]) by nschwotgx03p.mx.bigpond.com with ESMTP id <20080529130306.GPIO1860.nschwotgx03p.mx.bigpond.com@mail.heuristicsystems.com.au>; Thu, 29 May 2008 13:03:06 +0000 Received: from black (black.hs [10.0.5.1]) (authenticated bits=0) by mail.heuristicsystems.com.au (8.14.3/8.14.3) with ESMTP id m4TD31md056051 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 29 May 2008 23:03:01 +1000 (EST) (envelope-from dewayne.geraghty@heuristicsystems.com.au) From: "Dewayne Geraghty" To: "=?iso-8859-1?Q?'Gerrit_K=FChn'?=" References: <20080527165232.2acbb00f.gerrit@pmp.uni-hannover.de><20080528002823.GA63696@cdnetworks.co.kr><20080528175610.0ffe4c1c.gerrit@pmp.uni-hannover.de> <20080529115825.2da70cba.gerrit@pmp.uni-hannover.de> Date: Thu, 29 May 2008 23:03:01 +1000 Message-ID: <7827655D32C747BE861B939EDF20F6E3@hs> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20080529115825.2da70cba.gerrit@pmp.uni-hannover.de> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 Thread-Index: AcjBcseln6K40tSIQPytBcGUxLmJVQAF7Q6Q X-RPD-ScanID: Class confirmed; VirusThreatLevel unknown, RefID str=0001.0A150204.483E1461.008C,ss=4,sh,fgs=12 Cc: freebsd-stable@freebsd.org Subject: RE: broken re(4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 May 2008 15:56:05 -0000 >-----Original Message----- >From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Gerrit K=FChn >Sent: Thursday, 29 May 2008 7:58 PM >To: Gerrit K=FChn >Cc: pyunyh@gmail.com; freebsd-stable@freebsd.org >Subject: Re: broken re(4) > >On Wed, 28 May 2008 17:56:10 +0200 Gerrit K=FChn = wrote about Re: broken re(4): > >GK> PY> http://people.freebsd.org/~yongari/re/re.HEAD.20080519 . >GK> Somehow the two interfaces seem to interfer with each other. Can I=20 >GK> provide further information for fixing this? > >Meanwhile I booted the machine with the patch several times. I get = either the same status as without the patch (both interfaces basically working, = but with hangs and checksum errors under load) or I get one interface = working fine and one not working at all. >I tried turning one if off in the bios, but this didn't change the >situation: The remaining one is either working with problems or not at = all. > >Can I do anything else? Is the newer patch (from yesterday) in your directory above worth giving a try? > > >cu > Gerrit --- Reply --- You might try, after rebooting, to physically unplug and replug your networking cables. I have a few EN-15000 and SN-18000 motherboards attached to different = types of switches. With the SN-18000 on FreeBSD 7.0R-p1 to make the vge NIC function even after rebooting I need to unplug the NIC's. Doesn't matter what switch, or even using a crossover cable, the card needs to = reinitialise itself. This may be similar the problem that you're experiencing. And = as Pyon YongHyeon mentions there is a lot of variety with rl and re cards, = I also use re in my ITX motherboards, without experiencing your issues. Also, after rebooting your machines try performing tcpdump -vv on the interface that isn't working while (ie before & after) you try the unplug/plug sequence. (vge's since 6.1R experience a lot of incorrect checksums.) I'm suggesting these steps as they might also assist others with clues to assist diagnoses with your re's) Regards, Dewayne.