From owner-freebsd-bugs@freebsd.org  Mon Jun 29 13:29:56 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 3203598F852
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Mon, 29 Jun 2015 13:29:56 +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 16E9A1D2D
 for <freebsd-bugs@FreeBSD.org>; Mon, 29 Jun 2015 13:29:56 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t5TDTtvF014540
 for <freebsd-bugs@FreeBSD.org>; Mon, 29 Jun 2015 13:29:55 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 177108] [mvs] mvs driver with MV88SX6081 have timeout waiting
 for write DRQ [regression]
Date: Mon, 29 Jun 2015 13:29:55 +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: 9.1-PRERELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: joseph.brower@gmail.com
X-Bugzilla-Status: In Progress
X-Bugzilla-Priority: Normal
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-177108-8-wXINtV94rO@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-177108-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-177108-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: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2015 13:29:56 -0000

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

Joseph Brower <joseph.brower@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |joseph.brower@gmail.com

--- Comment #1 from Joseph Brower <joseph.brower@gmail.com> ---
We are also affected by this bug, in this case we're on 9.3.  It would be
awesome to see some motion on this since we'd like not needing to swap out
hardware that is perfectly good.  We can easily provide access to hardware that
is exhibiting this behaviour along with making it easily reproduced (takes
about 5 minutes from bootup to start seeing this happen.)

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