Hi!
> > > > > Thanks for trying it out. I have quite accurate time here on my
> > > > > systems, and sleep works as it should. I wonder what's happening on
> > > > > your system? If you have a chance, could you please post the results
> > > > > from following simple tests?
> > > >
> > > > On patched 2.6.11-rc1:
> > > >
> > > > [Heh, clock is two times too fast, perhaps that makes ntpdate fail? --
> > > > yes.
> > > >
> > > > [EMAIL PROTECTED]:~# dmesg | grep -i time; for i in 1 2 3 4 5; do
> > > > ntpdate -b tak.cesnet.cz && sleep 10; done ; date && sleep 10 && date;
> > > > while [ 1 ]; do date; done | uniq
> > > > PCI: Setting latency timer of device 0000:00:11.5 to 64
> > > > dyn-tick: Enabling dynamic tick timer
> > > > dyn-tick: Timer using dynamic tick
> > >
> > > Thanks. Looks like you're running on PIT only, I guess my patch
> > > currently breaks PIT (and possibly HPET) No dmesg message for "
> > > "Using XXX for high-res timesource".
> >
> > This machine definitely has TSC... What do I have to do in .config to
> > make it do something interesting? My .config is:
>
> I suspect it's the HPET_TIMER, see below. CONFIG_X86_PM_TIMER is
> optional, otherwise TSC is used.
Okay, so I tried to measure power consumption. Patched kernel seems to
be about 200mW better. That's on 22W... I'll see if I can tweak ACPI
somehow to decrease it a bit more.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
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/
