All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: linux@bohmer.net
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:16:08 +0100	[thread overview]
Message-ID: <20070102161608.GA19214@elte.hu> (raw)
In-Reply-To: <3efb10970701020601i13dd3809y56c2c6aafeb228b@mail.gmail.com>


* 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

  reply	other threads:[~2007-01-02 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-02 14:01 [BUG-RT] RTC has been stopped-> long delay during boot, soft reboot->GRUB fails to call getrtsecs() Remy Bohmer
2007-01-02 16:16 ` Ingo Molnar [this message]
2007-01-02 16:38   ` Remy Bohmer
     [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=20070102161608.GA19214@elte.hu \
    --to=mingo@elte.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@bohmer.net \
    /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.