Re: Clock runs too fast
Tilman Linneweh [EMAIL PROTECTED] writes: I have a problem with my ASUS P5A-B motherboard, where the timer runs too fast. This is with -CURRENT, cvsup'd from 1.5 weeks ago. Same motherboard, same problem. No idea. I used to have the same problem with the same board. At the time, I worked around it by disabling ACPI. However, the problem no longer occurs on my system, even though I've reenabled ACPI. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Clock runs too fast
Hi, I have a problem with my ASUS P5A-B motherboard, where the timer runs too fast. This is with -CURRENT, cvsup'd from 1.5 weeks ago. I encountered this problem before, and found a fix which worke;: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=145760+0+archive/2002/freebsd-current/20020915.freebsd-current However, this fix (adding kern.timecounter.hardware=i8254 to /etc/sysctl.conf) does not seem to work anymore. The clock still runs too fast. Here are my sysctl values for kern.timecounter kern.timecounter.nbinuptime: 450054 kern.timecounter.nnanouptime: 3 kern.timecounter.nmicrouptime: 0 kern.timecounter.nbintime: 21313 kern.timecounter.nnanotime: 15 kern.timecounter.nmicrotime: 21298 kern.timecounter.ngetbinuptime: 0 kern.timecounter.ngetnanouptime: 95 kern.timecounter.ngetmicrouptime: 60405 kern.timecounter.ngetbintime: 0 kern.timecounter.ngetnanotime: 0 kern.timecounter.ngetmicrotime: 142134 kern.timecounter.hardware: i8254 kern.timecounter.tick: 1 Any ideas? Thanks. -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Clock runs too fast
I have a problem with my ASUS P5A-B motherboard, where the timer runs too fast. This is with -CURRENT, cvsup'd from 1.5 weeks ago. I encountered this problem before, and found a fix which worke;: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=145760+0+archive/2002/freebsd-current/20020915.freebsd-current However, this fix (adding kern.timecounter.hardware=i8254 to /etc/sysctl.conf) does not seem to work anymore. The clock still runs too fast. You are not alone. Same motherboard, same problem. No idea. regards tilman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Clock runs too fast
In message [EMAIL PROTECTED], Tilman Linneweh writes: I have a problem with my ASUS P5A-B motherboard, where the timer runs too fast. This is with -CURRENT, cvsup'd from 1.5 weeks ago. I encountered this problem before, and found a fix which worke;: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=145760+0+archive/2002/freebsd-current/20020915.freebsd-current However, this fix (adding kern.timecounter.hardware=i8254 to /etc/sysctl.conf) does not seem to work anymore. The clock still runs too fast. You are not alone. Same motherboard, same problem. No idea. Are you saying that the i8254 also runs twice as fast as it should ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Clock runs too fast
On Tue, Nov 12, 2002 at 05:18:13PM +0100, Poul-Henning Kamp wrote: Are you saying that the i8254 also runs twice as fast as it should ? It looks like it. Here is some additional output from dmesg. Does it give a clue? Calibrating clock(s) ... TSC clock: 400911902 Hz, i8254 clock: 1193190 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method [snip] ACPI timer looks BAD min = 0, max = 5, width = 6 ACPI timer looks BAD min = 0, max = 16777210, width = 16777211 ACPI timer looks BAD min = 1, max = 16777215, width = 16777215 ACPI timer looks BAD min = 2, max = 16777204, width = 16777203 ACPI timer looks BAD min = 0, max = 16777215, width = 16777216 ACPI timer looks BAD min = 0, max = 16777215, width = 16777216 ACPI timer looks BAD min = 2, max = 16777210, width = 16777209 ACPI timer looks BAD min = 2, max = 16777208, width = 16777207 ACPI timer looks BAD min = 0, max = 16777208, width = 16777209 ACPI timer looks BAD min = 2, max = 16777215, width = 16777214 Timecounter ACPI-safe frequency 3579545 Hz acpi_timer0: 24-bit timer at 3.579545MHz port 0xec08-0xec0b on acpi0 acpi_cpu0: CPU on acpi0 [snip] Timecounters tick every 10.000 msec -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Clock runs too fast
On Tue, Nov 12, 2002 at 10:20:00AM -0500, Craig Rodrigues wrote: However, this fix (adding kern.timecounter.hardware=i8254 to /etc/sysctl.conf) does not seem to work anymore. The clock still runs too fast. Could you try kern.timecounter.hardware=TSC - this worked for someone else sometime last week. If the TSC works and the i8254 doesn't it may give phk some better idea about what is going on. David. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Clock runs too fast
On Tue, Nov 12, 2002 at 05:44:36PM +, David Malone wrote: On Tue, Nov 12, 2002 at 10:20:00AM -0500, Craig Rodrigues wrote: However, this fix (adding kern.timecounter.hardware=i8254 to /etc/sysctl.conf) does not seem to work anymore. The clock still runs too fast. Could you try kern.timecounter.hardware=TSC - this worked for someone else sometime last week. If the TSC works and the i8254 doesn't it may give phk some better idea about what is going on. I just tried this, and it seems to work fine. So TSC seems to work, and i8254 does not seem to work. -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Clock runs too fast
In message [EMAIL PROTECTED], Craig Rodrigues writes: On Tue, Nov 12, 2002 at 05:44:36PM +, David Malone wrote: On Tue, Nov 12, 2002 at 10:20:00AM -0500, Craig Rodrigues wrote: However, this fix (adding kern.timecounter.hardware=i8254 to /etc/sysctl.conf) does not seem to work anymore. The clock still runs too fast. Could you try kern.timecounter.hardware=TSC - this worked for someone else sometime last week. If the TSC works and the i8254 doesn't it may give phk some better idea about what is going on. I just tried this, and it seems to work fine. So TSC seems to work, and i8254 does not seem to work. And ACPI doesn't work either, right ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Clock runs too fast
On Tue, Nov 12, 2002 at 07:23:51PM +0100, Poul-Henning Kamp wrote: I just tried this, and it seems to work fine. So TSC seems to work, and i8254 does not seem to work. And ACPI doesn't work either, right ? That's right, doing: sysctl -w kern.timecounter.hardware=ACPI-safe does not work either, ie. clock is too fast. -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Clock runs too fast
On Sun, Sep 08, 2002 at 12:16:26PM +0200, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Craig Rodrigues writes: Is there a problem with the ACPI code or with my hardware (an ASUS P5A-B motherboard from about 3 or 4 years ago). How can I default to i8254 as my default timer? Is there something I should put in device.hints? Put it in /etc/rc.early: sysctl kern.timecounterhardware=i8254 I put the following lin in /etc/sysctl.conf and it did the job: kern.timecounter.hardware=i8254 I have not been able to understand in what way this board fails :-( Does the time run uniformly fast, ie: 7 minutes every 5, all the time, or is it erratic ? I didn't do a very thorough analysis of the problem, but it seemed to erratic. -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Clock runs too fast
On Sat, Sep 07, 2002 at 11:19:52PM -0400, Craig Rodrigues wrote: Is there a problem with the ACPI code or with my hardware (an ASUS P5A-B motherboard from about 3 or 4 years ago). Several people (including me) have reported this problem with this motherboard. Poul had a look at it, but couldn't figure out why the clock was running fast - I'd guess the hardware is busted in some obscure way. (I may have a look at it once I have the machine running -current again. At the moment it is my NAT box, so it is running -stable). David. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Clock runs too fast
Craig Rodrigues schrieb: Hi, I have been having this problem with -current for the past 2 weeks now (I am new to -current and just started using it 2 weeks ago). I just did a cvsup and rebuilt the kernel and rebuilt the world. My clock seems to be running too fast, and I keep resetting it with ntpdate. [...] Now the clock seems to run at a more reasonable rate. Is there a problem with the ACPI code or with my hardware (an ASUS P5A-B motherboard from about 3 or 4 years ago). How can I default to i8254 as my default timer? Is there something I should put in device.hints? I had similar problems with a Gigabyte GA-5AX (also with ALi Aladdin V chipset). Without setting debug.acpi.disable = timer the clock runs twice as fast as it should be. This problem seems to be introduced in the ACPI update around July 2001. I didn't find any solution other than disabling ACPI timecounter. Daniel To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Clock runs too fast
In message [EMAIL PROTECTED], Craig Rodrigues writes: I reset my timecounter: sysctl kern.timecounter.hardware=i8254 Now the clock seems to run at a more reasonable rate. Is there a problem with the ACPI code or with my hardware (an ASUS P5A-B motherboard from about 3 or 4 years ago). How can I default to i8254 as my default timer? Is there something I should put in device.hints? Put it in /etc/rc.early: sysctl kern.timecounterhardware=i8254 I have not been able to understand in what way this board fails :-( Does the time run uniformly fast, ie: 7 minutes every 5, all the time, or is it erratic ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Clock runs too fast
Hi, I have been having this problem with -current for the past 2 weeks now (I am new to -current and just started using it 2 weeks ago). I just did a cvsup and rebuilt the kernel and rebuilt the world. My clock seems to be running too fast, and I keep resetting it with ntpdate. I looked at this FAQ entry for hints, Why is the clock on my laptop keep incorrect time? http://www.unixguide.net/freebsd/faq/05.26.shtml My default sysctl value for kern.timecounter hardware is: kern.timecounter.hardware: ACPI-safe The Timecounters available on my system are: dmesg | grep Timecounter Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 400910436 Hz Timecounter ACPI-safe frequency 3579545 Hz Timecounters tick every 10.000 msec I reset my timecounter: sysctl kern.timecounter.hardware=i8254 Now the clock seems to run at a more reasonable rate. Is there a problem with the ACPI code or with my hardware (an ASUS P5A-B motherboard from about 3 or 4 years ago). How can I default to i8254 as my default timer? Is there something I should put in device.hints? -- Craig Rodrigues http://www.gis.net/~craigr [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
