From owner-freebsd-current Sat May 3 02:49:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA21252 for current-outgoing; Sat, 3 May 1997 02:49:46 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA21247 for ; Sat, 3 May 1997 02:49:43 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id FAA02259 for current@freebsd.org; Sat, 3 May 1997 05:48:36 -0400 (EDT) From: Peter Dufault Message-Id: <199705030948.FAA02259@hda.hda.com> Subject: Current is spinning down disk To: current@freebsd.org Date: Sat, 3 May 1997 05:48:35 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A warning: yesterdays -current seems to have enabled some power saving with my normal config file on my crash-compaq that I've never known it had. The consolse is now blank (and that won't come back) and the wd0 drive is spinning down. It comes back to life with: > wd0: interrupt timeout: > wd0: status 58 error 0 The system mostly works though I do see a cron job that died with what is probably a disk error. I'm turning on "apm" to see if that does anything such as catch this error, or give me some diagnostics about the capabilities, or make the display come back to life. Peter -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936