From owner-freebsd-bugs@freebsd.org  Mon Oct 12 17:32:51 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 6D344A11C53
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon, 12 Oct 2015 17:32:51 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 58738996
 for <freebsd-bugs@FreeBSD.org>; Mon, 12 Oct 2015 17:32:51 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9CHWpFO077345
 for <freebsd-bugs@FreeBSD.org>; Mon, 12 Oct 2015 17:32:51 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 191348] [mps] LSI2308 with WD3000FYYZ drives disappears after
 hotswapping
Date: Mon, 12 Oct 2015 17:32:50 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.0-RELEASE
X-Bugzilla-Keywords: patch-ready
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: slm@freebsd.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-191348-8-DZ9zgIX3uT@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-191348-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-191348-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Oct 2015 17:32:51 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191348

--- Comment #28 from Stephen McConnell <slm@freebsd.org> ---
Hi Karli, I don't see anything in the logs that makes me think this is the same
issue as the original issue.  Can you explain why you think so?  The original
problem was a spinup delay that the driver needed to account for.  There were
messages regarding SATA Identify in the original logs.

For your current issue, I don't see anything in the logs that makes me think
this is a driver problem.  What is happening is that the driver is getting SAS
Topology Change List events when you insert the SATA disk.  But, in order for
the driver to enumerate that disk, the PhyStatus must by "Target Added".  In
your case, the PhyStatus is always "PHY Link Status Change" and never "Target
Added".  So, this tells me that the Firmware is never getting enough
information from that disk to add it.  All I can think of is that something is
wrong with your disk.  Do you have this issue with any other disk?  Do you know
that this disk is operating normally in other cases?

Right now, I don't see any problem with the driver for this.

-- 
You are receiving this mail because:
You are the assignee for the bug.