From owner-freebsd-current@FreeBSD.ORG Thu Nov 27 19:30:58 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DC45816A4CE for ; Thu, 27 Nov 2003 19:30:58 -0800 (PST) Received: from siralan.org (12-223-227-231.client.insightbb.com [12.223.227.231]) by mx1.FreeBSD.org (Postfix) with ESMTP id 188DE43FE9 for ; Thu, 27 Nov 2003 19:30:57 -0800 (PST) (envelope-from mikes@siralan.org) Received: from siralan.org (localhost [127.0.0.1]) by siralan.org (8.12.10/8.12.10) with ESMTP id hAS3Uiss001828; Thu, 27 Nov 2003 22:30:44 -0500 (EST) (envelope-from mikes@siralan.org) Received: (from mikes@localhost) by siralan.org (8.12.10/8.12.10/Submit) id hAS3UcNF001827; Thu, 27 Nov 2003 22:30:38 -0500 (EST) (envelope-from mikes) From: "Michael L. Squires" Message-Id: <200311280330.hAS3UcNF001827@siralan.org> To: sam@errno.com (Sam Leffler) Date: Thu, 27 Nov 2003 22:30:38 -0500 (EST) In-Reply-To: <200311261451.23521.sam@errno.com> from "Sam Leffler" at Nov 26, 2003 02:51:23 PM X-Mailer: ELM [version 2.5 PL6] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: Leo Bicknell cc: FreeBSD current mailing list Subject: Re: 5.2-BETA + netatalk = crash X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Nov 2003 03:30:59 -0000 Sam Leffler > > > > On Wednesday 26 November 2003 06:51 am, Michael L. Squires wrote: > > > > On my dual CPU P6DGH the 11/22 cvsup of 5.2-BETA and netatalk crashes > > > > on boot. Stopping netatalk from starting stops the crash. > > > > > > > > I wasn't able to catch any crash information, but am currently > > > > recompiling with sources from last night to see if it's repeatable. > > > > > > Please try the attached patch, it should fix at least one problem in the > > > netatalk code (Leo this should fix the panics you've seen during > > > shutdown). Michael, hopefully this will also fix your problem--whatever > > > it is. The patch certainly fixes the panic, thanks. I'm running a make buildworla, etc., on my notebook which NFS mounts the box running netatalk, which should trigger the IPv4 bug if I have it. Mike Squires