Date: Wed, 25 May 2016 00:15:39 +0100 From: Steven Hartland <killing@multiplay.co.uk> To: freebsd-current@freebsd.org Subject: Re: ATA? related trouble with r300299 Message-ID: <89aa4fa2-8e66-45e6-ec92-97dfc78c284f@multiplay.co.uk> In-Reply-To: <20160524205645.GA71641@mithlond.kdm.org> References: <16296020.R5v2TQkD2c@asus.theweb.org.ua> <4098903.NVJrBtROzX@asus.theweb.org.ua> <20160524201733.GA71011@mithlond.kdm.org> <1940214.zTZhPdnZGe@asus.theweb.org.ua> <20160524205645.GA71641@mithlond.kdm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24/05/2016 21:56, Kenneth D. Merry wrote: > On Tue, May 24, 2016 at 23:54:09 +0300, Oleg V. Nauman wrote: >> On Tuesday 24 May 2016 16:17:33 you wrote: >>> Okay, I've got a basic idea of what may be going on. The resets that are >>> getting sent are triggering another probe, which then triggers a reset, >>> which triggers a probe...and so on. >>> >>> So here is another patch that should work for you: >>> >>> https://people.freebsd.org/~ken/cam_smr_ada_patch.20160524.2.txt >>> >>> I have commented out the quirk for this drive, and the driver will now only >>> start the SMR probe on drives that claim to be SMR-capable. So, for the >>> vast majority of drives out there right now, it won't even start the extra >>> probe steps. >> It fixes this issue. I was able to boot with your latest patch. > Great! I'll check it in with that fix as well as a quirk entry. That way, > if we have other reasons later on to issue a read log, we'll know that > it doesn't work for those drives. Might be worth seeing if smartmontools can read the log from that drive before committing the quirk as a double check. Regards Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?89aa4fa2-8e66-45e6-ec92-97dfc78c284f>