**** BEGIN LOGGING AT Fri May 23 03:00:01 2014
May 23 03:20:44 <5EXAA8SU8> build #467 of mcs814x is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/467
May 23 04:26:15 <5EXAA8SU8> build #66 of pxa is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/pxa/builds/66
May 23 05:05:23 * russell-- just noticed commit 86b4d5ef68ca77ff6724ebb9bddd6b93239c87fc, which includes the comment 'Hopefully there are not many howtos using "mtd" command.' ...try googling the three words: mtd trx linux 
May 23 05:06:29 <DonkeyHotei> link?
May 23 05:06:43 <russell--> it'd be nice if whoever thought that changing the partition name was a good idea would go and fix those
May 23 05:07:05 <russell--> the commit is from openwrt.git
May 23 05:07:24 <russell--> aka r38973
May 23 05:14:06 <russell--> i guess it would have been nice to be cc'd on the discussion of this
May 23 06:17:11 <5EXAA8SU8> build #571 of ar7 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/571
May 23 06:19:23 <OpenWrt-Commits> cyrus r40824 trunk/package/network/ipv6/odhcp6c/Makefile * odhcp6c: add support for option passthru
May 23 06:27:48 <OpenWrt-Commits> cyrus r40825 trunk/package/network/ipv6/odhcp6c/files/dhcpv6.script * odhcp6c: export passthru options as netifd data
May 23 06:30:38 <OpenWrt-Commits> cyrus r40826 trunk/package/network/ipv6/odhcp6c/Makefile * odhcp6c: improve passthru filter
May 23 06:57:53 <5EXAA8SU8> build #68 of x86_64 is complete: Failure [failed compile_1]  Build details are at http://buildbot.openwrt.org:8010/builders/x86_64/builds/68
May 23 07:56:51 <5EXAA8SU8> build #67 of adm8668 is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/adm8668/builds/67
May 23 08:09:29 * russell-- encountered problems with building mac80211 for wzr600dhp
May 23 08:10:57 <5EXAA8SU8> build #507 of au1000 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/507
May 23 08:11:20 <russell--> /home/openwrt/src/openwrt/build_dir/target-mips_34kc_uClibc-0.9.33.2/linux-ar71xx_generic/compat-wireless-2014-05-19/include/linux/ath9k_platform.h /home/openwrt/src/openwrt/build_dir/target-mips_34kc_uClibc-0.9.33.2/linux-ar71xx_generic/linux-3.10.36/include/linux/ath9k_platform.h differ: char 1332, line 43
May 23 08:18:24 <OpenWrt-Commits> luka r40827 trunk/target/linux/ kirkwood/profiles/120-pogoplug.mk kirkwood/patches-3.14/150-pogoplug_e02.patch * kirkwood: add Pogoplug E02 kernel support for 3.14
May 23 08:18:26 <OpenWrt-Commits> luka r40828 trunk/package/boot/uboot-kirkwood/ patches/200-openwrt-config.patch patches/140-pogoplug_e02.patch Makefile * [package] uboot-kirkwood: re-add Pogoplug E02 support
May 23 08:18:27 <OpenWrt-Commits> luka r40829 trunk/package/boot/uboot-envtools/files/kirkwood * [package] uboot-envtools: add Pogoplug E02 support
May 23 08:18:37 <luka> heffer: very nice work ;)
May 23 08:42:14 <5EXAA8SU8> build #466 of gemini is complete: Failure [failed shell]  Build details are at http://buildbot.openwrt.org:8010/builders/gemini/builds/466
May 23 08:55:03 <OpenWrt-Commits> cyrus r40830 trunk/target/linux/ generic/patches-3.13/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch generic/patches-3.12/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch generic/patches-3.14/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch generic/patches-3.10/666-Add-support-for-MAP-E-FMRs-mesh-mode.patch * Add missing bracket in MAP-E FMR kernel support
May 23 09:32:49 <dape> nbd, ping please, if you can take a look at this compile problem for d-link dir-825 with dfs.. http://codepad.org/nIorevRv
May 23 09:36:52 <OpenWrt-Commits> luka r40831 trunk/package/kernel/linux/modules/other.mk * kernel: other.mk: add pps-gpio support
May 23 11:15:46 <Mazilo> Can any openwrt.org admin please help? It looks like my IP Address gets blacklisted again by the sshguard when I perform an 'svn up; make package/symlinks'.
May 23 11:16:09 <karlp> stop using svn? :)
May 23 11:16:30 <Mazilo> Did you mean to use git?
May 23 11:16:37 <karlp> yeah
May 23 11:17:04 <Mazilo> I have a limited amount of HDD space to use git.
May 23 11:17:18 <cyrusff> git uses way less disk space compared to svn btw.
May 23 11:17:26 <cyrusff> that is in most cases
May 23 11:18:40 <Mazilo> I thought when using git pull, it also pulls the deltas.
May 23 11:18:54 <cyrusff> yep but they are compressed
May 23 11:19:26 <dottedmag> 148M svn checkout compared to 182M git checkout, and the difference is more-or-less constant.
May 23 11:19:28 <cyrusff> and svn keeps 2 uncompressed copies of the current version of each file
May 23 11:19:35 <Mazilo> cyrusff: BTW, I now can git push to telephony repo. Thank you.
May 23 11:19:46 <Mazilo> IC.
May 23 11:19:57 <cyrusff> dottedmag: YMMV ;)
May 23 11:20:14 <dottedmag> Yes, depends on FS, SVN version etc.
May 23 11:20:20 <cyrusff> but you can easily nuke some of the git history
May 23 11:20:28 <cyrusff> if you don't need it
May 23 11:20:47 <dottedmag> Eh, 38 megs different not worth mentioning -- build artifacts will take much more.
May 23 11:20:52 <cyrusff> ok lunch break
May 23 11:20:54 <dottedmag> *difference
May 23 11:20:58 <Mazilo> cyrusff: can you please elaborate on how to do that? I am much interested in this.
May 23 11:20:58 <cyrusff> right
May 23 11:21:19 <dottedmag> Mazilo: git clone --depth <number of revisions to check out> ...
May 23 11:21:35 <Mazilo> dottedmag: Cool and thank you.
May 23 11:22:06 <dottedmag> Mazilo: but the resulting repository is basically read-only.
May 23 11:22:20 <dottedmag> You can fetch new revisions to it though.
May 23 11:22:37 <Mazilo> dottedmag: so long as I can do a pull to update later on.
May 23 11:23:38 <Mazilo> dottedmag: If you look at FS git repo which is huge.
May 23 11:23:57 <dottedmag> uhm?
May 23 11:24:21 <Mazilo> dottedmag: When compressed with xz, it is about 200MB in size.
May 23 11:24:37 <karlp> still insignificant compared to he build artifacts
May 23 11:25:22 <dottedmag> Mazilo: .git contents is compressed, so packing it in a xz-ed tarball does not significantly change its size.
May 23 11:25:30 <Mazilo> dottedmag: That's right. But, if I can cut that down to 10%, that is a savings I an use on build.
May 23 11:26:48 <Mazilo> dottedmag: IIRC, there is almost 2x reductions in size from bz2 to xz on FS source.
May 23 11:29:02 <Mazilo> dottedmag: If I can cut down from 400MB in size (bz2) to about 30MB in size (xz with git clone --depth <number of revisions to check out>), there will be about 350MB+ space I can use. Right now, I only have a 200GB HHD on my computer and it is almost filled.
May 23 11:30:18 <Mazilo> Anyway, Is there any openwrt.org admin here who can help to remove my IP Address from the blacklist?
May 23 11:32:54 <swalker> russell--: clean your kernel, if you haven't already
May 23 11:43:49 <Mazilo> Can any openwrt.org admin help to remove my IP Address from the blacklist? I can even access the openwrt forum.
May 23 11:49:12 <g10h4ck> nbd i have another problem happening that maybe can help us understanding what is the cause
May 23 11:49:37 <g10h4ck> macaddr is not applied both if setted in device section or in interface section
May 23 12:47:48 <DonkeyHotei> i grabbed a wrt54gs v2 with a sticker on it saying "bricked" and got a jtag header onto it, but urjtag reports "TDO seems to be stuck at 1" after the LEDs come on and settle to a blinking power. anyone ever seen similar?
May 23 12:59:45 <5EXAA8SU8> build #68 of mpc83xx is complete: Failure [failed compile_8]  Build details are at http://buildbot.openwrt.org:8010/builders/mpc83xx/builds/68
May 23 13:40:02 <5EXAA8SU8> build #69 of cns21xx is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/cns21xx/builds/69
May 23 14:54:40 <karlp> jow_laptop: I'm trying to follow http://wiki.openwrt.org/doc/techref/ubus#access.to.ubus.over.http but getting a bit stuck,
May 23 14:54:50 <karlp> I can use ubus -v call file read '{"path": "/tmp/tfile"}' from the cli, and that works well,
May 23 14:54:58 <karlp> but curl --data "method=list" http://eg-134867.local/ubus/
May 23 14:55:11 <karlp> and curl --data-urlencode "method=call&object=file&function=read&data={'path':'/tmp/tfile'}" http://eg-134867.local/ubus don't work at all
May 23 14:55:26 <karlp> I just get {"jsonrpc":"2.0","id":null,"error":{"code":-32700,"message":"Parse error"}} returned all the time
May 23 14:58:28 <cyrusff> karlp: you have to send json in the post-body
May 23 14:58:39 <cyrusff> see jsonrpc-specs
May 23 14:58:52 <karlp> wher eis jsonrpc-specs?
May 23 14:58:56 <cyrusff> google ;)
May 23 14:59:06 <cyrusff> version 2.0
May 23 14:59:09 <cyrusff> for the specs
May 23 15:00:07 <karlp> ok, wasn't aware this was any standard thing :)
May 23 15:00:49 <karlp> the access.ubus.over.http section was just showing "method=call&sid=...&object=...&function=...&data=..."
May 23 15:00:54 <cyrusff> yeah you can actually find implementations for most major programming languages
May 23 15:01:15 <cyrusff> this wiki page looks wrong if you ask me
May 23 15:01:50 <jow_laptop> yeah that wiki page is completely wrong
May 23 15:01:56 <karlp> that would agree with what I was seeing :)
May 23 15:02:03 <jow_laptop> its also way more complicated
May 23 15:02:20 <jow_laptop> for the current ubus via http you need to setup acls and login to be able to see anything
May 23 15:02:44 <jow_laptop> unless you disable authentication in uhttpd-mod-ubus with the "-a" flag
May 23 15:03:05 <karlp> so /etc/config/uhttpd just has "option ubus_prefix '/ubus'"
May 23 15:03:14 <karlp> and that won't actually do anything without further config then?
May 23 15:03:58 <jow_laptop> it will
May 23 15:04:14 <jow_laptop> but you'll get permission denied for all accesses because you need to setup acls first
May 23 15:04:17 <jow_laptop> moment...
May 23 15:06:35 <jow_laptop> #1 an acl definition in /usr/share/rpcd/acl.d/whatever.json - http://pastebin.com/Pc9GgSsv
May 23 15:07:19 <karlp> ok, and jsonrpc docs say "{"jsonrpc": "2.0", "method": "subtract", "params": {"subtrahend": 23, "minuend": 42}, "id": 3}" for calls with named params
May 23 15:07:36 <karlp> how does that translate to ubus call <path> <method> [<message with further named args>]
May 23 15:07:49 <jow_laptop> #2 a login account in /etc/config/rpcd: http://pastebin.com/AQYBzxqD
May 23 15:08:44 <karlp> ok, I already have #2 out of the box on current trunk it seems
May 23 15:09:14 <jow_laptop> nope, only an unauthenticated acl which just grants enough rights to allow you to call login
May 23 15:09:43 <karlp> what should "wahtever" be, in /usr/share/rpcd, there's already unauthenticated.json,
May 23 15:09:53 <jow_laptop> name is arbritary
May 23 15:09:58 <jow_laptop> the files are read via globbing
May 23 15:10:09 <jow_laptop> but you can call it "superuser" or "root" for clarity
May 23 15:11:07 <karlp> you mean there can only be one file?
May 23 15:11:18 <jow_laptop> there can be as many as you like
May 23 15:11:23 <jow_laptop> they're all merged
May 23 15:12:15 <karlp> so the top level key in blah.json and whatever.json is used rather thean the filename then I presume, and where do _those_ match to?
May 23 15:12:42 <jow_laptop> to the "list read" and "list write" keys in config login of /etc/config/rpcd
May 23 15:12:50 <jow_laptop> those map acl roles to user accounts
May 23 15:12:53 <karlp> right, thanks :) that's the bit I was missing
May 23 15:13:33 <jow_laptop> on to step #3 - perform a login: http://pastebin.com/awTkKHHU
May 23 15:14:02 <jow_laptop> the sessionid "00000000000000000000000000000000" is a speciall nul-session which just has enough access rights for the session.login ubus call
May 23 15:14:13 <karlp> does the number of those 0s matter?
May 23 15:14:18 <jow_laptop> yes, 32
May 23 15:16:19 <karlp> ok, calling the login without setting up the acls gives me no erorrs, just a {"jsonrpc":"2.0","id":1,"result":[6]} which is ok, I didn't follow the rules, but is that what's meant to be received if you don't have access?
May 23 15:17:36 <karlp> in your example superuser.json file, it lists ubus: * and uci: *
May 23 15:17:50 <jow_laptop> yes, code 6 is the ubus return code - UBUS_STATUS_PERMISSION_DENIED
May 23 15:18:09 <karlp> is it correct to presume that ubus: [file,log, service] would be valid too? and do you need uci:* when uci is avialable via ubus as well?
May 23 15:18:20 <karlp> that's just for the existing json-rpc for uci, from luci1 right?
May 23 15:19:13 <jow_laptop> ubus: { file: [ "*" ], log: [ "*" ], service: [ "*" ] } would be valid
May 23 15:19:38 <jow_laptop> it would grant access to ubus call file *, ubus call log *, ubus call service *
May 23 15:19:47 <karlp> ok, that makes sense.
May 23 15:20:07 <jow_laptop> the uci: scope is used for the uci api provided by rpcd
May 23 15:20:18 <jow_laptop> to allow defining per-file permissions
May 23 15:20:29 <jow_laptop> because using the ubus scope you can onyl say uci set is allowed or not allowed
May 23 15:20:44 <jow_laptop> but not specify that it is allowed to e.g. modify /e/c/system but not /e/c/network
May 23 15:21:23 <jow_laptop> if you do not use the ubus uci api then you do not need to define uci: acls either
May 23 15:22:38 <karlp> ok, do you have an example of making a call now that I have the ubus_rpc_session key now?
May 23 15:22:44 <jow_laptop> http://pastebin.com/KiixX6Vt
May 23 15:23:54 <jow_laptop> so the json container format is:   { "jsonrpc": "2.0", "id": <unique-id-to-identify-request>, "method": "call", "params": [ <ubus_rpc_session>, <ubus_object>, <ubus_method>, { <ubus_arguments> } ] }
May 23 15:24:01 <karlp> yay, it worked.
May 23 15:24:26 <karlp> ok, thanks heaps, now to spend a bunch of time writing into the wiki :|
May 23 15:24:43 <jow_laptop> the "id": key is merely echo'ed by the server, so its most not be strictly unique
May 23 15:24:45 <karlp> I'll just replace the whole section in http://wiki.openwrt.org/doc/techref/ubus#access.to.ubus.over.http ok?
May 23 15:25:00 <jow_laptop> its mainly intended for client software to easily relate responses to previously made requests
May 23 15:25:03 <jow_laptop> yep
May 23 15:25:14 <jow_laptop> *it must not be strictly unique
May 23 15:25:44 <jow_laptop> its type is also not specified afair
May 23 15:26:02 <jow_laptop> can be an sha1 hash, md5 sum, sequence counter, unix timestamp, ...
May 23 15:26:09 <jow_laptop> either number or string
May 23 15:26:29 <karlp> I was looking into this to try and make some web pages simpler than calling luci1 lua controllers to do stuff and squirt responses back, I guess this moves all the coding into my javascript instead now :)
May 23 15:26:38 <jow_laptop> yes
May 23 15:26:51 <jow_laptop> there is also some initial luci2 prototype implemented in js
May 23 15:27:02 <karlp> yeah, I've seen teh discussions a bit, haven't tried it out yet
May 23 15:27:25 <karlp> eventually there'll be a magical ubus-websockets right? ;)
May 23 15:27:40 <jow_laptop> dunno, if someone implements it - why not
May 23 15:28:00 <jow_laptop> as far as I understood it, just the transport layer would change
May 23 15:28:04 <jow_laptop> the json protocol would remain
May 23 15:28:46 <karlp> yeah, not my strength either
May 23 15:29:10 <jow_laptop> one thing I will add soon is to add CORS headers to uhttpd-mod-ubus
May 23 15:29:28 <jow_laptop> so ajax2 capable browser can access it from anywhere, not just within the same origin domain
May 23 15:29:53 <jow_laptop> this way you can host the webui somewhere else and can login using ip + user + pass to any router
May 23 15:29:59 <karlp> I've got an mqtt broker on my device, just because it plays with more people than ubus/dbus, at least from my poitn of view, and I want to get a lot of that out into the browser, we've been doing writing out to files and lua controllers to read them in again, and delete old ones, which is a bit lunky.
May 23 15:30:16 <karlp> sounds interesting
May 23 15:30:28 <karlp> I need to make sure https works too really,
May 23 15:30:40 <jow_laptop> yeah, thats more or less a precondition
May 23 15:31:54 <karlp> at least it only needs _a_ cert, it can be the same cert on all devices
May 23 15:32:01 <jow_laptop> btw, here's a more complicated acl file as used by luci2 atm: http://git.openwrt.org/?p=project/luci2/ui.git;a=blob;f=luci2/share/acl.d/luci2.json
May 23 15:32:25 <jow_laptop> instead of granting access to anything it defines multiple scopes needed for various pages
May 23 15:32:32 <karlp> thanks, that's a good example to help understand what you can do
May 23 15:33:20 <jow_laptop> and an example guest account: http://pastebin.com/gfcMDY7p
May 23 15:33:23 <karlp> do those then need different users in /etc/config/rpcd for each of them?
May 23 15:33:38 <jow_laptop> read only access to everything except the software tasks (opkg calls etc.)
May 23 15:33:48 <jow_laptop> no write access
May 23 15:33:57 <karlp> so $p$xxxx is passwords from /etc/passwd
May 23 15:34:11 <jow_laptop> $p$<user> refers to /etc/shadow
May 23 15:34:11 <karlp> what's $1? is this some traditional linux password thing I should know from somewhere else?
May 23 15:34:26 <jow_laptop> $1$ is just a crypt() hash
May 23 15:34:32 <jow_laptop> using sha1
May 23 15:34:37 <jow_laptop> the same stuff used in /etc/shadow
May 23 15:34:53 <jow_laptop> you can generate it using e.g. "uhttpd -m secret"
May 23 15:35:46 <karlp> so in the big luci2.json, those are just _definitions_ of sections and access,
May 23 15:35:47 <jow_laptop> or on a normal linux using "mkpasswd -m md5 secret"
May 23 15:35:54 <jow_laptop> right
May 23 15:36:06 <karlp> you still need to setup the rpcd users to give accesses to each of those blocks
May 23 15:36:13 <jow_laptop> yes
May 23 15:36:47 <karlp> ok, my brain's about full for right now, I'll try and digest a bit of this and write it up, but there'll probably still be mistakes on the wiki when I'm finished :)
May 23 15:36:49 <jow_laptop> and the default account shipped is http://pastebin.com/wrBkeHix
May 23 15:37:19 <jow_laptop> means: username root, password from root (same as ssh etc.) and read+write access to any definition in any /usr/share/rpcd/acl.d/*.json
May 23 15:37:43 <karlp> oh, ok, and because the default _definitions_ are that unauthenticated.json, you can login, but you can't actually do anyuthing even after logging in
May 23 15:37:52 <jow_laptop> exactly
May 23 15:38:04 <jow_laptop> if you issue via ssh "ubus call session list"
May 23 15:38:18 <jow_laptop> you should see a dump of all sessions including their effective acls
May 23 15:40:19 <mhei> Hi all. I would like to play a little bit with an own instance of a buildbot. Is the configuration/scripts which drives the buildbots somewhere documented. I didn't find anything at the wiki/google...
May 23 15:43:37 <karlp> one more thing, currently, with the lua controllers, once you're logged in, you're in, and I don't hve to do anything to handle session expiry/timouts,
May 23 15:43:59 <karlp> do you have any advice on how to handle this via the jsonrpc interface?
May 23 15:44:20 <jow_laptop> sessions timeout after by default 300s
May 23 15:44:31 <karlp> I saw that I got :-32002, Access denied when the session had expired
May 23 15:44:46 <jow_laptop> whenever you use the session, e.g. performing a call, the coutdown is reset
May 23 15:45:07 <karlp> just hinking about how to handle this in the UI actually,
May 23 15:45:26 <jow_laptop> luci2 performs aheartbeat every 5 seconds
May 23 15:45:51 <jow_laptop> it calls session.access on its own sessions to see whether it is still logged in
May 23 15:45:59 <jow_laptop> if not, the login prompt will pop up
May 23 15:46:35 <jow_laptop> so as  long as the network connectivity works, the session never expires
May 23 15:48:39 <karlp> ok, that's if I'm in the luci2 ui. fair enough :)
May 23 15:48:55 <karlp> I was looking at using this in our existing luci app, but I guess that's my problem then :)
May 23 15:48:57 <jow_laptop> "timeout": is a property of the login call btw, so you can specify something higher - like 3600s
May 23 15:49:15 <jow_laptop> I plan to switch luci1 to ubus sessions as well
May 23 15:49:43 <karlp> before or after barrier breaker gets released? ;)
May 23 15:49:47 <jow_laptop> but not decided yet as this would pull in rpcd and uhttpd-mod-ubus as requirements, making it bigger again
May 23 15:50:04 <karlp> would be a nicer position to go forward from though,
May 23 15:50:16 <jow_laptop> on the other hand I got remove a lot of server side data gathering code from the controlers and do it in js instead
May 23 15:50:22 <jow_laptop> *I could
May 23 16:00:10 <karlp> so, the /ubus url, that's not really actually _ubus_, that's rpcd? is that correct?
May 23 16:00:47 <jow_laptop> no, uhttpd
May 23 16:01:03 <jow_laptop> rpcd is just a service which happens to provide the serssion.* namespace which uhttpd uses to aurthenticate
May 23 16:01:06 <jow_laptop> brb
May 23 16:04:30 <karlp> the reason I asked, is that ubus from the command line doesn't need any logins or acls, but uhttpd-mod-ubus does, and those acls are setup in the rpcd directory, not any ubus directory
May 23 16:14:32 <jow_laptop> yes, basically for any request received by /ubus, uhttpd runs "ubus call session access '{ ubus-rpc-session, requested-object, requested-method }'
May 23 16:14:48 <jow_laptop> and however is providing the ubus session.* namespace is in charge of implementing the acl
May 23 16:14:53 <jow_laptop> this happens to be rpcd
May 23 16:15:05 <jow_laptop> *whoever
May 23 16:15:34 <jow_laptop> in the very beginning the sessioning was part of uhttpd but we decided it belongs into a separate service
May 23 16:16:05 <jow_laptop> because the ubus-json-http bridge is just one of various possible access methods for ubus
May 23 16:16:47 <jow_laptop> another theoretical access method would be a tcp server directly speaking blobmsg, instead of using the json<>blobmsg conversion with http as transport
May 23 16:17:00 <jow_laptop> that json+http approach was implemented to be browser friendly
May 23 16:17:32 <jow_laptop> for native client applications, e.g. some Qt program running on a mobile phone there'd be more efficient protocols, like plain tcp + tls + blobmsg
May 23 16:51:05 <g10h4ck> jow_laptopi am trying to debug the multiple 8021ad device problem
May 23 17:19:03 <russell--> swalker: duh, thank you for the reminder.
May 23 17:39:44 <5EXAA8SU8> build #573 of ppc44x is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/573
May 23 17:40:00 <5EXAA8SU8> build #573 of rb532 is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/573
May 23 17:40:34 <5EXAA8SU8> build #542 of sibyte is complete: Failure [failed shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/542
May 23 18:38:58 <5EXAA8SU8> build #613 of cobalt is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/613
May 23 18:39:16 <5EXAA8SU8> build #480 of iop32x is complete: Failure [failed shell shell_10]  Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/480
May 23 18:45:31 <5EXAA8SU8> build #583 of uml is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/583
May 23 18:49:52 <OpenWrt-Commits> nbd r40832 trunk/include/kernel-version.mk * kernel: remove md5sum for 3.7
May 23 18:49:57 <OpenWrt-Commits> nbd r40833 trunk/target/linux/ (9 files in 9 dirs) * kernel: add a ssb backport required for a new mac80211 update
May 23 18:50:01 <OpenWrt-Commits> nbd r40834 trunk/package/kernel/ (18 files in 2 dirs) * mac80211: update to wireless-testing 2014-05-22
May 23 19:04:35 <5EXAA8SU8> build #619 of orion is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/619
May 23 19:05:07 <DonkeyHotei> i grabbed a wrt54gs v2 with a sticker on it saying "bricked" and got a jtag header onto it, but urjtag reports "TDO seems to be stuck at 1" after the LEDs come on and settle to a blinking power. anyone ever seen similar?
May 23 19:21:30 <5EXAA8SU8> build #508 of au1000 is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/508
May 23 19:47:02 <5EXAA8SU8> build #553 of avr32 is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/553
May 23 20:43:09 <5EXAA8SU8> build #468 of mcs814x is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/468
May 23 21:00:10 <OpenWrt-Commits> nbd r40835 branches/attitude_adjustment/target/linux/generic/patches-3.3/020-ssb_update.patch * kernel: add a ssb backport required for a new mac80211 update
May 23 21:02:08 <OpenWrt-Commits> nbd r40836 trunk/package/kernel/mac80211/Makefile * mac80211: fix probing of rtl8180
May 23 21:07:06 <OpenWrt-Commits> nbd r40837 trunk/package/kernel/mac80211/patches/620-rt2x00-rt3352-rf-id.patch * rt2x00: fix rt3352 rf probing (#14322)
May 23 22:14:36 <OpenWrt-Commits> nbd r40838 trunk/package/kernel/gpio-button-hotplug/src/gpio-button-hotplug.c
May 23 22:14:36 <OpenWrt-Commits> gpio-button-hotplug: remove #ifdef CONFIG_HOTPLUG, it is gone in newer kernels (fixes #16413)
May 23 22:14:39 <OpenWrt-Commits> nbd r40839 trunk/package/kernel/button-hotplug/src/button-hotplug.c * button-hotplug: remove #ifdef CONFIG_HOTPLUG, it is gone in newer kernels
May 23 22:16:32 <tharvey> nbd: was the 3.9 regression re 4addr header mode resolved: http://marc.info/?l=linux-wireless&m=136743495526905&w=2 ?
May 23 22:16:48 <nbd> tharvey: yes
May 23 22:18:52 <tharvey> in mainline?  http://wireless.kernel.org/en/users/Documentation/iw needs to be updated
May 23 22:19:18 <nbd> hm, not sure if it's fixed in mainline yet
May 23 22:19:26 <nbd> haven't looked at this in a while
May 23 22:20:00 <tharvey> so we have a patch for it being maintained in target/linux/generic then?
May 23 22:20:31 <nbd> yes
May 23 22:20:38 <nbd> i submitted it once
May 23 22:20:44 <nbd> but i think i need to re-submit it with some changes
May 23 22:22:34 <tharvey> ok, thx
May 23 22:24:02 <nbd> fyi, i suspect your ath9k rx flush fix was causing a regression resulting in rx lockups after a certain number of resets
May 23 22:24:12 <nbd> i made a fix for it
May 23 22:24:15 <tharvey> really?
May 23 22:24:30 <tharvey> thx - can you point me to your commit?
May 23 22:24:34 <nbd> i noticed that this was causing buffers to be passed to the hw via register writes after rx was already stopped
May 23 22:30:06 <nbd> tharvey: http://www.spinics.net/lists/linux-wireless/msg122832.html
May 23 22:39:26 <tharvey> nbd: how often would these lockups occur and was the result a hard rx lock?
May 23 22:56:29 <HeXiLeD> is there any dev.openwrt.org amdin here? since a few days ago i keep getting : Error: Bad Request Missing or invalid form token. Do you have cookies enabled? - when trying to login. It seems to log me in but soon as i click anything i am logged out.
**** ENDING LOGGING AT Sat May 24 02:59:58 2014