/srv/irclogs.ubuntu.com/2014/01/08/#ubuntu-kernel.txt

=== tdmackey_ is now known as tdmackey
ppisatimoin08:12
* apw yawns08:19
smbBees!08:21
smbThough that is RAOF 's line...08:21
apwbees ... oh where, i am thirsty08:24
* smb rather suggests T's in that case08:25
apwjibel, do you still look after the adt tests ?08:36
jibelapw, yes08:36
apwjibel, dunno if this has been reported, but it looks like the tests (for linux anyhow) are failing with a a testbed error08:37
apwquitting: testbed failed: cannot send to testbed: ['IOError: [Errno 32] Broken pipe\n']08:38
jibelapw, there is a timeout, but 1h is a bit short, it is set to 10k seconds by default. I'll have a look08:42
apwjibel, hey thanks08:46
infinityapw: What is the linux autopkgtest anyway?  Just a rebuild test?08:46
apwinfinity, yeah just a rebuild test08:48
infinityapw: 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:48
infinityYeah, just looked it up in git too.08:49
apwyeah there is no way to represent that apparently08:49
infinitySo, I'll just skip it (the rdep rebuild test of glibc went fine, so yay)08:49
apwthanks08:49
opecunhey everyone. who can help me - http://pastebin.com/wcY5jV2N ?09:43
opecunand then server reboots unexpected09:44
apwppisati, hey, CONFIG_ARM_HIGHBANK_CPUIDLE seems to be off for generic and on for generic-lpae, is that to be expected ?11:26
ppisatiapw: yes, becasue it caused trouble, we were expecting a fw update for that11:26
ppisatiapw: but i suspect we will never get one11:26
apwso why is it not off for both11:27
ppisatiapw: because it's working for midway (ecx-2000) while it's broken for ecx-100011:27
apwppisati, ok thanks11:29
ppisatiapw: 0bdf6c4 in S11:30
apwppisati, and am i right in assuming that CPU_FREQ is not needed on arm11:38
ppisatiapw: it's a mixed bag, it works (and it was explicitely requested to be on) on calxeda (all revisions)11:39
ppisatiapw: while it had problem in the past on other chips (like omapX)11:39
apwppisati, and yet it is off on arm ... hmmm11:39
ppisatiapw: you mean the default config is off?11:40
apwyeah in 3.13 it is off11:40
* ppisati senses apw is preparing for a config review/diff...11:40
ppisatiapw: ok, leave it off11:40
ppisatiapw: i'll turn it on one by one11:41
apwppisati, ok great, and yes that is what i am doing11:41
* ppisati -> out for lunch12:06
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
rtgogra_, nope13:24
rtgogra_, I think I'm gonna have to figure out how to make 4.8 work (if that is possible)13:25
apwogra_, those have likely not changes since trusty opened13:29
apwogra_, i guess if we needed to build 'em in the short term we'd build them in saucy and copy them forward; far from ideal13:29
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
popeyHey kernel people. 3.13 broke my desktop (nvidia doesn't build).13:43
tjaaltonreplied to k-t@ about this13:43
popeyI suspect I am not the only one running 14.04 on nvidia hardware.13:43
seb128tjaalton, k-t@?13:43
tjaaltonkernel-team@13:43
ogra_kernel-team13:43
apwogra_, in a saucy chroot perhaps13:44
ogra_sigh, yeah ... 13:44
ogra_(2Mbit here ... takes ages to set up, but thats what i will do then)13:44
apwtjaalton, i thought we pre-vetted fglrx and nvidia to make sure they built13:44
tjaaltonapw: "this week" is not done yet ;)13:45
apwpopey, indeed not, which is why we have testing for nvidia which said it built, wtf13:45
tjaaltonahh, so the test is broken?13:45
tseliotaah, that's actually tricky13:45
apwtseliot, tricky?13:46
tseliotit will probably build but complain once the module is loaded13:46
apwbah13:46
apwtseliot, do we know what the issue is ?13:47
apwpopey, does your card work if you disable nvidia ?13:47
apwmight be interesting to test with 3.13 anyhow13:47
tseliotapw: yes, they don't export a symbol any more. I'm testing my patches as we speak13:47
tjaaltonhmm 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 it13:48
apwtseliot, sigh ...13:48
apwok then at least the testing is working, even if it is of little value13:49
tseliotok, my patches work13:49
tseliotat least with nvidia 33113:50
tseliotI haven't touched fglrx yet13:50
tseliotor the other nvidia drivers13:50
apware we saying all of them are bust the same way, fgrlx as well i mean?13:51
popeyapw: I end up in VESA13:51
popeyapw: i need to go to a hangout, can test more after13:51
apw3.12 is your friend then13:52
tseliotapw: I haven't tested them all13:52
tseliotfglrx won't build, as rtg said13:52
apwhow is that not on the failed list in our testing.  i have to say jenkins UI is designed by a moron13:53
* tseliot shrugs13:54
xnoxapw: 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 URLs14:00
apwjibel, ^^ is that in your pervue, and does it make sense for the dkms testing stuff ?14:03
tseliotapw, tjaalton, popey: nvidia-331 and nvidia-331-updates are in14:10
tjaaltontseliot: thanks!14:10
tseliotnow I *only* have to fix the rest...14:11
tjaalton:)14:11
popeynice one14:15
jibelapw, that'd be for the CI team but integrating DKMS testing to the ci dashboard has been postponed for a while. 15:59
=== medberry is now known as med_
=== lfaraone_ is now known as lfaraone
=== hughhalf is now known as hugh_afk

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!