=== tdmackey_ is now known as tdmackey [08:12] moin [08:19] * apw yawns [08:21] Bees! [08:21] Though that is RAOF 's line... [08:24] bees ... oh where, i am thirsty [08:25] * smb rather suggests T's in that case [08:36] jibel, do you still look after the adt tests ? [08:36] apw, yes [08:37] 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] quitting: testbed failed: cannot send to testbed: ['IOError: [Errno 32] Broken pipe\n'] [08:42] 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] jibel, hey thanks [08:46] apw: What is the linux autopkgtest anyway? Just a rebuild test? [08:48] infinity, yeah just a rebuild test [08:48] 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] Yeah, just looked it up in git too. [08:49] yeah there is no way to represent that apparently [08:49] So, I'll just skip it (the rdep rebuild test of glibc went fine, so yay) [08:49] thanks [09:43] hey everyone. who can help me - http://pastebin.com/wcY5jV2N ? [09:44] and then server reboots unexpected [11:26] ppisati, hey, CONFIG_ARM_HIGHBANK_CPUIDLE seems to be off for generic and on for generic-lpae, is that to be expected ? [11:26] apw: yes, becasue it caused trouble, we were expecting a fw update for that [11:26] apw: but i suspect we will never get one [11:27] so why is it not off for both [11:27] apw: because it's working for midway (ecx-2000) while it's broken for ecx-1000 [11:29] ppisati, ok thanks [11:30] apw: 0bdf6c4 in S [11:38] ppisati, and am i right in assuming that CPU_FREQ is not needed on arm [11:39] apw: it's a mixed bag, it works (and it was explicitely requested to be on) on calxeda (all revisions) [11:39] apw: while it had problem in the past on other chips (like omapX) [11:39] ppisati, and yet it is off on arm ... hmmm [11:40] apw: you mean the default config is off? [11:40] yeah in 3.13 it is off [11:40] * ppisati senses apw is preparing for a config review/diff... [11:40] apw: ok, leave it off [11:41] apw: i'll turn it on one by one [11:41] ppisati, ok great, and yes that is what i am doing [12:06] * ppisati -> out for lunch [13:24] 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] ogra_, nope [13:25] ogra_, I think I'm gonna have to figure out how to make 4.8 work (if that is possible) [13:29] ogra_, those have likely not changes since trusty opened [13:29] 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] 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] Hey kernel people. 3.13 broke my desktop (nvidia doesn't build). [13:43] replied to k-t@ about this [13:43] I suspect I am not the only one running 14.04 on nvidia hardware. [13:43] tjaalton, k-t@? [13:43] kernel-team@ [13:43] kernel-team [13:44] ogra_, in a saucy chroot perhaps [13:44] sigh, yeah ... [13:44] (2Mbit here ... takes ages to set up, but thats what i will do then) [13:44] tjaalton, i thought we pre-vetted fglrx and nvidia to make sure they built [13:45] apw: "this week" is not done yet ;) [13:45] popey, indeed not, which is why we have testing for nvidia which said it built, wtf [13:45] ahh, so the test is broken? [13:45] aah, that's actually tricky [13:46] tseliot, tricky? [13:46] it will probably build but complain once the module is loaded [13:46] bah [13:47] tseliot, do we know what the issue is ? [13:47] popey, does your card work if you disable nvidia ? [13:47] might be interesting to test with 3.13 anyhow [13:47] apw: yes, they don't export a symbol any more. I'm testing my patches as we speak [13:48] 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] tseliot, sigh ... [13:49] ok then at least the testing is working, even if it is of little value [13:49] ok, my patches work [13:50] at least with nvidia 331 [13:50] I haven't touched fglrx yet [13:50] or the other nvidia drivers [13:51] are we saying all of them are bust the same way, fgrlx as well i mean? [13:51] apw: I end up in VESA [13:51] apw: i need to go to a hangout, can test more after [13:52] 3.12 is your friend then [13:52] apw: I haven't tested them all [13:52] fglrx won't build, as rtg said [13:53] 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] 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] jibel, ^^ is that in your pervue, and does it make sense for the dkms testing stuff ? [14:10] apw, tjaalton, popey: nvidia-331 and nvidia-331-updates are in [14:10] tseliot: thanks! [14:11] now I *only* have to fix the rest... [14:11] :) [14:15] nice one [15:59] apw, that'd be for the CI team but integrating DKMS testing to the ci dashboard has been postponed for a while. === medberry is now known as med_ === lfaraone_ is now known as lfaraone === hughhalf is now known as hugh_afk