From owner-freebsd-scsi@freebsd.org Wed Dec 20 00:29:15 2017 Return-Path: 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 7BCCEE85CD0 for ; Wed, 20 Dec 2017 00:29:15 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 F33D572FE6 for ; Wed, 20 Dec 2017 00:29:14 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x235.google.com with SMTP id g63so75013lfl.11 for ; Tue, 19 Dec 2017 16:29:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=kRiBNQ2cNUpZ3yl/pEjSdTE+8VDqcfpBSzxs3uUPkOw=; b=clxylIeZZjGS5Q9tiIol5WSp02fBhcmwOwRCURokeGmjDIbrbOmz2SkBiUNRkqT4qv MxMy5+gYwpH4N3Wdr5WuhZXyB725RWUeWqkXEsocK74xbUTBlpgpFemBFDt+aVkDcRIU +oA7fTLduWn3fv9KFT/nxDn3SQSmBfgPhV7Eh6xkCF9EN8RZ/YnWIakaIMTGHQiYK9QF DctMm72xkkYaGSodyVUxk30pz2aC3nfzgFmIvVnJhUZYsnIOXnZXZJ6Oa+Ec6IaqxlGW kRkt9JC9ALB19VEK3WNQNGtVFvcu8pMmphvqpmDdlRgKDizKjAVb+G7YzTxPFclo5s7R uJwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=kRiBNQ2cNUpZ3yl/pEjSdTE+8VDqcfpBSzxs3uUPkOw=; b=dtMx9wy5PFseZgkIVREs/HUwNUV11V6CjNDKkIysHerYSea6FI/kegsxKq4sLcAQXk pOmnGb5qTXR8algtggp5cBzrC4tfxLe230p/JaTPevAnZW6Q5jHRinXfW6hifrd1Lwfj GjnDvQcnIY5spCiXA6htFy2UxyFZcNuWH093xLYmobhiHztUfEJ1ftLaOQOR22VSv9Br zh7Z3K5EiYZG8FCgBzii7lM4VzXVaNmjCjQOjII2IoX//yYtuxdzhaT7t25GWXzQ9YAD 1nzu7lUl0pzORyVm8Mdty+uYbunB1IEXOpmopZ2n85PBuF/xdv0IY4Mce5gowFAOEbCZ 3Nfw== X-Gm-Message-State: AKGB3mKzIkT8RN8hn2AXGoNE0ePDarlKwmYrQnEPKsu7IQUXsZrQs6Kk Dt8fcpzw8KdvU/KTUWSxgMh0JtolOg927AEeJT0= X-Google-Smtp-Source: ACJfBovoxDl3HNOYkVWyXqsZlzqKyJO2FXiJRYslHHbas7SICrRdwasce9Wq8nk5m2xMuQpIDllgIira7M2nW9seBCI= X-Received: by 10.25.221.131 with SMTP id w3mr3405204lfi.90.1513729751749; Tue, 19 Dec 2017 16:29:11 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.76.19 with HTTP; Tue, 19 Dec 2017 16:29:11 -0800 (PST) In-Reply-To: <87ad0e0a-0183-d123-d7f3-2735c8cf854e@bluestop.org> References: <87ad0e0a-0183-d123-d7f3-2735c8cf854e@bluestop.org> From: Alan Somers Date: Tue, 19 Dec 2017 17:29:11 -0700 X-Google-Sender-Auth: SDuHZD9humuwCg-LCrU1G3T-c0I Message-ID: Subject: Re: FreeBSD 11 not sending repeated TURs until good status returned? To: Rebecca Cran Cc: FreeBSD-scsi Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Dec 2017 00:29:15 -0000 On Tue, Dec 19, 2017 at 12:30 PM, Rebecca Cran wrote: > I've been asked about a bug report at $work for a SAS drive, which is > failing to be detected when hot-plugged under FreeBSD 11 since I used to be > a FreeBSD developer. Not being being familiar with the *scsi* code however, > I thought people on this mailing list might have a better idea! > > From the report: > > "[the affected drive] is more closely conforming to the T10 spec as a Mode > Sense command does not require media access." > > "The proper thing for the system to do is send repeated TURs to the drive > until good status is returned. After that moment, the drive can properly do > I/O." > > > > The log file contains: > > READ(10). CDB: 28 00 2e 93 90 af 00 00 01 00 > > CAM status: SCSI Status Error > > SCSI status: Check Condition > > SCSI sense: NOT READY asc:4,1 (Logical unit is in process of becoming > ready) > > Progress: 0% (2/65536) complete > > Polling device for readiness > > mpssas_prepare_remove: Sending reset for target ID 123 > > da12 at mps0 bus 0 scbus0 target 123 lun 0 > > ... > > > Does this sound like a valid bug? > What's the problem exactly? Does FreeBSD poll the device or not? Does FreeBSD give up too soon, or poll with the wrong command, or what? And if you don't mind me asking, what sort of drive is this that takes so long to come ready? -Alan