misc/183980: Unreliable hotplug support with Intel Patsburg AHCI SATA controller

[Marie]

The following reply was made to PR misc/183980; it has been noted by GNATS.

From: Marie <marieheleneka at gmail.com>
To: FreeBSD-gnats-submit at freebsd.org, freebsd-bugs at freebsd.org
Cc:  
Subject: Re: misc/183980: Unreliable hotplug support with Intel Patsburg AHCI
 SATA controller
Date: Fri, 15 Nov 2013 11:25:41 +0100

 --001a11331e46cbbc9004eb349edd
 Content-Type: text/plain; charset=ISO-8859-1
 
 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)
 
 --001a11331e46cbbc9004eb349edd
 Content-Type: text/html; charset=ISO-8859-1
 Content-Transfer-Encoding: quoted-printable
 
 <div dir=3D"ltr">Following suggestions from mav@ on the FreeBSD forums (<a =
 href=3D"http://forums.freebsd.org/showthread.php?t=3D43238">http://forums.f=
 reebsd.org/showthread.php?t=3D43238</a>), I've discovered that the prob=
 lem was somehow caused by SWAP being enabled on the device which was being =
 unplugged. Considering that 'top' output indicated no swap was bein=
 g used, and that the system had nearly 63 GB unused memory at the time, I w=
 ould be surprised if anything was swapped.<div>
 <br></div><div>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 a=
 rbitary 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)</div>
 </div>
 
 --001a11331e46cbbc9004eb349edd--