Date: Thu, 3 Oct 2013 12:54:56 -0400 From: Ryan Stone <rysto32@gmail.com> To: Tugrul Erdogan <h.tugrul.erdogan@gmail.com> Cc: freebsd-net <freebsd-net@freebsd.org> Subject: Re: The reason of "ping: sendto: No buffer space available" and link_irq variable Message-ID: <CAFMmRNzU3Q7%2BiWzsT1ZCSixg%2BZ4muAPqSCj-fi9guoDiuP_KqA@mail.gmail.com> In-Reply-To: <CA%2Bwhn7TWm=WHxhNjVZzXC0hd3ZV4menhrYccy%2Bv-bYHBkxo6qw@mail.gmail.com> References: <CA%2Bwhn7TWm=WHxhNjVZzXC0hd3ZV4menhrYccy%2Bv-bYHBkxo6qw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Oct 3, 2013 at 11:42 AM, Tugrul Erdogan <h.tugrul.erdogan@gmail.com> wrote: > Hi, > > I am using FreeBSD alpha2 amd64 on my router and after packet loaded test > attack I am taking > "ping: sendto: No buffer space available" error when running ping from > router to victim directoion. The nic is "Intel 82599EB". Whenever this > problem began to show, I can track the packages by tcpdump but I think the > packages can not be created physically when they are reached physical > layer. Doing the nic down/up can not be solved the problem. > > When I testing I have found the "dev.ix.0.link_irq" value is increased very > differently from other nic's link_irq values. So after assigning the value > of 2 to this link_irq variable the problem solved. > > I want to your help at two path; firstly why should I take this error. > Secondly what is the role of the link_irq variable, what is the situations > which are trigger to increase the link_irq variable and is the real reason > of this problem the link_irq variable or anything else under this > mechanism? > > Thanks and best regards, dev.ix.0.link_irq is not supposed to be a writeable sysctl. It is a read-only sysctl that reflects the number of times that the hardware informed the driver (through an interrupt, or irq) that the state of the link changed. If you are seeing this increase then something is causing the NIC to lose link momentarily. I would recommend checking for things like dirty fibre, bad cables, failing optics (SFP+), etc. Check on both ends of the link.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNzU3Q7%2BiWzsT1ZCSixg%2BZ4muAPqSCj-fi9guoDiuP_KqA>