pmac-time.c bug in 2.4.0-test3 (and still in -test8)

[Benjamin Herrenschmidt]

>
>Aug 30 09:50:01 c22234-c kernel: pmac_set_rtc_time: got 3 byte reply
>Aug 30 09:51:00 c22234-c kernel: pmac_set_rtc_time: got 3 byte reply
>
>etc., once per minute.
>
>This is on a Performa 6400/180.  I don't see it in Paul's test6.  It
>doesn't seem to be a real problem except for the excessive logging,
>since the clock seemed accurate (xntpd is running).  Does anyone know
>what's happening and how to shut it up?  CONFIG_PPC_RTC was n for all
>of these kernels.

This message is logged by code in arch/ppc/kernel/pmac_time.c, you can
comment it out. It appears that we get various reply length from Cuda and
our original test didn't always work.

The CONFIG_PPC_RTC will only enable the userland device /dev/rtc. The
basic RTC read code is still there.

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/