**** BEGIN LOGGING AT Mon Aug 20 02:59:59 2012
Aug 20 07:49:48 <builder_> build #62 of pxcab is complete: Failure [failed shell_11]  Build details are at http://buildbot.openwrt.org:8010/builders/pxcab/builds/62
Aug 20 09:08:50 <BasicXP> jow_laptop: ping
Aug 20 09:35:01 <builder_> build #61 of rb532 is complete: Failure [failed shell_11]  Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/61
Aug 20 09:38:25 <builder_> build #61 of ppc44x is complete: Failure [failed shell_11]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/61
Aug 20 11:32:47 <builder_> build #58 of x86 is complete: Failure [failed compile_1]  Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/58
Aug 20 14:23:46 <bluse> Hi all, while experimenting on our OpenWrt testbed, I discovered some error messages generated by the mac80211.sh script triggert by a wifi restart
Aug 20 14:25:31 <bluse> if you have an adhoc and monitor interface specified in /etc/config/wireless ( in my case based on ath5k), the following line in mac80211.sh returns an "Ressource bussy" error
Aug 20 14:25:37 <bluse> if [ ! "$mode" = "ap" -a ! "$mode" = "monitor" -a ! "$mode" = "adhoc" ]; then
Aug 20 14:25:37 <bluse>         # We attempt to set the channel for all interfaces, although
Aug 20 14:25:37 <bluse>         # mac80211 may not support it or the driver might not yet
Aug 20 14:25:37 <bluse>         # for ap mode this is handled by hostapd
Aug 20 14:25:37 <bluse>         [ -n "$fixed" -a -n "$channel" ] && iw dev "$ifname" set channel "$channel
Aug 20 14:25:37 <bluse> fi
Aug 20 14:26:26 <bluse> I think it is not necessary to set a channel for a monitor interface ... and in case of an adhoc interface, the channel is allready set by the iw join command forther up in the script
Aug 20 14:26:57 * bluse the second issue is that the line:
Aug 20 14:26:59 <bluse> [  "$mode" = "ap"  ] || ifconfig "$ifname" hw ether "$vif_mac"
Aug 20 14:27:35 <bluse> tries to set a mac adress with ifconfig to an monitor interface.. leading to an :Invalide argument" error
Aug 20 14:51:56 <builder_> build #63 of cobalt is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/63
Aug 20 14:54:41 <builder_> build #52 of sibyte is complete: Failure [failed shell_11]  Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/52
Aug 20 16:30:07 <builder_> build #64 of lantiq is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/64
**** ENDING LOGGING AT Tue Aug 21 02:59:58 2012