From owner-freebsd-bugs@freebsd.org  Tue Oct 13 16:50:41 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 2C08EA12976
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue, 13 Oct 2015 16:50:41 +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 18FF7B8D
 for <freebsd-bugs@FreeBSD.org>; Tue, 13 Oct 2015 16:50:41 +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 t9DGoeE0057641
 for <freebsd-bugs@FreeBSD.org>; Tue, 13 Oct 2015 16:50:40 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: Tue, 13 Oct 2015 16:50:41 +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-296SvDjeLB@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: Tue, 13 Oct 2015 16:50:41 -0000

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

--- Comment #32 from Stephen McConnell <slm@freebsd.org> ---
OK. I might be able to set something up and run some I/O to see what happens. 
In the meantime, can you run a test where you set the debug_level to 0x1F and
then send me the complete log?  I don't know if that will be too much debug
info in the log, but what I want to see is what happens before the beginning of
the initial command timeout all the way through the re-insertion of the disk,
including system time.

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