From owner-freebsd-stable@FreeBSD.ORG Fri Dec 4 03:46:57 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63CA51065672 for ; Fri, 4 Dec 2009 03:46:57 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by mx1.freebsd.org (Postfix) with ESMTP id F1C9F8FC14 for ; Fri, 4 Dec 2009 03:46:56 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 22so490970eye.9 for ; Thu, 03 Dec 2009 19:46:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=+BCdFSupzDw7t4N8GUT0loedTKCvduXeuegurmAJGpA=; b=HfB2xRRKrRA5BKtPXSvl249nVpt/smnOcAiOzj55LKIYVlEHEmKGXn8iv4kWoNbqsq nEY9HhVIao7+30+9HzcMHAPP+dGlNseNSFff+RpAEQ66vuk1Sv5LeX/0ne9oThCEpwQn kU8NKKahthhyNmhQVY/DNwKkMvVcgmnnYJOsI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=erY112Ln4ocvyG8BLZUND4lrsxAa7l23SBFNbyiB7Iqk887sHQW1si67g36frNe3jR PpPWrS89jVvNoWAaGzlUP0+Sa0dNlGwgFPTRx40vNGeVCxvBCdl/BV3HTXUizanqdFWq lMLeVuWi/MEhoV7eeEWI8xXohuoF6tsoiY+v8= MIME-Version: 1.0 Received: by 10.216.90.146 with SMTP id e18mr804029wef.153.1259898415960; Thu, 03 Dec 2009 19:46:55 -0800 (PST) Date: Thu, 3 Dec 2009 22:46:55 -0500 Message-ID: <5f67a8c40912031946v1ab3efua5e43bd7d767361a@mail.gmail.com> From: Zaphod Beeblebrox To: FreeBSD Stable Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Quggaa locking hard. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Dec 2009 03:46:57 -0000 I'm still investigating this, but my quagga is locking hard on FreeBSD 8.0 and not locking hard on 7.2. It seems (at this early point in the investigation) that both bgpd and zebra are wedging and zebra is listed as being in the "RUN" state. curiously, the load is also 4.0 (exactly the number of cores in the machine) even though the machine also reads 100% idle.