From owner-freebsd-i386@FreeBSD.ORG Sat Dec 25 10:40:27 2004 Return-Path: Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 824F516A4CE for ; Sat, 25 Dec 2004 10:40:27 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B24243D2D for ; Sat, 25 Dec 2004 10:40:27 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id iBPAeRx4018473 for ; Sat, 25 Dec 2004 10:40:27 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id iBPAeRjh018472; Sat, 25 Dec 2004 10:40:27 GMT (envelope-from gnats) Date: Sat, 25 Dec 2004 10:40:27 GMT Message-Id: <200412251040.iBPAeRjh018472@freefall.freebsd.org> To: freebsd-i386@FreeBSD.org From: Peter Trifonov Subject: Re: i386/75441: fxp device timeout X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Peter Trifonov List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Dec 2004 10:40:27 -0000 The following reply was made to PR i386/75441; it has been noted by GNATS. From: Peter Trifonov To: freebsd-gnats-submit@FreeBSD.org, petert@dcn.infos.ru Cc: Subject: Re: i386/75441: fxp device timeout Date: Sat, 25 Dec 2004 13:43:04 +0300 After further testing I have found a deterministic way to reproduce the problem. Doing flood ping over both fxp interfaces always causes the system to say "device timeout" on both of them. Moreover, bringing both fxp's down, waiting for a few seconds and bringing them up in most cases fixes the problem.