/srv/irclogs.ubuntu.com/2016/05/18/#ubuntu-kernel.txt

=== yuning-afk is now known as yuning
mwhudsonapw: is there an eta on the fix for https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1574982 ?03:18
ubot5Launchpad bug 1574982 in dkms (Ubuntu) "Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler" [High,Confirmed]03:18
mwhudson(it looks like it will be fixed in the kernel?)03:19
=== leftyfb_ is now known as leftyfb
=== inaddy is now known as tinoco
apwmwhudson, 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 too08:18
apwmwhudson, it got delayed some by anembargoed cve08:18
mwhudsonapw: ta08:29
apwmwhudson, applying the fix locally by hand is eminently doable if you are blocked by it08:30
mwhudsonapw: it's causing an autopkgtest failure so that wouldn't be very helpful :-)08:32
apwmwhudson, 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 timing08:38
mwhudsonapw: https://bostongazette.files.wordpress.com/2014/02/the-lego-movie-awesome-e1392309318427.png?w=60008:39
apwmwhudson, oh so very true08:40
=== TJ_Remix is now known as TJ-
=== xnox_ is now known as xnox
=== Ursinha_ is now known as Ursinha
=== dgadomski_ is now known as dgadomski
=== tai271828_ is now known as tai271828
=== henrix_ is now known as henrix
=== caribou_ is now known as caribou
tjaaltonideas 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 xenial13:25
tjaaltonit just hangs at "loading initrd"13:25
tjaaltondropping quiet et al does nothing13:25
tjaaltonit's a rather old mainline checkout (3.18-rc5+), newer kernels built on this machine boot fine there13:27
rtgtjaalton, disable splash screen ?13:30
tjaaltonnope13:30
tjaaltonhmm I could try a chroot build on trusty13:31
TJ-tjaalton: kernel or initrd.img corrupt? the message "Loading initrd" comes from GRUB; next step is the kernel starts spewing messages to console13:37
TJ-tjaalton: is it booting with GRUB in GFX mode? if so, try changing it to text mode13:37
tjaaltonI've done a number of builds, thought it was my config that failed to work on this (baytrail) machine13:38
tjaaltonguess it's gfx mode13:38
tjaaltonthe default13:38
TJ-tjaalton: also is it UEFI? I've seen some weirdness with UEFI GOP causing no video output13:39
apwtjaalton, cirtianly we build the mainline builds in a chroot, the BUILT file tells you which13:39
tjaaltonTJ-: efi13:40
tjaaltonapw: right, it's actually vivid13:45
manjoapw, did you guys decide after uds what kernel version 16.10 might end up being ? 14:46
manjoogasawara, ^ ? 14:46
apwi am assuming 4.7/8 most likely 4.8, though its early to be deciding on the version in a non-LTS release14:48
manjoapw, ack thank for confirming 14:48
manjoapw, I guess when we get close to freeze dates we might have a better idea 14:49
manjoapw, I needed a ballpark for advising cust on what they should target wrt upstream patches .. I think we should tell them 4.714:49
apwwell they need to be pushing their patches a week ago to hit 4.7 anyhow right ?14:50
manjoyeah and they are for the most part 14:50
manjoapw, 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 14:52
=== ghostcube__ is now known as ghostcube
=== mamarley is now known as Guest75717
=== mamarley_ is now known as mamarley
=== zequence_ is now known as zequence

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