From owner-freebsd-bugs@FreeBSD.ORG Sun Feb 10 12:10:03 2008 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE36516A418 for ; Sun, 10 Feb 2008 12:10:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A24C113C4D1 for ; Sun, 10 Feb 2008 12:10:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m1ACA3ZT099812 for ; Sun, 10 Feb 2008 12:10:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m1ACA3Pv099811; Sun, 10 Feb 2008 12:10:03 GMT (envelope-from gnats) Date: Sun, 10 Feb 2008 12:10:03 GMT Message-Id: <200802101210.m1ACA3Pv099811@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Bruce Cran Cc: Subject: Re: kern/99567: [ata] Powerup of sleeping IDE drives causes system reboot. X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Bruce Cran List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Feb 2008 12:10:03 -0000 The following reply was made to PR kern/99567; it has been noted by GNATS. From: Bruce Cran To: bug-followup@FreeBSD.org, lordrictus@hotmail.com Cc: Subject: Re: kern/99567: [ata] Powerup of sleeping IDE drives causes system reboot. Date: Sun, 10 Feb 2008 12:00:33 +0000 It sounds like you're using ataidle to put the drives into sleep mode. Since it bypasses the kernel and talks directly to the hardware there are cases where it just doesn't work with certain controllers. Unfortunately the only solution at the moment is simply not to use it if it doesn't work with the combination of hardware you have. The READ_DMA timeouts are expected: the kernel doesn't expect to have to wait for a drive to spin up before data can be read. Since there were still 2 retries left, this only becomes a problem if the operation fails after all the retries have been done. -- Bruce