-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 20/02/2010 23:42, Jeremy Chadwick wrote:
For sake of example -- look at ntpq's delay column for each peer, and
then look at the same column but for ntpdc. You'll see that for ntpdc
they're divided by 1000 (presumably kern.hz rate):
No -- those
On Sun, 21 Feb 2010 16:08:23 +1100
Peter Jeremy peterjer...@acm.org wrote:
That's definitely not good - though it's marginally better than before.
I have checked on a local machine and the timecounter frequency definitely
needs to be adjusted in the opposite direction to the ntpd drift.
I
today i upgraded to the latest stable from source, and tried to use the
iwn driver, but when i `kldload if_iwn`:
iwn0 Intel(R) PRO/Wireless 1000 mem 0xfeafe000-0xfeaf irq 17 at
device 0.0 on pci2
iwn: MIMO 1T2R, , address 00:00:00:00:00:00
panic: ieee80211_get_ratetable: not rate table for
On Sun, Feb 21, 2010 at 09:25:45AM +0200, Daniel Braniss wrote:
I'm willing to bet this is something simple I've overlooked, but I'm out
of ideas. Client is 8.0-RELEASE i386, server is 8.0-STABLE amd64
(kernel/world 2010/01/16). NFS version used is v3. Server filesystem
is UFS2.
On Sun, Feb 21, 2010 at 12:02:28PM +0200, Daniel Braniss wrote:
I'm not sure if you're referring to NFS here, or my TFTP comment. My
TFTP comment should be discussed elsewhere -- it's broken/odd behaviour,
but the workaround for TFTP (to set the file permissions to 0644 for
read) I'm fine
On Sun, Feb 21, 2010 at 12:02:28PM +0200, Daniel Braniss wrote:
I'm not sure if you're referring to NFS here, or my TFTP comment. My
TFTP comment should be discussed elsewhere -- it's broken/odd behaviour,
but the workaround for TFTP (to set the file permissions to 0644 for
read) I'm
On Sunday 21 February 2010 10:42:41 tech...@callooh.com wrote:
today i upgraded to the latest stable from source, and tried to use the
iwn driver, but when i `kldload if_iwn`:
iwn0 Intel(R) PRO/Wireless 1000 mem 0xfeafe000-0xfeaf irq 17 at
device 0.0 on pci2
iwn: MIMO 1T2R, , address
On Sun, 21 Feb 2010 16:08:23 +1100
Peter Jeremy peterjer...@acm.org wrote:
Having re-checked my maths, using both your time reset results, can
you please try:
sysctl machdep.acpi_timer_freq=3570847
That should result in a drift of close to zero (well within NTP's
lock range of +/- 300ppm).
Am Sun, 21 Feb 2010 13:41:13 +0100
schrieb Bernhard Schmidt bschm...@techwires.net:
On Sunday 21 February 2010 10:42:41 tech...@callooh.com wrote:
today i upgraded to the latest stable from source, and tried to use
the iwn driver, but when i `kldload if_iwn`:
iwn0 Intel(R) PRO/Wireless
On Feb 21, 2010, at 11:36, Torfinn Ingolfsen wrote:
On Sun, 21 Feb 2010 16:08:23 +1100 Peter Jeremy
peterjer...@acm.org wrote:
Having re-checked my maths, using both your time reset results, can
you please try:
sysctl machdep.acpi_timer_freq=3570847
That should result in a drift of close
On Sun, Feb 21, 2010 at 4:12 AM, C. P. Ghost cpgh...@cordula.ws wrote:
On Sun, Feb 21, 2010 at 12:35 AM, Jeremy Chadwick free...@jdc.parodius.com
wrote:
Some Linux users have reported AHCI-related issues with the SB600
southbridge, but the core of the problem turned out to be MSI on certain
On 2010-Feb-21 17:36:19 +0100, Torfinn Ingolfsen
torfinn.ingolf...@broadpark.no wrote:
*kg-omni1.kg4.no 78.157.115.4 3 u 31 64 3770.174 -10.253 0.160
r...@kg-f2# ntpdc -c loopi -c sysi
offset: -0.010253 s
frequency:6.744 ppm
That looks much healthier
Harald Weis wrote:
Has anybody encountered the following problem ?
Mac OS X does recognize FreeBSD partitions on USB disks, but doesn't
want to mount them because ``Incorrect super block''.
This is extremely annoying for my ``client'' because he relies on dayly
backups on USB keys. Is there a
On Sun, Feb 21, 2010 at 12:44:50AM +0300, Slawa Olhovchenkov wrote:
On Fri, Feb 19, 2010 at 01:12:01PM -0800, Pyun YongHyeon wrote:
Normally you should not have any FCS errors, it could be related
with signal quality and these errors might not be correctly
counted.
I can't check cable
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I've made a post to -arch regarding my plans for BIND in the base, along
with some information about getting ready for DNSSEC, including the
upcoming signing of the root zone. You can find the message at
On Sun, Feb 21, 2010 at 03:41:53PM -0800, Pyun YongHyeon wrote:
On Sun, Feb 21, 2010 at 12:44:50AM +0300, Slawa Olhovchenkov wrote:
On Fri, Feb 19, 2010 at 01:12:01PM -0800, Pyun YongHyeon wrote:
Normally you should not have any FCS errors, it could be related
with signal quality and
16 matches
Mail list logo
