From owner-freebsd-mobile Wed Jul 22 12:38:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08815 for freebsd-mobile-outgoing; Wed, 22 Jul 1998 12:38:15 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.133.1] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08730; Wed, 22 Jul 1998 12:37:49 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id VAA00864; Wed, 22 Jul 1998 21:32:27 +0200 (CEST) To: Brian Somers cc: Bruce Evans , freebsd-current@FreeBSD.ORG, jak@cetlink.net, freebsd-mobile@FreeBSD.ORG Subject: Re: tickadj -t not changing tick In-reply-to: Your message of "Tue, 21 Jul 1998 21:10:45 BST." <199807212010.VAA20743@awfulhak.org> Date: Wed, 22 Jul 1998 21:32:26 +0200 Message-ID: <862.901135946@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199807212010.VAA20743@awfulhak.org>, Brian Somers writes: >[Follow-up-to pointed at freebsd-mobile] > >> >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 It seems to me that this gadget has something which is hosed or at least doesn't react as we'd expect it to. Without access to the machine it is all but impossible for me to isolate the problem, but if you're not afraid to look at some weird C code, the right place to look is in sys/i386/isa/clock.c, startrtclock() and thereabout. What chipset does this machine use ? a compaq invention ? if so they may have done something stupid to the timers in the 8254. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message