Just experiment with changing the kern.eventtimer.periodic and
kern.timecounter.hardware values.
Thanks,
Adrian
On 28 February 2013 03:20, Derrick Dantavious Edwards
wrote:
> On 27 February 2013 18:59, Derrick Dantavious Edwards
> wrote:
>>
>> Yes. When I start the system, I get those me
On 27 February 2013 18:59, Derrick Dantavious Edwards
wrote:
>
> Yes. When I start the system, I get those messages. Wireless Link fails
to
> establish thus causing all services requring link to failie NFS . Soon
> after I am at the command prompt or GUI, I can ping hosts however, I have
On 27 February 2013 18:59, Derrick Dantavious Edwards
wrote:
>
> Yes. When I start the system, I get those messages. Wireless Link fails to
> establish thus causing all services requring link to failie NFS . Soon
> after I am at the command prompt or GUI, I can ping hosts however, I have t
On Wednesday, February 27, 2013 06:45:04 PM you wrote:
> These are only during probe requests, right?
>
>
>
>
> adrian
>
>
> On 27 February 2013 16:30, Derrick Dantavious Edwards
>
> wrote:
> > Hi,
> >
> > During recent upgrades to Current, I have been experiencing timeouts with
>
These are only during probe requests, right?
adrian
On 27 February 2013 16:30, Derrick Dantavious Edwards
wrote:
> Hi,
> During recent upgrades to Current, I have been experiencing timeouts with the
> ath0 device. These are the errors that I am receiving. Any ideas?
>
> V/r
>
> Derri
Hi,
During recent upgrades to Current, I have been experiencing timeouts with the
ath0 device. These are the errors that I am receiving. Any ideas?
V/r
Derrick
ath0: ath_tx_tid_drain_print: norm: node 0xff802adf3000:
bf=0xff8001d6e000: addbaw=0, dobaw=0, seqno=0, retry=0
ath0
