Date: Fri, 09 Apr 2021 22:53:43 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 254841] usr.sbin/mpsutil: add functionality (temperature monitoring, PCIe speed etc) Message-ID: <bug-254841-227-5cT54nZLFT@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254841-227@https.bugs.freebsd.org/bugzilla/> References: <bug-254841-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254841 Daniel Austin <freebsd-ports@dan.me.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #223884|0 |1 is obsolete| | --- Comment #1 from Daniel Austin <freebsd-ports@dan.me.uk> --- Created attachment 223965 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D223965&action= =3Dedit Add functionality to mpsutil I've updated the patch to show whether SATA NCQ is enabled in 'show adapter' and also added a new command "set ncq [enable|disable]" which enables or disables NCQ in the NVRAM of the card. This is particularly useful in some external JBOD enclosures. For example, I use a QNAP TL-D1600S 16 bay and with NCQ enabled wth mps car= ds I receive errors from all attached drives. Once the system is booted, you can use camcontrol tags to effectively disab= le NCQ which works around the problem, but the kernel still has to suffer befo= re that point (e.g. with ZFS, just probing for pools could make my system take= 5+ mins to boot)... I discovered this workaround via Google. I had worked around it by using lsiutil in Linux to disable NCQ on the card, and with this patch users of FreeBSD / TrueNAS etc can set that setting in their chosen OS. Note: this diff also adds a new file (mps_set.c) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254841-227-5cT54nZLFT>