From owner-freebsd-bugs@FreeBSD.ORG Fri Jan 3 09:29:54 2014 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.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 C2E3AE6B; Fri, 3 Jan 2014 09:29:54 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 95C5E19CC; Fri, 3 Jan 2014 09:29:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s039Ts2d060285; Fri, 3 Jan 2014 09:29:54 GMT (envelope-from tijl@freefall.freebsd.org) Received: (from tijl@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s039TrNG060284; Fri, 3 Jan 2014 10:29:53 +0100 (CET) (envelope-from tijl) Date: Fri, 3 Jan 2014 10:29:53 +0100 (CET) Message-Id: <201401030929.s039TrNG060284@freefall.freebsd.org> To: samm@os2.kiev.ua, c.kworr@gmail.com, tijl@FreeBSD.org, freebsd-ports-bugs@FreeBSD.org, freebsd-bugs@FreeBSD.org From: tijl@FreeBSD.org Subject: Re: kern/177371: [cam] ATA_IDENTIFY command timeout, disk lost X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jan 2014 09:29:54 -0000 Old Synopsis: sysutils/smartmontools - triggers channel blocking New Synopsis: [cam] ATA_IDENTIFY command timeout, disk lost State-Changed-From-To: feedback->open State-Changed-By: tijl State-Changed-When: Fri Jan 3 10:18:28 CET 2014 State-Changed-Why: While the problem has been described using smartmontools it is not believed to be a ports PR. Responsible-Changed-From-To: freebsd-ports-bugs->freebsd-bugs Responsible-Changed-By: tijl Responsible-Changed-When: Fri Jan 3 10:18:28 CET 2014 Responsible-Changed-Why: While the problem has been described using smartmontools it is not believed to be a ports PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=177371