From: Martin Costabel <costabel@wanadoo.fr>
To: linuxppc-dev@lists.linuxppc.org
Subject: pmac-time.c bug in 2.4.0-test3
Date: Sun, 09 Jul 2000 08:38:50 +0200 [thread overview]
Message-ID: <39681DFA.57D95536@wanadoo.fr> (raw)
In-Reply-To: 3965F335.42ABEEFD@erols.com
Symptom: Booting a recent 2.4.0-test3 kernel from bitkeeper gives me a
wrong system time. The corresponding boot message is, for example
Jul 7 06:54:51 chezmoi kernel: GMT Delta read from XPRAM: 0 minutes,
DST: off
This is 2 hours off.
Booting with 2.2.17pre10 gives me the correct message
Jul 8 12:10:05 chezmoi kernel: GMT Delta read from XPRAM: 120 minutes,
DST: on
Looking through my log files, I find that this has been the same
situation since the changes in pmac-time.c were introduced:
In Paul's pmac-stable 2.2.16 and then in 2.2.17-pre5 from bk (patch of
21 June, according to bk sccstool), this XPRAM stuff showed up and
worked correctly.
In the bk linuxppc_2_3 tree, this showed up in 2.4.0-test3 on 27/28 June
(according to my logs), and it did not work correctly. In addition to
the wrong reading of the initial system time, I get the following
message every 61 (!) seconds
Jun 29 01:27:31 chezmoi kernel: pmac_set_rtc_time: got 3 byte reply
Jun 29 01:28:32 chezmoi kernel: pmac_set_rtc_time: got 3 byte reply
Jun 29 01:29:33 chezmoi kernel: pmac_set_rtc_time: got 3 byte reply
and so on.
I tried to set CONFIG_PPC_RTC to y or n, but this didn't seem to have an
influence. Other ideas for debugging?
My system is still the old Pmac 6400.
--
Martin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-07-09 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-07 16:03 2.2.17pre10-ben1 & dmasound & atfb driver Iain Sandoe
2000-07-07 15:11 ` Nelson Abramson
2000-07-07 19:29 ` Claus Enneper
2000-07-09 6:38 ` Martin Costabel [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=39681DFA.57D95536@wanadoo.fr \
--to=costabel@wanadoo.fr \
--cc=linuxppc-dev@lists.linuxppc.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.