From owner-freebsd-stable@FreeBSD.ORG Fri Aug 2 12:55:05 2013 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 7C6A2DA9 for ; Fri, 2 Aug 2013 12:55:05 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (unknown [IPv6:2001:470:8:162::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4F5992584 for ; Fri, 2 Aug 2013 12:55:05 +0000 (UTC) Received: from gjp by mail.in-addr.com with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1V5Esm-000FO4-GM; Fri, 02 Aug 2013 08:55:00 -0400 Date: Fri, 2 Aug 2013 08:54:59 -0400 From: Gary Palmer To: Mike Tancsa Subject: Re: Listen queue overflow Message-ID: <20130802125459.GA52064@in-addr.com> References: <51FA750C.50502@sentex.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51FA750C.50502@sentex.net> X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false Cc: FreeBSD-STABLE Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Aug 2013 12:55:05 -0000 On Thu, Aug 01, 2013 at 10:47:40AM -0400, Mike Tancsa wrote: > After upgrading from a RELENG9 kernel from June 18th to July 27th, I am > seeing this odd new message. Is this a new bug, or just a new > diagnostic message ? I am guessing it happened after r253035 ? > > > sonewconn: pcb 0xfffffe001ac76930: Listen queue overflow: 8 already in > queue awaiting acceptance > sonewconn: pcb 0xfffffe001ac76930: Listen queue overflow: 8 already in > queue awaiting acceptance > sonewconn: pcb 0xfffffe001ac76930: Listen queue overflow: 8 already in > queue awaiting acceptance > sonewconn: pcb 0xfffffe001ac76930: Listen queue overflow: 8 already in > queue awaiting acceptance > sonewconn: pcb 0xfffffe001ac76930: Listen queue overflow: 8 already in > queue awaiting acceptance > sonewconn: pcb 0xfffffe001ac76930: Listen queue overflow: 8 already in > queue awaiting acceptance If you run netstat -naA | grep fffffe001ac76930 you should be able to identify which socket is producing the warning messages. That should give you a better understanding of what is triggering the messages Regards, Gary