From owner-freebsd-current@FreeBSD.ORG Sat Mar 8 16:07:23 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 98C521065677; Sat, 8 Mar 2008 16:07:23 +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 4B81F8FC1A; Sat, 8 Mar 2008 16:07:22 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by virtual.micronet.sk (Postfix) with ESMTP id F143F10E934; Sat, 8 Mar 2008 17:06:07 +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 zBrfww1HGAOW; Sat, 8 Mar 2008 17:06:06 +0100 (CET) Received: from DANGER-PC (danger.mcrn.sk [84.16.37.254]) by virtual.micronet.sk (Postfix) with ESMTP id 85DBA10E8A8; Sat, 8 Mar 2008 17:06:06 +0100 (CET) Date: Sat, 8 Mar 2008 17:07:10 +0100 From: Daniel Gerzo X-Mailer: The Bat! (v3.99.3) Professional Organization: The FreeBSD Project X-Priority: 3 (Normal) Message-ID: <918167276.20080308170710@rulez.sk> To: Daniel Gerzo In-Reply-To: <1373272150.20080308001103@rulez.sk> References: <20080306200532.GA84961@cvsup.sk.freebsd.org> <20080307043815.GA92464@cdnetworks.co.kr> <1373272150.20080308001103@rulez.sk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Pyun YongHyeon , current@FreeBSD.org, yongari@FreeBSD.org Subject: Re[3]: 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: Sat, 08 Mar 2008 16:07:23 -0000 Hello, Saturday, March 8, 2008, 12:11:03 AM, has been written: > 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. If I won't hear from anybody in next 24 hours, I will have to replace the network device in this box, in order to get it running properly. However, I don't consider this step as a right solution and I would rather better like to have it fixed in the driver. Thanks. -- Best regards, Daniel mailto:danger@FreeBSD.org