i386/133218: use of carp(4) causes system to freeze

[Philip Drapeau]

>Number:         133218
>Category:       i386
>Synopsis:       use of carp(4) causes system to freeze
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-i386
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar 30 18:00:08 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     Philip Drapeau
>Release:        7.1-RELEASE-p4
>Organization:
Skysurfer Communications
>Environment:
FreeBSD pen-rdd-01.skysurfer.ca 7.1-RELEASE-p4 FreeBSD 7.1-RELEASE-p4 #1: Sun Mar 29 19:37:42 PDT 2009     philipd at pen-mweb-01.skysurfer.ca:/usr/obj/usr/src/sys/RDD  i386
>Description:
We have had the same issue on two separate machines running this release and earlier releases of FreeBSD when trying to use carp for failover. After creating the interfaces with ifconfig and setting it up so that traffic is hitting the carp IP the machines both just mysteriously freeze where they are 100% unresponsive.

The machines are both Dell PowerEdge servers. One is a 2650, and one is a older 2500.

The both are using Intel(R) PRO/1000 Gigabit Ethernet adapters (the em driver)

The both have RAID controllers in them using the aac driver and mirrored system disk pairs.
>How-To-Repeat:
Just simply create the carp interfaces (does not matter if both machines are up or not) and pass traffic to the IP they are set to. Any sort of larger volume traffic causes the machine to instantly lock.
>Fix:
I have not been able to find any workaround to this problem.

>Release-Note:
>Audit-Trail:
>Unformatted: