[08:12] <ppisati> moin
[08:19]  * apw yawns
[08:21] <smb> Bees!
[08:21] <smb> Though that is RAOF 's line...
[08:24] <apw> bees ... oh where, i am thirsty
[08:25]  * smb rather suggests T's in that case
[08:36] <apw> jibel, do you still look after the adt tests ?
[08:36] <jibel> apw, yes
[08:37] <apw> jibel, dunno if this has been reported, but it looks like the tests (for linux anyhow) are failing with a a testbed error
[08:38] <apw> quitting: testbed failed: cannot send to testbed: ['IOError: [Errno 32] Broken pipe\n']
[08:42] <jibel> apw, there is a timeout, but 1h is a bit short, it is set to 10k seconds by default. I'll have a look
[08:46] <apw> jibel, hey thanks
[08:46] <infinity> apw: What is the linux autopkgtest anyway?  Just a rebuild test?
[08:48] <apw> infinity, yeah just a rebuild test
[08:48] <infinity> apw: if so, that makes sense for rdeps changing, but not so much for linux itself (since it literally just built), so maybe I'll skip it.
[08:49] <infinity> Yeah, just looked it up in git too.
[08:49] <apw> yeah there is no way to represent that apparently
[08:49] <infinity> So, I'll just skip it (the rdep rebuild test of glibc went fine, so yay)
[08:49] <apw> thanks
[09:43] <opecun> hey everyone. who can help me - http://pastebin.com/wcY5jV2N ?
[09:44] <opecun> and then server reboots unexpected
[11:26] <apw> ppisati, hey, CONFIG_ARM_HIGHBANK_CPUIDLE seems to be off for generic and on for generic-lpae, is that to be expected ?
[11:26] <ppisati> apw: yes, becasue it caused trouble, we were expecting a fw update for that
[11:26] <ppisati> apw: but i suspect we will never get one
[11:27] <apw> so why is it not off for both
[11:27] <ppisati> apw: because it's working for midway (ecx-2000) while it's broken for ecx-1000
[11:29] <apw> ppisati, ok thanks
[11:30] <ppisati> apw: 0bdf6c4 in S
[11:38] <apw> ppisati, and am i right in assuming that CPU_FREQ is not needed on arm
[11:39] <ppisati> apw: it's a mixed bag, it works (and it was explicitely requested to be on) on calxeda (all revisions)
[11:39] <ppisati> apw: while it had problem in the past on other chips (like omapX)
[11:39] <apw> ppisati, and yet it is off on arm ... hmmm
[11:40] <ppisati> apw: you mean the default config is off?
[11:40] <apw> yeah in 3.13 it is off
[11:40]  * ppisati senses apw is preparing for a config review/diff...
[11:40] <ppisati> apw: ok, leave it off
[11:41] <ppisati> apw: i'll turn it on one by one
[11:41] <apw> ppisati, ok great, and yes that is what i am doing
[12:06]  * ppisati -> out for lunch
[13:24] <ogra_> rtg, apw, was linux-maguro ever built in trusty ? i cant build it here due to gcc-4.6 not being available in the archive anymore 
[13:24] <rtg> ogra_, nope
[13:25] <rtg> ogra_, I think I'm gonna have to figure out how to make 4.8 work (if that is possible)
[13:29] <apw> ogra_, those have likely not changes since trusty opened
[13:29] <apw> ogra_, i guess if we needed to build 'em in the short term we'd build them in saucy and copy them forward; far from ideal
[13:43] <ogra_> apw, well, i would like to do a test cross build with swap disabled in the config ... seems i cant do that on my trusty machines 
[13:43] <popey> Hey kernel people. 3.13 broke my desktop (nvidia doesn't build).
[13:43] <tjaalton> replied to k-t@ about this
[13:43] <popey> I suspect I am not the only one running 14.04 on nvidia hardware.
[13:43] <seb128> tjaalton, k-t@?
[13:43] <tjaalton> kernel-team@
[13:43] <ogra_> kernel-team
[13:44] <apw> ogra_, in a saucy chroot perhaps
[13:44] <ogra_> sigh, yeah ... 
[13:44] <ogra_> (2Mbit here ... takes ages to set up, but thats what i will do then)
[13:44] <apw> tjaalton, i thought we pre-vetted fglrx and nvidia to make sure they built
[13:45] <tjaalton> apw: "this week" is not done yet ;)
[13:45] <apw> popey, indeed not, which is why we have testing for nvidia which said it built, wtf
[13:45] <tjaalton> ahh, so the test is broken?
[13:45] <tseliot> aah, that's actually tricky
[13:46] <apw> tseliot, tricky?
[13:46] <tseliot> it will probably build but complain once the module is loaded
[13:46] <apw> bah
[13:47] <apw> tseliot, do we know what the issue is ?
[13:47] <apw> popey, does your card work if you disable nvidia ?
[13:47] <apw> might be interesting to test with 3.13 anyhow
[13:47] <tseliot> apw: yes, they don't export a symbol any more. I'm testing my patches as we speak
[13:48] <tjaalton> hmm right, the dkms build log is messy but looks like it built nevertheless.. dmesg log would be interesting to see when it tries to load it
[13:48] <apw> tseliot, sigh ...
[13:49] <apw> ok then at least the testing is working, even if it is of little value
[13:49] <tseliot> ok, my patches work
[13:50] <tseliot> at least with nvidia 331
[13:50] <tseliot> I haven't touched fglrx yet
[13:50] <tseliot> or the other nvidia drivers
[13:51] <apw> are we saying all of them are bust the same way, fgrlx as well i mean?
[13:51] <popey> apw: I end up in VESA
[13:51] <popey> apw: i need to go to a hangout, can test more after
[13:52] <apw> 3.12 is your friend then
[13:52] <tseliot> apw: I haven't tested them all
[13:52] <tseliot> fglrx won't build, as rtg said
[13:53] <apw> how is that not on the failed list in our testing.  i have to say jenkins UI is designed by a moron
[13:54]  * tseliot shrugs
[14:00] <xnox> apw: ask CI team to setup ci.ubuntu.com view for you? that one has AMBER & RED for regressions & non-moron URLs direct to failed artifacts / logs of the hidden jenkins URLs
[14:03] <apw> jibel, ^^ is that in your pervue, and does it make sense for the dkms testing stuff ?
[14:10] <tseliot> apw, tjaalton, popey: nvidia-331 and nvidia-331-updates are in
[14:10] <tjaalton> tseliot: thanks!
[14:11] <tseliot> now I *only* have to fix the rest...
[14:11] <tjaalton> :)
[14:15] <popey> nice one
[15:59] <jibel> apw, that'd be for the CI team but integrating DKMS testing to the ci dashboard has been postponed for a while.