From owner-freebsd-net@FreeBSD.ORG Fri Feb 1 14:30:03 2008 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5C6916A46E for ; Fri, 1 Feb 2008 14:30:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B6E6113C4D5 for ; Fri, 1 Feb 2008 14:30:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m11EU3Cf095450 for ; Fri, 1 Feb 2008 14:30:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m11EU3VT095447; Fri, 1 Feb 2008 14:30:03 GMT (envelope-from gnats) Date: Fri, 1 Feb 2008 14:30:03 GMT Message-Id: <200802011430.m11EU3VT095447@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Gleb Smirnoff Cc: Subject: Re: kern/120130: carp causes kernel panics in any constellation X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Gleb Smirnoff List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2008 14:30:03 -0000 The following reply was made to PR kern/120130; it has been noted by GNATS. From: Gleb Smirnoff To: Christoph Weber-Fahr Cc: bug-followup@FreeBSD.org Subject: Re: kern/120130: carp causes kernel panics in any constellation Date: Fri, 1 Feb 2008 17:04:45 +0300 Christoph, > 2.) is is alsow possible to have a crash using only one crap interface. We > found the following script to reliably produce a kernel panic within > 15-20 minutes: > > while [ 1 ] > do > /etc/rc.d/netif restart > sleep 35 > ifconfig carp0 destroy > sleep 35 > done This reproduce recipe will be complete only if you give configuration of network interface in rc.conf. Can you supply this information, please? Also, have you tried to produce kernel coredump or at least backtrace, when kernel panics? -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE