Date: Fri, 23 Jan 2015 10:58:08 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Dmitry Sivachenko <trtrmitya@gmail.com> Cc: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: network locks up with udp traffic Message-ID: <CAJ-Vmo=v5S=cRM3QPo0mGiNS8OS8so=915vx6R1fhDaKWS6BhQ@mail.gmail.com> In-Reply-To: <5B08402C-67A7-49E7-ADF8-390C94DCF1D7@gmail.com> References: <5B08402C-67A7-49E7-ADF8-390C94DCF1D7@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, When this next happens, please do this as root: procstat -ka That'll hopefully provide enough information to figure out which processes are blocking where and how they got there. -a On 23 January 2015 at 06:27, Dmitry Sivachenko <trtrmitya@gmail.com> wrote: > Hello! > > I am using FreeBSD-10/stable. We have a program at work that transmits data via UDP. > When I run several instances of this program simultaneously, after a few seconds network stops working. > If I login from console, I see some network daemons like ntpd, snmpd are in "*udp" state. > > If I try to deal with network interface (ifconfig igb0 for instance), ifconfig utility stuck in "L" state (Marks a process that is waiting to acquire a lock.). > I found the only way to fix that: reboot. > > What can be the cause for such a behaviour? > > Thanks. > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=v5S=cRM3QPo0mGiNS8OS8so=915vx6R1fhDaKWS6BhQ>