linux-kernel - [BUG-RT] RTC has been stopped-> long delay during boot, soft reboot->GRUB fails to call getrtsecs()

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <3efb10970701020601i13dd3809y56c2c6aafeb228b@mail.gmail.com>
Date:	Tue, 2 Jan 2007 15:01:37 +0100
From:	"Remy Bohmer" <l.pinguin@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: [BUG-RT] RTC has been stopped-> long delay during boot, soft reboot->GRUB fails to call getrtsecs()

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)
2. After reboot the next boot into grub hangs on the getrtsecs() call
(in Grub 0.97 code). (RTC clock does not run or has been stopped by
the last boot)
3. After the same reboot, looking into the BIOS, the time-of-day clock
is stopped also (system clock).

Do you recognise this problem?
Can it be related to the CONFIG_NO_HZ option?

Notice that we do not call "hwclock  --systohc" on shutdown or reboot
to sync the hardware clock. Does this call also restart the RTC clock
normally? (If it does, I think this would be strange (I believe that
if the kernel itself stops the RTC, it has to restarted by the kernel
also), otherwise it is probably not allowed to execute this command
during normal runtime)

Kind Regards,

Remy Bohmer

Download attachment "kernel-i686.config" of type "application/octet-stream" (36437 bytes)