[03:18] <mwhudson> apw: is there an eta on the fix for https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1574982 ?
[03:19] <mwhudson> (it looks like it will be fixed in the kernel?)
[08:18] <apw> mwhudson, yes, that is already fixed in the unstable kernel and will be fixed in the curretn xenial sru kernel. when that copies out it will hit yakkety too
[08:18] <apw> mwhudson, it got delayed some by anembargoed cve
[08:29] <mwhudson> apw: ta
[08:30] <apw> mwhudson, applying the fix locally by hand is eminently doable if you are blocked by it
[08:32] <mwhudson> apw: it's causing an autopkgtest failure so that wouldn't be very helpful :-)
[08:38] <apw> mwhudson, yeah we ahve a very large pile of those cause red on a lot of my packages, its been a huge pain to fix and deploy due to timing
[08:39] <mwhudson> apw: https://bostongazette.files.wordpress.com/2014/02/the-lego-movie-awesome-e1392309318427.png?w=600
[08:40] <apw> mwhudson, oh so very true
[13:25] <tjaalton> ideas why self-built drm-intel-next kernel (for bisecting) fails to boot on a machine where the mainline build boots fine. same .config used, the new build built on xenial
[13:25] <tjaalton> it just hangs at "loading initrd"
[13:25] <tjaalton> dropping quiet et al does nothing
[13:27] <tjaalton> it's a rather old mainline checkout (3.18-rc5+), newer kernels built on this machine boot fine there
[13:30] <rtg> tjaalton, disable splash screen ?
[13:30] <tjaalton> nope
[13:31] <tjaalton> hmm I could try a chroot build on trusty
[13:37] <TJ-> tjaalton: kernel or initrd.img corrupt? the message "Loading initrd" comes from GRUB; next step is the kernel starts spewing messages to console
[13:37] <TJ-> tjaalton: is it booting with GRUB in GFX mode? if so, try changing it to text mode
[13:38] <tjaalton> I've done a number of builds, thought it was my config that failed to work on this (baytrail) machine
[13:38] <tjaalton> guess it's gfx mode
[13:38] <tjaalton> the default
[13:39] <TJ-> tjaalton: also is it UEFI? I've seen some weirdness with UEFI GOP causing no video output
[13:39] <apw> tjaalton, cirtianly we build the mainline builds in a chroot, the BUILT file tells you which
[13:40] <tjaalton> TJ-: efi
[13:45] <tjaalton> apw: right, it's actually vivid
[14:46] <manjo> apw, did you guys decide after uds what kernel version 16.10 might end up being ? 
[14:46] <manjo> ogasawara, ^ ? 
[14:48] <apw> i am assuming 4.7/8 most likely 4.8, though its early to be deciding on the version in a non-LTS release
[14:48] <manjo> apw, ack thank for confirming 
[14:49] <manjo> apw, I guess when we get close to freeze dates we might have a better idea 
[14:49] <manjo> apw, I needed a ballpark for advising cust on what they should target wrt upstream patches .. I think we should tell them 4.7
[14:50] <apw> well they need to be pushing their patches a week ago to hit 4.7 anyhow right ?
[14:50] <manjo> yeah and they are for the most part 
[14:52] <manjo> apw, but there are a lot of acpi bindings that might not make 4.7 but 4.8 instead .. probably I will need to sru those when the time comes