[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-10-19 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-08-20 Thread Joseph Salisbury
** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1331150 Title: arp fails to update, 3.13.0-{24,29} Status in “linux”

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-07-10 Thread Joseph Salisbury
Thanks for the update. I just wanted to touch base and see if you would like me to build a test kernel with commit 2724680 reverted? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1331150

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-07-03 Thread BOSH Eng
quick update: git bisect points at commit 2724680. it appears that net.ipv4.neigh.default.gc_thresh1 conf is now being used to skip pruning of table entries. setting gc_thresh1=0 brings back old (desired) behavior. we are continuing to investigate this problem. ``` git bisect start # bad:

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-07-01 Thread Joseph Salisbury
Thanks for the update, Dave. Were you able to test the latest mainline kernel mentioned in comment #9 to see if this bug is already fixed upstream? If the bug is fixed in mainline, we can perform a Reverse bisect to find the commit that fixes it. Otherwise, we can perform a regular bisect to

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-06-24 Thread Dave Liebreich
we are seeing the same problem with 3.15.0-6 #11 kernel (we used an utopic ami and added our bosh stemcell bits to it). Does that kernel include the fix listed above? Sorry it took so long to get this up and running our environment. We do *not* see the problem in a precise system (3.2.0-64 #97)

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-06-23 Thread Dave Liebreich
That commit does not appear to have fixed our problem. we took the 3.13.0-29 #53 kernel source, applied the patch above, and deployed to our environment. We are seeing the same behavior with this patch. We are currently setting up a parallel test environment, as well as building a precise image

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-06-23 Thread Joseph Salisbury
It would be good to test the latest mainline kernel, which is 3.16-rc1. That will tell us if it is already fixed upstream. If it is, we can perform a Reverse kernel bisect to identify the commit that fixes this. The latest mainline kernel is available from:

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-06-17 Thread Dave Liebreich
vcap@34fd733b-3ec0-4f6f-bdf7-24ab74b89b37:~$ cat /proc/version_signature Ubuntu 3.13.0-24.47-generic 3.13.9 vcap@34fd733b-3ec0-4f6f-bdf7-24ab74b89b37:~$ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 vcap@34fd733b-3ec0-4f6f-bdf7-24ab74b89b37:~$ -- You received this bug

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-06-17 Thread Joseph Salisbury
Did this issue occur in a previous version of Ubuntu, or is this a new issue? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0]. If this bug is fixed in the mainline kernel, please add

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-06-17 Thread Joseph Salisbury
** Tags added: kernel-key ** Changed in: linux (Ubuntu) Importance: Medium = Critical ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-06-17 Thread Dustin Kirkland 
Kamal suggests that this upstream kernel commit *might* be related to this issue: http://kernel.ubuntu.com/git?p=ubuntu/linux.git;a=commitdiff;h=d85f62f554904c778bd4d0eb1eb2b629753771b2 Completely untested. Just FYI. -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-06-17 Thread Dave Liebreich
It may take a day or so to integrate a 3.15 kernel into our ami - we'll have to modify our build process [0], then deploy it into one of the environments that is exhibiting the problem. We will start on that track later today - please let us know if you need any additional info. [0]

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-06-17 Thread Joseph Salisbury
Possible fix that is in mainline as of 3.15: cc2f338 batman-adv: fix local TT check for outgoing arp requests in DAT Will be included in upstream 3.13 soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-06-17 Thread Joseph Salisbury
** Changed in: linux (Ubuntu) Importance: Critical = High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1331150 Title: arp fails to update, 3.13.0-{24,29} Status in “linux” package

[Kernel-packages] [Bug 1331150] Re: arp fails to update, 3.13.0-{24, 29}

2014-06-17 Thread Dave Liebreich
Thanks for the quick response and offers of help to test. We have a workaround in-flight that we are focusing on, so someone from our org may pick up testing and merging the 3.13 + fix kernel tomorrow (at the earliest). Thanks again. -- You received this bug notification because you are a