https://bugzilla.novell.com/show_bug.cgi?id=436717
User rob.opensuse.linux@googlemail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=436717#c10
Robert Davies changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
Info Provider|mdrolc@gmail.com |
Priority|P1 - Urgent |P3 - Medium
--- Comment #10 from Robert Davies 2008-12-23 12:26:05 MST ---
fir:~ # cat /proc/acpi/thermal_zone/THRM/{temperature,trip_points}
temperature: 15 C
critical (S5): 95 C
passive: 75 C: tc1=4 tc2=3 tsp=60 devices=CPU0
active[0]: 75 C: devices= FAN
The good news is, I've seen it bump up from 1000 sometimes.
This is what I'm running, 2 long running md5sum's simultaneously, so almost all
the time, there's no output because it's stuck on 1,000 Mhz but some of the
time it does get up to max speed, but rarely.
while (true); do cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq |
grep -v 1000000; done
It's not locked to the lowest speed. What's happening is that it's on the
lowest speed, even if there's only 30% idle time on both CPUs (1 doing i/o
wait, the other blocking on i/o idle which makes sense).
What I would expect is for the CPU to be on max frequency, and go idle, rather
than go slow, and idle less for max power saving.
There's obviously sampling problems here, because if it's at lowest frequency
when idle, and then you get a chance to sample the speed it's going to mostly
sample when it's going slow.
2 simultaneous, "cat /dev/urandom | md5sum" put the frequency up to the max
reliably. top shows less than < 0.1% idle time on both CPUs.
So I would say the bug I'm seing is the reported frequency from /proc/cpuinfo
and the bogomips value, also the way the current frequency works.
So now frankly I'd want better evidence, that this is a real performance issue,
due to CPUFREQ and not just the kernel reporting information in a way that
"disturbs" the user.
I would suggest to lower the priority, and panic over. Personally if this
becomes my bug, I'd change title to CPU speed reporting locked.
It'd be better if the recent_max_freq was reported, something like the highest
freq used, in the last 2 seconds. Because it does give the impression that it
runs slow almost all the time.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.