From owner-freebsd-current@FreeBSD.ORG Fri Mar 7 23:11:16 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1A341065673; Fri, 7 Mar 2008 23:11:16 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from virtual.micronet.sk (smtp.micronet.sk [84.16.32.237]) by mx1.freebsd.org (Postfix) with ESMTP id 5704E8FC28; Fri, 7 Mar 2008 23:11:16 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by virtual.micronet.sk (Postfix) with ESMTP id 9AE9010EBB1; Sat, 8 Mar 2008 00:10:00 +0100 (CET) X-Virus-Scanned: by amavisd-new at virtual.micronet.sk Received: from virtual.micronet.sk ([127.0.0.1]) by localhost (virtual.micronet.sk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4rFXJ462DKWU; Sat, 8 Mar 2008 00:09:59 +0100 (CET) Received: from DANGER-PC (danger.mcrn.sk [84.16.37.254]) by virtual.micronet.sk (Postfix) with ESMTP id 3D6EE10EBB0; Sat, 8 Mar 2008 00:09:58 +0100 (CET) Date: Sat, 8 Mar 2008 00:11:03 +0100 From: Daniel Gerzo X-Mailer: The Bat! (v3.99.3) Professional Organization: The FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1373272150.20080308001103@rulez.sk> To: Pyun YongHyeon In-Reply-To: <20080307043815.GA92464@cdnetworks.co.kr> References: <20080306200532.GA84961@cvsup.sk.freebsd.org> <20080307043815.GA92464@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Daniel Gerzo , current@FreeBSD.org, yongari@FreeBSD.org Subject: Re[2]: re(4) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Gerzo List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2008 23:11:16 -0000 Hello Pyun, Friday, March 7, 2008, 5:38:15 AM, you wrote: > I guess your issue is not related with bus_dma fixes but improper > handling of link state. Try attached patch and let me know how it > goes. The attached patch didn't help, the box is again in the same status. Can I provide you with some more detailed debugging info, or do you have some other ideas what could be fixed? I could probably manage a remote access to that box, but no remote console is available, and I don't know exactly how to trigger this scenario, but I think it depends on the amount of traffic being sent over the device. -- Best regards, Daniel mailto:danger@FreeBSD.org