It seems some recent change (as in the last 7-10 days)
has caused an instability in wlan0. Just a small
excerpt from /var/log/messages,
Dec 4 18:54:16 laptop kernel: wlan0: link state changed to UP
Dec 4 19:11:16 laptop kernel: wlan0: link state changed to DOWN
Dec 4 19:11:16 laptop kernel: wl
on 04/12/2010 02:38 Jung-uk Kim said the following:
> If my understanding is correct, your patch uses the dummy timecounter
> until a real timecounter is chosen.
Perhaps this is one way to look at it.
But I look at it differently - the patch makes cpu_ticks refer to tc_cpu_ticks.
That is, it make
TB --- 2010-12-04 07:30:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-12-04 07:30:00 - starting HEAD tinderbox run for amd64/amd64
TB --- 2010-12-04 07:30:00 - cleaning the object tree
TB --- 2010-12-04 07:30:14 - cvsupping the source tree
TB --- 2010-12-04 07:30:14 - /usr/bin
TB --- 2010-12-04 07:30:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-12-04 07:30:00 - starting HEAD tinderbox run for i386/i386
TB --- 2010-12-04 07:30:00 - cleaning the object tree
TB --- 2010-12-04 07:30:11 - cvsupping the source tree
TB --- 2010-12-04 07:30:11 - /usr/bin/c
TB --- 2010-12-04 07:30:00 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-12-04 07:30:00 - starting HEAD tinderbox run for i386/pc98
TB --- 2010-12-04 07:30:00 - cleaning the object tree
TB --- 2010-12-04 07:30:10 - cvsupping the source tree
TB --- 2010-12-04 07:30:10 - /usr/bin/c