From owner-freebsd-bugs@FreeBSD.ORG  Fri Nov 15 10:25:42 2013
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 542FE166;
 Fri, 15 Nov 2013 10:25:42 +0000 (UTC)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com
 [IPv6:2607:f8b0:400e:c02::22c])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2B1EF2E6B;
 Fri, 15 Nov 2013 10:25:42 +0000 (UTC)
Received: by mail-pd0-f172.google.com with SMTP id q10so3307815pdj.31
 for <multiple recipients>; Fri, 15 Nov 2013 02:25:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=W9cwKF1htR/WpoBZ3yHNLUp7Dc9dXsWiSraagrR83mY=;
 b=KDldrS4XLqlPz1lTmQd5GOgkuekTYo31qjop99G+RtYoOMUPz+4vbCavVtXT87au1d
 93oQsU+xmhKE8RIY7ePXhlhFFUhwdLt5d18/ywLnJMyMhg0LnENpFmdeIYvYxb92GgfF
 mNwfphWbZWbiXzf1DlzV70J2frQc4fv7HEhkNO/KjXnaWk025N8zZQccbCEorqFv1Jxe
 3yLlwbw3aWYKfYFlL6yGdDzVWSnzYnLmOupaKaStYOi86vASLOIJiGzEICrILHCEXuKs
 5TwNMO8scuuEWCJFY9GySamg//W5fWaGWCfLmrMXOQnz5zaTt5TYfSyuzfQaJqmYxKyz
 tVtQ==
MIME-Version: 1.0
X-Received: by 10.66.142.107 with SMTP id rv11mr6221506pab.17.1384511141820;
 Fri, 15 Nov 2013 02:25:41 -0800 (PST)
Received: by 10.68.102.35 with HTTP; Fri, 15 Nov 2013 02:25:41 -0800 (PST)
In-Reply-To: <CALXRTbefRyMgZCLRyRDy9bSqhUaxjiM7WG0wHGxSipvn0Sg5Cg@mail.gmail.com>
References: <201311150318.rAF3IsB4001517@oldred.freebsd.org>
 <201311150320.rAF3K0ik017451@freefall.freebsd.org>
 <CALXRTbefRyMgZCLRyRDy9bSqhUaxjiM7WG0wHGxSipvn0Sg5Cg@mail.gmail.com>
Date: Fri, 15 Nov 2013 11:25:41 +0100
Message-ID: <CALXRTbcBvWh0PjK31Fuz1dW1RmEHpUzPW0COBUOjBGr0Q1SHuA@mail.gmail.com>
Subject: Re: misc/183980: Unreliable hotplug support with Intel Patsburg AHCI
 SATA controller
From: Marie <marieheleneka@gmail.com>
To: FreeBSD-gnats-submit@freebsd.org, freebsd-bugs@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.16
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.16
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: Fri, 15 Nov 2013 10:25:42 -0000

Following suggestions from mav@ on the FreeBSD forums (
http://forums.freebsd.org/showthread.php?t=43238), I've discovered that the
problem was somehow caused by SWAP being enabled on the device which was
being unplugged. Considering that 'top' output indicated no swap was being
used, and that the system had nearly 63 GB unused memory at the time, I
would be surprised if anything was swapped.

Although the issue is not what I initially thought it was, I still believe
this is a problem which needs resolving, as a hdd dying for whatever reason
should not make a port unavailable for what seems like an arbitary period
of time. (I have not yet managed to make the port work again by any other
way than a reboot, but I only left the system running for up to 15 minutes)