public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Fred Labrosse <ffl-4CLdheC3Iye1Qrn1Bg8BZw@public.gmane.org>
To: hgfelger-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org
Cc: Charles Kendricks
	<ckendricks-rGvcZsxnnNR8Odgaehf8fA@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Problem with acpi_power_off
Date: Fri, 25 Jun 2004 13:59:53 +0100	[thread overview]
Message-ID: <16604.8649.415502.900850@aber.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.60.0406251252280.1488-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>

hgfelger-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org writes:
 > -----BEGIN PGP SIGNED MESSAGE-----
 > Hash: SHA1
 > 
 > Salut Charles,
 > 
 > On Thu, 24 Jun 2004, Charles Kendricks wrote:
 > > I am in charge of several linux 2.6.4 systems with Dragon P4I875P 
 > > motherboards.  I am relatively new to acpi so my question might seem a little 
 > > elementary, but I can't seem to get my systems to power off consistently when 
 > > I issue an init 0.  It seems that all of them will power down sometimes, and 
 > > at other times the same systems won't power down.  Once powered down I have 
 > > no problem (at least not yet anyway) waking the systems back up.  What can be 
 > > causing this inconsistent behavior?????
 > there are two things you may try:
 >   1. If your system does not use the local APIC you might build a kernel
 >    without "Local APIC support on uniprocessors" CONFIG_X86_UP_APIC
 >   2. do not use the rtc-module "Enhanced Real Time Clock Support", but if
 >    you need the generic RTC CONFIG_GEN_RTC instead.

As some of you may remember, this is what solved the problem for me some
times ago.  However, in the last few days, I noticed on 2 occasions that my
laptop did not power off.  The only thing I changed was playing with usb
stuff, making some of it as modules and not.

The worrying thing is that it is not consistent.  At least I haven't been
able to see the pattern yet (as it only happened twice).  Will try to
figure out and report back if/when I do.

Fred



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

  parent reply	other threads:[~2004-06-25 12:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24 20:21 Problem with acpi_power_off Charles Kendricks
     [not found] ` <40DB37BD.3050904-rGvcZsxnnNR8Odgaehf8fA@public.gmane.org>
2004-06-25 11:01   ` hgfelger-9nAOAgdJVo4b1SvskN2V4Q
     [not found]     ` <Pine.LNX.4.60.0406251252280.1488-KnfdeQs3A3X/9pzu0YdTqQ@public.gmane.org>
2004-06-25 12:59       ` Fred Labrosse [this message]
     [not found]         ` <16604.8649.415502.900850-4CLdheC3Iye1Qrn1Bg8BZw@public.gmane.org>
2004-06-25 15:34           ` Nico Sabbi
  -- strict thread matches above, loose matches on Subject: below --
2004-06-25 16:04 Charles E. Kendricks, Jr.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=16604.8649.415502.900850@aber.ac.uk \
    --to=ffl-4cldhec3iye1qrn1bg8bzw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ckendricks-rGvcZsxnnNR8Odgaehf8fA@public.gmane.org \
    --cc=hgfelger-9nAOAgdJVo4b1SvskN2V4Q@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox