Date: Tue, 02 Apr 2013 20:39:20 +0200 From: Matthias Andree <mandree@FreeBSD.org> To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Cc: Alexander Motin <mav@FreeBSD.org> Subject: Re: Any objections/comments on axing out old ATA stack? Message-ID: <515B25D8.7050902@FreeBSD.org> In-Reply-To: <C699FE76-B456-49C7-8D3A-DD54F98DAFC1@samsco.org> References: <51536306.5030907@FreeBSD.org> <20130331130409.GO3178@equilibrium.bsdes.net> <C699FE76-B456-49C7-8D3A-DD54F98DAFC1@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4607F44AD83573971B4E25C3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 31.03.2013 23:02, schrieb Scott Long: > So what I hear you and Matthias saying, I believe, is that it should be= easier to > force disks to fall back to non-NCQ mode, and/or have a more responsive= > black-list for problematic controllers. Would this help the situation?= It's hard to > justify holding back overall forward progress because of some bad contr= ollers; > we do several Tbps off of AHCI controllers with NCQ enabled on FreeBSD = 9.x, > enough to make up a sizable percentage of the internet's traffic, and w= e see no > problems. How can we move forward but also take care of you guys with > problematic hardware? Well, I am running the driver fine off of my WD Caviar RE3 disk, and the problematic drive also works just fine with Windows and Linux, so it must be something between the problematic drive and the FreeBSD driver. I would like to see any of this, in decreasing order of precedence: - debugged driver - assistance/instructions on helping how to debug the driver/trace NCQ stuff/... (as in Jeremy Chadwick's followup in this same thread - this helps, I will attempt to procure the required information; "back then", reducing the number of tags to 31 was ineffective, including an error message and getting a value of 32 when reading the setting back) - "user-space" contingency features, such as letting camcontrol limit the number of open NCQ tags, or disable NCQ, either on a per-drive basis I am capable of debugging C - mostly with gdb command-line, and graphical Windows IDEs - but am unfamiliar with FreeBSD kernel debugging. If necessary, I can pull up a second console, but the PC that is affected is legacy-free, so serial port only works through a serial/USB converter. --------------enig4607F44AD83573971B4E25C3 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iEYEARECAAYFAlFbJd0ACgkQvmGDOQUufZXgTQCdHbEU7eARpq9xywE6doCJKcs1 5HEAoJibxdGKMztwTmtPi5GaVGnuTW4q =sEXh -----END PGP SIGNATURE----- --------------enig4607F44AD83573971B4E25C3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?515B25D8.7050902>