=== yuning_ is now known as yuning
[08:23] <samson-uo> Hello
[08:23] <samson-uo> Someone mind pushing the latest set of tags to git?
[08:24] <samson-uo> for the now-public CVE-2015-5307
[08:26] <samson-uo> well, to their respective git repos anyway. Precise (3.2), Trusty (3.13), Vivid (3.19), and wily (4.2)
=== kbingham is now known as kbingham_fn
[09:08] <henrix> samson-uo: sure, that will happen in the next couple of hours.
[10:49] <henrix> and for anyone who cares: all git repositories should now be updated with that CVE fix
=== mamarley is now known as Guest27905
=== mamarley_ is now known as mamarley
[13:56] <rtg> cking, re: bug #1480349 - a new intel-microcode was synced to Xenial from Debian a few hours ago. intel-microcode | 3.20151106.1
[13:56] <ubot5> bug 1480349 in intel-microcode (Ubuntu) "Intel Microcode Breaks frequency scaling in Xeon® E5-2687W v3 & E5-1650 v3" [High,In progress] https://launchpad.net/bugs/1480349
[13:57] <cking> rtg, yep, i'll prod the users to test with the latest fixes, whatever they were, since intel does not like divulging the details
[13:58] <rtg> indeed. lets hope isn't the disaster the last update was
[13:58] <rtg> it isn't*
[13:58] <cking> rtg, will this intel microcode be available for Wily, or is it just a Xenial sync?
[13:59] <rtg> cking, just xenial for now. if it makes a positive difference, then we can pursue an SRU
[14:01] <cking> rtg, considering I've not found any H/W (nor has Intel) that can reproduce this issue, it is a weird one
[14:02] <rtg> cking, yeah, we might have to rely on the kindness (or frustration) of strangers :)
[14:03] <cking> and considering it may be a microcode issue, it's not possible to reverse engineer it to fix it :-/
[14:24] <mamarley> I am trying to recompile the kernel package for 4.2.0-18-generic on wily (so that I can apply a patch), but when I compile it (using "fakeroot debian/rules binary-generic"), I get the error "cc1: fatal error: /home/michael/Source/linux/linux-4.2.0/ubuntu/vbox/vboxguest/include/VBox/VBoxGuestMangling.h: No such file or directory".
[14:25] <mamarley> I didn't get that error when I compiled 4.2.0-17-generic the same way.
[14:34] <rtg> mamarley, try compiling from the git repository ?
[14:34] <rtg> though it sounds like there could be an error in packaging.
[14:42] <mamarley> rtg: This one? http://kernel.ubuntu.com/git/ubuntu/ubuntu-wily.git/
[14:43] <rtg> mamarley, yup, then 'git reset --hard Ubuntu-4.2.0-18.22; fakeroot debian/rules clean binary-generic'
[14:43] <mamarley> OK, thanks, I will try that.
=== adrian is now known as alvesadrian
[15:45] <mamarley> rtg: That worked, thanks!
[16:51] <samson-uo> henrix: I see them now, thanks!
=== jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ ||  If you have a question just ask, and do wait around for an answer!  If the question is should I file a bug for something, likely you can assume yes. || Channel logs: http://irclogs.ubuntu.com/
=== dkessel_ is now known as dkessel
[17:53] <cristian_c> jsalisbury: hi
[17:59] <jsalisbury> cristian_c, sorry, I really havnen't had much time to dig into that bug recently.  I'll try to get to it soon.
[17:59] <cristian_c> jsalisbury: if you don'tmhave time, I can talk with guys in #linux-wireless channel
[18:00] <cristian_c> jsalisbury: could it be a good idea?
[18:00] <jsalisbury> cristian_c, it wouldn't hurt.  It would be good to get some feedback from the upstream developers and see if they have any ideas
[18:01] <cristian_c> jsalisbury: ok
[18:02] <kdub> hey all, trying to compile the flo vivid kernel, but when trying to pack the zImage into the boot.img from phablet-dev-bootstrap, its complaining that the produced zImage is too big
[18:02] <kdub> any ideas?
[18:04] <rtg> kdub, turn off ext2/ext3 in favour of CONFIG_EXT4_USE_FOR_EXT23=y
[18:04] <kdub> rtg, thanks, will give it a try
[18:04] <rtg> kdub, have a look at the mako branch
[18:35] <kdub> rtg, thanks for the tip, that seemed to get me over that hurdle
[18:37] <rtg> kdub, no problem