360201 – cpufreq broken after updating kernel to 2.6.22.16-02

Bug 360201 - cpufreq broken after updating kernel to 2.6.22.16-02

Summary: cpufreq broken after updating kernel to 2.6.22.16-02

Status:	RESOLVED DUPLICATE of bug 357598

Alias:	None

Product:	openSUSE 10.3
Classification:	openSUSE
Component:	Kernel (show other bugs)
Version:	Final
Hardware:	i586 openSUSE 10.3

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	Thomas Renninger
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2008-02-08 21:40 UTC by Mathieu JUCKER
Modified:	2008-02-14 10:56 UTC (History)
CC List:	0 users

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

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

Note You need to log in before you can comment on or make changes to this bug.

Description Mathieu JUCKER 2008-02-08 21:40:38 UTC

Hi,
After installation of the last kernel patch 2.6.22.16-02, cpufreq doesn't work correctly on my laptop. I have the same behavior as bug #357598 fixed by this patch.

To fix it, i need to reload acpi_cpufreq and set freq governance to "onDemand".
Laptop:asus W7J dual core


Here is the log found in /var/log/messages

Feb  8 21:18:44 localhost kernel: klogd 1.4.1, log source = /proc/kmsg started.
Feb  8 21:18:44 localhost kernel: IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk>
Feb  8 21:18:44 localhost kernel: powernow: This module only works with AMD K7 CPUs
Feb  8 21:18:44 localhost kernel: ACPI Exception (exoparg2-0442): AE_AML_PACKAGE_LIMIT, Index (0FFFFFFFC) is beyond end of object [20070126]
Feb  8 21:18:44 localhost kernel: ACPI Error (psparse-0537): Method parse/execution failed [\_PR_.CPU1._PSS] (Node dffda9dc), AE_AML_PACKAGE_LIMIT
Feb  8 21:18:44 localhost kernel: ACPI Exception (processor_perflib-0234): AE_AML_PACKAGE_LIMIT, Evaluating _PSS [20070126]

Comment 1 Thomas Renninger 2008-02-14 10:56:51 UTC

Hmm, the message is slightly different, than the others.
Please check whether this is fixed with the very latest update kernel.
If not, you see another problem (then pls reopen this bug).

*** This bug has been marked as a duplicate of bug 357598 ***