> went ok. I wonder if something changed in acpi recently that caused this > change in behaviour ? Len ? Dave, I'm no expert but I think it was you that made this change in http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blobdiff;h=567b39bea07e4fbbe091b265b010905e3d30ff5a;hp=1a7bdcef19261deff5a7ea8ee13d5a8ddb434a19;hb=911cb74bb9e77e40749abc2fca6fe74d87d940f3;f=arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.c + /* Do initialization in ACPI core */ + acpi_processor_preregister_performance(acpi_perf_data); + return 0; +} :-) -- http://www.PowerDNS.com Open source, database driven DNS Software http://netherlabs.nl Open and Closed source services - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- From: bert hubert <[email protected]>
- Re: 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- From: Tomasz Torcz <[email protected]>
- Re: 2.6.17 -> 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- From: bert hubert <[email protected]>
- Re: 2.6.17 -> 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- From: Alexey Starikovskiy <[email protected]>
- Re: 2.6.17 -> 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- From: bert hubert <[email protected]>
- Re: 2.6.17 -> 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- From: Dave Jones <[email protected]>
- 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- Prev by Date: [BUG] sched: big numa dynamic sched domain memory corruption
- Next by Date: Re: ipw3945 status
- Previous by thread: Re: 2.6.17 -> 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- Next by thread: Re: 2.6.17 -> 2.6.18 regression: cpufreq broken since 2.6.18-rc1 on pentium4
- Index(es):
 |