Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Apr 2019 10:51:44 +0200
From:      "Patrick M. Hausen" <hausen@punkt.de>
To:        Warner Losh <imp@bsdimp.com>
Cc:        FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject:   Re: NVME aborting outstanding i/o and controller resets
Message-ID:  <63F643CA-EDB1-41EB-A27E-EB427F3886B4@punkt.de>
In-Reply-To: <C0349078-63ED-4133-BA80-138D379B338B@punkt.de>
References:  <818CF16A-D71C-47C0-8A1B-35C9D8F68F4E@punkt.de> <CF2365AE-23EA-4F18-9520-C998216155D5@punkt.de> <CANCZdfoPZ9ViQzZ2k8GT5pNw5hjso3rzmYxzU=s%2B3K=ze%2BLZwg@mail.gmail.com> <58E4FC01-D154-42D4-BA0F-EF9A2C60DBF7@punkt.de> <CANCZdfpeZ-MMKB3Sh=3vhsjJcmFkGG7Jq8nW52D5S45PL3menA@mail.gmail.com> <45D98122-7596-4E8A-8A0D-C33E017C1109@punkt.de> <CANCZdfrcnRwqDPXMyT6xNKUZ5nX8x9Fj6DHbCnh%2BQ4mWzx0vGQ@mail.gmail.com> <92DAD65A-9BFE-4294-9066-977F498300A3@punkt.de> <CANCZdfr_0xV=QmeTRtQbtvcp3wN0rw4C7KpgrXt3zVpmADwArg@mail.gmail.com> <C5B0DD7B-4337-4F6D-B4BD-FDBCF2C091F8@punkt.de> <CANCZdfpWTSF2xDYOYLpzJ0c-wMWpK5xgHQVznnD=F-GxPw_8Zg@mail.gmail.com> <26B9E28E-8BA5-41EE-9146-5336AA7605A6@punkt.de> <CANCZdfqLLr56xRAgPdY5085vDvaCcx-m81_pVT901k4MhohO0A@mail.gmail.com> <1A448217-C0FA-4B62-9A7F-5AF9A83D207B@punkt.de> <C0349078-63ED-4133-BA80-138D379B338B@punkt.de>

next in thread | previous in thread | raw e-mail | index | archive | help
> Am 15.04.2019 um 08:46 schrieb Patrick M. Hausen <hausen@punkt.de>:
> So I=E2=80=99ll test RELENG_12 next. If that works, I can probably =
craft
> a FreeNAS 11.2 installation with a 12 kernel. I would be hesitating to =
run
> HEAD in production, though.

root@hurz:/var/tmp # uname -a
FreeBSD hurz 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335510: Fri Jun 22 =
04:32:14 UTC 2018     =
root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC  amd64
root@hurz:/var/tmp # dd if=3D/dev/urandom of=3Dhurz bs=3D10m

Result:

Apr 15 09:56:07 hurz kernel: nvme4: resetting controller
Apr 15 09:56:07 hurz kernel: nvme3: resetting controller
Apr 15 09:56:07 hurz kernel: nvme4: aborting outstanding i/o
Apr 15 09:56:07 hurz kernel: nvme4: WRITE sqid:5 cid:126 nsid:1 =
lba:188361216 len:208
Apr 15 09:56:07 hurz kernel: nvme4: ABORTED - BY REQUEST (00/07) sqid:5 =
cid:126 cdw0:0
Apr 15 09:56:07 hurz kernel: nvme4: aborting outstanding i/o
Apr 15 09:56:07 hurz kernel: nvme4: WRITE sqid:5 cid:127 nsid:1 =
lba:188368784 len:64
Apr 15 09:56:07 hurz kernel: nvme4: ABORTED - BY REQUEST (00/07) sqid:5 =
cid:127 cdw0:0
Apr 15 09:56:07 hurz kernel: nvme4: aborting outstanding i/o
Apr 15 09:56:07 hurz kernel: nvme4: WRITE sqid:5 cid:125 nsid:1 =
lba:188371408 len:48
Apr 15 09:56:07 hurz kernel: nvme4: ABORTED - BY REQUEST (00/07) sqid:5 =
cid:125 cdw0:0
Apr 15 09:56:07 hurz kernel: nvme4: aborting outstanding i/o
Apr 15 09:56:07 hurz kernel: nvme4: WRITE sqid:5 cid:124 nsid:1 =
lba:188371456 len:16
Apr 15 09:56:07 hurz kernel: nvme4: ABORTED - BY REQUEST (00/07) sqid:5 =
cid:124 cdw0:0
[=E2=80=A6]


Now, RELENG_12 kernel, 11.2-RELEASE userland:

root@hurz:/var/tmp # uname -a
FreeBSD hurz 12.0-STABLE FreeBSD 12.0-STABLE r346220 GENERIC  amd64
root@hurz:/var/tmp #  dd if=3D/dev/urandom of=3Dhurz bs=3D10m

Result:

no problems, not with two of these jobs running in parallel, not with a =
zpool scrub at the same time =E2=80=A6


I uploaded a complete dmesg of the system running RELENG_12:
https://cloud.hausen.com/s/5dRMsewCtDFHRYA

Is there anything else I should send? pciconf, nvmecontrol =E2=80=A6?

Kind regards
Patrick
--=20
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?63F643CA-EDB1-41EB-A27E-EB427F3886B4>