From owner-freebsd-questions@FreeBSD.ORG Wed Jan 31 01:39:53 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 05FDB16A400 for ; Wed, 31 Jan 2007 01:39:53 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id E7D8A13C4A5 for ; Wed, 31 Jan 2007 01:39:52 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C7D371A4D80; Tue, 30 Jan 2007 17:39:52 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7291A512EF; Tue, 30 Jan 2007 20:39:41 -0500 (EST) Date: Tue, 30 Jan 2007 20:39:41 -0500 From: Kris Kennaway To: Joe Vender Message-ID: <20070131013941.GA59719@xor.obsecurity.org> References: <200701301920.48499.jvender@owensboro.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: <200701301920.48499.jvender@owensboro.net> User-Agent: Mutt/1.4.2.2i Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD 6.1 & 6.2 hanging and/or spontaneous rebooting X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2007 01:39:53 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 30, 2007 at 07:20:47PM -0600, Joe Vender wrote: > I think I've fixed the spontaneous reboot and system hang problem I've be= en=20 > having with FBSD 6.1 & 6.2 as described in earlier threads of the same=20 > subject. I'm now using FBSD 6.2 to send this message. >=20 > What I did was to set a hint in /boot/device.hints and also /boot/loader.= conf=20 > to disable acpi > hint.acpi.0.disabled=3D"1" >=20 > and then I set a hint to enable apm > hint.apm.0.disabled=3D"0" > hint.apm.0.flags=3D"0x20" >=20 > plus I set apm and apmd to start at boot in /etc/rc.conf > apm_enable=3D"YES" > apmd_enable=3D"YES" >=20 > and in /boot/loader.conf, I put > apm_load=3D"YES" >=20 > The messages log shows that APM is being detected, and the computer now f= ully=20 > powers down via "shutdown -p now". >=20 > I've a suggestion. It would be nice if freebsd could try to detect if acp= i is=20 > supported on the computer in which it is being installed, and if none is= =20 > found, it should completely disable acpi and then check if apm is support= ed.=20 > It should then set the appropriate settings to enable the correct power= =20 > management support for the computer. This would prevent this particular= =20 > spontaneous rebooting and hanging on old computers like mine which are=20 > pre-acpi but have apm support. It does try to detect it; the problem is apparently that your BIOS lies and says "yep, ACPI capable!", but is in fact too buggy to use. Look for a BIOS update if possible. kris --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFFv/NcWry0BWjoQKURAoHkAKDHPJXwcsZ0ZOX5FcAL7JnQoIiJWACfe/Lq w9/RODeYafIMi6a6+SXlHcc= =w6Bt -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh--