From owner-freebsd-current Sun Jul 19 23:03:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00423 for freebsd-current-outgoing; Sun, 19 Jul 1998 23:03:57 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00418 for ; Sun, 19 Jul 1998 23:03:54 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA15267; Mon, 20 Jul 1998 16:03:16 +1000 Date: Mon, 20 Jul 1998 16:03:16 +1000 From: Bruce Evans Message-Id: <199807200603.QAA15267@godzilla.zeta.org.au> To: bde@zeta.org.au, brian@Awfulhak.org Subject: Re: tickadj -t not changing tick Cc: freebsd-current@FreeBSD.ORG, jak@cetlink.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hmm, I have a timer problem with a Compaq Presario (notebook). It >seems that the timer chip (i8254 is the only one probed) is acting a >big strangely and returning ``past'' times - this is disastrous at >the start of a programs life as it tends to exceed the maximum >runtime (all set correctly to infinity in login.conf) and result in a >sig 24. It can't be a problem with the i8254 hardware, because the i8254 timecounter never goes backwards (if the hardware goes backwards, then the timecounter jumps forwards). >The laptop: > >: FreeBSD 3.0-CURRENT #10: Tue Jul 14 10:02:00 BST 1998 >: brian@woof.lan.awfulhak.org:/usr/src/sys/compile/WOOF >: Timecounter "i8254" frequency 1193182 Hz cost 1296 ns >: CPU: Cyrix GXm (17.09-MHz 586-class CPU) >: Origin = "CyrixInstead" Id = 0x540 Stepping=0 DIR=0x3346 >: Features=0x808131 >: real memory = 33554432 (32768K bytes) >: avail memory = 30597120 (29880K bytes) > >This is *really* a 233MHz chip. APM seems to be preventing use of the TSC timecounter. Otherwise the clock would go non-backwards 233/17 faster :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message