From owner-freebsd-stable@FreeBSD.ORG Fri Aug 5 21:17:32 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 870E816A425 for ; Fri, 5 Aug 2005 21:17:32 +0000 (GMT) (envelope-from mse_software@charter.net) Received: from mxsf18.cluster1.charter.net (mxsf18.cluster1.charter.net [209.225.28.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1797343D45 for ; Fri, 5 Aug 2005 21:17:31 +0000 (GMT) (envelope-from mse_software@charter.net) Received: from mxip26a.cluster1.charter.net (mxip26a.cluster1.charter.net [209.225.28.181]) by mxsf18.cluster1.charter.net (8.12.11/8.12.11) with ESMTP id j75LHUmS012667 for ; Fri, 5 Aug 2005 17:17:30 -0400 Received: from 68-186-85-19.dhcp.knwk.wa.charter.com (HELO yak.mseubanks.net) ([68.186.85.19]) by mxip26a.cluster1.charter.net with ESMTP; 05 Aug 2005 17:17:30 -0400 X-IronPort-AV: i="3.95,171,1120449600"; d="scan'208"; a="26705287:sNHT16437224" From: Mike Eubanks To: stable@freebsd.org In-Reply-To: References: <1123187556.786.25.camel@yak.mseubanks.net> <1123190717.786.49.camel@yak.mseubanks.net> <1123213427.786.94.camel@yak.mseubanks.net> Content-Type: text/plain Date: Fri, 05 Aug 2005 14:17:28 -0700 Message-Id: <1123276648.4278.24.camel@yak.mseubanks.net> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Garance A Drosihn Subject: Re: ``shutdown -p now'' not working in 5.4 STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mse_software@charter.net List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2005 21:17:32 -0000 On Fri, 2005-08-05 at 16:03 -0400, Garance A Drosihn wrote: > At 8:43 PM -0700 8/4/05, Mike Eubanks wrote: > >On Thu, 2005-08-04 at 19:14 -0400, Garance A Drosihn wrote: > > > > >> Hmm. The more I think about this, the more I think I tripped > >> across something similar once. I think it was something like > >> I turned on 'APM' somewhere, or I added it to my kernel, or > > > something. For power-down, you need to be using ACPI, not APM. > >> But from your dmesg output, it looks like you are using ACPI, > > > so I am probably not helping much with that guess either. > > > >Ok, I built APM into the kernel and gave it a few tries, fiddling > >with different things. > > Sorry, my comments were not as clear as they should have been. > What I meant is that my problem was *caused* by adding APM into > the mix, when it should not have been there. That's what I > meant by: For power-down, you need to be using ACPI, not APM. > > But all of this is just vague memory anyway. I haven't had any > problems with my machines powering down for quite awhile now. > (through many different system builds...) > Garance, That's ok. I figured it wouldn't hurt to give it a try anyway. I am currently rebuilding it. I've never had a problem quite like this one. Evidence for problem seems to be inconsistent in the fact that it works fully on one version, and sometimes on the other. In the end, I fear my install is the only thing questionable at this point when considering the other dual-Athlon 5.4 system operates without a problem. Thanks again -- Mike Eubanks