From deischen@freebsd.org  Mon Mar 14 05:58:00 2005
Return-Path: <deischen@freebsd.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6787016A4CE; Mon, 14 Mar 2005 05:58:00 +0000 (GMT)
Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id DF38943D31; Mon, 14 Mar 2005 05:57:59 +0000 (GMT)
	(envelope-from deischen@freebsd.org)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
	by mail.ntplx.net (8.13.3/8.13.3/NETPLEX) with ESMTP id j2E5vwJi015396;
	Mon, 14 Mar 2005 00:57:58 -0500 (EST)
Message-Id: <Pine.GSO.4.43.0503140050290.2753-100000@sea.ntplx.net>
Date: Mon, 14 Mar 2005 00:57:58 -0500 (EST)
From: Daniel Eischen <deischen@freebsd.org>
Reply-To: Daniel Eischen <deischen@freebsd.org>
To: Mario Sergio Fujikawa Ferreira <lioux@freebsd.org>
Cc: FreeBSD-gnats-submit@freebsd.org
In-Reply-To: <20050314015711.71040.qmail@exxodus.fedaykin.here>
Subject: Re: ping: sendto: No buffer space available

>Number:         78804
>Category:       kern
>Synopsis:       Re: ping: sendto: No buffer space available
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar 14 06:00:20 GMT 2005
>Closed-Date:    Tue Mar 15 04:08:21 GMT 2005
>Last-Modified:  Tue Mar 15 04:08:21 GMT 2005
>Originator:     
>Release:        
>Organization:
>Environment:
>Description:
 On 14 Mar 2005, Mario Sergio Fujikawa Ferreira wrote:
 >
 >
 > 	About every 24 hours, I get several
 >
 >  I have been experiencing this
 >
 > $ ping 10.1.1.1
 > PING 10.1.1.1 (10.1.1.1): 56 data bytes
 > ping: sendto: No buffer space available
 > ping: sendto: No buffer space available
 >
 >   Does anyone have any ideas? Doing
 >
 > # ifconfig fxp0 down
 > # ifconfig fxp0 up
 >
 > fixes it but it won't recover otherwise.
 >
 > 	Considering that it might be a bad interaction with APIC,
 > I disabled but it did not do any good.
 >
 > 	Also, I considered some weird fxp(4) IRQ problem but switching
 > PCI slots did not help.
 >
 > >How-To-Repeat:
 >
 > 	I am not sure it will be easy to reproduce in other systems
 > but I have gotten at least one confirmation over email of someone
 > with the same problem and with an fxp(4) as well. I am CC:ing
 > deischen since he had similar complains.
 
 It happens to me on a 4.9 (or so) router box with 5 interfaces.
 4 interfaces are sf and 1 interface is de.  Only on the first
 sf (sf0) interface does this occur and ifconfig up/down does
 indeed fix the problem.
 
 It occurs once every week or two.  All interfaces except sf0
 are connected to switches.  sf0 is connected to a hub.
 
 I believe the previous router box with all de interfaces use
 to exhibit the same behavior (this was a couple or more years
 ago with 3.x, so I can't be too sure).
 
 -- 
 DE
 
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: linimon 
State-Changed-When: Tue Mar 15 04:07:49 GMT 2005 
State-Changed-Why:  
Misfiled followup to kern/78801; content migrated. 


Responsible-Changed-From-To: gnats-admin->freebsd-bugs 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Tue Mar 15 04:07:49 GMT 2005 
Responsible-Changed-Why:  

http://www.freebsd.org/cgi/query-pr.cgi?pr=78804 
>Unformatted:
