: Tuesday, December 06, 2005 11:17 PM
Subject: Re: cpu-timer rate
On Mon, 2005-Dec-05 10:15:52 -0800, Kevin Oberman wrote:
On Mon, Dec 05, 2005 at 09:42:08AM +0100 I heard the voice of
kama, and lo! it spake thus:
I appreciate that you took time to answer about the different
clocks. But that does
On Wed, 2005-Dec-07 03:51:47 -0800, Ed wrote:
I certainly do not have a full understanding of the interactions between
the various FreeBSD software timers and i386 hardware clocks, but I do know
this is not the first time we've seen a problem with the APIC/ACPI
timers/clocks.
You have a
from 5.x.
- Original Message -
From: Peter Jeremy [EMAIL PROTECTED]
To: Ed [EMAIL PROTECTED]
Cc: freebsd-stable@freebsd.org
Sent: Wednesday, December 07, 2005 10:22 AM
Subject: Re: cpu-timer rate
On Wed, 2005-Dec-07 03:51:47 -0800, Ed wrote:
I certainly do not have a full
On Wed, Dec 07, 2005 at 03:39:04PM -0800, Ed wrote:
For these reasons, I believe your technically unsupported assertion that
This is nothing to do with the core team should be shelved, pending
actual investigation of the phenomenon.
Peter's assertion is entirely correct. You misunderstand
PROTECTED]
Cc: Peter Jeremy [EMAIL PROTECTED];
freebsd-stable@freebsd.org
Sent: Wednesday, December 07, 2005 4:03 PM
Subject: Re: cpu-timer rate
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
On Wed, Dec 07, 2005 at 04:23:04PM -0800, Ed wrote:
My apologies, I did not understand this specific meaning of core team
when I wrote that.
What term should I use in the future, when discussing problems of this
nature? FreeBSD kernel developers, or some such?
FreeBSD developers is fine.
On Wed, 2005-Dec-07 15:39:04 -0800, Ed wrote:
With all due respect, vmware plays fast and loose with the clocks is not
a satisfactory technical explanation.
Hi-jacking unrelated e-mail threads and top posting is not good
etiquette either.
It is no doubt true that those of us who run FreeBSD in
On Friday, 2 December 2005 at 14:32:58 +0100, kama wrote:
Hi,
I am just wondering why the cpu-timer is doubled from what I set in
kern.hz?
# vmstat -i
...
cpu0: timer 14314031 1999
# sysctl -a | grep hz
kern.clockrate: { hz = 1000, tick = 1000, profhz = 666,
On Mon, 2005-Dec-05 10:15:52 -0800, Kevin Oberman wrote:
On Mon, Dec 05, 2005 at 09:42:08AM +0100 I heard the voice of
kama, and lo! it spake thus:
I appreciate that you took time to answer about the different
clocks. But that does not answer why vmstat -i shows a rate of 2000
when I
On Sat, 3 Dec 2005, Peter Jeremy wrote:
On Fri, 2005-Dec-02 14:32:58 +0100, kama wrote:
I am just wondering why the cpu-timer is doubled from what I set in
kern.hz?
# vmstat -i
interrupt total rate
...
cpu0: timer 14314031 1999
On Mon, Dec 05, 2005 at 09:42:08AM +0100 I heard the voice of
kama, and lo! it spake thus:
I appreciate that you took time to answer about the different
clocks. But that does not answer why vmstat -i shows a rate of 2000
when I have set the hz to 1000.
Because the rate is always twice hz.
Date: Mon, 5 Dec 2005 06:49:10 -0600
From: Matthew D. Fuller [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
On Mon, Dec 05, 2005 at 09:42:08AM +0100 I heard the voice of
kama, and lo! it spake thus:
I appreciate that you took time to answer about the different
clocks. But that does not
On Mon, Dec 05, 2005 at 10:15:52AM -0800 I heard the voice of
Kevin Oberman, and lo! it spake thus:
From: Matthew D. Fuller [EMAIL PROTECTED]
Because the rate is always twice hz.
While I will concede that I have no explanation, but on all of my
systems rate = HZ +/-1. I have never seen
Date: Mon, 5 Dec 2005 13:47:56 -0600
From: Matthew D. Fuller [EMAIL PROTECTED]
On Mon, Dec 05, 2005 at 10:15:52AM -0800 I heard the voice of
Kevin Oberman, and lo! it spake thus:
From: Matthew D. Fuller [EMAIL PROTECTED]
Because the rate is always twice hz.
While I will
Hi,
I am just wondering why the cpu-timer is doubled from what I set in
kern.hz?
# vmstat -i
interrupt total rate
irq1: atkbd0 4 0
irq6: fdc087 0
irq13: npx01
On Fri, 2005-Dec-02 14:32:58 +0100, kama wrote:
I am just wondering why the cpu-timer is doubled from what I set in
kern.hz?
# vmstat -i
interrupt total rate
...
cpu0: timer 14314031 1999
Total 14750922 2060
16 matches
Mail list logo
