From owner-freebsd-current@freebsd.org Tue May 24 20:56:48 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 81D21B49BA6 for ; Tue, 24 May 2016 20:56:48 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6B6DE1A98 for ; Tue, 24 May 2016 20:56:48 +0000 (UTC) (envelope-from ken@kdm.org) Received: by mailman.ysv.freebsd.org (Postfix) id 66DD3B49BA5; Tue, 24 May 2016 20:56:48 +0000 (UTC) Delivered-To: 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 6680EB49BA4 for ; Tue, 24 May 2016 20:56:48 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mithlond.kdm.org (mithlond.kdm.org [96.89.93.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "A1-33714", Issuer "A1-33714" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 335291A97 for ; Tue, 24 May 2016 20:56:47 +0000 (UTC) (envelope-from ken@kdm.org) Received: from mithlond.kdm.org (localhost [127.0.0.1]) by mithlond.kdm.org (8.15.2/8.14.9) with ESMTPS id u4OKukgh071646 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 24 May 2016 16:56:46 -0400 (EDT) (envelope-from ken@mithlond.kdm.org) Received: (from ken@localhost) by mithlond.kdm.org (8.15.2/8.14.9/Submit) id u4OKukag071645; Tue, 24 May 2016 16:56:46 -0400 (EDT) (envelope-from ken) Date: Tue, 24 May 2016 16:56:46 -0400 From: "Kenneth D. Merry" To: "Oleg V. Nauman" Cc: current@freebsd.org Subject: Re: ATA? related trouble with r300299 Message-ID: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1940214.zTZhPdnZGe@asus.theweb.org.ua> User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (mithlond.kdm.org [127.0.0.1]); Tue, 24 May 2016 16:56:46 -0400 (EDT) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mithlond.kdm.org 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 20:56:48 -0000 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. Ken -- Kenneth Merry ken@FreeBSD.ORG