=== gerald is now known as Guest35211
=== bandit-led is now known as bandit-sleeping
=== willcooke is now known as francooke
=== francooke is now known as JupiterWhistles
=== JupiterWhistles is now known as willcooke
[12:43] <jtaylor> hi, is the lts utopic kernel currently in proposed based on 3.16.7-ckt9?
[12:44] <jtaylor> if yes is debian bug 782362 taken care of? couldn't find it in the changelog
[12:44] <ubot5> Debian bug 782362 in src:linux "Regression: 3.16.7-ckt9-1: mouning rootpartition cause a deadlock at mount time" [Important,Fixed] http://bugs.debian.org/782362
[12:46] <rtg> jtaylor, 3.16.7-ckt9 was merged as of Ubuntu-3.16.0-35.46
[12:46] <jtaylor> so the proposed kernel is affected?
[12:47] <rtg> jtaylor, yup, looks like it.
[12:49] <jtaylor> rtg: what needs to be done to prevent the unfixed kernel from hitting updates?
[12:50] <henrix> jtaylor: looking at the bug, it seems that commit 9c4f61f01d269815bb7c37 fixes it.  and this commit is already queued for the 3.16.7-ckt11 stable release
[12:50] <henrix> jtaylor: which means it will hit the lts-utopic kernel in the next SRU cycle
[12:50] <rtg> jtaylor, if it is a serious regression, then contact bjf
[12:51] <jtaylor> henrix: what does that mean? the current proposed kernel will go to updates and the fix will come next time?
[12:52] <henrix> jtaylor: correct.  i'm still going through that bug report
[12:52] <rmariotti> Hi, i've just built a new kernel, looking in /boot i noticed that the initrd of the custom kernel is 5 times bigger than generic's initrd (~100 mb vs ~20 mb). it is normal?
[12:52] <apw> rmariotti, sounds like an unstripped build, how did you build it
[12:53] <rmariotti> apw: the initramfs or the kernel?
[12:53] <apw> the kernel, as that initramfs just sucks up whatever is in /lib/modules
[12:56] <rmariotti> i've just extracted the kernel, patched it, then i runned "make mrproper", "make menuconfig" and i buit it with "make bzImage modules" and "make modules_install".  Then i copied bzImage, System.map and config in /boot.
[12:56] <jtaylor> henrix: a report in ubuntu: bug 1445252
[12:56] <ubot5> bug 1445252 in linux (Ubuntu) "[vivid] btrfs deadlock at mount/boot" [High,Triaged] https://launchpad.net/bugs/1445252
[12:57] <henrix> jtaylor: looks like the issue is not actually a regression in the kernel in -proposed, the issue is already present in the kernel in -updates
[12:57] <jtaylor> henrix: current updates is based on ckt7?
[12:57] <jtaylor> that should be good
[12:58] <henrix> jtaylor: the commit that introduced the issue was commit 381cf6587f8a8a8e981bc0c1aaaa8859b51dc756, which you can seen in the changelog with "btrfs: fix leak of path in btrfs_find_item"
[12:58] <henrix> jtaylor: and no, current -updates is based on 3.16.7-ckt8
[12:59] <jtaylor> ah ok its probably affected then
[12:59] <jtaylor> k then nothing needs to be done for current proposed I guess
[13:00] <henrix> jtaylor: anyway, thanks for the heads-up -- i'll keep track of your bug report and make sure the fix is in the next cycle
=== pgraner-afk is now known as pgraner
[13:00] <henrix> jtaylor: i'm pretty sure it will be, as -ckt11 should be released with the fix
[13:01] <apw> henrix, mark it up with a break-fix ...
[13:02] <henrix> apw: on it ;)
[13:02] <jtaylor> thanks for checking it
[13:04] <apw> henrix, this is an egg :)
[13:08] <rmariotti> apw: i followed the right process? The kernel works.
[13:10] <apw> rmariotti, ok to do that you need to turn off debug symbols else you get huge binaries as you have, CONFIG_DEBUG_INFO needs to be off to avoid that, the ubuntu packaging packages those as are into debug packages and then strips them for the main packages
[13:11] <rmariotti> apw: thank you for the help.
=== mwenning is now known as mwenning-wfh
=== bladernr-lex is now known as bladernr
=== bladernr is now known as bladernr_
=== pgraner is now known as pgraner-afk
[22:51] <zzmp> I'm on 3.10.18 and I don't have nfnetlink or nfnetlink_queue modules available in my kernel. I've looked through some of the wikis, but can't find how to get it. Does anyone know how I could either get those *.ko files, or compile them myself?
[23:04] <zzmp> anyone?