From owner-freebsd-current@FreeBSD.ORG Wed Sep 17 19:03:45 2014 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6E8A81BD; Wed, 17 Sep 2014 19:03:45 +0000 (UTC) Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C278EA24; Wed, 17 Sep 2014 19:03:44 +0000 (UTC) Received: by mail-lb0-f173.google.com with SMTP id w7so2451967lbi.32 for ; Wed, 17 Sep 2014 12:03:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=p6LDmmmVFM8K7xSWchQtW3CyfXijc2aeQbj1FqHjWpw=; b=GdEZgJumQLE4eUXAFuF4xGGF4Q4+izqzkSG9UPLQv/sLIxVymMDgL0ms/+BcxGyhgF 5UclXkBrPL81agyrazCb1uTX+9Nuv6L0V3LkecvBwAuLH/Ji0B8X9cJ6v+8tuSO+wRcv 8nfilSrEp50O7bWvIqmOHOyo37c89UiOjxocP29bCwMP4Wmk16SePolipJ19WfAgv4Wh 49rv+hnvCfVjBsMQVU31DA84NGDW/Jk1puFmln3PYMBAQa1kkyQzkKG9+NCAa7yobFc5 IprUz1I/RKiQsd9ZWfGBqyxOw8Cy3YuovOBDFSnMIYsVp5yWG49oaa6815alCYA6kE9x aPoQ== MIME-Version: 1.0 X-Received: by 10.152.163.66 with SMTP id yg2mr31252989lab.38.1410980620685; Wed, 17 Sep 2014 12:03:40 -0700 (PDT) Received: by 10.25.21.166 with HTTP; Wed, 17 Sep 2014 12:03:40 -0700 (PDT) In-Reply-To: <5419AB24.9050809@FreeBSD.org> References: <5418F1B9.2000903@FreeBSD.org> <5419AB24.9050809@FreeBSD.org> Date: Wed, 17 Sep 2014 15:03:40 -0400 Message-ID: Subject: Re: Cam panic on r271170 From: Ryan Stone To: Bryan Drewery Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 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: Wed, 17 Sep 2014 19:03:45 -0000 Could you try turning on memguard for the CAM CCB malloc area? That should locate the problem quite quickly.