From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Paul Rolland <rol@as2917.net>, "'Randy.Dunlap'" <rddunlap@osdl.org>
Cc: "'Andrew S. Johnson'" <andy@asjohnson.com>, linux-kernel@vger.kernel.org
Subject: Re: [2.5.54 + ACPI] Slow [Was: Re: [2.5.53] So sloowwwww......]
Date: Sun, 05 Jan 2003 16:59:05 -0800 [thread overview]
Message-ID: <173080000.1041814744@titus> (raw)
In-Reply-To: <013701c2b4f2$3f3e0670$2101a8c0@witbe>
>> | | acpi= kernel parameters, I tried :
>> | | - acpi=no-idle
>> |
>> | This one (above) is the correct syntax.
>> | Looking at the code, it only takes effect if you are using
>> only 1 CPU.
>>
>> Sorry, I was looking at old source code.
>> apm=no-idle isn't in 2.5.54.
>
> Too bad...
> Does this mean there is no easy way to have ACPI running correctly
> on my machine ?
> If anyone knows ACPI code, please tell me if you want me to run
> some specific code to understand what's going on...
I've seen this in multiple different places, and it seems to be a royal
pain in the butt. Could you log this in Bugzilla (bugme.osdl.org) so
we can track it and get it fixed? I started to log it myself, but realised
I don't really have the required information, or the data to reproduce it.
Bugs logged under Power Mangement / ACPI will automatically go to the ACPI
maintainer ...
Oh, and if you could dump /proc/interrupts, that might help ... last time
I recall some conversation about it generating millions of interrupts,
though that might be fixed by now ...
Thanks,
M
next prev parent reply other threads:[~2003-01-06 0:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.el8u04v.1jks783@ifi.uio.no>
[not found] ` <fa.f29f77v.on2i97@ifi.uio.no>
2003-01-02 7:26 ` [2.5.53] So sloowwwww Andrew S. Johnson
2003-01-05 14:19 ` [2.5.54 + ACPI] Slow [Was: Re: [2.5.53] So sloowwwww......] Paul Rolland
2003-01-05 19:11 ` Randy.Dunlap
2003-01-05 19:34 ` Randy.Dunlap
2003-01-05 19:40 ` Paul Rolland
2003-01-05 19:46 ` Randy.Dunlap
2003-01-06 0:59 ` Martin J. Bligh [this message]
2003-01-06 7:24 ` Paul Rolland
2003-01-06 3:08 ` Bill Davidsen
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=173080000.1041814744@titus \
--to=mbligh@aracnet.com \
--cc=andy@asjohnson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=rol@as2917.net \
/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