From owner-freebsd-net@FreeBSD.ORG Sun Feb 20 02:40: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 D9FE9106564A; Sun, 20 Feb 2011 02:40:09 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 78BEB8FC08; Sun, 20 Feb 2011 02:40:09 +0000 (UTC) Received: by vxa40 with SMTP id 40so2805907vxa.13 for ; Sat, 19 Feb 2011 18:40: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=3LwggtY88fi/XzOy000iC9l5qKGTjuw7dEDUk2DzSG0=; b=DMrBhZizShYrWav5qGW3JL6Wv2N0Mq/tg6JLAMcxOQvxnkn5YwtOagag8EOveYTlKq CvNEkLEVFlFeY86xPcFyJcRV8MlIyjebAivAdU2OTTeLBGvyYFUV8U/O31HHI1ExadzY FiIpn6HA3tEB0BKqV2KtnkCEAzxwWAk3PD1zg= 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=UDnUA/ho1RACWn71+4YqwWmzosfjSZv6d6XXGCxHHIhsHiq7833ARa8kFaurbE3M1f TWeRbGzoBRo4olltQyUJQEkBDnWzrHwKlhvwApCjvB9zX8Fwz2k09zgWwZys3sjFcTAF 00CtuLY0JCvcwkxAq6lp9Y3C8x2tedRgTMLbM= MIME-Version: 1.0 Received: by 10.52.165.136 with SMTP id yy8mr3951665vdb.68.1298169608385; Sat, 19 Feb 2011 18:40:08 -0800 (PST) Received: by 10.52.160.5 with HTTP; Sat, 19 Feb 2011 18:40:08 -0800 (PST) In-Reply-To: References: <410175608.20110220013900@nitronet.pl> Date: Sat, 19 Feb 2011 18:40:08 -0800 Message-ID: From: Jack Vogel To: Brandon Gooch Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Pawel Tyll , freebsd-net@freebsd.org, Luigi Rizzo , freebsd-ipfw@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:40:09 -0000 I've never seen a trace like this, and no absolutely nothing about dummynet, sorry. If it is in some way em's fault, then making sure you have the latest code would be a good idea. I have a test driver that is under selective test, it does effect the code path that you seem to be in, so it might be worth a try. If you want to try it early just pipe up and I'll send it. Jack On Sat, Feb 19, 2011 at 6:16 PM, Brandon Gooch wrote: > 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 >