**** BEGIN LOGGING AT Wed Nov 27 03:00:00 2013 Nov 27 03:38:02 build #455 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/455 Nov 27 04:05:17 build #471 of at91 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/471 Nov 27 04:12:08 build #387 of sibyte is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/387 Nov 27 07:06:10 build #397 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/397 Nov 27 07:32:43 build #17 of mxs is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mxs/builds/17 Nov 27 08:46:17 build #335 of iop32x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/335 Nov 27 09:04:23 kaloz r38925 trunk/package/kernel/mac80211/Makefile * [mac80211]: fix typo in wl128x firmware names Nov 27 09:31:52 build #18 of mvebu is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/18 Nov 27 10:58:04 nbd r38926 trunk/package/kernel/mac80211/patches/ (9 files) * ath9k: merge initval updates Nov 27 12:10:39 nbd r38927 trunk/package/kernel/mac80211/Makefile * mac80211: include 802.11n support when wl12xx is selected Nov 27 12:27:20 kaloz r38928 trunk/target/linux/generic/config-3.12 * [generic/3.12]: add TI wireless symbols and enable the platform glue by default Nov 27 12:31:13 kaloz r38929 trunk/target/linux/generic/patches-3.12/998-enable_wilink_platform_without_drivers.patch * [generic/3.12]: make the wl12xx glue code available with compat-wireless, too Nov 27 12:33:05 kaloz r38930 trunk/target/linux/generic/patches-3.12/442-block2mtd_logmessages.patch * [generic/3.12]: refresh patch Nov 27 12:35:06 kaloz r38931 trunk/target/linux/omap/patches-3.12/002-ARM-dts-AM33xx-Correct-gpio-interrupt-cells-property.patch * [omap]: fix gpio interrupt-cells property on AM335x Nov 27 12:36:41 kaloz r38932 trunk/target/linux/omap/ (52 files) * [omap]: refresh/rename patches Nov 27 12:42:07 kaloz r38933 trunk/ (18 files in 3 dirs) * add device tree based initialization to wl12xx Nov 27 12:43:06 how and where to add custom kernel module build with openwrt buildbot? Nov 27 12:53:35 kaloz r38934 trunk/target/linux/omap/patches-3.12/950-am335x-evmsk-wilink-dts.patch * [omap]: initialize wl12xx from the device tree Nov 27 14:59:14 I have posted this (https://forum.openwrt.org/viewtopic.php?pid=218497#p218497) indicating the recent build for a Marvell Kirkwood for a Seagate DockStar still won't boot. Has anyone encountered this issue? Nov 27 15:11:02 KanjiMonster: the one in sysntpd doesn't have a default value Nov 27 15:11:11 but I added it and then it takes the default value and ignores the list Nov 27 15:11:25 (my cable modem crapped out last night while we were talking about this) Nov 27 15:34:34 [florian]: is safe to make an image with ubifs and bcm63xx? Nov 27 15:39:23 i want to close the jffs2 issue as soon as posible Nov 27 15:40:49 and i will make all that can if blogic and you give me some help Nov 27 15:41:01 *i can Nov 27 16:04:27 Pteridium: as a random guess, can you try http://patchwork.linux-mips.org/patch/5469/ ? Nov 27 16:05:10 ok, i'll test that patch Nov 27 16:05:13 thanks Nov 27 16:07:14 in this moment i'm testing a jffs2 image Nov 27 16:15:23 KanjiMonster: http://pastebin.com/XtQp3BFU Nov 27 16:15:31 stupid jffs2 Nov 27 16:17:23 so this is without overlay? Nov 27 16:18:12 yes Nov 27 16:19:02 could be a regression in jffs2 driver? Nov 27 16:21:30 I have some ideas Nov 27 16:21:42 I'll have to check some things later Nov 27 16:22:56 ok, i'll keep you informed Nov 27 16:25:26 KanjiMonster: in which boards have you tested bmips smp and what fs have you used?? Nov 27 16:29:21 Pteridium: tbh, I mostly tested ramdisk images Nov 27 16:29:42 (and my test targets were 6362, 6368 and 63168) Nov 27 16:30:25 gotta head home, bbl Nov 27 16:31:01 ok, now understand why nobody noticed this problem Nov 27 16:34:54 KanjiMonster: all the programs i've tested with smp enabled worked fine Nov 27 16:35:01 including cpuminer Nov 27 16:53:31 nbd: has the ath: phy2: Failed to stop TX DMA, queues=0x004! been fixed or is it still an ongoing problem ( AR9590 in 12.09) ? Nov 27 16:57:15 nighty^: that message is not an issue in itself, it is a symptom shared by many different issues, most of which have been fixed Nov 27 16:57:37 there may be some cases remaining where this message might still show up in the log Nov 27 16:57:48 but stability has significantly improved since 12.09 Nov 27 16:58:02 ok I see. Nov 27 16:58:52 would those fixe be in Attitude Adjustement ? Nov 27 16:58:57 or in Barrier Breaker ? Nov 27 16:59:00 or both Nov 27 16:59:30 nbd, Nov 27 17:03:41 many fixes are only in BB right now (waiting for more test feedback) Nov 27 17:13:11 are there more improvements since we grabbed your git tree backport about a month ago ? Nov 27 17:14:10 With that code running here, my experience is, very very few log messages on the ubiquiti hardware, and I've retired my wrt160nl stuff because it never did work well, right from the day I bought it. Nov 27 17:24:30 I am running on soekris6501 with some ar9590 mini pcie cards Nov 27 17:24:39 3 to be exact Nov 27 17:24:49 groz: haven't merged the big update in trunk to that aa-mac80211 git yet Nov 27 17:25:35 ok, just wondering Nov 27 17:25:48 it's running well for me right now, so, it aint broke, I dont need to fix it Nov 27 17:26:52 KanjiMonster: no luck with the patch you mentioned. http://pastebin.com/e9AxGur3 Nov 27 17:27:41 Pteridium: well, it was a stab in the dark - but currently it rather sounds like a race condition in jffs2 Nov 27 17:28:18 yes, or in overlayfs? Nov 27 17:28:34 I thought you had the issues without overlayfs? Nov 27 17:28:40 +also Nov 27 17:29:03 yes, only happens with jffs2 Nov 27 17:29:27 then the issue is likely not in overlayfs Nov 27 17:29:40 yes Nov 27 17:30:12 jffs2 is quite "old" and has its share of issues, I wouldn't wonder about the problem being there Nov 27 17:30:14 surely as you said: a stupid race condition Nov 27 17:32:20 What do you think about this: http://lists.infradead.org/pipermail/linux-mtd-cvs/2012-November/008218.html ? Nov 27 17:32:31 dual armv7 Nov 27 17:33:44 looks old enough to already be in 3.10 Nov 27 17:36:02 yes, the patch is applied, but other multicore architectures had a problem with jffs2 Nov 27 17:36:20 *have been applied Nov 27 17:39:02 KanjiMonster: are bcm63xx caches write-through or write-back? Nov 27 17:39:49 better question: can they be disabled? Nov 27 17:40:16 disable is easy, pull the power plug, everything disabled Nov 27 17:40:37 :D Nov 27 17:40:40 but you probably want somewhat more selective disable me thinks Nov 27 17:41:13 groz: disable l1 i and d caches Nov 27 17:41:24 fussy fussy Nov 27 17:42:06 yes ;) Nov 27 17:48:47 Pteridium: tbh, this rather smells like a race condition where e.g. the same buffer is used by two threads at the same time Nov 27 17:49:08 or a use-after-free issue, or something similar Nov 27 17:52:41 blogic: and while I agree with you that there are smp enabled platforms on openwrt that don't have that issue, I wonder how many smp enabled platforms are there that use jffs2? Nov 27 18:00:00 KanjiMonster: i think the same too: a stupid race condition Nov 27 20:37:15 hi Nov 27 20:37:30 quilt doesn't do interactive patching with -f Nov 27 20:37:43 i.e. Apply anyway? [n] Skipping patch. Nov 27 20:38:07 But I'd like it to apply anyway or at least ask me the question Nov 27 20:38:13 is there an option or something? Nov 27 20:40:50 according to the man page it does Nov 27 20:41:00 interactive unless -q is specified Nov 27 20:41:05 but might be version specific Nov 27 20:41:21 yep, but I push -f and it answers "n" itself Nov 27 20:41:25 also depending on your .quiltrc or QUILT_* env vars Nov 27 20:42:08 I set my .quiltrc as indicated in http://wiki.openwrt.org/doc/devel/patches Nov 27 20:43:21 -f is a forced apply Nov 27 20:43:54 groz: interactive force apply, if no -q. Nov 27 20:47:15 v0n: what quilt version do you use? Nov 27 20:47:30 v0n: the one bundled with openwrt (0.60) seems to confirm the behaviour documented in the man page Nov 27 20:47:42 specifying -f just relays -f to the patch program Nov 27 20:47:51 no special handling or adding of non-interactive flags Nov 27 20:48:05 ah nvm Nov 27 20:48:26 jow_laptop: 0.48, from OpenWRT 12.09 Nov 27 20:49:41 I'm looking at 0.60 and it only adds -f to patch if -f is *not* passed to quilt Nov 27 20:49:55 so quilt push -f results in no -f passed to patch Nov 27 20:50:06 but that might be different in 0.48 Nov 27 20:50:27 in doubt you can also use a newer quilt if one is shipped by your distro Nov 27 20:51:43 ok, trying with the distro one Nov 27 20:52:30 unfortunately there seems to be no counter-"-f" options for gnu patch which one could pass via env vars Nov 27 20:52:48 nop, 0.60 from distro doesn't ask either Nov 27 20:52:59 odd Nov 27 20:53:36 you could edit the quilt executable (its just a shell script) and dump $more_patch_args Nov 27 20:53:46 see what it contains in the end Nov 27 20:54:04 my brain is a bit ineffective when it comes to evaluating shell code :) Nov 27 21:18:32 jow_laptop: $more_patch_args? Nov 27 21:19:18 v0n: ? Nov 27 21:19:46 jow_laptop: was that a real variable in quilt? Nov 27 21:19:50 yes Nov 27 21:20:18 .../usr/share/quilt/push Nov 27 21:20:33 (subcommands are in extra scripts) Nov 27 21:21:17 for the openwrt bundled quilt its staging_dir/host/share/quilt/push Nov 27 21:29:01 jow_laptop: looking for the "Apply anyway? [n]" question and: Nov 27 21:29:04 $ grep -r 'anyway?' /usr/bin/quilt /usr/share/quilt/ Nov 27 21:29:08 returns nothing Nov 27 21:29:26 Am I missing something? Nov 27 21:29:41 the Apply anyway message comes from GNU patch Nov 27 21:29:51 yep ok Nov 27 21:32:04 maybe patch somehow detects that it runs in a pipe and does not ask interactive questions Nov 27 21:32:15 maybe Nov 27 21:32:17 but this is all just speculation Nov 27 21:32:38 I'm looking if there's a patch option to force this "Apply anyway?" to yes Nov 27 21:35:58 I just want to favor the file from my patch, even if the tree already has that file Nov 27 21:36:07 patch/quilt is driving me crazy Nov 27 22:01:56 KanjiMonster: is not needed an #else or an #if defined(BCMCPU_RUNTIME_DETECT) after line 28? Nov 27 22:02:12 http://lxr.free-electrons.com/source/arch/mips/include/asm/mach-bcm63xx/cpu-feature-overrides.h?v=3.10;a=mips#L27 Nov 27 22:04:45 to set #define cpu_has_dc_aliases 1 Nov 27 23:03:00 I finally have my patch ported to 12.09, but I get lots of message like: "iptable_filter: no symbol version for module_layout" Nov 27 23:03:10 seems like the kernel cannot load any module Nov 27 23:03:12 any clue? Nov 28 00:51:48 build #419 of rb532 is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/419 Nov 28 00:53:55 build #419 of ppc44x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/419 Nov 28 01:27:46 build #431 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/431 **** ENDING LOGGING AT Thu Nov 28 02:59:58 2013