**** BEGIN LOGGING AT Wed Feb 20 02:59:58 2013 Feb 20 04:05:10 build #194 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/194 Feb 20 04:09:11 build #176 of rb532 is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/176 Feb 20 04:12:45 build #176 of ppc44x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/176 Feb 20 04:14:53 build #193 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/193 Feb 20 04:42:17 build #166 of sibyte is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/166 Feb 20 04:51:49 build #181 of uml is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/181 Feb 20 06:26:24 build #178 of x86 is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/178 Feb 20 06:49:17 juhosg r35688 trunk/rules.mk * fix ARCH_SUFFIX for mips64{,el}r2 Feb 20 08:27:40 juhosg r35689 trunk/target/linux/mpc85xx/image/Makefile * mpc85xx: use a foreach loop to copy boot images Feb 20 08:27:42 juhosg r35690 trunk/target/linux/mpc85xx/ config-3.7 patches-3.7/140-powerpc-85xx-tl-wdr4900-v1-support.patch * mpc85xx: add kernel support for the TL-WDR4900 v1 board Feb 20 09:42:02 juhosg r35691 trunk/package/kernel/modules/ (7 files) * package/kernel: remove trailing whitespaces from *.mk files Feb 20 09:59:13 build #149 of iop32x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/149 Feb 20 10:35:19 build #145 of gemini is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/145 Feb 20 13:54:55 jogo r35692 packages/net/asterisk-chan-sccp-b/Makefile * packages: asterisk-chan-sccp-b: update svn repo url Feb 20 13:54:58 jogo r35693 packages/libs/ curl/Makefile curl/patches/100-cross-compile.patch * packages: curl: update to 7.29.0 Feb 20 13:55:00 jogo r35694 packages/net/weechat/Makefile * packages: weechat: update to 0.4.0 Feb 20 13:55:02 jogo r35695 packages/net/p910nd/Makefile * packages: p910nd: move to Printing Feb 20 13:55:04 jogo r35696 packages/net/cups-bjnp/Makefile * packages: cups-bjnp: move to Printing Feb 20 13:55:06 jogo r35697 packages/net/cups-bjnp/Makefile * packages: cups-bjnp: update from 0.5.4 to 1.2. Feb 20 13:55:08 jogo r35698 packages/net/cups/Makefile * packages: cups: do not try to package pdftops Feb 20 13:55:10 jogo r35699 packages/net/tig/Makefile * packages: tig: update to 1.1, and fix description. Feb 20 13:55:12 jogo r35700 packages/net/krb5/ (5 files in 3 dirs) * packages: krb5: update to 1.11 Feb 20 13:55:14 jogo r35701 packages/net/aria2/Makefile * packages: aria2: update to 1.16.3 Feb 20 13:55:15 jogo r35702 packages/net/madwifi/Makefile * packages: madwifi: mark as broken for bcm63xx Feb 20 15:03:54 build #135 of octeon is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/135 Feb 20 15:06:25 jow r35703 trunk/ toolchain/Config.in toolchain/wrapper/Makefile scripts/ext-toolchain.sh * buildroot: allow specifying libc personality for external toolchains Feb 20 15:31:57 hauke r35704 trunk/target/linux/ brcm47xx/base-files/lib/preinit/05_set_failsafe_switch_brcm brcm47xx/base-files/lib/preinit/15_set_preinit_interface_brcm brcm47xx/base-files/etc/init.d/netconfig * brcm47xx: do not use vlan0 any more. Feb 20 17:29:55 nbd, you around ? I think I've narrowed down this test case considerably here Feb 20 17:30:04 yes Feb 20 17:30:21 got my units all flashed with tip of trunk, svn up and clean build yesterday Feb 20 17:30:29 and, to sum it up in a nutshell Feb 20 17:30:38 my issues with dma error messages in dmesg Feb 20 17:30:52 seem to go away, if I dont do background scans on the client mode wds adapters Feb 20 17:31:20 so it seems to be related to having traffic flowing over the link, with a background iw dev adapter scan happening Feb 20 17:31:43 i have been issuing that scan against the client mode adapter which is the client end of a wds connection Feb 20 17:32:15 which, I thought was a safe thing to do, but, when I stop doing that, system doesn't eject those errors at any repeatable frequency anymore Feb 20 17:32:53 and, the output from cat /sys/kernel/debug/ieee80211/phy0/ath9k/reset now consistently shows 0 everywhere Feb 20 17:33:18 but with the scans running behind the scenes occaisionally, I was getting incrementing counts on the tx path hang number Feb 20 17:33:46 configuration was, unit has an ap mode adapter running, wds to another one, both bridged Feb 20 17:33:57 then a client pulling data thru that bridge Feb 20 17:34:26 eliminate the scan, and, on first round of testing here, errors seem to have gone away, or, at least reduced significantly Feb 20 17:34:46 gonna do some more testing here, and try narrow this a bit more if I can Feb 20 17:36:16 but i see no increments now on the tx path hang, which I suspect has made the root cause go away Feb 20 17:37:36 gonig to continue here narrowing this down more if i can, and try generate a repeatable test case, which demonstrates the issue, on demand Feb 20 17:39:10 interesting Feb 20 17:39:34 the setup i am working on here, is to try replace something i've used for years, with wrt54g hardware Feb 20 17:39:47 it's kind of an offbeat system, here's the setup Feb 20 17:40:03 have an ap at the house, hard wired, solid reliable power, and network Feb 20 17:40:19 another out at the barn, which is also hard wired, but, occaisionally goes offline when breakers trip Feb 20 17:40:28 and its sometimes a day before we get it back online Feb 20 17:40:43 out at the observatory, I have another ap, the wds client, it connects to the one at the barn Feb 20 17:40:52 but, when barn goes offline, it cannot see the house Feb 20 17:41:05 so, got another one, on a solar power setup, in between Feb 20 17:41:17 observatory hops thru that one, to the house, when barn is offline Feb 20 17:41:31 BUT, that one sometimes goes out, battery runs down after cloudy weather Feb 20 17:41:39 i have no way to get reliable power out there Feb 20 17:41:56 so,process on the one at the observatory, monitors the other two, and shifts wds links on the fly as needed Feb 20 17:42:02 hence the background scans Feb 20 17:42:13 it's checking to see which path is available Feb 20 17:42:51 just replicating what I had with wrt54 a long time ago, but, wrt could just make both wds at once Feb 20 17:43:21 i went this route, because when I first started fussing with it, some time back on this hardware Feb 20 17:43:34 I had lots of problems with mesh point adapters, and stability Feb 20 17:43:59 never really went back to try them again after that Feb 20 17:45:21 once I have it narrowed a bit farther, going to see if I can unravel ath9k stuff somewhat , and get to understand it Feb 20 17:45:36 and try figure out how this comes about Feb 20 18:05:55 and ofc, this may all become moot in a month, wife may be transferred in march, so, we end up moving Feb 20 18:06:03 and i gotta redo everything, based on where we move Feb 20 19:14:32 juhosg r35705 trunk/package/kernel/modules/netdevices.mk * package/kernel: add package for the Freescale Gianfar driver Feb 20 19:14:34 juhosg r35706 trunk/package/kernel/modules/other.mk * package/kernel: add package for the Gianfar PTP driver Feb 20 23:15:09 anybody look at my atheros 3.8 patch yet? **** ENDING LOGGING AT Thu Feb 21 02:59:59 2013