RTC Bug on Indy?

[Edwin Kwan <ekwan@rawbw.com>]

Hi,

	I have installed "woody" on an SGI Indy.  "uname -r"
gives 2.4.16.

	I noticed a problem with the "Hardware Clock".  Looks
like "hwclock" could not read an hour value >= 20 (and <=23 of
course).  Writing it seems to be okay.  Please see the log 
below.

	As a result, the system time is screwed up whenever
I boot up the machine between 8pm and midnight. :)  I glanced
through the "hwclock" source code a bit, and I suspect this is
a bug in the kernel (ioctl call).  Right?  Which version has
this fixed?  Any other suggestion?

	Thanks!


gundam:~# hwclock --set --date="09/17/03 23:59:45"
gundam:~# hwclock --debug --show
hwclock 2.4c/util-linux-2.11n
Using /dev/rtc interface to clock.
Last drift adjustment done at 1063868385 seconds after 1969
Last calibration done at 1063868385 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
/dev/rtc does not have interrupt functions. Waiting in loop for time
from /dev/rtc to change
...got clock tick
Time read from Hardware Clock: 2003/09/17 03:59:53
Hw clock time : 2003/09/17 03:59:53 = 1063796393 seconds since 1969
Wed Sep 17 03:59:53 2003  -0.614611 seconds
gundam:~# hwclock --debug --show
hwclock 2.4c/util-linux-2.11n
Using /dev/rtc interface to clock.
Last drift adjustment done at 1063868385 seconds after 1969
Last calibration done at 1063868385 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
/dev/rtc does not have interrupt functions. Waiting in loop for time
from /dev/rtc to change
...got clock tick
Time read from Hardware Clock: 2003/09/17 03:59:59
Hw clock time : 2003/09/17 03:59:59 = 1063796399 seconds since 1969
Wed Sep 17 03:59:59 2003  -0.077334 seconds
gundam:~# hwclock --debug --show
hwclock 2.4c/util-linux-2.11n
Using /dev/rtc interface to clock.
Last drift adjustment done at 1063868385 seconds after 1969
Last calibration done at 1063868385 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
/dev/rtc does not have interrupt functions. Waiting in loop for time
from /dev/rtc to change
...got clock tick
Time read from Hardware Clock: 2003/09/18 00:00:03
Hw clock time : 2003/09/18 00:00:03 = 1063868403 seconds since 1969
Thu Sep 18 00:00:03 2003  -0.212929 seconds
gundam:~#