On 07/17/2013 06:14 PM, Michael Cree wrote: > Tested the patch series applied against 3.10.1 on a 3-CPU ES45. System came > up fine but I noticed date was wrong and had been reset back to the start > of the epoch (Jan 1 1970). Appears it is not reading hardware clock > correctly on boot. Please scan the dmesg for the "Using epoch 2000 for rtc year 13" line, and compare vs a similar message on the previous kernel. > I manually set the clock to the correct time but noticed it is running slow, > indeed in a period of 60s the system clock incremented by 21s (+/-1s) so > would appear clock is running slow by a factor given by the number of CPUs. That's curious. I wonder if somehow I botched the smp changes, and I'm not getting the timer interrupt either (1) enabled or (2) registered on the secondary cpus... Perhaps /proc/interrupts will confirm or deny this? r~ -- To unsubscribe from this list: send the line "unsubscribe linux-alpha" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
