On Thu, Jun 12, 2014 at 10:12:53AM +0200, Sascha Wildner wrote: > On Thu, 05 Jun 2014 22:31:14 +0200, Sven Gaerner <sgaer...@gmx.net> wrote: > > >On Thu, Jun 05, 2014 at 03:15:26PM +0200, Sven Gaerner wrote: > >>On Thu, Jun 05, 2014 at 08:46:22AM +0200, Sascha Wildner wrote: > >>> On Wed, 04 Jun 2014 22:25:59 +0200, Sven Gaerner > >><sgaer...@gmx.net> wrote: > >>> > >>> >That should not be a problem as neither wpa-supplicant nor > >>hostapd are > >>> >loaded. Just running "ifconfig ath0 up" stops the system. > >>> > >>> Would this not be wlan0? Like, "ifconfig wlan0 create wlandev ath0; > >>> ifconfig wlan0 up" > >> > >> > >>But I will check that later. > > > >The second call, "ifconfig wlan0 up" freezes the system. > > Can you check if Johannes' most recent ath fix changes anything about it? > > http://lists.dragonflybsd.org/pipermail/commits/2014-June/270210.html > > If you are running 3.8, you can just cherry-pick it on the 3.8 > branch locally: git cherry-pick ed6e0e1b5a651
Thanks for the patch. I applied that to my 3.8 branch, but it did not help. The system still locks up. I recently discovered a kernel message when trying to configure the network. I guess I missed adding this message to the other mails. The kernel message is: ath0: _ath_power_restore_power_state.refcount=0? Is there a way to build the ATH driver with more output to get closer to the problem? Can I do anything else to provide more details about the freeze? Sven