**** BEGIN LOGGING AT Tue Dec 15 02:59:58 2015 Dec 15 05:27:10 build #179 of ramips is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/179 Dec 15 08:29:11 i am looking for a way to build only specific router models and versions instead of all or having to build one by one at a time. Not sure how to do it. Can anyone point me to some doc or info that addresses what i want to do ? Dec 15 08:29:27 maybe something to do with profiles? Dec 15 08:38:25 HeXiLeD: yes you have to select the router model you want to build as a profile, if the target supports this Dec 15 08:41:04 the idea is to build only single band in one shoot or dual band Dec 15 08:41:35 so i have create a createa profile with all the single band routers and another for dual band. correct? Dec 15 08:51:38 build #157 of netlogic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/netlogic/builds/157 Dec 15 09:15:48 HeXiLeD: yes Dec 15 09:46:14 am i on the right track ? http://dpaste.com/261597W Dec 15 11:02:09 nbd r47893 trunk/package/network/config/netifd/Makefile Dec 15 11:02:09 netifd: update to the latest version, fixes reload issues on routing table changes Dec 15 11:20:53 kaloz r47894 trunk/ (6 files in 3 dirs) * generic/4.4: bump to -rc5 Dec 15 11:28:00 build #177 of bcm53xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/bcm53xx/builds/177 Dec 15 11:30:23 build #145 of avr32 is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/145 Dec 15 11:30:32 build #149 of xburst is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/149 Dec 15 11:46:03 build #177 of brcm47xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/177 Dec 15 11:49:28 build #177 of brcm47xx.legacy is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx.legacy/builds/177 Dec 15 11:49:41 build #142 of ixp4xx is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/142 Dec 15 11:50:00 build #144 of kirkwood is complete: Failure [failed svn shell_15 compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/144 Dec 15 12:53:36 build #174 of ramips.rt3883 is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.rt3883/builds/174 Dec 15 13:24:55 build #172 of x86.64 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/x86.64/builds/172 Dec 15 14:20:21 build #180 of ramips is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/180 Dec 15 15:13:37 build #142 of ramips.mt7620 is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.mt7620/builds/142 Dec 15 18:02:31 build #134 of mpc83xx is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/mpc83xx/builds/134 Dec 15 18:02:39 build #177 of ipq806x is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/ipq806x/builds/177 Dec 15 18:06:49 build #173 of realview is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/realview/builds/173 Dec 15 18:10:14 what is the default lan.igmp_snooping in openwrt ? Dec 15 18:10:18 build #133 of ep93xx is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/133 Dec 15 18:10:26 is it enabled or not ? Dec 15 18:18:08 build #176 of ramips.mt7621 is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/ramips.mt7621/builds/176 Dec 15 18:18:13 build #178 of lantiq is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/178 Dec 15 19:41:24 nbd: are you around? Dec 15 19:41:39 while doing final tests with my own atm patch I noticed that you atm patch from monday broke adsl on latiq Dec 15 19:42:21 the nas0 device doesn't come up at all Dec 15 19:44:43 since my patch might be related, may i ask you to explain how does the race condition shows up and how should it work after your commit Dec 15 19:49:53 obstnerd: which patch? Dec 15 19:50:17 47891? Dec 15 19:51:04 r47891 Dec 15 19:51:19 so the race condition is this: Dec 15 19:51:32 nas0 shows up while it's not fully configured yet (doesn't have a mac address) Dec 15 19:51:38 netifd detects it, tries to bring it up Dec 15 19:51:42 fails because of the mac address issue Dec 15 19:51:55 yeah, my patch is related Dec 15 19:52:02 my patch basically tells netifd to not attempt to bring up nas0 yet Dec 15 19:52:09 waits for a second until br2684ctl is started Dec 15 19:52:13 then tells netifd that it's available Dec 15 19:52:44 i did test this on lantiq hw and it worked just fine for me Dec 15 19:52:56 so not sure what's going on in your setup Dec 15 19:53:07 my patch adds carrier status settings to the lantiq atm and ptm driver Dec 15 19:53:07 did you try it as-is without any patches? Dec 15 19:53:16 yes for sure Dec 15 19:53:19 hm Dec 15 19:53:36 two hours ago Dec 15 19:54:02 do you have some time to debug this now? Dec 15 19:54:13 unfortunally not Dec 15 19:54:23 ok, please ping me again when you have some time Dec 15 19:54:32 i mean it's not the time that i doesn't have, it's the adsl line Dec 15 19:54:32 because i can't reproduce the issue Dec 15 19:55:02 do you have hw not connected to the adsl line that you could use for testing? Dec 15 19:55:03 i have to use the backup adsl line from my company to due adsl related tests Dec 15 19:55:11 -due do Dec 15 19:55:13 theoretically the issue should show up even without an adsl connection Dec 15 19:55:24 since nas0 bringup is independent of dsl carrier sync Dec 15 19:55:43 in that case, i have time Dec 15 19:55:47 ok, great Dec 15 19:55:54 when the issue occured, was nas0 down? Dec 15 19:56:12 or was it up and simply not working? Dec 15 19:56:29 no, it wasn't up Dec 15 19:56:32 ok Dec 15 19:56:40 then we should be able to debug this without an adsl line Dec 15 19:57:14 what i'd like to know is if it shows up if you run /etc/init.d/br2684ctl restart Dec 15 19:57:24 after the system has finished booting Dec 15 19:57:32 or if it just stays down at boot time Dec 15 19:57:38 btw. what device are you using? Dec 15 19:57:57 bt homehub 5 Dec 15 19:58:08 moded to work on annex b Dec 15 20:00:37 /etc/init.d/br2684ctl restart brings the device up Dec 15 20:01:32 maybe related, I'm only doing a ramboot Dec 15 20:02:11 ok, so we need to figure out what's going on at boot time Dec 15 20:02:25 do this: Dec 15 20:02:46 write an init script that runs early (START=11) that starts the following command: Dec 15 20:03:35 ubus -m status -m invoke -M t monitor > /tmp/ubuslog.txt & Dec 15 20:04:01 let the system boot up completely Dec 15 20:04:08 copy that file from your router Dec 15 20:04:14 and throw it in a pastebin or send it to me Dec 15 20:05:11 actually, wait Dec 15 20:05:15 let's change the command a little Dec 15 20:05:25 ubus -m status -m invoke monitor > /tmp/ubuslog.txt & Dec 15 20:18:03 nbd: http://paste.debian.net/347204/ Dec 15 20:20:12 hm Dec 15 20:20:20 seems that nas0 does not become ready in time Dec 15 20:20:35 at service_running() time in the init script, the device isn't there Dec 15 20:20:39 so it doesn't clear the defer flag Dec 15 20:20:43 that's strange Dec 15 20:21:18 i guess i need to find a way to make br2684ctl call a script when the device is ready Dec 15 20:22:29 nbd: maybe it makes sense to turn it into a proper daemon Dec 15 20:23:28 actually, the code looks so trivial that it probably makes sense to move it into netifd Dec 15 20:23:54 and just get rid of this scripting hackery Dec 15 20:26:08 it just opens a socket and does a few simple ioctls Dec 15 20:26:16 it's not involved in the datapath in any way Dec 15 20:26:25 doesn't even poll anything Dec 15 20:26:31 just stays alive to keep the socket open Dec 15 20:26:42 gime a few minutes, I would like to send my patches which enable carrier signaling based on showtime status to the ml Dec 15 20:27:30 may i'm wrong, but that would let allow netifd to bring up the nas device when needed Dec 15 20:28:17 i don't think it's enough Dec 15 20:28:26 because carrier signalling only works after the device has been brought up Dec 15 20:28:51 so even with proper carrier signaling, the race is still there Dec 15 20:29:20 or are you doing this a different way for the actual atm device and triggering scripts based on that? Dec 15 20:53:24 yeah, i already noticed that the device need to be up for carrier signaling Dec 15 20:53:37 any ideas about why some smartphones are having a problem with this setup https://forum.openwrt.org/viewtopic.php?pid=303701#p303701 Dec 15 20:54:12 and i havn't had the time to check why it's the case Dec 15 21:13:25 build #134 of mvebu is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/134 Dec 15 21:16:30 Package kmod-hwmon-gpiofan is missing dependencies for the following libraries: thermal_sys.ko Dec 15 21:16:54 mvebu compiled successfully for me today.. Dec 15 21:18:45 ah, I had linux-4.4 Dec 15 22:23:03 build #169 of malta is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/malta/builds/169 Dec 15 23:40:03 from ubnt sales: "Our newer gear no longer allows for use with 3rd party firmware because we were having trouble with people counterfeiting our products. If using your firmware is required then using Ubiquiti gear is not going to help much." Dec 15 23:40:35 ubnt-- Dec 15 23:41:29 never mind locking out 3rd party firmware does nothing wrt counterfeiting, afaict Dec 15 23:48:16 russell--: that 3rd party hippy stuff was just good enough to bootstrap their own platform ;) Dec 15 23:48:34 mikrotik#2 now, I guess Dec 16 00:10:59 build #129 of mpc52xx is complete: Failure [failed shell_10] Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/129 Dec 16 00:53:32 jow_laptop: yeah ... /me wonders if they are still using uboot Dec 16 00:54:26 * russell-- guesses the bean counters have seized control, like at meraki Dec 16 00:55:17 or it's part of an elaborate pump-and-dump stock manipulation conspiracy Dec 16 01:30:32 russell--: So the newer ubnt devices have a locked bootloader? Dec 16 02:55:06 build #145 of mxs is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/mxs/builds/145 **** ENDING LOGGING AT Wed Dec 16 02:59:59 2015