From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] kacpidpc process takes 100% of CPU
Date: Tue, 13 Nov 2001 17:57:01 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805495@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805494@msgid-missing>
>>>>> On Tue, 13 Nov 2001 09:43:52 -0800, "Paris, DavidX" <davidx.paris@intel.com> said:
>> I've just built 2.4.13 and 2.4.14 with and without the KDB patch
>> and in all cases when the system comes up there is a kacpidpc
>> process (PID 10) taking 100% of one of the cpus (changes which
>> CPU it's on every boot). The system is a 4 processor Lion (733
>> Mhz B3) with 1 gig of ram. This process isn't even running when I
>> build the same kernels on a BigSpur. I've even tried copying over
>> the very kernel that works fine on the BigSpur, but when I boot
>> it on the Lion I get this kacpidpc process. Naturally the process
>> ignores my 'kill -9's. I've tried booting the kernel on single
>> proc Lions (733 C0s), but the kernel won't even boot on those
>> systems (hangs right after it loads the SCSI driver is begins
>> looking for devices). Does anyone have any idea why this kacpidpc
>> process is hogging one of the CPUs, and how I go about getting
>> rid of it? Unlike in the IA32 kernels, it doesn't look like you
>> can turn off ACPI in the IA64 kernel. Thanks,
What ACPI configuration do you use? In my kernels, I turn on the
following ACPI related configs:
CONFIG_ACPI=y
CONFIG_ACPI_EFI=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_KERNEL_CONFIG=y
All other ACPI stuff I turn off.
What firmware are you using? In my experience, Lions need build 99 or
newer.
--david
next prev parent reply other threads:[~2001-11-13 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 17:43 [Linux-ia64] kacpidpc process takes 100% of CPU Paris, DavidX
2001-11-13 17:57 ` David Mosberger [this message]
2001-11-13 18:13 ` Paris, DavidX
2001-11-13 19:20 ` Grover, Andrew
2001-11-13 20:41 ` Paris, DavidX
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=marc-linux-ia64-105590698805495@msgid-missing \
--to=davidm@hpl.hp.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox