On Fri, 16 Feb 2007 08:24:54 -0800, Daniel Walker wrote:
>On Fri, 2007-02-16 at 22:28 +0800, Adam J. Richter wrote:
>> My system clock runs at approximately half speed in
>> linux-2.6.20, 2.6.20-git10 and 2.6.20-git11.
[...]
>cat
On Fri, 2007-02-16 at 22:28 +0800, Adam J. Richter wrote:
> My system clock runs at approximately half speed in
> linux-2.6.20, 2.6.20-git10 and 2.6.20-git11. That is, it takes about
> two hours for "date" to report that one hour has elapsed. "hwclock"
> returns the correct time, of
My system clock runs at approximately half speed in
linux-2.6.20, 2.6.20-git10 and 2.6.20-git11. That is, it takes about
two hours for "date" to report that one hour has elapsed. "hwclock"
returns the correct time, of course.
I do not have this problem in linuux 2.6.18.1. I
My system clock runs at approximately half speed in
linux-2.6.20, 2.6.20-git10 and 2.6.20-git11. That is, it takes about
two hours for date to report that one hour has elapsed. hwclock
returns the correct time, of course.
I do not have this problem in linuux 2.6.18.1. I will
On Fri, 2007-02-16 at 22:28 +0800, Adam J. Richter wrote:
My system clock runs at approximately half speed in
linux-2.6.20, 2.6.20-git10 and 2.6.20-git11. That is, it takes about
two hours for date to report that one hour has elapsed. hwclock
returns the correct time, of course.
On Fri, 16 Feb 2007 08:24:54 -0800, Daniel Walker wrote:
On Fri, 2007-02-16 at 22:28 +0800, Adam J. Richter wrote:
My system clock runs at approximately half speed in
linux-2.6.20, 2.6.20-git10 and 2.6.20-git11.
[...]
cat /sys/devices/system/clocksource/clocksource0/current_clocksource
6 matches
Mail list logo