Date: Mon, 25 Jul 2005 01:04:06 GMT From: meka <meka@softhome.net> To: freebsd-gnats-submit@FreeBSD.org Subject: amd64/84027: if_nve gets stuck Message-ID: <200507250104.j6P146Aw002737@www.freebsd.org> Resent-Message-ID: <200507250110.j6P1AKO9015715@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 84027
>Category: amd64
>Synopsis: if_nve gets stuck
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-amd64
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Jul 25 01:10:19 GMT 2005
>Closed-Date:
>Last-Modified:
>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:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200507250104.j6P146Aw002737>