From owner-freebsd-current Sun Nov 9 11:08:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA28688 for current-outgoing; Sun, 9 Nov 1997 11:08:29 -0800 (PST) (envelope-from owner-freebsd-current) Received: from bagpuss.visint.co.uk (bagpuss.visint.co.uk [194.207.134.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28680 for ; Sun, 9 Nov 1997 11:08:24 -0800 (PST) (envelope-from steve@visint.co.uk) Received: from dylan.visint.co.uk (dylan.visint.co.uk [194.207.134.180]) by bagpuss.visint.co.uk (8.7.5/8.7.3) with SMTP id TAA24229 for ; Sun, 9 Nov 1997 19:08:22 GMT Date: Sun, 9 Nov 1997 19:08:21 +0000 (GMT) From: Stephen Roome To: freebsd-current@freebsd.org Subject: Current with SMP and netatalk panics. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Just got current about an hour ago and recompiled netatalk-1.4b2 with the patch from the netatalk site for current (freebsd3.diff). First time I ran atalkd it went okay, so -stupidly- I turned it on in startup and... oops, I get something like this on bootup now... SMP: I'm on cpu1 I need to be on cpu0. timeout getting cpu0 This seems to be happening when afpd starts up, not sure what's going on here as, I've got atalkd to start again, but as soon as I try to run afpd it goes and crashes again. It's refreshing though as I'm normally stuck with atalkd refusing to add multicast addresses rather than afpd crashing. Steve. -- Steve Roome - Vision Interactive Ltd. Tel:+44(0)117 9730597 Home:+44(0)976 241342 WWW: http://dylan.visint.co.uk/