Skip to contentSkip to conversation

ACPI P-States vs Longhaul

DISCUSSION Rafał Bilski 2 participants 2 messages Nov 20, 2006

lore
Share & tools
lore
#0 lore raw

Hello,

I know that a lot has changed since 2.6.18 in "ACPI P-States" driver, but I wasn't paing attention. Just in case if this issue isn't known. Reported by user. System: VIA Epia SP13000 (VIA C3-2 "Nehemiah" 6.9.8)
Kernel: 2.6.18.2 custom config, apci-cpufreq=m, longhaul=m
Issue:
"ACPI P-States driver" is loaded (by distro) and stays loaded. When user try to load "Longhaul" CPU is already owned by other driver and "Longhaul" fails with -EBUSY. Of course rmmod does the trick. But why acpi-cpufreq didn't failed? This processor don't support P-states. Sadly "Longhaul" don't work too. No ACPI C3 support in BIOS and CN400 chipset on mainboard.

Regards
Rafa³

----------------------------------------------------------------------
PS. >>> http://link.interia.pl/f19a6

#1 lore raw
Quoted 15 lines · RafaÅ‚ Bilski

Hello,

I know that a lot has changed since 2.6.18 in "ACPI P-States" driver, but I wasn't paing attention. Just in case if this issue isn't known. Reported by user.
System: VIA Epia SP13000 (VIA C3-2 "Nehemiah" 6.9.8)
Kernel: 2.6.18.2 custom config, apci-cpufreq=m, longhaul=m Issue:
"ACPI P-States driver" is loaded (by distro) and stays loaded. When user try to load "Longhaul" CPU is already owned by other driver and "Longhaul" fails with -EBUSY. Of course rmmod does the trick. But why acpi-cpufreq didn't failed? This processor don't support P-states.
Sadly "Longhaul" don't work too. No ACPI C3 support in BIOS and CN400 chipset on mainboard.

Probably due to the 'sticky' bug that was fixed in 2.6.18.3

Dave

Signature · 1 line
http://www.codemonkey.org.uk