All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Schlichter <thomas.schlichter@web.de>
To: "Prakash K. Cheemplavam" <PrakashKC@gmx.de>
Cc: Len Brown <len.brown@intel.com>,
	john stultz <johnstul@us.ibm.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	Dominik Brodowski <linux@brodo.de>
Subject: Re: ACPI PM Timer vs. C1 halt issue
Date: Thu, 11 Mar 2004 14:46:52 +0100	[thread overview]
Message-ID: <200403111446.53470.thomas.schlichter@web.de> (raw)
In-Reply-To: <40502794.60907@gmx.de>

Am Donnerstag, 11. März 2004 09:47 schrieb Prakash K. Cheemplavam:
> Thomas Schlichter wrote:
> > you may try to boot with ACPI PM timer enabled but with the additional
> > boot option 'noapic'. If this also cools down your processor, you maybe
> > should try the attached patch....
>
> I am currently not using APIC, so above wouldn't make a difference.

I just thought you use an APIC because the .config you sent contains:
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y

But you're right, if you don't use an APIC, my patch makes no difference...

   Thomas


  reply	other threads:[~2004-03-11 13:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09 21:35 ACPI PM Timer vs. C1 halt issue Prakash K. Cheemplavam
2004-03-09 22:11 ` john stultz
2004-03-09 22:45   ` Prakash K. Cheemplavam
2004-03-10 21:49     ` john stultz
2004-03-10 22:11       ` Len Brown
2004-03-10 22:48         ` Prakash K. Cheemplavam
2004-03-11  0:15           ` Thomas Schlichter
2004-03-11  8:47             ` Prakash K. Cheemplavam
2004-03-11 13:46               ` Thomas Schlichter [this message]
2004-03-11 14:23                 ` Prakash K. Cheemplavam
2004-03-10 22:53         ` Prakash K. Cheemplavam
2004-03-11 18:14         ` Prakash K. Cheemplavam

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=200403111446.53470.thomas.schlichter@web.de \
    --to=thomas.schlichter@web.de \
    --cc=PrakashKC@gmx.de \
    --cc=akpm@osdl.org \
    --cc=johnstul@us.ibm.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@brodo.de \
    --cc=torvalds@osdl.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.