From owner-freebsd-current Sat Aug 21 12:12:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id D980A14F36 for ; Sat, 21 Aug 1999 12:12:34 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn2.imasy.or.jp [202.227.24.194]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id EAA25036; Sun, 22 Aug 1999 04:12:13 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199908211912.EAA25036@tasogare.imasy.or.jp> To: plm@xs4all.nl Cc: freebsd-current@FreeBSD.ORG Subject: Re: recent apm changes In-Reply-To: Your message of "Mon, 16 Aug 1999 22:36:44 +0200 (CEST)" <14264.30300.546811.726638@muon.xs4all.nl> References: <14264.30300.546811.726638@muon.xs4all.nl> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sun, 22 Aug 1999 04:15:40 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 56 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry to late... plm> Now suspend works. However still the disks keep spinning until they plm> reach their BIOS timeout. In Linux & Windows, there is some hook when plm> going to suspend mode that spins down the (IDE) disks. This is nice, plm> since it is well possible that you go to suspend but do not set a disk plm> spindown timeout. I read linux source code closely again, I found their hack in IDE device driver. Does anyone know this could make differences on suspending?