Date: Wed, 24 Oct 2007 11:00:55 GMT From: Hans Middelhoek <freebsd@ospito.nl> To: freebsd-gnats-submit@FreeBSD.org Subject: i386/117448: [CARP] 6.2 kernel crash Message-ID: <200710241100.l9OB0t6c007307@www.freebsd.org> Resent-Message-ID: <200710241110.l9OBA2eB039450@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 117448 >Category: i386 >Synopsis: [CARP] 6.2 kernel crash >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Wed Oct 24 11:10:02 UTC 2007 >Closed-Date: >Last-Modified: >Originator: Hans Middelhoek >Release: 6.2 with all patchlevels >Organization: >Environment: FreeBSD server01.domain.tld 6.2-RELEASE-p8 FreeBSD 6.2-RELEASE-p8 #11: Fri Oct 19 15:14:49 CEST 2007 username@server01.domain.tld:/usr/obj/usr/src/sys/CUSTOMERNAME-SMP-PAE i386 >Description: Two servers are configured for failover using CARP. Originally this is configured with FreeBSD 6.0 and all kernel updates went fine, till we moved to 6.2. System hangs after it's started within an unpredictable time, sometimes within 30 seconds, after a reboot it sometimes takes over 2 minutes. Although it seems a problem when the servers are negotiating about the owner of an IP-address. The problem can be forced with the following command: ifconfig carp2 destroy. CARP interfaces are setup from within the /etc/rc.conf cloned_interfaces="carp2 carp3" ifconfig_carp2="vhid 3 pass XXXXXXX xx.xx.xx.xx netmask 255.255.255.0 advskew 100" ifconfig_carp3="vhid 4 pass YYYYYYY xx.xx.xx.xx netmask 255.255.255.0" The system isn't accessible after the crash, a hard reboot is necessary. I couldn't find any fix for this except not using CARP... The problem exists with all patchlevels in 6.2 version. I also tried building a default kernel, without PAE, no solution. To fix this temporarily I've build the newest 6.1 kernel and the problem is solved. ifconfig carp2 destroy is working without any problem. >How-To-Repeat: Configure CARP interfaces with /etc/rc.conf and activate them. Just one system is enough to repeat the problem. After the CARP interfaces are up the problem will occur automatically, or force it with ifconfig carp2 destroy >Fix: Bugreport 92776 - http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/92776 looks like the same, but patching the kernel manually doesn't sound like a solution, also that problem persists in 6.0 and our problem doesn't. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200710241100.l9OB0t6c007307>