From owner-freebsd-stable@FreeBSD.ORG Thu May 21 15:33:59 2015 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CB5FDE99 for ; Thu, 21 May 2015 15:33:59 +0000 (UTC) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9B1EF1D2C for ; Thu, 21 May 2015 15:33:59 +0000 (UTC) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 3A3E220E74 for ; Thu, 21 May 2015 11:33:58 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Thu, 21 May 2015 11:33:58 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=smkelly.org; h= content-type:date:from:message-id:mime-version:subject:to :x-sasl-enc:x-sasl-enc; s=mesmtp; bh=8GS+UbLrcYPmwW6zfxZlE7E0V3s =; b=b40yqQHxFaDlZV0Whav5MO05TKq4Vp7IYsijislh5i/4hV+RLwbCu1JI9xI nmITNDLaWo+3y6BiGnvj4kHTIg2t11+0AnrGHnhTtrc8g686S5BJ4yaTTRZ18S9X QylenGVQxwpzyRzwVRpTPO9ttwRYXq5txLYSRCGhClGP4ink= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=8G S+UbLrcYPmwW6zfxZlE7E0V3s=; b=fxs3TB/O30Wmk0JzamZ3kuf4qVEzQAVRkT RL9SqgOhDMZRF9VGRoTuBb+2TE2mbAziyYrhckUsz3yDl8KqVlCkLL96E2KBOAvp x4rVNVhGedtQluud1i2o23vACWNNAgC1tveCoxE4aS6PTlnzr/dcrMZ57vwr4mgU WgGLxr4Cg= X-Sasl-enc: Xy7YI3Jou0PdcyZpgWdkG7FwmW65C6WFzWo4HsaK1PLE 1432222438 Received: from tardis.gwp.corp.flightaware.com (unknown [38.100.147.146]) by mail.messagingengine.com (Postfix) with ESMTPA id F24D56800C7 for ; Thu, 21 May 2015 11:33:57 -0400 (EDT) From: Sean Kelly Subject: 10.1 NVMe kernel panic Message-Id: <90B2D392-01FD-415A-B3D9-3CEDFC8373C4@smkelly.org> Date: Thu, 21 May 2015 10:33:56 -0500 To: freebsd-stable@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2100\)) X-Mailer: Apple Mail (2.2100) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 May 2015 15:33:59 -0000 Greetings. I have a Dell R630 server with four of Dell=E2=80=99s 800GB NVMe SSDs = running FreeBSD 10.1-p10. According to the PCI vendor, they are some = sort of rebranded Samsung drive. If I boot the system and then load = nvme.ko and nvd.ko from a command line, the drives show up okay. If I = put nvme_load=3D=E2=80=9CYES=E2=80=9D nvd_load=3D=E2=80=9CYES=E2=80=9D in /boot/loader.conf, the box panics on boot: panic: nexus_setup_intr: NULL irq resource! If I boot the system with =E2=80=9CSafe Mode: ON=E2=80=9D from the = loader menu, it also boots successfully and the drives show up. You can see a full =E2=80=98boot -v=E2=80=99 here: http://smkelly.org/stuff/nvme-panic.txt = Anyone have any insight into what the issue may be here? Ideally I need = to get this working in the next few days or return this thing to Dell. Thanks! --=20 Sean Kelly smkelly@smkelly.org http://smkelly.org