All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: "Brown, Len" <len.brown@intel.com>, Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Hyper-threaded pickle
Date: Thu, 04 Mar 2004 23:52:37 -0500	[thread overview]
Message-ID: <40480795.5000402@pobox.com> (raw)


So,

Just now getting my dual athlon going under 2.6.x.  It _really_ doesn't 
like ACPI.

ACPI specifications dictate some hardware characteristics, as well as 
specifying table structures and such.  One of those characteristics is 
the 4-second poweroff:  if you hold down the power button for 4-5 
seconds, your motherboard is required to poweroff the machine.  This is 
supposed to be a hard poweroff, and on most machines this works even 
when various pieces of hardware are frozen/locked-up.

Turning on ACPI kills my 4-second poweroff, which is pretty darn 
impressive.  So I proceed to disable ACPI...  but CONFIG_ACPI_BOOT 
doesn't want to disable.  I am trying to restore my working, non-ACPI 
configuration under 2.6, but this seems to be preventing me from doing so:

drivers/acpi/Kconfig:
config ACPI_BOOT
         bool
         depends on ACPI || X86_HT
         default y

arch/i386/Kconfig:
config X86_HT
         bool
         depends on SMP && !(X86_VISWS || X86_VOYAGER)
         default y

My dual athlon _definitely_ doesn't have hyperthreading, and I am 
willing to bet that force-enabling the ACPI boot and HT code for all SMP 
machines breaks other older-SMP boxes as well.

	Jeff





             reply	other threads:[~2004-03-05  4:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05  4:52 Jeff Garzik [this message]
2004-03-05  6:44 ` Hyper-threaded pickle Len Brown
2004-03-06 15:40   ` Jeff Garzik
2004-03-08  5:02     ` Len Brown
     [not found] <1wfBD-6GI-9@gated-at.bofh.it>
     [not found] ` <1whjQ-8sH-25@gated-at.bofh.it>
     [not found]   ` <1wMeo-Sr-3@gated-at.bofh.it>
     [not found]     ` <1xlbI-6Rl-5@gated-at.bofh.it>
2004-03-09 20:14       ` Bill Davidsen
2004-03-14  3:35       ` Andi Kleen

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=40480795.5000402@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.