From owner-freebsd-net@FreeBSD.ORG Thu Mar 24 10:00:05 2011 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A92C9106566C for ; Thu, 24 Mar 2011 10:00:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 87B9B8FC13 for ; Thu, 24 Mar 2011 10:00:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p2OA05Aw069212 for ; Thu, 24 Mar 2011 10:00:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p2OA05It069204; Thu, 24 Mar 2011 10:00:05 GMT (envelope-from gnats) Date: Thu, 24 Mar 2011 10:00:05 GMT Message-Id: <201103241000.p2OA05It069204@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Vladimir Kutakov Cc: Subject: Re: kern/155597: [panic] Kernel panics with "sbdrop" message X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vladimir Kutakov List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Mar 2011 10:00:05 -0000 The following reply was made to PR kern/155597; it has been noted by GNATS. From: Vladimir Kutakov To: bug-followup@FreeBSD.org, vova@ashmanov.com Cc: Subject: Re: kern/155597: [panic] Kernel panics with "sbdrop" message Date: Thu, 24 Mar 2011 12:35:34 +0300 We are looking into this problem a bit. The panic is reproducible easily by means of big http trafic. We ran apache benchmark on 3 next servers: ab -c40 -n20000000 'http://thehost/somesmallfile'. After just some minutes panic occurs. However, after decreasing hw.igb.num_queues to 4 (default value is 8), it occurs only after 2 hours. Finally, the server with hw.igb.num_queues=1 works good already 7 days. It seems that some problem happens during parallel tcp processing. -- WBR, Vladimir mailto:vova@ashmanov.com