More data on this. I have 3 dual-processor machines here, two Acer and one IBM. The first Acer (epsilon) shows: Have a lot of fun... epsilon:~ # cat /proc/interrupts CPU0 CPU1 0: 57209857 57643418 IO-APIC-edge timer 1: 3188 3316 IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 8: 0 2 IO-APIC-edge rtc 16: 18849937 18862192 IO-APIC-level eth0 17: 2871504 2887248 IO-APIC-level Mylex DAC960PU 19: 0 0 IO-APIC-level usb-uhci 22: 842810 842008 IO-APIC-level aic7xxx 23: 1193685 1192898 IO-APIC-level aic7xxx NMI: 0 0 LOC: 57435627 57435698 ERR: 0 MIS: 0 epsilon:~ # cat /proc/driver/rtc rtc_time : 13:34:35 rtc_date : 2002-11-12 rtc_epoch : 1900 alarm : 01:02:03 DST_enable : no BCD : yes 24hr : yes square_wave : no alarm_IRQ : no update_IRQ : no periodic_IRQ : no periodic_freq : 1024 batt_status : okay You have new mail in /var/mail/root epsilon:~ # date Tue Nov 12 14:33:55 EDT 2002 epsilon:~ # Epsilon is a production machine, so I am adjusting its clock from my NTP server from cron at each minute. The second Acer machine, orion, a backup/experimental machine shows: Have a lot of fun... orion:~ # cat /proc/interrupts CPU0 CPU1 0: 1906750 947684 IO-APIC-edge timer 1: 0 6 IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 8: 1 0 IO-APIC-edge rtc 12: 3 9 IO-APIC-edge PS/2 Mouse 16: 63206 133721 IO-APIC-level eth0 17: 9829 25659 IO-APIC-level Mylex DAC960PG 19: 0 0 IO-APIC-level usb-uhci 22: 117 35 IO-APIC-level aic7xxx 23: 71 99 IO-APIC-level aic7xxx NMI: 0 0 LOC: 1427268 1427267 ERR: 0 MIS: 0 orion:~ # cat /proc/driver/rtc rtc_time : 09:01:12 rtc_date : 2002-11-13 rtc_epoch : 1900 alarm : 00:55:** DST_enable : no BCD : yes 24hr : yes square_wave : no alarm_IRQ : no update_IRQ : no periodic_IRQ : no periodic_freq : 1024 batt_status : okay orion:~ # date Tue Nov 12 18:33:07 EDT 2002 orion:~ # And the only dual-processor machine were I have the clock working correctly, pi: pi:~ # date Tue Nov 12 14:20:33 EDT 2002 pi:~ # cat /proc/interrupts CPU0 CPU1 0: 197115991 0 local-APIC-edge timer 1: 19777 39496 IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 8: 1 1 IO-APIC-edge rtc 12: 139785 126338 IO-APIC-edge PS/2 Mouse 14: 45 39 IO-APIC-edge ide0 16: 13157704 17479198 IO-APIC-level PCnet/FAST III 79C975 17: 7 9 IO-APIC-level aic7xxx 18: 7 9 IO-APIC-level aic7xxx 19: 572 734 IO-APIC-level usb-ohci 22: 3316552 3902549 IO-APIC-level ips NMI: 0 0 LOC: 197136025 197136538 ERR: 0 MIS: 0 pi:~ # cat /proc/driver/rtc rtc_time : 13:36:46 rtc_date : 2002-11-12 rtc_epoch : 1900 alarm : 00:00:00 DST_enable : no BCD : yes 24hr : yes square_wave : no alarm_IRQ : no update_IRQ : no periodic_IRQ : no periodic_freq : 1024 batt_status : okay pi:~ # date Tue Nov 12 14:36:47 EDT 2002 pi:~ # So, looks to me that may be a problem with the /dev/rtc driver on SMP machines, or with the SMP kernel. Anyone knows were I can look for help about SMP and/or the /dev/rtc clock, please? Thank you, AC -----Mensagem original----- De: Antônio L. F. Cruz [mailto:alfcruz@hcpa.ufrgs.br] Enviada em: terça-feira, 12 de novembro de 2002 13:49 Para: 'suse-linux-e@suse.com' Assunto: [SLE] PC/Intel clock Hello all, I have a dual-Pentium II 400MHz machine that show this strange behaviour: the clock runs much faster than it should, about 3 or 4 times the real time. This happens only under Linux; under "that other OS", version 4.0 didn't happens. Is this an hardware or software/firmware problem? I run SLES 7.0 here. Thank you, AC