From owner-freebsd-stable@freebsd.org Sat Apr 13 00:38:01 2019 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 35B9B154E22D for ; Sat, 13 Apr 2019 00:38:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-qt1-x833.google.com (mail-qt1-x833.google.com [IPv6:2607:f8b0:4864:20::833]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A04993BD1 for ; Sat, 13 Apr 2019 00:37:59 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-qt1-x833.google.com with SMTP id z17so13255349qts.13 for ; Fri, 12 Apr 2019 17:37:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ER3s+BE1jCThM9SxAVnAyvCl7BwC9WvOrX4igKBoupQ=; b=Ay61AaDpNyV5Jt8qdkPdKmCPane9b8MIrIaJmhMDtD3UPt0AvJeeU1a1SlxuDpTdo+ XzphJDNAkSKpXqfuLnWIlZO3pX9PYk/A9Tt2/u97ydSM9HxczTtB12MZDoraRSGlpOB8 BQxCIlzQmKlna8ntsSxAdxrbwnNvpnWz6mhe8GqKbm6N5QQ6JE4aOc7HD9goi9uSrBtH pkqcCy82r0nKKF06n5kT47cqD8D/YPIFjPIFAgCqrPUt6CaA8N6RlGoaksRfCyobSttD IjLACeiZP0tWJ9ubWc1Xqe00CmHGVZxX7B/IVF0WvsMentolV04KHjyGbbGx/Vbsdlj1 R+aA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ER3s+BE1jCThM9SxAVnAyvCl7BwC9WvOrX4igKBoupQ=; b=IAARF1+7ZkC4O48AEaxctLyEt2ToqHPNZ/t+oG3Vm77xxiWE9kOTXCKh2RhX20uGeZ 6o198VVrAZp+H8IQOFIxOCYiod9PETjG2N4TGUCkCWsqR1EWG6Zq913Cvq8gN2O9eZxz vNibVOpTG3gmIM9wSDNgUt8r3GL+J1Kj73hJV8ZbG3v8RWQodkxZyrOeBeFCe4TsN18W l+tpK4zmBKS3NCIKZ9C+Z2QM3YFAT+nJpgqpQ54LJSa3XkE15jYSa+gCmhcFkLvAH8Ov lgQvoUSemyeRE6uNZtAMTIHGNRwAZQVQFWoGKkOGpmJX89D0HEWqb/aIlwq+b9z6vwZW tudQ== X-Gm-Message-State: APjAAAUlSZfK2riA3OlCO1bcUPIPqvrSCpqpWU4xkrkrXQ9mSN+LmI1c V0dLucSnpleydODiUS8Yih9CVU+CgXGC3Ew2b0Nsb5U5 X-Google-Smtp-Source: APXvYqzKdNYTqlyhRdNlW6mA2FUCYgTNrWQ+qWj5p3GV2YYFrj7e2Ox0zP7BjNJdvuHbrRDq83VS2blgB71aYxZykmA= X-Received: by 2002:ac8:5493:: with SMTP id h19mr35899324qtq.23.1555115879008; Fri, 12 Apr 2019 17:37:59 -0700 (PDT) MIME-Version: 1.0 References: <818CF16A-D71C-47C0-8A1B-35C9D8F68F4E@punkt.de> <58E4FC01-D154-42D4-BA0F-EF9A2C60DBF7@punkt.de> <45D98122-7596-4E8A-8A0D-C33E017C1109@punkt.de> <92DAD65A-9BFE-4294-9066-977F498300A3@punkt.de> In-Reply-To: <92DAD65A-9BFE-4294-9066-977F498300A3@punkt.de> From: Warner Losh Date: Fri, 12 Apr 2019 18:37:47 -0600 Message-ID: Subject: Re: NVME aborting outstanding i/o and controller resets To: "Patrick M. Hausen" Cc: FreeBSD-STABLE Mailing List X-Rspamd-Queue-Id: 8A04993BD1 X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=bsdimp-com.20150623.gappssmtp.com header.s=20150623 header.b=Ay61AaDp X-Spamd-Result: default: False [-5.71 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; R_DKIM_ALLOW(-0.20)[bsdimp-com.20150623.gappssmtp.com:s=20150623]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_SHORT(-0.92)[-0.915,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; DMARC_NA(0.00)[bsdimp.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; MX_GOOD(-0.01)[cached: ALT1.aspmx.l.google.com]; DKIM_TRACE(0.00)[bsdimp-com.20150623.gappssmtp.com:+]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[3.3.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.2.0.0.4.6.8.4.0.b.8.f.7.0.6.2.list.dnswl.org : 127.0.5.0]; R_SPF_NA(0.00)[]; FORGED_SENDER(0.30)[imp@bsdimp.com,wlosh@bsdimp.com]; MIME_TRACE(0.00)[0:+,1:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FROM_NEQ_ENVFROM(0.00)[imp@bsdimp.com,wlosh@bsdimp.com]; IP_SCORE(-2.79)[ip: (-8.73), ipnet: 2607:f8b0::/32(-2.95), asn: 15169(-2.19), country: US(-0.06)]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Apr 2019 00:38:01 -0000 On Fri, Apr 12, 2019, 1:22 PM Patrick M. Hausen wrote: > Hi Warner, > > thanks for taking the time again =E2=80=A6 > > > OK. This means that whatever I/O workload we've done has caused the NVM= E > card to stop responding for 30s, so we reset it. > > I figured as much ;-) > > > So it's an intel card. > > Yes - I already added this info several times. 6 of them, 2.5=E2=80=9C NV= ME =E2=80=9Edisk > drives=E2=80=9C. > Yea, it was more of a knowing sigh... > OK. That suggests Intel has a problem with their firmware. > > I came across this one: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211713 > > Is it more probable that Intel has got buggy firmware here than that > =E2=80=9Ewe=E2=80=9C are missing interrupts? > More probable bad firmware. One of the things I think that is in HEAD is a mitigation for this that looks for completed IO on timeout before doing a reset. The mainboard is the Supermicro H11SSW-NT. Two NVME drive bays share > a connector on the mainboard: > > NVMe Ports ( NVMe 0~7, 10, 11, 14, 15) > > The H11SSW-iN/NT has tweleve (12) NVMe ports (2 ports per 1 Slim > SAS connector) on the motherboard. > These ports provide high-speed, low-latency PCI-E 3.0 x4 > connections directly from the CPU to NVMe Solid > State (SSD) drives. This greatly increases SSD data- throughput > performance and significantly reduces PCI-E > latency by simplifying driver/software requirements resulting fro= m > direct PCI-E interface from the CPU to the NVMe SSD drives. > > Is this purely mechanical or do two drives share PCI-E resources? Which > would explain > why the problems always come in pairs (nvme6 and nvme7, for example). > I'm unfamiliar with this setup, but coming in pairs increases the missed interrupt theory in my mind. Firmware issues usually don't come in pairs. This afternoon I set up a system with 4 drives and I was not able to > reproduce the problem. > (We just got 3 more machines which happened to have 4 drives each and no > M.2 directly > on the mainboard). > I will change the config to 6 drives like with the two FreeNAS systems in > our data center. > > > [=E2=80=A6 nda(4) ...] > > I doubt that would have any effect. They both throw as much I/O onto th= e > card as possible in the default config. > > I found out - yes, just the same. > NDA drives with an iosched kernel will be able to rate limit, which may be useful as a diagnostic tool... > There's been some minor improvements in -current here. Any chance you > could experimentally try that with this test? You won't get as many I/O > abort errors (since we don't print those), and we have a few more > workarounds for the reset path (though honestly, it's still kinda stinky)= . > > HEAD or RELENG_12, too? > HEAD is preferred, but any recent snapshot will do. Warner Kind regards, > Patrick > -- > punkt.de GmbH Internet - Dienstleistungen - Beratung > Kaiserallee 13a Tel.: 0721 9109-0 Fax: -100 > 76133 Karlsruhe info@punkt.de http://punkt.de > AG Mannheim 108285 Gf: Juergen Egeling > >