From owner-freebsd-net@FreeBSD.ORG Sat Jan 24 17:29:45 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 17214B7A for ; Sat, 24 Jan 2015 17:29:45 +0000 (UTC) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D0D8497F for ; Sat, 24 Jan 2015 17:29:44 +0000 (UTC) Received: by mail-ig0-f174.google.com with SMTP id b16so2442820igk.1 for ; Sat, 24 Jan 2015 09:29:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=s9C1nUE/AqZwuylWON3SkaVJqquOtJiFsIRyKpUa3u4=; b=jxlOkmUZxnu5dDp/JKBEnPTdM/H1AQzfQM9oI9ULZijpR+G6HEKHoqSmX2jf3CXuao b0hlmEvb2gKvhV9dkRPwh1b1rwRo90BPqLPe1lPO+kPL3BjL/doyDZVIQH+SbYT60tZp S3po2JsmaHRVUAXwgiuDzWWTHUj54RrNZIBxbkdg0Gy1CYp5D+V2zQN56gxiJJn5kyvd qhrx4tpt7RkYJXU1SQUn0jzrFpfto3z8rCKTvnSyCs28hPMiloN90Ls6qgc+C8uIa1Yc R2VzEDECVmt8F1kpg1oQPFsMnjr9zGfl887wh+f+pDB52PmLp0WX+a5pJtj9v1KJjadx ljGQ== MIME-Version: 1.0 X-Received: by 10.50.164.227 with SMTP id yt3mr8240227igb.32.1422120584187; Sat, 24 Jan 2015 09:29:44 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.36.78.14 with HTTP; Sat, 24 Jan 2015 09:29:44 -0800 (PST) In-Reply-To: References: <5B08402C-67A7-49E7-ADF8-390C94DCF1D7@gmail.com> Date: Sat, 24 Jan 2015 09:29:44 -0800 X-Google-Sender-Auth: v-QuFU8mAQ1Ivzk7csoK5Wsx9zY Message-ID: Subject: Re: network locks up with udp traffic From: Adrian Chadd To: Dmitry Sivachenko Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Net X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 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, 24 Jan 2015 17:29:45 -0000 Hi, Can you compile your kernel with WITNESS and repeat this test? It looks like it's stuck in some lock ordering thing between some UDP paths and an inpcb lookup. It should log in dmesg the first time a LOR occurs, regardless of whether it actively causes a hang. (And yes, this is definitely critical enough to be a FreeBSD PR... :) Thanks! -adrian On 24 January 2015 at 02:14, Dmitry Sivachenko wrote: > >> On 23 =D1=8F=D0=BD=D0=B2. 2015 =D0=B3., at 21:58, Adrian Chadd wrote: >> >> 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. >> >> > > > Hello, > > I am attaching procstat -ka output (and top output to see snmpd process i= n "*udp" state). > ifconfig process was started with "net0" argument (net0 is a renamed igb0= in my case). >