Bug 446298

Summary:	amd cool n quiet does not work well with recent kernel
Product:	[Fedora] Fedora	Reporter:	Martin Jürgens <ma>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	9	CC:	nhorman
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-05-18 14:49:53 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Jürgens 2008-05-13 23:16:35 UTC

Description of problem:
I have AMD cool n quiet activated in my kernel. I noticed starting from a later
kernel release in rawhide (2.6.25 or later) that this causes some problems. For
example, when I am surfing using Firefox, the cpu is set to 1 GHz, but sometimes
Firefox hangs, and instead of getting 1,8 GHz out of my cpu, it just stays at 1
GHz which is why Firefox hangs.

i had a similar problem with Fedora 7 which was fixed by some kernel update.

Comment 1 Dave Jones 2008-05-13 23:25:14 UTC

it'd be interesting to know what firefox is doing when it hangs.
If it's blocking on network or disk, then that would explain it, as raising the
CPU speed wouldn't change the situation.

Can you strace it, and observe what it's doing when it hangs ?

Comment 2 Martin Jürgens 2008-05-13 23:34:35 UTC

I'll do it tomorrow. I have the feeling that it appears often when scrolling and
only when having booted up. As soon as I surf for 15 minutes, I never encounter
the lags to the next restart.

I'll also check some older kernels, I think that it did not happen with
2.6.25-1. Maybe some realtime thingies?

Comment 3 Martin Jürgens 2008-05-18 14:49:53 UTC

Well, it is more likely due to a bug in Firefox and has nothing to do with the previous bug. I'll wait for RC1 
flow in to Fedora and then reopen it if needed (there were reports that it was a bug in FF)