From owner-freebsd-current@freebsd.org Tue May 24 23:15:42 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54C9DB493CC for ; Tue, 24 May 2016 23:15:42 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E72091278 for ; Tue, 24 May 2016 23:15:41 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by mail-wm0-x234.google.com with SMTP id z87so41817000wmh.0 for ; Tue, 24 May 2016 16:15:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=multiplay-co-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to; bh=TU8hxa8ulGle8UID6W3MMyU0cS1Xv2xbXE/RbBybrcU=; b=QifZZdHhCkoNa4ELO8aTRfJwGJWQanXeMAEmBDHYliIlZ4+KTLjSNF7A9G4YgpURQs n0FHGofGTYHB0lZA7SKp34an6zs8QyRcLXY2vk0XiOsF7dD2KntlQX19LNnLgOktuxZi gb4CMzEm2N9ehgrfHobznJWMnv9AD+Zgh5hA+yFhkDe2Sk9CRE+ncb0/QxawMdNkg7IB Fngff0SJUyuTxJOPu9c41c4jPF8+jGFvKDa+h+PGbzohhKMp5iIIANEwl3KrBlbN/nPx S0F+efOVI72ITUVHnw4ijoA96noOMpaqKXEIBVyVxFWaOb77becfTJnMJNoWdYt+OX0y cELQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to; bh=TU8hxa8ulGle8UID6W3MMyU0cS1Xv2xbXE/RbBybrcU=; b=VXfczlJSsw1yvGUJKUGWLQjzotXsVP8K1CqYukPF5BzD+q2RinTXdtJk4Yz5QOk29t Ir7kQ2bHu04+0Am7RGpHgVU85nUHiKZ4Gh25rQVFk5LFYzAd+iif3YRK9IOrSRY/i/da l9NZJ4WmAOMii2P4+ahkPQvhmfCNJtFlIS/fDauDBE6OP83+FKb1MUsavczwAxIXPbP4 WJBIXWIZaS6YfjB2nU9/WKV6h6sR7mAMNLL3SyJHhpjjELMjy3kK8AoU+R3R48dglsac j7jzOs3DHOfQONe/QM0PocBStmti0Jd6IeYLEnhmt+R42Ox+VEqkNhBAX2uqjNuPPUHK qDxA== X-Gm-Message-State: ALyK8tJWKG3Ug0+oq7nNu7/FbKUQZQWL34iPb6PPwWMZAyJQgU8NJIXQvpTbcw6iwLAjbuYA X-Received: by 10.28.213.1 with SMTP id m1mr122838wmg.103.1464131740239; Tue, 24 May 2016 16:15:40 -0700 (PDT) Received: from [10.10.1.58] (liv3d.labs.multiplay.co.uk. [82.69.141.171]) by smtp.gmail.com with ESMTPSA id t13sm6028902wmt.14.2016.05.24.16.15.37 for (version=TLSv1/SSLv3 cipher=OTHER); Tue, 24 May 2016 16:15:37 -0700 (PDT) Subject: Re: ATA? related trouble with r300299 To: freebsd-current@freebsd.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> From: Steven Hartland Message-ID: <89aa4fa2-8e66-45e6-ec92-97dfc78c284f@multiplay.co.uk> Date: Wed, 25 May 2016 00:15:39 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <20160524205645.GA71641@mithlond.kdm.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2016 23:15:42 -0000 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