rtc not behaving in etch?
[There seems to be a problem with the RTC and the kernel in Etch. I thought
I'd run this by the list before I filed a bug report. This is combination of
a repost (of a post that originally went to debian-user, and got no response)
and a post to the VMWare forums, which is where I tracked part of this
problem down.]
During boot on my Etch machine (Dell PowerEdge 830 with an Intel Pentium D CPU
2.80GHz, kernel 2.6.16-2-686-smp), there is a message about select() timing
out on /dev/rtc. That message displays twice, a few more messages, then
there is a message about "trying to set the system clock again." I've looked
through the syslog and dmesg, and these messages are not in there. Or else
I'd post the exact messages. :)
Ah, a google search found the exact message for me:
select to /dev/rtc to wait for clock tick timed out
But no solution.
That leads to this: When I start up VMWare server, I start getting these
messages in the syslog:
Sep 2 06:25:13 <hostname> kernel: rtc: lost some interrupts at 512Hz.
Sep 2 06:25:44 <hostname> last message repeated 1521 times
Sep 2 06:26:45 <hostname> last message repeated 3050 times
Sep 2 06:27:46 <hostname> last message repeated 3050 times
Sep 2 06:28:47 <hostname> last message repeated 3049 times
Sep 2 06:29:48 <hostname> last message repeated 3050 times
Sep 2 06:30:49 <hostname> last message repeated 3050 times
Sep 2 06:31:50 <hostname> last message repeated 3050 times
Sep 2 06:32:51 <hostname> last message repeated 3050 times
Sep 2 06:33:52 <hostname> last message repeated 3050 times
Sep 2 06:34:53 <hostname> last message repeated 3050 times
Sep 2 06:35:54 <hostname> last message repeated 3049 times
Sep 2 06:36:55 <hostname> last message repeated 3050 times
Sep 2 06:37:56 <hostname> last message repeated 3049 times
Sep 2 06:38:57 <hostname> last message repeated 3049 times
Sep 2 06:39:58 <hostname> last message repeated 3050 times
Sep 2 06:40:59 <hostname> last message repeated 3050 times
Sep 2 06:42:00 <hostname> last message repeated 3050 times
Sep 2 06:43:01 <hostname> last message repeated 3050 times
Sep 2 06:44:02 <hostname> last message repeated 3050 times
/proc/interrupts shows:
CPU0 CPU1
0: 3613286 0 IO-APIC-edge timer
1: 12 0 IO-APIC-edge i8042
8: 0 0 IO-APIC-edge rtc
9: 1 0 IO-APIC-level acpi
12: 113 0 IO-APIC-edge i8042
14: 65 0 IO-APIC-edge ide0
50: 59827 0 IO-APIC-level libata, uhci_hcd:usb1, ehci_hcd:usb4
169: 56297 0 IO-APIC-level eth0
177: 0 0 IO-APIC-level uhci_hcd:usb2
185: 0 0 IO-APIC-level uhci_hcd:usb3
NMI: 0 0
LOC: 3613227 3613226
ERR: 0
MIS: 0
Since VMWare is the only app at the moment that uses the RTC, during its
execution is the only time I get those error messages.
Someone on the VMWare Forum suggested adding 'nohpet' to the kernel boot
parameters, but that did not fix anything.
Anyone have any suggestions?
j
--
Joshua Kugler
Lead System Admin -- Senior Programmer
http://www.eeinternet.com
PGP Key: http://pgp.mit.edu/ ID 0xDB26D7CE
PO Box 80086 -- Fairbanks, AK 99708 -- Ph: 907-456-5581 Fax: 907-456-3111
Reply to: