mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kathy Frazier" <kfrazier@mdc-dayton.com>
To: "Mike Dresser" <mdresser_l@windsormachine.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: [APM]  CPU idle calls causing problem with ASUS P4PE MoBo
Date: Thu, 7 Aug 2003 11:40:12 -0500	[thread overview]
Message-ID: <PMEMILJKPKGMMELCJCIGOEPPCDAA.kfrazier@mdc-dayton.com> (raw)
In-Reply-To: <Pine.LNX.4.56.0308071108110.18325@router.windsormachine.com>

Mike,

Actually, using APM was not done on purpose.  It was configured in already
from our Red Hat 9 install.  We really don't need any Power Management at
all, since it is not a lap top.  I have not tried the ACPI at all.  I did
try the allow_ints feature (test #5), but it still locked up.  From this
test I gathered that it was not some "cli" that was never undone.  So maybe
the BIOS hoses something?

>5) Power Management disabled in BIOS							locked up after a few minutes
>   Kernel configured with CONFIG_APM_CPU_IDLE_CALLS=y
>   Kernel parameter passed in: amp=allow_ints

Kathy


-----Original Message-----
From: Mike Dresser [mailto:mdresser_l@windsormachine.com]
Sent: Thursday, August 07, 2003 10:11 AM
To: Kathy Frazier
Cc: linux-kernel@vger.kernel.org
Subject: Re: [APM] CPU idle calls causing problem with ASUS P4PE MoBo


<snip>

I'm curious why you are using the APM method.

Have you tried ACPI(which replaced APM a long time ago)

And also out of curiosity, have you played with the config_apm_allow_ints?

Mike


  reply	other threads:[~2003-08-07 15:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07 16:08 Kathy Frazier
2003-08-07 15:10 ` Mike Dresser
2003-08-07 16:40   ` Kathy Frazier [this message]
2003-08-07 15:38 ` Herbert Pötzl
2003-08-07 16:57 ` Arjan van de Ven
2003-08-07 19:46   ` Kathy Frazier
2003-08-07 19:43     ` Arjan van de Ven
2003-08-07 21:44       ` Kathy Frazier

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=PMEMILJKPKGMMELCJCIGOEPPCDAA.kfrazier@mdc-dayton.com \
    --to=kfrazier@mdc-dayton.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdresser_l@windsormachine.com \
    /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

all inboxes | Powered by JetHome®