FC3 SMP Kernel Loosing Ticks!
Eric Mader
mader at jtcsv.com
Wed Nov 24 21:12:04 UTC 2004
(I sent this yesterday and it never showed up in the list, sorry if you
see this twice)
I'm running FC3 w/ the latest updates (as of yesterday afternoon ;-) on
an IBM Think Centre 8187-KU. This machine has a 3G Pentium 4 w/
hyperthreading. After the machine has been running for some number of
hours, probably more than 6, the clock stops ticking. I'm running the
SMP kernel:
root at Doramichan ~]# uname -a
Linux Doramichan.sanjose.ibm.com 2.6.9-1.681_FC3smp #1 SMP Thu Nov 18
15:19:10 EST 2004 i686 i686 i386 GNU/Linux
[root at Doramichan ~]#
Here's the tail end of /var/log/messages:
Nov 23 03:49:04 Doramichan kernel: Losing too many ticks!
Nov 23 03:49:04 Doramichan kernel: TSC cannot be used as a timesource.
Nov 23 03:49:04 Doramichan kernel: Possible reasons for this are:
Nov 23 03:49:04 Doramichan kernel: You're running with Speedstep,
Nov 23 03:49:04 Doramichan kernel: You don't have DMA enabled for your
hard disk (see hdparm),
Nov 23 03:49:04 Doramichan kernel: Incorrect TSC synchronization on an
SMP system (see dmesg).
Nov 23 03:49:04 Doramichan kernel: Falling back to a sane timesource now.
Nov 23 03:49:04 Doramichan sshd(pam_unix)[4073]: session opened for user
emader by (uid=0)
(I rebooted the machine into the non-SMP kernel, and it's been up now
for over 22 hours and still knows what time it is!)
Anybody have any idea what's going on here?
(I have text files w/ the last 150 lines of /var/log/messages, the
output of dmesg, lsmod and lspci, Xorg.0.log and modprobe.conf which I'm
not including this time in case they make the message too big for the
list...)
Thanks,
Eric Mader
IBM GCoC - San José
5600 Cottle Rd. M/S 50-2/B11
San Jose, CA 95193
More information about the fedora-list
mailing list