**** BEGIN LOGGING AT Thu Aug 09 02:59:59 2012 Aug 09 08:09:15 <_trine> Do we need to have/keep aircrack-ptw in trunk,, I cant see why we would need a separate package for that Aug 09 09:06:37 florian * r33071 /trunk/target/linux/mcs814x/files-3.3/drivers/net/ethernet/mcs8140/nuport_mac.c: Aug 09 09:06:37 [mcs814x] nuport-mac: use dma_mapping_error() instead of checking pointers Aug 09 09:06:37 Thanks Gabor for spotting this Aug 09 09:41:24 jow * r33072 /trunk/target/linux/x86/patches-3.3/003-via-rhine-crash-fix.patch: (log message trimmed) Aug 09 09:41:24 Fix hard reset of alix/soekris hardware under heavy NIC load Aug 09 09:41:24 The following patch corrects a hard reset that occurs on alix and Aug 09 09:41:24 soekris net5501 hardware. Specifically, this is an issue with the via Aug 09 09:41:24 rhine NIC driver. Under periods of extreme load, the via rhine driver Aug 09 09:41:25 can cause a reset of the entire system. When this happens no output is Aug 09 09:41:26 seen on the console, the device simply reboots. This was reported in the Aug 09 10:26:06 acinonyx * r33073 /packages/net/sslh/ (Makefile files/sslh.init): [packages] sslh: Fix typo in init script (#11998) Aug 09 11:14:11 build #53 of pxcab is complete: Failure [failed shell_11] Build details are at http://buildbot.openwrt.org:8010/builders/pxcab/builds/53 Aug 09 13:13:29 jogo * r33074 /trunk/package/linux-atm/ (Makefile files/br2684ctl): Aug 09 13:13:29 package: linux-atm: br2684ct: fix nas interface bringup on boot Aug 09 13:13:29 Give nas interface time to setup them selves before configuring them. Aug 09 13:13:29 Should fix #11826. Aug 09 13:13:29 Contributed by T-Labs, Deutsche Telekom Innovation Laboratories Aug 09 13:13:30 Signed-off-by: Jonas Gorski Aug 09 13:28:49 build #58 of at91 is complete: Failure [failed shell_17] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/58 Aug 09 13:31:26 build #52 of rb532 is complete: Failure [failed shell_7 shell_11] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/52 Aug 09 13:33:43 build #52 of ppc44x is complete: Failure [failed shell_11] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/52 Aug 09 14:29:39 build #43 of sibyte is complete: Failure [failed shell_11] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/43 Aug 09 18:23:14 build #36 of iop32x is complete: Failure [failed shell_11] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/36 Aug 09 18:26:28 build #36 of etrax is complete: Failure [failed shell_11] Build details are at http://buildbot.openwrt.org:8010/builders/etrax/builds/36 Aug 09 18:30:03 build #35 of gemini is complete: Failure [failed shell_11] Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/35 Aug 09 18:30:50 jow * r33075 /trunk/package/base-files/ (Makefile files/sbin/sysupgrade): [package] base-files: fix option parsing of -F/--force parameter Aug 09 21:17:44 build #33 of octeon is complete: Failure [failed shell_11] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/33 Aug 09 21:20:08 hmm. my net45xx kernel panic went away with a clean tree. Aug 09 21:20:30 also, with a minimal .config Aug 09 21:42:14 there also was an via-rhine fix for net5501, not sure if it affected net45xx too Aug 09 22:31:22 jow_laptop: the rev i'm testing was prior to that Aug 09 22:32:15 * russell-- is building one of my more complicated .config's to see if that is okay or not Aug 09 22:34:31 hmm Aug 09 22:34:42 * danmackay goes to try to build a ar71xx trunk build again Aug 09 22:44:55 jow * r33076 /trunk/package/netifd/files/etc/init.d/network: (log message trimmed) Aug 09 22:44:55 [package] netifd: call "wifi down" before "wifi up" Aug 09 22:44:55 When the underlying /etc/config/wireless got changed since the last "wifi up" Aug 09 22:44:55 has been performed, the uci vap ifname state vars become inconsistent on a Aug 09 22:44:55 subsequent "wifi up" and multiple vaps get mapped to the same ifnames which Aug 09 22:44:56 confuses the gui and other processes relying on them. Aug 09 22:44:57 For now call an explicit "wifi down" prior to each "wifi up" which will clear **** ENDING LOGGING AT Fri Aug 10 02:59:58 2012