From owner-freebsd-current@FreeBSD.ORG Tue May 29 10:26:53 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3458A16A400 for ; Tue, 29 May 2007 10:26:53 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out2.smtp.messagingengine.com (out2.smtp.messagingengine.com [66.111.4.26]) by mx1.freebsd.org (Postfix) with ESMTP id 0D9EE13C45D for ; Tue, 29 May 2007 10:26:52 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 258B7228EFA; Tue, 29 May 2007 06:25:41 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Tue, 29 May 2007 06:25:54 -0400 X-Sasl-enc: YQzyfurb82EI5cQPbamgnFVUyt/tuk3G+zyDHhA0jdqU 1180434341 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 5E30520335; Tue, 29 May 2007 06:25:41 -0400 (EDT) Message-ID: <465BFFA3.300@incunabulum.net> Date: Tue, 29 May 2007 11:25:39 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Ian FREISLICH References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Rudy Rucker Subject: Re: ifconfig carp0 destroy = kernel panic 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: Tue, 29 May 2007 10:26:53 -0000 Ian FREISLICH wrote: > This is just a "mee too". > > I find that after giving a CARP interface an address, it is impossible > to remove the address using ifconfig carp200 delete ... Further > using ifconfig carp200 destroy results in a panic. > I believe that the carp issue should have been resolved for at least a month now. I fixed a similar problem in pfsync. Also, when reporting this kind of issue please provide the full panic message as well as the debugging trace; as well as the date your kernel sources are from, just a reminder that backtraces are useless without context information. I probably won't have time to look at this code for a while, however, it will help other volunteers to diagnose the problem. That said, this particular kind of issue is just symptomatic of deeper issues with the structure of the code. I would prefer to focus on fixing this sort of thing at its source (if I get free cycles to do so), so, I will let someone else step up to the podium this time... Regards, BMS