Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 05 Aug 2005 14:17:28 -0700
From:      Mike Eubanks <mse_software@charter.net>
To:        stable@freebsd.org
Cc:        Garance A Drosihn <drosih@rpi.edu>
Subject:   Re: ``shutdown -p now'' not working in 5.4 STABLE
Message-ID:  <1123276648.4278.24.camel@yak.mseubanks.net>
In-Reply-To: <p06230922bf1975e2f7f7@[128.113.24.47]>
References:  <1123187556.786.25.camel@yak.mseubanks.net> <p06230918bf183089b61b@[128.113.24.47]> <1123190717.786.49.camel@yak.mseubanks.net> <p0623091bbf1845419177@[128.113.24.47]> <1123213427.786.94.camel@yak.mseubanks.net> <p06230922bf1975e2f7f7@[128.113.24.47]>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <mse_software@charter.net>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1123276648.4278.24.camel>