=== rww is now known as rw
=== Mick_ is now known as malwarel
[16:10] <rtg> kamal, you should add CONFIG_DMADEVICES=y to your 4.2 stable build (and enable all of the dependent devices). I think you'll find a compile issue with drivers/dma/bcm2835-dma.c 
[16:11] <rtg> for the raspi2 build of course.
[16:14] <kamal> rtg, huh.  I do test build bcm2834_defconfig   ... shoudn't that probably enable those?
[16:15] <rtg> kamal, it doesn't by default
[16:15] <kamal> rtg, well that's annoying
[16:15] <kamal> (and yes, I see that's true)
=== AndrewMC` is now known as AndrewMC
[22:22] <apw> stgraber, just had a new ADT failure lp: #1542049
[22:22] <ubot5`> Launchpad bug 1542049 in lxc (Ubuntu) "lxc: ADT exercise test failing with linux-4.4.0-3.17 " [Undecided,New] https://launchpad.net/bugs/1542049
[22:24] <stgraber> apw: so it's hanging on lxc-test-apparmor-mount then
[22:25] <stgraber> could be network related maybe
[22:25] <apw> stgraber, isn't that the bits jjohansen1 just changed for us ...
[22:25] <stgraber> yeah, so either it's getting stuck on network somehow, or it's actually getting stuck on apparmor
[22:27] <jjohansen1> well, not saying it isn't apparmor, but a better trace would sure help
[22:28] <jjohansen1> apw: does 4.4.0-3 have the mount patch I did?
[22:28] <apw> jjohansen1, i believe it does
[22:29] <jjohansen1> apw, stgraber: maybe its time for me to just drop the patch bomb that has been waiting for ever behind other work
[22:29] <jjohansen1> it has a lot of locking fixes in it
[22:30] <apw> jjohansen1, confirmed
[22:30] <jjohansen1> I need to port another couple of patches to it (I'll do that today), then lets give it a test build
[22:30] <apw> jjohansen1, works for me
[22:31] <apw> stgraber, can we tell if it is hanging there somehow, to confirm it is not just a network issue and we are doing this update for nothing
[22:32] <jjohansen1> apw: well I would say some version of this has to drop for xenial, whether its this set or the moster 3.5 patchset that is still in dev and that won't make feature freeze
[22:32] <stgraber> apw: I'll manually kick a retry on amd64 now. I confirmed locally that on current xenial, I can pull an image just fine so the network bits we're hitting seem fine right now.
[22:33] <apw> jjohansen1, ok, i'd love to not have to rush them in but ...
[22:34] <jjohansen1> apw: well the patchset I'm talking about was meant for vivid/wily and has been mostly just sitting for about 2 months, I agree we don't want to rush the 3.5 thing
[22:35] <apw> jjohansen1, well if you want that in wily, we prolly want to get it into xenial first for sure
[22:35] <jjohansen1> yeah