**** BEGIN LOGGING AT Fri Jun 25 02:59:57 2010 Jun 25 04:37:16 acoul * r21897 /trunk/target/linux/ixp4xx/patches-2.6.35/ (4 files): ixp4xx: remove 2.6.35 unedded patches Jun 25 07:50:05 build #60 of iop32x is complete: Failure [failed shell_6] Build details are at http://tksite.gotdns.org:8010/builders/iop32x/builds/60 Jun 25 08:08:07 hcg * r21898 /trunk/target/linux/omap35xx/ (5 files in 4 dirs): Use modules for wifi and usb Jun 25 08:11:56 hcg * r21899 /trunk/target/linux/omap35xx/gumstix/base-files/lib/ (. wifi/ wifi/mac80211.sh): Jun 25 08:11:56 Add script support for Marvell 88W8686 mac80211. Jun 25 08:11:56 This is a hack now, but it works. cfg80211 is very broken Jun 25 08:11:56 in the current mainline Marvell driver. A new patch set to Jun 25 08:11:56 address this is in linux-next, I just do not have time Jun 25 08:11:57 today to address it. Jun 25 13:50:10 <[Fate]> ok, so what is a "data bus error"? Jun 25 13:51:51 [Fate]: A CPU exception Jun 25 13:53:04 <[Fate]> something which clearly shouldn't happen on an AP :/ Jun 25 13:54:23 probably :) Jun 25 13:54:50 It can happen on invalid access of memory mapped I/O spacer Jun 25 13:54:53 space Jun 25 15:08:18 <[Fate]> in general: is there is a good reason to do the hw_init() and phy_connect() already in a network driver's probe function instead of its open() function? Jun 25 15:14:42 <[florian]> not really Jun 25 15:14:55 <[florian]> some driver do it in the open, some other in the probe, up to you Jun 25 18:44:04 <[Fate]> what exactly is the following supposed to tell me? Jun 25 18:44:06 <[Fate]> WARNING: at kernel/softirq.c:143 local_bh_enable+0x50/0xa8() Jun 25 18:44:09 <[Fate]> some irq locking trouble? Jun 26 00:20:20 build #82 of atheros is complete: Success [build successful] Build details are at http://tksite.gotdns.org:8010/builders/atheros/builds/82 Jun 26 01:55:30 build #77 of ar71xx is complete: Failure [failed shell_6] Build details are at http://tksite.gotdns.org:8010/builders/ar71xx/builds/77 **** ENDING LOGGING AT Sat Jun 26 02:59:57 2010