**** BEGIN LOGGING AT Thu Aug 15 03:00:00 2013 Aug 15 06:16:13 build #356 of brcm47xx is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/356 Aug 15 08:17:21 build #319 of rb532 is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/319 Aug 15 08:28:27 build #319 of ppc44x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/319 Aug 15 09:23:28 nbd r37790 trunk/target/linux/ generic/patches-3.10/131-mips_inline_dma_ops.patch generic/patches-3.10/131-improve_noncoherent_dma_checks.patch generic/patches-3.10/132-mips_inline_dma_ops.patch generic/patches-3.10/130-mips_remove_plat_dma_functions.patch * kernel: improve dma ops inlining patches Aug 15 09:30:14 nbd r37791 trunk/target/linux/generic/patches-3.10/131-improve_noncoherent_dma_checks.patch * kernel: fix a small #ifdef bug in the noncoherent dma check rework Aug 15 09:53:30 build #332 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/332 Aug 15 09:57:48 build #302 of sibyte is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/302 Aug 15 10:34:12 jow r37792 trunk/package/system/procd/Makefile * procd: update to git head Aug 15 12:55:56 build #312 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/312 Aug 15 13:57:31 nbd r37793 trunk/package/kernel/mac80211/patches/300-pending_work.patch * mac80211: merge upstream change to fix mesh rssi thresholds Aug 15 14:11:11 build #351 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/351 Aug 15 15:40:45 can anyone explain this? http://pastebin.com/Kz9gLhC6 Aug 15 16:00:08 Error pointer deref Aug 15 16:06:43 larsc: why is it doing that only when the usb is plugged on boot, and not later? Aug 15 16:09:36 don't know Aug 15 17:40:03 if I want to commit a package into openwrt. which mail list shall I send patch Aug 15 17:40:11 it is a patch for cups as some Canon printer need special backend called capt Aug 15 17:52:38 ayaka: https://dev.openwrt.org/wiki/SubmittingPatches Aug 15 17:59:02 KanjiMonster, I am sorry for my bad english, I have read it but I asked Aug 15 17:59:14 before I asked Aug 15 17:59:39 ayaka: it's openwrt-devel (requires registration) Aug 15 18:00:12 KanjiMonster, thank you Aug 15 18:01:37 ayaka: it's a bit hidden in https://dev.openwrt.org/wiki/SubmittingPatches#a5.Selecte-maildestination. ("Unless you have a reason NOT to do so, always CC openwrt-devel lists.openwrt.org. If no maintainer is listed, send your patch to the primary OpenWrt developer's mailing list.") Aug 15 18:01:54 build #267 of iop32x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/267 Aug 15 18:02:19 KanjiMonster, thank you so much Aug 15 18:06:27 ayaka: I have updated the section to link to the registration page for the mailing list Aug 15 18:39:15 heffer: you left out ohci in the preselected pkgs, and usb won't work without it Aug 15 18:48:30 DonkeyHotei: indeed. looks like that is the case Aug 15 18:48:42 never tried using USB 1.1 devices though Aug 15 18:49:41 most 3G dongles are 1.1 Aug 15 18:50:35 not really, they work fine with ehci Aug 15 18:51:09 is that the case? well mine all seem to be usb 2.0 Aug 15 18:53:34 i had 4 of them (one of which i sold to a friend so i can't test) Aug 15 18:53:47 of the remaining 3, 2 are 1.1 Aug 15 18:54:30 the third produces this: http://pastebin.com/Kz9gLhC6 Aug 15 18:56:30 and how can you say it is related to usb 1.1.? Aug 15 18:57:30 afaik, usb 2.0 is backwards compatible with 1.1 devices Aug 15 18:58:13 1.1 devices are not recognized without ohci included Aug 15 18:58:23 plugging them in does nothing Aug 15 18:59:01 i still do not know how to fix the kernel oops on 2.0, though Aug 15 18:59:04 yeah that's what i'd expect would happen. i guess we should be adding ohci then Aug 15 19:48:51 KanjiMonster, [florian]: excuse me; is this info enough? https://lists.openwrt.org/pipermail/openwrt-devel/2013-August/021058.html Aug 15 19:49:12 which more tests must i do? Aug 15 20:01:05 Pteridium: tbh, I don't even have an idea where to look for the issue (and didn't have time for trying to reproduce it yet) Aug 15 20:01:55 Pteridium: ah wait, you say the issue even happens on !SMP kernels? Aug 15 20:02:29 yes, sadly yes Aug 15 20:03:03 Pteridium: actually that means that isn't an SMP issue and it should be easier to reproduce, I'd call it a plus ;D Aug 15 20:03:17 xD Aug 15 20:03:53 if you have no time then leave it in the bottom of the TODO list Aug 15 20:04:30 I'll be away the next week; I'll take a look at it if I'm back Aug 15 20:04:43 but maybe [florian] has some time, too Aug 15 20:05:00 from what I can tell enabling fpu emulation is enough? Aug 15 20:05:15 no!, al of you are very busy and we can wait Aug 15 20:05:32 all* Aug 15 20:06:21 fpu emulation is not the problem Aug 15 20:07:07 the problem happens when we select block-mount only Aug 15 20:15:08 blogic: is there any way to make procd init messages more verbose? Aug 15 20:16:16 ah okay Aug 15 20:18:37 or in ubox Aug 15 20:18:52 KanjiMonster: okay? Aug 15 20:19:09 regarding the reproducability Aug 15 20:20:19 ah! Aug 15 20:21:12 Note: my brain works like a 80186 :( Aug 15 20:21:48 and I'm doing other stuff AFK so my responses often come with long delay ;) Aug 15 20:22:13 no problem, your stuff is the first Aug 15 20:36:05 KanjiMonster: any headway on the wgt634u switch detection? Aug 15 20:58:26 I'm trying to understand where this weird mac address came from, for the wireless interface Aug 15 20:58:33 google didn't help.. Aug 15 21:05:22 Devastator: some drivers use a random mac if the eeprom provided one is not valid Aug 15 21:05:36 russell--: not really, haven't had time for it lately Aug 15 21:06:07 russell--: if you are using gcc 4.6-linaro, you could try to use 4.8 in case it is a compiler bug (not that I expect it to be) Aug 15 21:11:06 KanjiMonster hummm, interesting.. Aug 15 21:11:24 Devastator: at least ath9k does Aug 15 21:19:22 ramips probably does as well Aug 15 21:19:32 let me see if I can access the device Aug 15 21:42:39 KanjiMonster while messing with base-files, do I have to make clean && make? Aug 15 21:43:22 Devastator: make package/base-files/clean should be enough Aug 15 21:43:35 then make? Aug 15 21:43:39 yes Aug 15 21:43:44 great Aug 15 21:44:36 wrong offset, I never thought there was a marker on the eeprom Aug 15 22:14:52 meh, it asked for if I wanted SPI_RALINK, I said yes, isn't it used in someway anyway? Aug 15 22:31:36 KanjiMonster git pull is to update my local openwrt repo, right? Aug 15 22:36:34 Devastator: depends on whether you have local commits or not Aug 15 22:37:29 not on master Aug 15 22:38:09 I forget frequently git commands Aug 15 22:38:21 the only I remember is git status heheh Aug 15 22:38:50 if you don't then a git pull --ff is enough Aug 15 22:39:16 thanks Aug 15 22:39:51 let's see git log to verify I have latest trunk Aug 15 23:55:22 build #270 of ep93xx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/270 Aug 16 00:19:38 luka r37794 trunk/tools/cmake/Makefile * [tools] cmake: upgrade to 2.8.11.2 Aug 16 00:19:39 luka r37795 trunk/tools/mm-macros/Makefile * [tools] mm-macros: upgrade to 0.9.6 Aug 16 00:19:41 luka r37796 trunk/tools/mtools/Makefile * [tools] mtools: upgrade to 4.0.18 Aug 16 00:19:42 luka r37797 trunk/tools/xz/Makefile * [tools] xz: upgrade to 5.0.5 Aug 16 01:49:23 build #291 of ar71xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/291 Aug 16 02:41:37 build #357 of brcm47xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/357 **** ENDING LOGGING AT Fri Aug 16 02:59:58 2013