Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 139861 - kernel frequency scalling bug
Summary: kernel frequency scalling bug
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-10 05:01 UTC by GNUtoo
Modified: 2007-01-23 21:47 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description GNUtoo 2006-07-10 05:01:34 UTC
port3 cpufreq # echo 700000>scaling_setspeed
bash: 700000: Bad file descriptor
port3 cpufreq # echo 700000 >scaling_setspeed
port3 cpufreq #

i don't know if it's a bug but usualy > works well without any space
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-07-10 05:17:50 UTC
Please, try w/ gentoo-sources-2.6.17-r2 (and/or latest vanilla) and report back. If it still doesn't work, attach your kernel .config and post emerge --info.
Comment 2 GNUtoo 2006-11-27 08:01:19 UTC
i tryed with 2.6.19-rc6 and there is the same bug
Comment 3 Daniel Drake (RETIRED) gentoo-dev 2006-12-08 17:45:15 UTC
Please compile CONFIG_CPU_FREQ_DEBUG into your kernel and boot with the  cpufreq.debug=3 parameter.

Run "dmesg" and note the last line of output. Then, "echo 700000>scaling_setspeed" and see which lines were added at the end. Then run the echo again, and see which extra lines appeared in dmesg that time.

Finally, save dmesg to a file and annotate it where you saw those events happening. Then attach it here :)
Comment 4 Daniel Drake (RETIRED) gentoo-dev 2006-12-25 15:29:06 UTC
see comment #3
Comment 5 GNUtoo 2006-12-26 10:15:00 UTC
(In reply to comment #3)
> Please compile CONFIG_CPU_FREQ_DEBUG into your kernel and boot with the 
> cpufreq.debug=3 parameter.
> 
> Run "dmesg" and note the last line of output. Then, "echo
> 700000>scaling_setspeed" and see which lines were added at the end. Then run
> the echo again, and see which extra lines appeared in dmesg that time.
> 
> Finally, save dmesg to a file and annotate it where you saw those events
> happening. Then attach it here :)
> 
when i do echo 1000000>scalling_setspeed it doesn't add anything to dmesg
but when i do echo 1000000 >scalling_setspeed it does add this:
pufreq-core: target for CPU 0: 1000000 kHz, relation 0
freq-table: request for target 1000000 kHz (relation: 0) for cpu 0
freq-table: target is 0 (1000000 kHz, 0)
speedstep-lib: P3 - MSR_IA32_EBL_CR_POWERON: 0xc6480020 0x0
speedstep-lib: speed is 700000
speedstep-ich: detected 700000 kHz as current frequency
speedstep-ich: transiting from 700000 to 1000000 kHz
cpufreq-core: notification 0 of frequency transition to 1000000 kHz
cpufreq-core: saving 2793664 as reference value for loops_per_jiffy; freq is 700000 kHz
cpufreq-core: scaling loops_per_jiffy to 3990948 for frequency 1000000 kHz


Comment 6 Daniel Drake (RETIRED) gentoo-dev 2006-12-30 18:13:36 UTC
Hmm actually I think it's much simpler than that.

Try:

    echo "700000" > scaling_setspeed

note the "" marks
Comment 7 Daniel Drake (RETIRED) gentoo-dev 2007-01-23 21:47:46 UTC
reopen if my judgement in comment #6 is wrong