From owner-freebsd-current@FreeBSD.ORG Wed Nov 15 09:03:29 2006 Return-Path: X-Original-To: current@freebsd.org 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 89A6816A40F for ; Wed, 15 Nov 2006 09:03:29 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4455043D4C for ; Wed, 15 Nov 2006 09:03:29 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id DC68546B46; Wed, 15 Nov 2006 04:03:28 -0500 (EST) Date: Wed, 15 Nov 2006 09:03:28 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Ian FREISLICH In-Reply-To: Message-ID: <20061115085427.R79655@fledge.watson.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: Panic during boot (in_arpinput). X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 15 Nov 2006 09:03:29 -0000 On Wed, 15 Nov 2006, Ian FREISLICH wrote: > Robert Watson wrote: >> On Wed, 15 Nov 2006, Ian FREISLICH wrote: >> >>> Ian FREISLICH wrote: >>>> >>>> I have 2 servers each with 255 vlan interfaces and carp interfaces in >>>> each vlan.During the boot up while it's configuring the interfaces, it >>>> reliably panics. It boots fine if no network cables are plugged in (and >>>> in the test evironment on a quient lan). >>>> >>>> It's an SMP machine. My guess (from the panic message below) is that an >>>> arp query arives on an interface it's in the middle of creating or >>>> something like that (highly unsophisticated debugging conjecture). >>>> >>>> In the mean time I'm going to try a UP kernel and see if that masks the >>>> problem. >>> >>> FWIW, a UP kernel has the same problem. >> >> What happens if you disable PREEMPTION on UP and try the same thing again? > > Same thing. > > If I don't assign the carp interfaces a vhid and pass at boot time, it boots > up OK, but I need the carp interfaces. I can arrange serial console access. > I have a similar system from ~"Tue Aug 29 09:47:50 SAST 2006" that works, > but I suspect it may suffer the same problem. I'm about to test this. This suggests that it is not the race I was worried it was, which is really good news :-). This makes me suspect a CARP-specific bug as opposed to the wider issue of under-synchronization of the address lists. Robert N M Watson Computer Laboratory University of Cambridge