Bug 148081

Summary:	Gnome Frequency Scaling Monitor: Setting governor for cpu1 fails
Product:	Gentoo Linux	Reporter:	Markus Herhoffer <markus>
Component:	[OLD] GNOME	Assignee:	Gentoo Linux Gnome Desktop Team <gnome>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Markus Herhoffer 2006-09-18 09:21:10 UTC

If Gnome Frequency Scaling Monitor 2.14.2 is used twice for CoreDuo systems, the second instance (configured for cpu1) doesn't work properly while the first instance for cpu0 works fine:
- setting the governor for cpu1 fails; no error message
- setting the frequency for cpu1 fails; no error message

Setting the frequency/governor with cpufreq-set or directly with echo "foobar" > /dev/sys/devices/system/cpu/cpux/...../governor works perfectly for both cores.

Comment 1 Rémi Cardona (RETIRED) gentoo-dev

2007-03-04 23:16:05 UTC

Check your sysfs, cpu1 should be a symlink to cpu0 as both cores always run at the same speed iirc.

Thanks

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