From owner-freebsd-current@FreeBSD.ORG  Wed Sep 24 16:16:58 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 1A12316D;
 Wed, 24 Sep 2014 16:16:58 +0000 (UTC)
Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com
 [IPv6:2a00:1450:4010:c04::22f])
 (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 6B38B405;
 Wed, 24 Sep 2014 16:16:57 +0000 (UTC)
Received: by mail-lb0-f175.google.com with SMTP id w7so5298088lbi.20
 for <multiple recipients>; Wed, 24 Sep 2014 09:16:55 -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=OC618AHxT0MIxX+64RL7d5DHlQ3F+ePemptg182aHEA=;
 b=YHH0SsU/g40ySPB/C7uBQBB2ePRHDKKhC0BM7SNvIXdrb3Z6/cMDQjM2LckuzeQe5O
 EBpL6RAuMcPGm+CJYTq5QAHH2UPxmp0gYvYpgeUMZjjNB7x8ZTs/hByEtZrI293L6b8A
 Jb1Sjbeon52tABfXXRJ7oNeJ4FdGY4tyrHJhqw8+u1MlfQC9hI22PtP0osPAYDQwtOOe
 SU8WHKRy1/eB84hwZj/6cdjcahVM4Z4PL02yJRih2u+tR7qICs8zEwB6HbnOS4hhcqU4
 SAMWTi37RVhSf6D7EqbX4wvBUxy9a22UkYwqQxgDUQpAg6Joi6pQ/VNhDcNFqAVEaeZL
 73rQ==
MIME-Version: 1.0
X-Received: by 10.112.198.131 with SMTP id jc3mr6907821lbc.42.1411575415080;
 Wed, 24 Sep 2014 09:16:55 -0700 (PDT)
Received: by 10.25.21.166 with HTTP; Wed, 24 Sep 2014 09:16:55 -0700 (PDT)
In-Reply-To: <5422E7C4.8070801@FreeBSD.org>
References: <5418F1B9.2000903@FreeBSD.org> <5419AB24.9050809@FreeBSD.org>
 <5422E7C4.8070801@FreeBSD.org>
Date: Wed, 24 Sep 2014 12:16:55 -0400
Message-ID: <CAFMmRNzGTjOd98UP_vPYauRJBBG+4inMVPNsGURZz+bEeed_Vg@mail.gmail.com>
Subject: Re: Cam panic on r271170
From: Ryan Stone <rysto32@gmail.com>
To: Bryan Drewery <bdrewery@freebsd.org>
Content-Type: text/plain; charset=UTF-8
Cc: FreeBSD Current <current@freebsd.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Sep 2014 16:16:58 -0000

On Wed, Sep 24, 2014 at 11:48 AM, Bryan Drewery <bdrewery@freebsd.org> wrote:
> Another, with much more information here:
> https://people.freebsd.org/~bdrewery/cam.panic.txt
>
> This was with memguard (vm.memguard.desc="CAM CCB") and a KASSERT in
> malloc(9) and uma_zalloc_arg() to prevent M_WAITOK in non-sleepable
> threads. Neither triggered.

Well that's unfortunate.  Are CCBs ever the target of DMA?

Does your hardware have an Intel chipset and is it new enough to
support an IOMMU?  You might try enabling the IOMMU, which would catch
out-of-bounds DMA by hardware:

http://svnweb.freebsd.org/changeset/base/257251

One caveat is that while I understand that the busdma infrastructure
for this is quite well tested, individual drivers and devices need to
be well-behaved so it's possible that this won't work on your hardware
right now.  Also, don't enable this if you use BHyve with PCI
Passthrough.