Johannes Weiner wrote:
Hi,
Stephen Clark <[email protected]> writes:
userspace
Please supply the full dmesg output on the non-working kernel the
corresponding .config (or /proc/config.gz).
Added Dave to CC.
Hannes
Duh - I rebooted into the new kernel and no longer see the behavior I
described above. Maybe I had something going in
the background i didn't realize. Thing was I even started a bash empty
while loop to see if /proc/cpuinfo speed would go
up and it did.
I have an applet that displays on my kde kicker panel that every 2
seconds reads /sys/.../cpuinfo_cur_freq and it was
sitting on the max speed all the time. Hmmm.
Well Thanks for the response and sorry for the false alarm.
Steve
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]