From owner-freebsd-scsi@freebsd.org  Wed Dec 20 16:37:35 2017
Return-Path: <owner-freebsd-scsi@freebsd.org>
Delivered-To: freebsd-scsi@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 BCA62E93AB4
 for <freebsd-scsi@mailman.ysv.freebsd.org>;
 Wed, 20 Dec 2017 16:37:35 +0000 (UTC)
 (envelope-from rebecca@bluestop.org)
Received: from muon.bluestop.org (muon.bluestop.org
 [IPv6:2605:7700:0:8:1:0:4a32:3323])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9CA627617A;
 Wed, 20 Dec 2017 16:37:35 +0000 (UTC)
 (envelope-from rebecca@bluestop.org)
Received: from muon.bluestop.org (localhost [127.0.0.1])
 by muon.bluestop.org (Postfix) with ESMTP id 9B9693CA8B;
 Wed, 20 Dec 2017 16:37:34 +0000 (UTC)
Received: from muon.bluestop.org ([127.0.0.1])
 by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id xTJBnY-w4uuZ; Wed, 20 Dec 2017 16:37:33 +0000 (UTC)
Received: from [IPv6:2603:3026:480::a14e] (unknown [IPv6:2603:3026:480::a14e])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128
 bits)) (No client certificate requested)
 by muon.bluestop.org (Postfix) with ESMTPSA;
 Wed, 20 Dec 2017 16:37:33 +0000 (UTC)
Subject: Re: FreeBSD 11 not sending repeated TURs until good status returned?
To: Ken Merry <ken@freebsd.org>
Cc: Alan Somers <asomers@freebsd.org>, FreeBSD-scsi <freebsd-scsi@freebsd.org>
References: <87ad0e0a-0183-d123-d7f3-2735c8cf854e@bluestop.org>
 <CAOtMX2jkxQ__2VYMsrj111Wza67ONQrrMPSmMPKFgugP+oYd-g@mail.gmail.com>
 <30772d0e-2456-a90e-54a2-7575987b25b4@bluestop.org>
 <9209CA38-750D-4966-911F-342092309DDF@freebsd.org>
From: Rebecca Cran <rebecca@bluestop.org>
Message-ID: <9d73844e-582f-3e08-3944-cada11a9c768@bluestop.org>
Date: Wed, 20 Dec 2017 09:37:32 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <9209CA38-750D-4966-911F-342092309DDF@freebsd.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi/>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
 <mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Dec 2017 16:37:35 -0000

On 12/20/2017 09:09 AM, Ken Merry wrote:

> I have seen this behavior on some HGST SSDs.  I haven’t had a chance to fully chase it down.

You're right, this is one of those drives.

> We’ll probably need full logs to get a better idea of what is going on.

Thanks, I've forwarded your email to the people working on it.

-- 
Rebecca Cran