From nobody@FreeBSD.org  Mon Jul 25 01:04:06 2005
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8EA8B16A41F
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 25 Jul 2005 01:04:06 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6514D43D45
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 25 Jul 2005 01:04:06 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j6P146xg002738
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 25 Jul 2005 01:04:06 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id j6P146Aw002737;
	Mon, 25 Jul 2005 01:04:06 GMT
	(envelope-from nobody)
Message-Id: <200507250104.j6P146Aw002737@www.freebsd.org>
Date: Mon, 25 Jul 2005 01:04:06 GMT
From: meka <meka@softhome.net>
To: freebsd-gnats-submit@FreeBSD.org
Subject: if_nve gets stuck
X-Send-Pr-Version: www-2.3

>Number:         84027
>Category:       amd64
>Synopsis:       [nve] if_nve gets stuck
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    yongari
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jul 25 01:10:19 GMT 2005
>Closed-Date:    Tue Aug 23 20:30:53 UTC 2011
>Last-Modified:  Tue Aug 23 20:30:53 UTC 2011
>Originator:     meka
>Release:        6.0-BETA1
>Organization:
>Environment:
FreeBSD hal9000 6.0-BETA1 FreeBSD 6.0-BETA1 #0: Sun Jul 24 04:00:43 CEST 2005     root@hal9000:/usr/src/sys/amd64/compile/HAL9000  amd64

>Description:
Some kind of if_nve buffer is geting full. I keep getting messages:
nve0: device timeout (2). When I get the "final" message nve0: device
timeout (64), I can not do anything on the LAN. I've noticed that this
buffer is fulled faster when I'm accessing NET (through gateway). I've
marked this bug as serious with medium priority because of FreeBSD's
policy "made to serve". Simple kldunload/kldload makes this buffer empty,
but this is not what one wants to do every 15 minutes.
>How-To-Repeat:
Use it on MSI nforce3 board.
>Fix:
      
>Release-Note:
>Audit-Trail:

From: Paul Richards <paul.richards@gmail.com>
To: bug-followup@FreeBSD.org, meka@softhome.net
Cc:  
Subject: Re: amd64/84027: if_nve gets stuck
Date: Sun, 9 Oct 2005 11:09:37 +0100

 Just like to note that this problem is still present on 6.0 BETA5 with
 an Epox nForce4 motherboard.
 
 --
 Paul Richards
State-Changed-From-To: open->analyzed 
State-Changed-By: andreas 
State-Changed-When: Thu Oct 27 11:06:34 GMT 2005 
State-Changed-Why:  
Could you please check the following patch from Quentin, see: 
http://www.freebsd.org/cgi/query-pr.cgi?pr=88045 

Index: if_nve.c 
=================================================================== 
RCS file: /data/ncvs/src/sys/dev/nve/if_nve.c,v 
retrieving revision 1.7.2.4 
diff -u -r1.7.2.4 if_nve.c 
--- if_nve.c    9 Oct 2005 04:18:17 -0000       1.7.2.4 
+++ if_nve.c    27 Oct 2005 09:58:45 -0000 
@@ -727,7 +727,7 @@ 

DEBUGOUT(NVE_DEBUG_INIT, "nve: nve_init_rings - entryn"); 

-       sc->cur_rx = sc->cur_tx = sc->pending_rxs = sc->pending_txs = 0; 
+       sc->cur_rx = sc->cur_tx = sc->pending_rxs = 0; 
/* Initialise RX ring */ 
for (i = 0; i < RX_RING_SIZE; i++) { 
struct nve_rx_desc *desc = sc->rx_desc + i; 



Responsible-Changed-From-To: freebsd-amd64->obrien 
Responsible-Changed-By: andreas 
Responsible-Changed-When: Thu Oct 27 11:06:34 GMT 2005 
Responsible-Changed-Why:  
obrien is author of driver according to source 

http://www.freebsd.org/cgi/query-pr.cgi?pr=84027 
State-Changed-From-To: analyzed->feedback 
State-Changed-By: andreas 
State-Changed-When: Thu Oct 27 11:08:52 GMT 2005 
State-Changed-Why:  
waiting for feedback 

http://www.freebsd.org/cgi/query-pr.cgi?pr=84027 
State-Changed-From-To: feedback->open 
State-Changed-By: andreas 
State-Changed-When: Thu Oct 27 16:33:23 GMT 2005 
State-Changed-Why:  
Q referred to fix something in nv_stop() 
But this already is fixed. 
My wrong understanding from his patch suggestion lead to a bogus patch. 
I found the variable in the wrogn function as well and changed something 
in the ringbuffer initialization which was not intended by Q. 
Forget about my patch. It didn't work anyway. 
So the issue is still open. 
Thanks David for pointing that out. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=84027 
State-Changed-From-To: open->feedback 
State-Changed-By: yongari 
State-Changed-When: Tue Aug 23 20:26:41 UTC 2011 
State-Changed-Why:  
Use of nve(4) is not recommended any more. nfe(4) should support 
all NVIDIA ethernet controllers.  Doesn't nfe(4) support your 
controller? If yes, please submit full dmesg output. 
If nfe(4) supports this controller I believe there is no reason to 
leave PR open since nfe(4) replaced nve(4) long time ago. 


Responsible-Changed-From-To: obrien->yongari 
Responsible-Changed-By: yongari 
Responsible-Changed-When: Tue Aug 23 20:26:41 UTC 2011 
Responsible-Changed-Why:  
Take.  It's time to nuke nve(4). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=84027 
State-Changed-From-To: feedback->closed 
State-Changed-By: yongari 
State-Changed-When: Tue Aug 23 20:30:26 UTC 2011 
State-Changed-Why:  
Close, mail bounced. 
If nfe(4) does not support your controller, please open a new PR.  

http://www.freebsd.org/cgi/query-pr.cgi?pr=84027 
>Unformatted:
