Comment 4 for bug 21814

Yes booting from old kernels 2.6.10-5-686 and 2.6.11-1-686 are both fine, when I
go back to 2.6.12-8-686 the problems start again. I can find an error that is
produced whenever the freeze happens - if I switch to a text console just before
it freezes, the following is echod to the console:
cpufreq: change failed with new_state 1 and result 0

Looking at my frequency monitor applet, I can see that the freeze co-incides
with the CPU stepping down from 1.8 GHz to 1.2 GHz (the two speeds my machine
operate at).

I have attached dmesg outputs from old and new kernels as per your request.