=== JanC_ is now known as JanC
=== FJKong_afk is now known as FJKong
[10:12] <Laney> hey
[10:12] <Laney> anyone know how to resume from suspend after some timeout?
[10:12] <Laney> I want to write a script to reproduce a suspend/resume bug by cycling it until it happens
[10:14] <davmor2> Laney: I think nuclearbob is doing something along those lines for UT he will be on in a US timezone later today if you get no joy prior to that
[10:15] <Laney> I just found something called rtcwake
[10:18] <Laney> seems to work
[10:32] <apw> unixabg, ok in theory i have a casper mod which lets it do multiple layers
[10:32] <apw> unixabg, now i am not sure i can test this well, but i think you can
=== ghostcube_ is now known as ghostcube
=== Elimin8r is now known as Elimin8er
[19:13] <mjeanson> Hi, I was wondering if there is a policy concerning micro release exceptions for dkms package that break after a kernel update/backport?
[19:24] <apw> we tend to backport things like that fairly agreessivly
[19:24] <apw> i dont thing it is written down anywhere
[19:47] <mjeanson> apw: I prepared updated packages of lttng-modules-dkms for trusty and vivid that build with all current kernels but I had to do minor version updates and cherry pick a lot of patches, any chances of having this sponsored?
[19:48] <apw> mjeanson, does it work with wily as well?
[19:52] <mjeanson> apw: wily has 2.6.x, vivid 2.5.x and trusty 2.4.x and hte major version must match with the userland tools version, so I backported kernel enablement patches in each branch
[19:53] <mjeanson> it would be so simple if we could just backport the wily package
[19:54] <mjeanson> but then we would also have to backport the userland stuff
[20:04] <apw> mjeanson, if you have packages we can get them reviewed and sponsored
[20:07] <mjeanson> apw: great, they are in my ppa, let me get the links
[20:07] <mjeanson> trusty: https://launchpad.net/~mjeanson/+archive/ubuntu/ppa/+sourcepub/5317334/+listing-archive-extra
[20:08] <mjeanson> vivid: https://launchpad.net/~mjeanson/+archive/ubuntu/ppa/+sourcepub/5317328/+listing-archive-extra
[20:11] <apw> mjeanson, won't be today, will look into them tommorrow if noone else has
[20:12] <mjeanson> apw: great, thanks for your help
[20:57] <infinity> mjeanson: Keep in mind that the trusty version needs to build with 3.13, 3.16, 3.19, and 4.2
[20:57] <infinity> mjeanson: Because of HWE kernels.
[20:58] <mjeanson> infinity: it was tested against 3.13, 3.16 and 3,19
[20:58] <mjeanson> 4.2 will require additionnal patches
[20:58] <infinity> mjeanson: Kay.  4.2 will be needed too in a couple of months, so may as well fix it now instead of then.
[20:59] <infinity> mjeanson: The 4.2 header packages from wily should install on trusty just fine, so easy enough to test that way.
[21:03] <mjeanson> infinity: isn't 4.1 the current kernel for wily?
[21:04] <infinity> mjeanson: It'll be 4.2 shortly, sorry, that's in the kteam PPA.
[21:04] <infinity> mjeanson: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+packages
[21:04] <infinity> Forgot we hadn't promoted that yet.
[21:04] <infinity> Though, part of why it's not promoted is that we're waiting on dkms fixes.
[21:05] <apw> infinity, and the other is the lack of a compiler that builds ppc64el
[21:05] <infinity> apw: Yeah, you could "fix" that by forcing 4.9 until doko fixes his -5 build.
[21:06] <apw> i was hoping he had it fixed, but i see his build is pants in the PPA
[21:06] <infinity> apw: He "fixed" it in the PPA, but it broke for other reasons.  Maybe I'll just upload to the archive with only the ppc64el fix.
[21:06] <infinity> In fact, I think I'll do that this afternoon.
[21:06] <apw> infinity, nice
[21:16] <mjeanson> infinity: well, the master branch of lttng-modules doesn't yet build against 4.2
[21:16] <infinity> mjeanson: That would be nice to fix. ;)
[21:18] <mjeanson> infinity: I'll get the devs attention when they get back from linuxcon
[21:19] <infinity> mjeanson: Shiny.
[21:19] <infinity> apw: Minimal GCC fix uploaded to adconrad/staging.  If it builds fine, I'll copy it to the kernel PPA (so your kernel can build), and -proposed.
[21:20] <apw> infinity, sounds good, i assume it'll be 24 hours, if its done when i wake i'll copy it over
[21:20] <infinity> apw: About 9 hours.
[21:21] <apw> ok cool, so it sounds like i should copy it in the morning
[21:21] <infinity> apw: Or I'll get it before bed, but that's about the same time.
[21:22] <infinity> apw: If you beat me to it, copy to proposed too, please. :)
[21:22] <infinity> Though, maybe not until we've validated that it fixes the kernel build.
[21:23] <infinity> Which takes about 25m to fail.
[21:23] <apw> if you've not copied it when i wake up, i'll cpoy it to the PPA and respin the build
[21:23] <infinity> I guess I can game that by copying the kernel into my staging PPA as soon as the ppc64el gcc build is done.
[21:26] <apw> yeah if you copy it with binaries, it will only build the broke one i think right ?
[21:36] <infinity> apw: Or copy source-only and kill all the other builds, whatever.
[21:37] <unixabg> apw: greetings, thank you for the repsonse on the mod of casper.
[21:37] <unixabg> Do you have available in a .deb?
[21:37] <unixabg> I could remaster a stock iso image to include that and then test stacking squashfs in overlay.
[21:40] <apw> unixabg, not in a .deb ... this pastebin is a replacement scripts/casper for in the initrd on the iso: http://paste.ubuntu.com/12137968/
[21:50] <apw> unixabg, that work for you ?
[21:50] <apw> (as in does that make sense to you)