[01:50] <samkottler> hi!
[01:51] <samkottler> I'm running into an issue with setting net.ipv4.neigh.default.gc_thresh1/2/3 on the 3.13.0-98-generic kernel on precise where I get the follow message when running `sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128`: error: "Invalid argument" setting key "net.ipv4.neigh.default.gc_thresh1"
[01:51] <samkottler> The problem starts in the 3.13.0-97-generic kernel, 3.13.0-96-generic works fine.
[01:51] <samkottler> Has anyone seen this before?
[01:52] <samkottler> http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts-backport-trusty&id=563cf19389d8e999e69d6c94995966aeaf7c3a08 and http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts-backport-trusty&id=7b82096b0ebc9bf487b390fe970d66ffa5a5774e seem related.
[07:09] <apw> samkottler, i have not heard reported before no.  could you file a bug with "ubuntu-bug linux" and add all that detail
[07:09] <apw> samkottler, and let us know here the bug number
[09:51] <michael-vb> apw: I talked to you a couple of days ago about problems running current mainline kernels in a virtual machine.  I just took a boot log over a serial console.  Lots of symbol version disagreements, mainly for mcount.
[09:51] <michael-vb> http://paste.debian.net/883626/
[11:49] <om26er> jsalisbury: Hey! that fixes the bug
[12:50] <michael-vb> Repaste: (11:51:32) michael-vb: apw: I talked to you a couple of days ago about problems running current mainline kernels in a virtual machine.  I just took a boot log over a serial console.  Lots of symbol version disagreements, mainly for mcount.
[12:50] <michael-vb> (11:51:39) michael-vb: http://paste.debian.net/883626/
[12:51] <michael-vb> And update: still affects the current daily.
[13:22] <samkottler> apw: done! https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1634892
[13:22] <ubot5`> Ubuntu bug 1634892 in linux-lts-trusty (Ubuntu) "Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error" [Undecided,New]
[13:27] <apw> samkottler, ta
[13:29] <michael-vb> apw: quick ping again.  "No time just now" is fine too though.
[13:30] <apw> michael-vb, i did look over it, that looks a lot like a missmatched initrd and kernel
[13:30] <michael-vb> apw: does that mean user error or package error?
[13:30] <apw> michael-vb, not 100% sure, i've not had any time to try that speciifc kernel on a vm here yet
[13:30] <apw> we are rather slammed doing z-opening
[13:31] <michael-vb> Had to think for a minute before I got that one...
[13:32] <michael-vb> Any ideas in the mean-time?  Or just build my own kernel?
[14:37] <michael-vb> apw: the mainline kernels are without any Ubuntu patches, aren't they?  I just reproduced a problem with mainline 4.8.0 that we saw with the Yakkety live kernel.  That means that it is probably nothing to do with you, doesn't it?
[14:47] <om26er> jsalisbury: ping
[14:47] <jsalisbury> om26er, hey
[14:47] <om26er> jsalisbury: the last kernel fixes the issue
[14:47] <om26er> time to release the patch :D
[14:47] <jsalisbury> om26er, that is good news.  Do you want to let upstream know, or do you want me to?
[14:48] <om26er> jsalisbury: I can do that, but if you do it, that would be better,.
[14:48] <jsalisbury> om26er, Ok, I'll reply and see if this will be the final version of the patch.