From owner-freebsd-stable Sun Sep 5 20:52:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 4225115894 for ; Sun, 5 Sep 1999 20:52:12 -0700 (PDT) (envelope-from paul@elvis.mu.org) Received: (from paul@localhost) by elvis.mu.org (8.9.1/8.9.1) id WAA77087 for stable@freebsd.org; Sun, 5 Sep 1999 22:51:04 -0500 (CDT) (envelope-from paul) Date: Sun, 5 Sep 1999 22:51:04 -0500 From: Paul Saab To: stable@freebsd.org Subject: Re: analyzing a crash of 3.2-RELEASE Message-ID: <19990905225104.A76960@elvis.mu.org> References: <199909050509.WAA02378@implode.root.com> <199909050623.XAA09791@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <199909050623.XAA09791@dingo.cdrom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm testing disabling PMTUD now, but I can't simulate the same load I got the panic on until Tuesday, when we really see high traffic utilization. If I stil panic, I'll patch radix.c and see what happens from there. paul Mike Smith (mike@smith.net.au) wrote: > > >This looks like a race in the route handling code that was fixed a > > >while back; you can either disable path MTU discovery (which prevents > > >the massive routing table growth that you may also see in your > > >application) or update to 3.2-stable in which I _believe_ that this has > > > > Why would disabling PMTUD have any affect on that? The clone routes should > > still be created just as before. > > They should? It was my understanding that the clone routes were only > created in order to hold the PMTU information as required. > > If not, then I guess we still have a race somewhere in the route > manipulation code, unless this is fixed as a side-effect of rev 1.18 of > radix.c. > > -- > \\ The mind's the standard \\ Mike Smith > \\ of the man. \\ msmith@freebsd.org > \\ -- Joseph Merrick \\ msmith@cdrom.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message