From owner-freebsd-stable@FreeBSD.ORG Thu Mar 23 19:32:31 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB68716A53A for ; Thu, 23 Mar 2006 19:32:31 +0000 (UTC) (envelope-from joao@matik.com.br) Received: from msrv.matik.com.br (msrv.matik.com.br [200.152.83.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF88D43D66 for ; Thu, 23 Mar 2006 19:31:49 +0000 (GMT) (envelope-from joao@matik.com.br) Received: from anb (anb.matik.com.br [200.152.83.34]) by msrv.matik.com.br (8.13.4/8.13.1) with ESMTP id k2NJV9KN027086; Thu, 23 Mar 2006 16:31:09 -0300 (BRT) (envelope-from joao@matik.com.br) From: JoaoBR To: "Bjoern A. Zeeb" Date: Thu, 23 Mar 2006 16:31:30 -0300 User-Agent: KMail/1.9.1 References: <20060323182910.1190845041@ptavv.es.net> <200603231540.33339.joao@matik.com.br> <20060323184852.G2181@maildrop.int.zabbadoz.net> In-Reply-To: <20060323184852.G2181@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200603231631.30866.joao@matik.com.br> X-Filter-Version: 1.11a (msrv.matik.com.br) X-Virus-Scanned: ClamAV version 0.88, clamav-milter version 0.87 on msrv.matik.com.br X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org Subject: Re: nve timeout (and down) regression? 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, 23 Mar 2006 19:32:31 -0000 On Thursday 23 March 2006 15:59, Bjoern A. Zeeb wrote: > If you have collisions you have most likeely a duplex mismatch. > yep, but I set manually matching with the switch and tried other speeds, no= =20 change > If you read the code and I remember right the above change is a NOP. > anyway, resolved my case ... > > The timeouts have been there and are there. The difference with the > last commits is that a lot of people couldn't get the NIC working at > all before and now it works (somewhat) but there are timeouts from > time to time which for some people seem to auto-recover and for > others still get things 'stuck'. > nve did not worked on 6.0R (for me) but cvsup to stable resolved the case (= for=20 me) in end of dezember since a month or so with recent releng_6 the problem came back, timeouts an= d=20 stopping rx/tx=20 > The problem is to diagnose what everyone really has > - branch running (RELENG_6 or HEAD) releng_6 last cvsup from thi monday > - i386 or amd64 amd64 > - exact FreeBSD revisions for if_nve.c > - if using patches which > - pciconf -lv | grep -A4 ^nve nve0: port 0xd400-0xd407 mem=20 0xec000000-0xec000fff irq 20 at device 5.0 on pci0 nve0: Ethernet address 00:04:61:98:97:d5 miibus0: on nve0 nve0@pci0:5:0: class=3D0x068000 card=3D0x100c1695 chip=3D0x00df10de rev=3D= 0xa2=20 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' device =3D 'Network Bus Enumerator' class =3D bridge > - which board > > - exact problems=20 > * is the interface working at all the system after probing HW comes up with=20 nve0 down nve0 up nve0 down=20 Jo=E3o > * is it just stuck from time to time > * ... > > See http://www.freebsd.org/cgi/query-pr.cgi?pr=3D94524 for more > questions. You my want to submit a fllow up and add your description > with the answer to these questions there. =2D-=20 Atenciosamente Infomatik Internet Technology (18)3551.8155 (18)8112.7007 http://info.matik.com.br A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br