Bug 10056 - PC becomes slow after processor ACPI module is loaded
Summary: PC becomes slow after processor ACPI module is loaded
Status: REJECTED UNREPRODUCIBLE
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Processor (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Venkatesh Pallipadi
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-20 12:16 UTC by Guennadi Liakhovetski
Modified: 2008-03-12 19:27 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.25-rc2
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Guennadi Liakhovetski 2008-02-20 12:16:48 UTC 
Latest working kernel version: unknown
Earliest failing kernel version: 2.6.22 (?)
Distribution: Debian Sarge / Etch
Hardware Environment: 2 x Pentium-II @ 400MHz, Compaq AP400
Software Environment: ---
Problem Description: As long as the processor ACPI module is loaded, the system becomes very slow, even slower than if only one CPU were running. If the driver is built in, the system is slow from the moment the module is initialized. See http://www.uwsg.indiana.edu/hypermail/linux/kernel/0802.0/0729.html

Steps to reproduce: modprobe the module
Comment 1 Len Brown 2008-02-20 19:21:40 UTC 
Please paste the output from this command sequence:
# cd /sys/devices/system/cpu
# grep . cpu*/cpufreq/*

Please attach the complete output from dmesg -s64000
Please attach the output from acpidump

> Earliest failing kernel version: 2.6.22 (?)

So this fails on all (ACPI enabled) versions of Linux tested?
Comment 2 Guennadi Liakhovetski 2008-02-25 04:22:59 UTC 
Len, thanks for taking your time to look at this. I initially reported this roblem around 2.6.24, then Andrew asked me to enter it into bugzilla. Now I cannot reproduce this problem with anything starting from 2.6.25-rc2. I'm changing this bug to "need more information" for now, will come back if I manage to reproduce it.

Thanks
Guennadi
Comment 3 Len Brown 2008-03-12 19:27:17 UTC 
please re-open if you are able to reproduce this with any recent kernel.
Note You need to log in before you can comment on or make changes to this bug.