From owner-freebsd-net@FreeBSD.ORG Wed Feb 28 15:08:26 2007 Return-Path: X-Original-To: freebsd-net@FreeBSD.org Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 56BEC16A400 for ; Wed, 28 Feb 2007 15:08:26 +0000 (UTC) (envelope-from _pppp@mail.ru) Received: from f21.mail.ru (f21.mail.ru [194.67.57.54]) by mx1.freebsd.org (Postfix) with ESMTP id 120F113C4CC for ; Wed, 28 Feb 2007 15:08:26 +0000 (UTC) (envelope-from _pppp@mail.ru) Received: from mail by f21.mail.ru with local id 1HMQPl-0005hz-00; Wed, 28 Feb 2007 18:08:21 +0300 Received: from [81.200.14.42] by koi.mail.ru with HTTP; Wed, 28 Feb 2007 18:08:21 +0300 From: dima <_pppp@mail.ru> To: Gleb Smirnoff Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [81.200.14.42] Date: Wed, 28 Feb 2007 18:08:21 +0300 In-Reply-To: <20070228122459.GK1621@FreeBSD.org> References: <20070228122459.GK1621@FreeBSD.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: Cc: freebsd-net@FreeBSD.org Subject: Re[2]: is CARP still impossible on SMP in 6.2? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dima <_pppp@mail.ru> List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 15:08:26 -0000 > On Wed, Feb 28, 2007 at 02:28:13PM +0300, dima wrote: > d> I'm trying to make CARP working on a 2-Xeon hardware. It worked OK on 5.5, but not on 6.2. > d> The result of compiling both > d> options SMP > d> device carp > d> into the kernel makes it crash in 'swi1: net' kernel thread on a random (usually first) use of the CARP facility. > > Can you please provide a backtrace? It's not that easy. The server becomes extremely unstable under these conditions. I tried to build the kernel with '-g' option and included 'dumpdev' in /etc/rc.conf. The server can't even make a memory dump: it either gets one more page fault or just stops responding to anything but Reset key in the beginning of the dump. It's strange since it rebooted well while the kernel was built without debugging symbols and a dumpdev. Any ideas how I can make a memory dump?