From owner-freebsd-current@FreeBSD.ORG Tue Mar 28 02:56:40 2006 Return-Path: X-Original-To: current@freebsd.org 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 08DB716A400 for ; Tue, 28 Mar 2006 02:56:40 +0000 (UTC) (envelope-from root@solink.ru) Received: from ns.itam.nsc.ru (ns.itam.nsc.ru [194.226.179.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49E9243D45 for ; Tue, 28 Mar 2006 02:56:38 +0000 (GMT) (envelope-from root@solink.ru) Received: from site.lan (itut.itam.nsc.ru [194.226.179.2]) by ns.itam.nsc.ru (8.13.1/8.13.1) with ESMTP id k2S2uZi8022922 for ; Tue, 28 Mar 2006 09:56:36 +0700 Received: from bocha.solink.office ([192.168.66.166]) (authenticated bits=0) by site.lan (8.12.11.20060308/8.12.11) with ESMTP id k2S2uUt2005661 for ; Tue, 28 Mar 2006 09:56:30 +0700 From: Bachilo Dmitry Organization: SoLink To: current@freebsd.org Date: Tue, 28 Mar 2006 09:56:30 +0700 User-Agent: KMail/1.8 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200603280956.30659.root@solink.ru> Cc: Subject: nve0: device timeout (1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 28 Mar 2006 02:56:40 -0000 I've recently upgraded one of my home PCs from Intel Celeron to AMD Athlon.= I=20 used to have Marvel Gigabit network (sk), and now I have nVidia nForce 3=20 network - nve (witch man says: "First appeared in FreeBSD 5.5", so it has n= ot=20 appeared yet? :-) The problem is that if this interface is online and I run something that us= es=20 network (for example XChat, or even Quake 4, witch is always accessing=20 127.0.0.1 for ID Server), then like every minute (interval is not always th= e=20 same) the computer hangs absolutely (even mouse is not moving) for like two= =20 seconds and then "Jan 2 09:41:12 gamer kernel: nve0: device timeout (1)"=20 falls on tty0. And dmesg says: Jan 2 09:39:13 gamer kernel: nve0: device timeout (1) Jan 2 09:39:13 gamer kernel: nve0: link state changed to DOWN Jan 2 09:39:14 gamer kernel: nve0: link state changed to UP Jan 2 09:39:44 gamer kernel: nve0: device timeout (1) Jan 2 09:39:44 gamer kernel: nve0: link state changed to DOWN Jan 2 09:39:46 gamer kernel: nve0: link state changed to UP Jan 2 09:40:16 gamer kernel: nve0: device timeout (1) Jan 2 09:40:16 gamer kernel: nve0: link state changed to DOWN Jan 2 09:40:17 gamer kernel: nve0: link state changed to UP Jan 2 09:40:48 gamer kernel: nve0: device timeout (1) Jan 2 09:40:48 gamer kernel: nve0: link state changed to DOWN Jan 2 09:40:49 gamer kernel: nve0: link state changed to UP Jan 2 09:41:12 gamer kernel: nve0: device timeout (1) Jan 2 09:41:12 gamer kernel: nve0: link state changed to DOWN Jan 2 09:41:13 gamer kernel: nve0: link state changed to UP Jan 2 09:41:22 gamer kernel: nve0: device timeout (1) Jan 2 09:41:22 gamer kernel: nve0: link state changed to DOWN Jan 2 09:41:23 gamer kernel: nve0: link state changed to UP and so on. This, you know, spoils all the mood from upgrade. Do I do something wrong o= r=20 is that driver or is that the device? =46irst I thought that it was overclocking problem, but no, I've set everyt= hing=20 to default and the problem stays. I use this PC for games, no secure data or anything else is there, so if it= =20 would be necessary, I could provide ssh shell to it. =2D-=20 =2D----------------------- =F3 =D5=D7=C1=D6=C5=CE=C9=C5=CD, =E2=C1=DE=C9=CC=CF =E4=CD=C9=D4=D2=C9=CA =F2=D5=CB=CF=D7=CF=C4=C9=D4=C5=CC=D8 =CF=D4=C4=C5=CC=C1 =D3=C9=D3=D4=C5=CD= =CE=CF=CA =C9=CE=D4=C5=C7=D2=C1=C3=C9=C9 =EF=EF=EF "=EB=CF=CD=D0=C1=CE=C9=D1 =F3=CF=EC=C9=CE=CB"