archive mirror
 help / color / mirror / Atom feed
From: Jan Dittmer <>
Subject: Clock skips (?) with 2.6 and games
Date: Mon, 03 Nov 2003 11:28:36 +0100	[thread overview]
Message-ID: <> (raw)

Hash: SHA1


I'm experiencing skips in games like q3demo and enemy territory on a
dual xeon p4. That means, if I'm walking around, about every 2-3 seconds
I'm skipping a bit of the way. It seems that the clock is running too
slow and the games are trying to catch up every x seconds with the
system time.
System is running 2.6.0-test9-mm1. This effect does not show with
2.4.23pre6aa3, though there are only two processors displayed. Is this
normal? Judging from the temperature sensors that is not just one
processor with its sibling but really the two physical processors. Is
there any way with 2.4 to show all 4 processors?
I've tried booting 2.6 with nosmp, but that results in most interrupts
not working anymore.
What can I try to get test9 working properly?


Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -


             reply	other threads:[~2003-11-03 10:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03 10:28 Jan Dittmer [this message]
2003-11-03 10:34 ` Clock skips (?) with 2.6 and games Nick Piggin
2003-11-03 15:48   ` Jan Dittmer
2003-11-04  2:37   ` Zwane Mwaikambo
2003-11-04  2:59     ` Nick Piggin
2003-11-04  3:07       ` Zwane Mwaikambo
2003-11-03 11:01 ` Andrea Arcangeli
2003-11-03 11:21   ` Jan Dittmer
2003-11-03 14:36     ` Andrea Arcangeli
2003-11-03 15:44       ` Jan Dittmer
2003-11-03 16:11         ` Stephan von Krawczynski
2003-11-03 16:44           ` Jan Dittmer
2003-11-03 16:59           ` Jan Dittmer
2003-11-04  2:40         ` Zwane Mwaikambo
2003-11-04 10:22           ` Andrea Arcangeli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).