Comment 15 for bug 295091

Hi Andy,

I'll try your kernel in the next few days.

In the meantime, I've been wondering about the timestamps in the 2.6.24-23 kernel output: the kernel stops after a few seconds, but the timestamp reads 180: does that mean 3 minutes? If this is the case, the kernel timer is off by a factor ten w.r.t. real time. Is it possible that 2.6.24-23 fails to configure some hw timer? Perhaps wrong timings can explain problems in thread synchronization and spurious timeouts during device probes.

Is there anything I can do try other time sources or check that the source is working correctly?

-- g