From owner-freebsd-net@FreeBSD.ORG Sun Feb 20 02:16:09 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB758106564A; Sun, 20 Feb 2011 02:16:09 +0000 (UTC) (envelope-from jamesbrandongooch@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 397AC8FC0A; Sun, 20 Feb 2011 02:16:09 +0000 (UTC) Received: by wyb32 with SMTP id 32so778680wyb.13 for ; Sat, 19 Feb 2011 18:16:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pUjBeBuXNG+Cpy4EH8113mhlvhl74esZ6CcNcmrDn3w=; b=scnPmIi4fMoQ8QUeeVUGYjRcMEodUTpw7bao2Ab44oW5ZfweSYIT8gWaKuog3DKoj7 pSSWSQKRbipQTN/mu/v3Cv6BHp47m7ahlFvElWD1TwcPTXdGkAcFKZsPIoxt+rsG3xh0 Ho7cGMZSXf3LZ1xZDwkZGfDoiemf61QgwDq8U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=uYCsrxKsGdhMkNhc3xuJbAAjN6thI3vaK4fVORExtkj9oBM25TgPrXub0HRZr5GBJu u0W4yn9HssXZHUdIRHi+QStF9srThGeOde6GYDIBac6KbRv7Fakqkie4dWXNWKAOdxEU 4WkAZ6lBx1jG9N7CB/YEG2P3Cpdl+yZPcdJiA= MIME-Version: 1.0 Received: by 10.216.150.129 with SMTP id z1mr1910577wej.113.1298168168046; Sat, 19 Feb 2011 18:16:08 -0800 (PST) Received: by 10.216.244.130 with HTTP; Sat, 19 Feb 2011 18:16:08 -0800 (PST) In-Reply-To: <410175608.20110220013900@nitronet.pl> References: <410175608.20110220013900@nitronet.pl> Date: Sat, 19 Feb 2011 20:16:08 -0600 Message-ID: From: Brandon Gooch To: Pawel Tyll Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-ipfw@freebsd.org, Luigi Rizzo , Jack Vogel , freebsd-net@freebsd.org Subject: Re: [Panic] Dummynet/IPFW related recurring crash. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Feb 2011 02:16:09 -0000 2011/2/19 Pawel Tyll : > Hi guys, lists, > > It's me, the bi-weekly panic guy. Guess what, it crashed today. As an > act of desperation I disabled the pipe dumping script after previous > crash, which today turned out to be merely a coincidence and didn't > prevent panics. (I thought it to be a longshot anyway, but it was the > only change I could associate with beginning of this). The only fix I > could come up with, that's very wrong on so many levels, is... > > 30 1 * * 7 /sbin/shutdown -r +210m "Scheduled weekly reboot." > > :( > > ...but it solves it all: panics, inability to dump (which leads to > freeze and requires manual intervention to bring system back up). Oh > well. > > Since nobody came up with any interest in having this properly > investigated, then I suppose I'm the only one that uses dummynet for > some larger-scale traffic shaping - maybe that's my mistake? What > others are using? Other tools, Linux, proprietary traffic shapers? I > really have trouble writing another sentence in a way that won't make > me look like an arrogant schmuck that feels entitled to free support, > so I'll stop here. Any more ideas/hints what to do next/pointers how > to debug this properly are of course still welcome. Same backtrace as reported here? http://www.freebsd.org/cgi/query-pr.cgi?pr=152360 What revision of the em(4) driver code are you using? I know Jack has been working out certain quirky issues lately, and there have been updates to the code since last you posted an update to your problem. STABLE: http://svn.freebsd.org/viewvc/base?view=revision&revision=217711 RELENG: http://svn.freebsd.org/viewvc/base?view=revision&revision=217865 Maybe Jack could shed some light on the whether the updates could somehow work out to be a fix for your problem -- or whether or not your issue is even related to the em(4) driver. -Brandon