Comment 74 for bug 157777

Still happening with vmlinuz-2.6.24-19-generic. One thing I've just noticed, printk() output in dmesg has a timestamp at the start of the line. It should be seconds since booting but this machine is consistently running at about 1600 "seconds" an hour. Could this be connected? Some kind of CPU power-saving causing problems? Or a separate bug? I've now got the netconsole module running with a second machine logging and /proc/sys/kernel/printk set to 9 and /proc/sys/kernel/printk_ratelimit to 0 so I'm hoping SysRq key will work on the next lock-up.