From: "Remy Bohmer" <l.pinguin@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG-RT] RTC has been stopped-> long delay during boot, soft reboot->GRUB fails to call getrtsecs()
Date: Tue, 2 Jan 2007 17:38:51 +0100 [thread overview]
Message-ID: <3efb10970701020838n61db5388l94b2f0ed38073edd@mail.gmail.com> (raw)
In-Reply-To: <20070102161608.GA19214@elte.hu>
Hello Ingo,
In the mean time I have tested more with this problem:
1. Once, the RTC clock gets stopped during shutdown, it is **NEVER**
going to run again.
And I continuously see the problems with grub and the BIOS
time-of-day. Finally I had to remove the battery from the motherboard
to reset the RTC clock (Nothing else worked, even total poweroff). Now
it is ticking again... until...
2. Using a kernel without CONFIG_NO_HZ seems to solve all the problems
with the RTC clock, even hwclock functions normally.
With CONFIG_NO_HZ enabled, the problem with hwclock **only** occurs
when it is called for the first time by the init scripts, directly
after kernel boot. Every sub sequential call to hwclock show normal
times like your measurement.
Best Regards and also a Happy New Year,
Remy
2007/1/2, Ingo Molnar <mingo@elte.hu>:
>
> * Remy Bohmer <l.pinguin@gmail.com> wrote:
>
> > Hello Ingo,
> >
> > I have discovered 3 problems that are likely all related to the same
> > root-cause, likely to be caused by the RT-kernel.
> > I use the 2.6.19-rt15 kernel, with the configuration attached to this mail.
> > It is running on a standard x86, i945, Celeron 2.93 GHZ (=UP), Fedora Core 6
> >
> > So, I have set the following options:
> > CONFIG_HIGH_RES_TIMERS=y
> > CONFIG_NO_HZ=y
> >
> > The problems:
> > 1. During (cold and warm) boot the synchronisation of the hardware
> > clock takes often very long time, up to approx. 30 seconds. (This is
> > the call: /sbin/hwclock --hctosys --localtime)
>
> i tried this on a recent -rt kernel and there's no delay:
>
> [root@europe ~]# time /sbin/hwclock --hctosys --localtime
>
> real 0m0.756s
> user 0m0.754s
> sys 0m0.002s
>
> could you try a more recent kernel like 2.6.20-rc2-rt3? We fixed a good
> number of high-res timers related bugs that could result in similar
> hangs. But maybe it's still unfixed, it's just a guess.
>
> Ingo
>
>
next prev parent reply other threads:[~2007-01-02 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-02 14:01 Remy Bohmer
2007-01-02 16:16 ` Ingo Molnar
2007-01-02 16:38 ` Remy Bohmer [this message]
[not found] <459E2F97.3040201@wis.kuleuven.be>
2007-01-05 12:43 ` Remy Bohmer
2007-01-05 16:27 ` Remy Bohmer
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=3efb10970701020838n61db5388l94b2f0ed38073edd@mail.gmail.com \
--to=l.pinguin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@bohmer.net \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®