From: Benjamin Herrenschmidt <bh40@calva.net>
To: Paul Schinder <schinder@pobox.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: pmac-time.c bug in 2.4.0-test3 (and still in -test8)
Date: Wed, 30 Aug 2000 18:54:29 +0200 [thread overview]
Message-ID: <20000830165429.22851@mailhost.mipsys.com> (raw)
In-Reply-To: <p04330100b5d2e13f47a5@[10.0.1.12]>
>
>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/
prev parent reply other threads:[~2000-08-30 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-30 16:21 pmac-time.c bug in 2.4.0-test3 (and still in -test8) Paul Schinder
2000-08-30 16:54 ` Benjamin Herrenschmidt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20000830165429.22851@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schinder@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).