Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#15207 - [kernel26] powersave-k8 set clock too low

Attached to Project: Arch Linux
Opened by Renan T. Fernandes (ShadowBelmolve) - Monday, 22 June 2009, 02:16 GMT
Last edited by Paul Mattal (paul) - Saturday, 07 November 2009, 23:36 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I have an Acer TravelMate 5210 notebook with a 1.80Ghz clock to accepting change for frequencies 800Mhz, 1.60Mhz and 1.80Mhz, usually use the "performance" that keeps the clock at 1.80Ghz
After some time of use (about 3 hours) the range of frequency drops to 800Mhz~1.08Ghz (my cpu does not support this) and the clock is at 800Mhz for about 5 ~ 10s (this creates a terrible lag), then the interval changes to 800Mhz~1.44Ghz clock remains at 800MHz, the lag decreases, about 3s then returns to normal.
To try to "fight" I make a while repeatedly sets the frequency, but the frequency during the bug can not be changed :(

Mobile AMD Sempron(tm) Processor 3500+
1Gb of RAM
Arch Linux is up to date with default kernel
This task depends upon

Closed by  Paul Mattal (paul)
Saturday, 07 November 2009, 23:36 GMT
Reason for closing:  Upstream
Comment by Gerardo Exequiel Pozzi (djgera) - Monday, 22 June 2009, 02:36 GMT
  • Field changed: Summary (powersave-k8 set clock too low → [kernel26] powersave-k8 set clock too low)
  • Field changed: Status (Unconfirmed → Assigned)
  • Task assigned to Tobias Powalowski (tpowa)
Looks like an upstream bug, please report to linux kernel mailing list or bugzilla ;)
Comment by Tobias Powalowski (tpowa) - Monday, 22 June 2009, 05:04 GMT
Are you running already 2.6.30 kernel?
Comment by Renan T. Fernandes (ShadowBelmolve) - Monday, 22 June 2009, 14:41 GMT
nop, kernel 2.6.29, kernel 2.6.30 conflicts with my catalyst-old driver, but at night I will remove it and upgrade kernel for test
Comment by Renan T. Fernandes (ShadowBelmolve) - Tuesday, 23 June 2009, 16:45 GMT
.30 is much worse, all time my freq still in 800Mhz-1.44Ghz and in certain times down to 800Mhz-800Mhz
I will try to compile my own kernel and see if this still
Ah, the module name is wrong, is powernow-k8 and not powersave-k8 :)
Comment by Renan T. Fernandes (ShadowBelmolve) - Thursday, 25 June 2009, 01:37 GMT
I've compiled the kernel from abs and disabled support for powernow-k6 and powernow-k7, and the problem turn equal to kernel .29
Is better than .30 defaul kernel bug :)
Comment by Roman Kyrylych (Romashka) - Saturday, 03 October 2009, 19:29 GMT
@Ranan: if I'm not mistaken the module does not set frequency by itself.
Do you use cpufrequtils or something like that?
Comment by Renan T. Fernandes (ShadowBelmolve) - Sunday, 04 October 2009, 18:44 GMT
yes, I change with command cpufreq-set and see with cpufreq-info, but, I think isn't a daemon running, how this app can change de freq without running?
//I don't start /etc/rc.d/cpufreqd

Loading...