From owner-freebsd-current@FreeBSD.ORG Wed Nov 15 09:38: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 6C29C16A49E; Wed, 15 Nov 2006 09:38:29 +0000 (UTC) (envelope-from if@hetzner.co.za) Received: from mail1a.your-server.co.za (mail1a.your-server.co.za [196.7.18.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id B745343D8A; Wed, 15 Nov 2006 09:35:54 +0000 (GMT) (envelope-from if@hetzner.co.za) Received: from [192.168.2.25] (helo=hetzner.co.za) by mail1a.your-server.co.za with esmtpa (Exim 4.63) (envelope-from ) id 1GkHBM-0000nf-Es; Wed, 15 Nov 2006 11:35:48 +0200 Received: from localhost ([127.0.0.1]) by hetzner.co.za with esmtp (Exim 4.63 (FreeBSD)) (envelope-from ) id 1GkHBL-0000vU-88; Wed, 15 Nov 2006 11:35:47 +0200 To: Robert Watson From: Ian FREISLICH In-Reply-To: Message from Robert Watson of "Wed, 15 Nov 2006 09:03:28 GMT." <20061115085427.R79655@fledge.watson.org> X-Attribution: BOFH Date: Wed, 15 Nov 2006 11:35:47 +0200 Message-Id: X-Authenticated-Sender: if@hetzner.co.za X-Virus-Scanned: Clear (ClamAV 0.88.4/2195/Tue Nov 14 21:53:04 2006) 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:38:29 -0000 Robert Watson wrote: > 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. Which is what I'm beginning to suspect. For a long time the CARP driver was broken in -CURRENT. IIRC commits to ipcarp.c (1.41, 1.42 maymbe a few more) around June/July this year by Sam and Max fixed CARP interfaces, but they have subsequently fallen into disrepair. I don't have the knowledge to debug this further. I do have a crashdump for further inspection though. Ian -- Ian Freislich