From owner-freebsd-stable@freebsd.org  Fri Jul 29 08:10:20 2016
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5F40BA844B
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Fri, 29 Jul 2016 08:10:20 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from cu1176c.smtpx.saremail.com (cu1176c.smtpx.saremail.com
 [195.16.148.151])
 (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 7EA191DA3
 for <freebsd-stable@freebsd.org>; Fri, 29 Jul 2016 08:10:19 +0000 (UTC)
 (envelope-from borjam@sarenet.es)
Received: from [172.16.8.36] (izaro.sarenet.es [192.148.167.11])
 by proxypop02.sare.net (Postfix) with ESMTPSA id B18B79DC625;
 Fri, 29 Jul 2016 10:10:16 +0200 (CEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: Intel NVMe troubles?
From: Borja Marcos <borjam@sarenet.es>
In-Reply-To: <CAJP=Hc-KdmScZtCRDcF=CTpNcMkn2brXiPx4XwJA0aTYgkxm+g@mail.gmail.com>
Date: Fri, 29 Jul 2016 10:10:16 +0200
Cc: FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <AAC8E93B-F263-4B7E-91DF-9EAC77FB2C3C@sarenet.es>
References: <CBC304D0-AA57-4EF5-A2DD-1888FB88DE12@sarenet.es>
 <CAJP=Hc-KdmScZtCRDcF=CTpNcMkn2brXiPx4XwJA0aTYgkxm+g@mail.gmail.com>
To: Jim Harris <jim.harris@gmail.com>
X-Mailer: Apple Mail (2.3124)
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2016 08:10:20 -0000


> On 28 Jul 2016, at 19:25, Jim Harris <jim.harris@gmail.com> wrote:
>=20
> Yes, you should worry.
>=20
> Normally we could use the dump_debug sysctls to help debug this - =
these
> sysctls will dump the NVMe I/O submission and completion queues.  But =
in
> this case the LBA data is in the payload, not the NVMe submission =
entries,
> so dump_debug will not help as much as dumping the NVMe DSM payload
> directly.
>=20
> Could you try the attached patch and send output after recreating your =
pool?

Just in case the evil anti-spam ate my answer, sent the results to your =
Gmail account.




Borja.