From owner-freebsd-bugs@FreeBSD.ORG Fri Sep 22 18:20:26 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC6F816A40F for ; Fri, 22 Sep 2006 18:20:26 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E70C43D5D for ; Fri, 22 Sep 2006 18:20:21 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8MIKLhY016635 for ; Fri, 22 Sep 2006 18:20:21 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8MIKLG1016634; Fri, 22 Sep 2006 18:20:21 GMT (envelope-from gnats) Resent-Date: Fri, 22 Sep 2006 18:20:21 GMT Resent-Message-Id: <200609221820.k8MIKLG1016634@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Mij Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86F1B16A52F for ; Fri, 22 Sep 2006 18:17:41 +0000 (UTC) (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 331DB43D5D for ; Fri, 22 Sep 2006 18:17:35 +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 k8MIHZ5c058297 for ; Fri, 22 Sep 2006 18:17:35 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.13.1/8.13.1/Submit) id k8MIHZCW058296; Fri, 22 Sep 2006 18:17:35 GMT (envelope-from nobody) Message-Id: <200609221817.k8MIHZCW058296@www.freebsd.org> Date: Fri, 22 Sep 2006 18:17:35 GMT From: Mij To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Cc: Subject: kern/103495: if_vr locks after carrier event X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Sep 2006 18:20:26 -0000 >Number: 103495 >Category: kern >Synopsis: if_vr locks after carrier event >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Sep 22 18:20:20 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Mij >Release: FreeBSD 6.2-PRERELEASE i386 >Organization: >Environment: System: FreeBSD lamehost 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #2: Sat Sep 16 14:42:39 CEST 2006 xyz@lamehost:/usr/obj/usr/src/sys/ck i386 >Description: The if_vr driver for VIA Rhine I and II stops processing both incoming and outgoing traffic after the following event vr0: link state changed to DOWN vr0: link state changed to UP (possibly repeated a few times) making the interface unusable reliably. A similar report is in PR kern/100499, but this amendment has to be specified wrt to it: no shutdown is required for having the driver handle traffic again. Conversely, the following is sufficient: # ifconfig vr0 down # ifconfig vr0 up this makes the driver run vr_reset(), after which the interface behaves correctly again. The linux driver via-rhine.c currently does not feature this behaviour and could be source of inspiration. >How-To-Repeat: initialize vr interface; unplug the cable off of the interface, physically; replug the cable into the interface >Fix: >Release-Note: >Audit-Trail: >Unformatted: