From owner-freebsd-net@FreeBSD.ORG Sat Oct 21 16:58:47 2006 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F4B116A407 for ; Sat, 21 Oct 2006 16:58:47 +0000 (UTC) (envelope-from net@dino.sk) Received: from bsd.dino.sk (bsd.dino.sk [213.215.72.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53FA043D64 for ; Sat, 21 Oct 2006 16:58:45 +0000 (GMT) (envelope-from net@dino.sk) Received: from [192.168.16.241] (home.dino.sk [84.245.95.252]) (AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by bsd.dino.sk with esmtp; Sat, 21 Oct 2006 19:07:12 +0200 id 00000030.453A53C0.0000CFF7 From: Milan Obuch To: freebsd-net@freebsd.org Date: Sat, 21 Oct 2006 18:58:29 +0200 User-Agent: KMail/1.9.4 References: <200610211618.11472.net@dino.sk> <20061021162630.I2879@fledge.watson.org> In-Reply-To: <20061021162630.I2879@fledge.watson.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610211858.30338.net@dino.sk> Subject: Re: Somewhat weird net behavior X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Oct 2006 16:58:47 -0000 On Saturday 21 October 2006 17:28, Robert Watson wrote: > On Sat, 21 Oct 2006, Milan Obuch wrote: > > I know this is really minimum information here, but I need just an idea > > what to look for. It is strange for me - is it some memory leak? How > > could it be cleared with simple ifconfig up? Did anyone seen something > > similar? > > It is pretty minimal information :-). > Agreed. I need some help in my investigation. I have no ide what to look for. > ifconfig down / up will cause the device driver to be reset, the link to be > re-negotiated, etc. The buffer full error from ping means that the > outbound interface queue has filled, and if the error doesn't go away, it > means it's likely wedged (no longer being processed). This could reflect a > bug in the device driver, a problem with the switch, etc. In the "wedged" > state, what does ifconfig report about link negotiation? When you reset > the interface, does the negotiated link type change? > I did only ifconfig up, not down/up sequence. That's a bit weird for me. Anyway, on next ocasion, I will do ifconfig before/after ifconfig up. Could there be some interesting information in some netstat output too? It happens once - twice a week, so I would rather be a bit prepared beforehand. Thanks for help. Regards, Milan -- This address is used only for mailing list response. Do not send any personal messages to it.