**** BEGIN LOGGING AT Fri Oct 05 02:59:58 2012 Oct 05 06:34:41 build #64 of ixp4xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/64 Oct 05 07:06:26 build #84 of brcm47xx is complete: Failure [failed compile_2] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/84 Oct 05 07:29:01 build #79 of uml is complete: Failure [failed compile_6] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/79 Oct 05 07:36:20 build #85 of atheros is complete: Failure [failed compile_2] Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/85 Oct 05 08:05:59 build #85 of orion is complete: Failure [failed compile_2] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/85 Oct 05 08:34:38 build #81 of lantiq is complete: Failure [failed compile_2] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/81 Oct 05 09:03:56 build #82 of ramips is complete: Failure [failed compile_2] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/82 Oct 05 09:08:18 build #77 of pxcab is complete: Failure [failed shell_11] Build details are at http://buildbot.openwrt.org:8010/builders/pxcab/builds/77 Oct 05 09:20:32 i've had a couple instances recently of eth0 going away inexplicably on a rb493g Oct 05 09:20:53 i don't have very much to go on Oct 05 09:22:25 rebooting fixes it, i see some speed/duplex negotiation messages in the syslogs, but i see the same (or extremely similar) messages when everything keeps working. Oct 05 09:22:59 i keep forgetting to look at "brctl show" output before rebooting Oct 05 09:25:43 check your ethernet cable maybe? Oct 05 09:26:10 there are 4 ports associated with eth0, all of them go away at once Oct 05 09:28:57 ok Oct 05 09:37:51 russell--: the whole interface vanishes? or does it stay in down mode? Oct 05 09:39:10 build #81 of ppc40x is complete: Failure [failed compile_2] Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/81 Oct 05 09:43:56 build #76 of rb532 is complete: Failure [failed shell_11] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/76 Oct 05 09:47:32 build #76 of ppc44x is complete: Failure [failed shell_11] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/76 Oct 05 10:18:24 build #74 of x86 is complete: Failure [failed compile_2] Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/74 Oct 05 10:47:25 build #73 of ar7 is complete: Failure [failed compile_2] Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/73 Oct 05 10:51:32 build #67 of sibyte is complete: Failure [failed shell_11] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/67 Oct 05 11:23:42 build #68 of avr32 is complete: Failure [failed compile_2] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/68 Oct 05 11:41:02 build #89 of at91 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/89 Oct 05 12:47:18 KanjiMonster: I'll have to look more thoroughly next time Oct 05 12:49:02 the first thing i notice is that that network stops getting leases and then i realize the people on it aren't connected anymore. then, i forget what i should be looking at, and reboot to let things work again. hopefully i'll remember next time ;-) Oct 05 12:49:36 * russell-- has an open network for the neighbors, they are on that interface. Oct 05 12:50:42 for reference, it's r33395 Oct 05 12:51:01 russell--: I know of at least one other report with the same smyptoms on a different device (iirc ar724x; using the internal switch) Oct 05 12:51:59 cool, hopefully i'll have more information next time Oct 05 12:52:11 i have eth0 and an wlanN interface bridged together Oct 05 12:54:42 uptime was in the neighborhood of a week each time, maybe a little less, i think Oct 05 15:16:38 I'm trying to compile a library that uses libev, and it works ok on trunk, but backfire complains about ""memory fences not defined for your architecture, please report" Oct 05 15:16:51 is that something I can fix, or is it something that's ging to be a problem in libev to fix? Oct 05 15:18:12 ask the libev people? Oct 05 18:36:56 build #80 of cobalt is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/80 Oct 06 00:25:40 build #62 of au1000 is complete: Failure [failed compile_2] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/62 Oct 06 00:28:38 build #55 of gemini is complete: Failure [failed shell_11] Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/55 Oct 06 00:59:17 build #52 of mcs814x is complete: Failure [failed compile_2] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/52 Oct 06 01:29:28 build #56 of adm5120 is complete: Failure [failed compile_2] Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/56 Oct 06 01:58:34 build #88 of brcm63xx is complete: Failure [failed compile_2] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/88 Oct 06 02:29:50 build #90 of at91 is complete: Failure [failed compile_2] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/90 **** ENDING LOGGING AT Sat Oct 06 03:00:01 2012