Date: Tue, 25 Oct 2011 20:27:55 -0400 From: Alexander Kabaev <kabaev@gmail.com> To: "Alexey Shuvaev" <shuvaev@physik.uni-wuerzburg.de> Cc: freebsd-current@freebsd.org Subject: Re: Panics after AHCI timeouts Message-ID: <20111025202755.4243ae74@kan.dyndns.org> In-Reply-To: <649509EEAEBA42D4A3DCC1FDF5DA72E5@multiplay.co.uk> References: <20111008201456.GA3529@lexx.ifp.tuwien.ac.at> <20111017190027.GA9873@lexx.ifp.tuwien.ac.at> <CAJ-Vmokbm5z3GPbKjc6_o0_Ea6u_b7twDu=xLeYpORiUpp6Z=Q@mail.gmail.com> <20111018131353.GA83797@lexx.ifp.tuwien.ac.at> <649509EEAEBA42D4A3DCC1FDF5DA72E5@multiplay.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/2RWuK30BG+OyUpX2_SDnE9k Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 18 Oct 2011 14:28:07 +0100 "Steven Hartland" <killing@multiplay.co.uk> wrote: >=20 > ----- Original Message -----=20 > From: "Alexey Shuvaev" <shuvaev@physik.uni-wuerzburg.de> > To: <freebsd-current@freebsd.org> > Sent: Tuesday, October 18, 2011 2:13 PM > Subject: Re: Panics after AHCI timeouts >=20 >=20 > > On Tue, Oct 18, 2011 at 06:19:19AM +0800, Adrian Chadd wrote: > > Done, kern/161768. > >=20 > > Question to the list: does anybody see successful recovery from AHCI > > timeout an a recent CURRENT? Recent means June 2011 or newer, so 9.0 > > branch counts also. That is, there are some kernel messages like > > this: > >=20 > > ahcich0: Timeout on slot 29 port 0 > > ahcich0: is 00000000 cs 00000000 ss ffffffff rs ffffffff tfd 40 > > serr 00000000 cmd 0000fc17 > >=20 > > but then AHCI recovers and the system does not panic? >=20 > Not a recent CURRENT but on 8.2-RELEASE we have seen recovery on > secondary ssd drives without a panic, but it does generally > drop the disk and need a power off, power on to recover the > disk properly; although we believe that's a firmware bug on > the ssds >=20 > Regards > Steve >=20 I do see timeouts on one of my Samsung ST3750330A disks and they definitely do not cause any panics. The weird part in my case is that disk then immediately reappears as online and mirror zpool can be rebuilt by just onlining the disk with 'zpool online <pool> <disk>' command. It seems to be happening once system has accumulated some uptime. If rebooted, it keeps running for a week or two with no issues, but then timeouts start to happen more or less reliably every single 24 hours. =20 --=20 Alexander Kabaev --Sig_/2RWuK30BG+OyUpX2_SDnE9k Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iD8DBQFOp1QRQ6z1jMm+XZYRAhjTAJ9gDhB2nZrzp0xevvMFb2ZfTfYdnQCeLZg7 tkcPOLKfkT9HtmSvxESxXW8= =ZipY -----END PGP SIGNATURE----- --Sig_/2RWuK30BG+OyUpX2_SDnE9k--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111025202755.4243ae74>