From: Olaf Hering <olh@suse.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>,
Roger Leigh <rleigh@whinlatter.ukfsn.org>,
debian-powerpc@lists.debian.org
Subject: Re: 2.6.16-rc2 powerpc timestamp skew
Date: Sun, 12 Feb 2006 20:55:15 +0100 [thread overview]
Message-ID: <20060212195514.GA18521@suse.de> (raw)
In-Reply-To: <87pslspkj5.fsf@hardknott.home.whinlatter.ukfsn.org>
On Sun, Feb 12, Roger Leigh wrote:
> In both these cases, the chrony NTP daemon is running, if that might
> be a problem.
I dont run Debian, but:
My G4/466 has the hwclock at 1970 for some reason. The early bootscripts
call klogd, which calls nanosleep. This syscall takes 3 hours to complete.
A bit userland debugging shows that hwclock is 1970, system time is also
1970 when nanosleep starts. But when it returns, the time is correct.
Its already at the end of the /etc/init.d/boot.d/S* scripts, nothing
else runs there. Bug exists since at least 2.6.15-git12, 2.6.15 was ok.
Fatfingerd kernel debug patch and lost remote access...
next prev parent reply other threads:[~2006-02-12 19:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 17:13 2.6.16-rc2 powerpc timestamp skew Roger Leigh
2006-02-12 17:39 ` Gabriel Paubert
2006-02-12 17:58 ` Roger Leigh
2006-02-12 20:15 ` Bin Zhang
2006-02-12 19:55 ` Olaf Hering [this message]
2006-02-13 10:57 ` Olaf Hering
2006-02-13 12:51 ` Olaf Hering
2006-02-12 21:33 ` Benjamin Herrenschmidt
2006-02-13 18:34 ` Roger Leigh
2006-02-13 22:34 ` Benjamin Herrenschmidt
2006-02-15 5:27 ` Paul Mackerras
2006-02-15 10:30 ` Olaf Hering
2006-02-15 11:53 ` Mikael Pettersson
2006-02-16 11:30 ` Roger Leigh
2006-02-13 0:13 ` Andrew Morton
2006-02-13 0:41 ` Roger Leigh
2006-02-13 4:00 ` [PATCH] powerpc: dont allow old RTC to be selected Anton Blanchard
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=20060212195514.GA18521@suse.de \
--to=olh@suse.de \
--cc=benh@kernel.crashing.org \
--cc=debian-powerpc@lists.debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rleigh@whinlatter.ukfsn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox