From owner-freebsd-bugs Mon Apr 1 09:06:11 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA07023 for bugs-outgoing; Mon, 1 Apr 1996 09:06:11 -0800 (PST) Received: from lserver.infoworld.com (lserver.infoworld.com [192.216.48.4]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA06947 Mon, 1 Apr 1996 09:05:56 -0800 (PST) Received: from ccgate.infoworld.com by lserver.infoworld.com with smtp (Smail3.1.29.1 #12) id m0u3nP0-000ws0C; Mon, 1 Apr 96 09:28 PST Received: from cc:Mail by ccgate.infoworld.com id AA828378286; Mon, 01 Apr 96 09:46:25 PST Date: Mon, 01 Apr 96 09:46:25 PST From: "Brett Glass" Message-Id: <9603018283.AA828378286@ccgate.infoworld.com> To: Michael Smith Cc: hdalog@zipnet.net, davidg@Root.COM, hardware@FreeBSD.ORG, bugs@FreeBSD.ORG Subject: Re: Cannot boot after install Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Note that there are some interesting comments in the ATA spec I was > referring to regarding power-saving modes. Basically, the "lowest" a > drive is allowed to go without an explicit command should still respond, > as per normal, to commands, however response may be delayed by up to 30 > seconds. If your drive is responding with an error condition (indicating > that it's gone into 'sleep' mode), it is violating the spec. In that case, the drive is absolutely within spec. It comes up within 30 seconds. However, FreeBSD literally locks up until it sees a response fron the drive. This is a problem with FreeBSD. It should not busy-wait in the kernel, forsaking all other tasks, until it gets a response. This is, after all, a multitasking OS! ;-) The kernel hack I did (turning off the power-saving mode) is appropriate for desktop machines; in fact, for them, it's a good idea. But it's NOT appropriate for laptops and other low-power applications. The kernel needs to be fixed so that the drive *can* spin down without locking up the entire machine. --Brett