=== yuning-afk is now known as yuning | ||
mwhudson | apw: is there an eta on the fix for https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1574982 ? | 03:18 |
---|---|---|
ubot5 | Launchpad 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 | ||
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:18 |
mwhudson | apw: ta | 08:29 |
apw | mwhudson, applying the fix locally by hand is eminently doable if you are blocked by it | 08:30 |
mwhudson | apw: it's causing an autopkgtest failure so that wouldn't be very helpful :-) | 08:32 |
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:38 |
mwhudson | apw: https://bostongazette.files.wordpress.com/2014/02/the-lego-movie-awesome-e1392309318427.png?w=600 | 08:39 |
apw | mwhudson, oh so very true | 08: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 | ||
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:25 |
tjaalton | it's a rather old mainline checkout (3.18-rc5+), newer kernels built on this machine boot fine there | 13:27 |
rtg | tjaalton, disable splash screen ? | 13:30 |
tjaalton | nope | 13:30 |
tjaalton | hmm I could try a chroot build on trusty | 13:31 |
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:37 |
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:38 |
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:39 |
tjaalton | TJ-: efi | 13:40 |
tjaalton | apw: right, it's actually vivid | 13:45 |
manjo | apw, did you guys decide after uds what kernel version 16.10 might end up being ? | 14:46 |
manjo | ogasawara, ^ ? | 14:46 |
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:48 |
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:49 |
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:50 |
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 | 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!