I upgraded to -CURRENT on a Xen machine yesterday, and found
that that the clock wasn't being updated because the dummy timecounter
was being used:
kern.timecounter.choice: TSC(-100) dummy(-100)
kern.timecounter.hardware: dummy
Shouldn't the TSC have been chosen since it has a higher quality?
From: Ganbold
To: PseudoCylon
Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu
Sent: Wed, June 16, 2010 6:33:47 AM
Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
AK-san,
>>> PseudoCylon wrote:
>>>
>>> Strange, looks like this
Dear FreeBSD community,
there has been a ZFS-related discussion at the meetBSD conference in
Krakow, Poland and we agreed to push ZFS version 15 (and not 16) to
-CURRENT.
An upgrade to version 16 gives us no valuable features (to be true, no
features at all besides ability to import v16 pools).
A
Not sure what happened, but it looks like the -current snapshots failed
to build? I only see ia64 images available.
ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/201007/
Sean
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/
>> From: Ganbold
>> To: PseudoCylon
>> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu
>> Sent: Wed, June 16, 2010 6:33:47 AM
>> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>>
>> AK-san,
>>
>>
> PseudoCylon wrote:
>>
Hi,
PseudoCylon: Can you try to reproduce this:
1) Setup OPEN HOST AP (ssid = xxx).
2) Configure WLAN client with:
ssid=xxx
auth_alg=SHARED
key_mgmt=NONE
Wait until wpa_cli announces that it tries to associate, but fails.
3) Then update wpa_supplicant.conf:
ssid=xxx
auth_alg=OPEN
key_mgmt=NO
