Date: Thu, 4 Apr 2019 13:25:15 +0200 From: "Patrick M. Hausen" <hausen@punkt.de> To: freebsd-stable@freebsd.org Subject: Re: NVME aborting outstanding i/o Message-ID: <F12079D6-C0D4-4628-83AF-6F58C8642704@punkt.de> In-Reply-To: <CF2365AE-23EA-4F18-9520-C998216155D5@punkt.de> References: <818CF16A-D71C-47C0-8A1B-35C9D8F68F4E@punkt.de> <CF2365AE-23EA-4F18-9520-C998216155D5@punkt.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > Am 04.04.2019 um 10:37 schrieb Patrick M. Hausen <hausen@punkt.de>: > But: >=20 > root@freenas01[~]# sysctl hw.nvme.per_cpu_io_queues > sysctl: unknown oid 'hw.nvme.per_cpu_io_queues' > root@freenas01[~]# sysctl hw.nvme.min_cpus_per_ioq > sysctl: unknown oid 'hw.nvme.min_cpus_per_ioq' > root@freenas01[~]# sysctl hw.nvme.force_intx > sysctl: unknown oid 'hw.nvme.force_intx' Looks like these can be set via loader.conf and reboot although they are not visible in the running system. Even when set they are not visible afterwards ... hw.nvme.per_cpu_io_queues=3D0 seems to cure the NVME errors. I=E2=80=99m still curious about the root problem here, bit at least I can now continue to use the machines for some real loads. 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?F12079D6-C0D4-4628-83AF-6F58C8642704>