Dear Alain,
thank you for your response. Am Sonntag, den 13.04.2008, 19:52 +0200 schrieb Alain Guibert: > On Thursday, April 10, 2008 at 9:42:45 +0200, Paul Menzel wrote: > > > I am experiencing this problem, too. > > It can be a hardware bug, a kernel bug, or something else. What is your > computer exactly? The motherboard is an ASUS P4C 800-E Deluxe. What other information do you need? > And what is the output of: > > | # hwclock --rtc=/dev/rtc0 --debug $ LANG=C sudo hwclock --rtc=/dev/rtc0 --debug hwclock from util-linux-ng 2.13.1 hwclock: Open of /dev/rtc0 failed, errno=2: No such file or directory. Using direct I/O instructions to ISA clock. Last drift adjustment done at 1208104267 seconds after 1969 Last calibration done at 1208104267 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ...got clock tick Time read from Hardware Clock: 2008/04/13 20:31:03 Hw clock time : 2008/04/13 20:31:03 = 1208118663 seconds since 1969 Sun Apr 13 22:31:03 2008 -0.130754 seconds $ LANG=C sudo hwclock --rtc=/dev/rtc --debug hwclock from util-linux-ng 2.13.1 Using /dev interface to clock. Last drift adjustment done at 1208104267 seconds after 1969 Last calibration done at 1208104267 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... select() to /dev/rtc to wait for clock tick timed out ...got clock tick > > Since some people say, this bug should be fixed in Linux, maybe this > > report should be reassigned? > > The same timeout symptom can hide different problems. Only one of these > problems is a kernel /dev/rtc device driver bug. We can imagine various > possible workarounds, in hwclock install, or in Debian kernel setup. > But the real fix is for the kernel, right. Understood. Thanks, Paul
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
