From owner-freebsd-current@FreeBSD.ORG Thu Oct 27 23:00:13 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F3932106564A for ; Thu, 27 Oct 2011 23:00:11 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9972A8FC14 for ; Thu, 27 Oct 2011 23:00:11 +0000 (UTC) Received: by qadz32 with SMTP id z32so4269006qad.13 for ; Thu, 27 Oct 2011 16:00:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; bh=4aOEHDlG896wTCVdttcssB4auLRC+ioiVGic7rnDOIM=; b=neZ9Lj8/lWczdOSfewuNrwWl1O1FoZp2LzokK5aZh2EKoyanpdYugXh6i76SXOGuW3 OrRvNwzyYllibm6VfwJCPRo7aK5wy3asWHa67pK5x5qK6/qJKMe5PnuirQrdC+iTDa8+ PYBNtwoegKgMIxT5pW2ouCic4IZekcSmt07gA= Received: by 10.229.187.202 with SMTP id cx10mr13341qcb.197.1319756410891; Thu, 27 Oct 2011 16:00:10 -0700 (PDT) Received: from kan.dyndns.org (c-24-63-226-98.hsd1.ma.comcast.net. [24.63.226.98]) by mx.google.com with ESMTPS id en3sm10805378qab.22.2011.10.27.16.00.04 (version=SSLv3 cipher=OTHER); Thu, 27 Oct 2011 16:00:05 -0700 (PDT) Date: Thu, 27 Oct 2011 18:59:57 -0400 From: Alexander Kabaev To: "C. P. Ghost" Message-ID: <20111027185957.54ece0ad@kan.dyndns.org> In-Reply-To: References: <20111008201456.GA3529@lexx.ifp.tuwien.ac.at> <20111017190027.GA9873@lexx.ifp.tuwien.ac.at> <20111018131353.GA83797@lexx.ifp.tuwien.ac.at> <649509EEAEBA42D4A3DCC1FDF5DA72E5@multiplay.co.uk> <20111025202755.4243ae74@kan.dyndns.org> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/_ehfTFplfGyk.y.4CYlV8t2"; protocol="application/pgp-signature" Cc: Alexey Shuvaev , freebsd-current@freebsd.org Subject: Re: Panics after AHCI timeouts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Oct 2011 23:00:13 -0000 --Sig_/_ehfTFplfGyk.y.4CYlV8t2 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 26 Oct 2011 16:00:55 +0200 "C. P. Ghost" wrote: > On Wed, Oct 26, 2011 at 2:27 AM, Alexander Kabaev > wrote: > > 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 > > ' 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 > Does it correlate with high disk activity, i.e. with periodic(8)? >=20 > On my machine, I have a feeling that timeouts occur more often > at that point, than normally... and that they also occur when multiple > processes access the disk simultaneously. >=20 > If it's only one process, the machine (usually) doesn't hang, even > when that process is copying big files back and forth for a long > period of time (it's a backup process). But interleave that process > with another one accessing the same disk, and poof!, almost > immediately ahci timeouts. occur. Very strange... Maybe a race > condition of some sort after all? >=20 No, I cannot say there is any specific correlation to IO load of the machine, timeouts I saw happen randomly and seem almost always happen as system uptime crosses two weeks boundary. I am suspecting Samsung firmware at this point. --=20 Alexander Kabaev --Sig_/_ehfTFplfGyk.y.4CYlV8t2 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iD8DBQFOqeJzQ6z1jMm+XZYRAnb/AJ4haF0NaxrpT1w3T5iHNwdNe6N/OQCfSSxf XCk/Nu1y9lrJXV+7hO/Mpvo= =miJa -----END PGP SIGNATURE----- --Sig_/_ehfTFplfGyk.y.4CYlV8t2--