Package: chrony
Version: 1.20-6
Followup-For: Bug #294030

Note that I came to the same rtc vs. genrtc conclusion independently, so
it seems chrony+genrtc is indeed the culprit here.

You can solve your problem by creating /etc/modprobe.d/local (for
example) and putting

        alias char-major-10-135 rtc

as a line in that file.

I believe this is actually a bug in modutils.  Note how
/etc/modutils/arch/i386 has that exact alias at the end.  But
/etc/modprobe.d/arch/i386 does not.

Hence, when modutils moved to the new system -- where instead of
generating /etc/modules.conf, it actually directly reads files in
/etc/modprobe.d -- it had no explicit alias for that device.

Instead, it falls back on the contents of

        /lib/modules/`uname -r`/modules.alias

which contains *both* aliases for rtc and genrtc.  Somehow, the genrtc
one takes precedence, unless you have your own entry in modprobe.d.

To the maintainer:  This would appear to warrant bugs in both modutils
and possibly the kernel itself.  Unless chrony's usage of the RTC is
considered atypical or improper, genrtc causing freezes seems like a
bug in itself.

Even without the bug in genrtc, though, using a software RTC instead
of hardware RTC, when a hardware RTC is generally universal to i386
system and was the default before, is (IMO) a bug in modutils too.

Note that I have also seen the occasional console message about
'genrtc: lost 3 jiffies' which helped alert me to the issue.

HTH.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing'), (300, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)

Versions of packages chrony depends on:
ii  libc6                       2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libncurses5                 5.4-4        Shared libraries for terminal hand
ii  libreadline4                4.3-15       GNU readline and history libraries

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to