I've bisected Ubuntu-3.13.0-96.143 to Ubuntu3.13.0-97.144 and it looks
like 7b82096b0ebc9bf487b390fe970d66ffa5a5774e introduced the problem.

thomasco@dev:/storage/ubuntu-trusty (7b82096...|BISECTING) $ git bisect bad
7b82096b0ebc9bf487b390fe970d66ffa5a5774e is the first bad commit
commit 7b82096b0ebc9bf487b390fe970d66ffa5a5774e
Author: Jiri Pirko <j...@resnulli.us>
Date:   Sat Dec 7 19:26:56 2013 +0100

    neigh: restore old behaviour of default parms values

    commit 1d4c8c29841b9991cdf3c7cc4ba7f96a94f104ca upstream.

    Previously inet devices were only constructed when addresses are added.
    Therefore the default neigh parms values they get are the ones at the
    time of these operations.

    Now that we're creating inet devices earlier, this changes the behaviour
    of default neigh parms values in an incompatible way (see bug #8519).

    This patch creates a compromise by setting the default values at the
    same point as before but only for those that have not been explicitly
    set by the user since the inet device's creation.

    Introduced by:
    commit 8030f54499925d073a88c09f30d5d844fb1b3190
    Author: Herbert Xu <herb...@gondor.apana.org.au>
    Date:   Thu Feb 22 01:53:47 2007 +0900

        [IPV4] devinet: Register inetdev earlier.

    Signed-off-by: Jiri Pirko <j...@resnulli.us>
    Signed-off-by: David S. Miller <da...@davemloft.net>
    BugLink: https://bugs.launchpad.net/bugs/994931
    Signed-off-by: Kamal Mostafa <ka...@canonical.com>
    Acked-by: Tim Gardner <tim.gard...@canonical.com>
    Acked-by: Brad Figg <brad.f...@canonical.com>

:040000 040000 b95e2490d8d94ffb3c4b5818b0ca05e2cdff17d2 
7296def1ea38ae1c46ec1a6ba4df3d26fe568545 M      include
:040000 040000 e78478aead22c4947b2b4f816a244272613fdc08 
12e3e33ddae9c141ae77b6eb471ab5b9d5214db8 M      net

thomasco@dev:/storage/ubuntu-trusty (7b82096...|BISECTING) $ git bisect log
# bad: [002556d23100065c43d60bfdab94fedf0a30cca6] UBUNTU: Ubuntu-3.13.0-97.144
# good: [d8590fec6790ab84c56f483bef6ce0caf71a40af] UBUNTU: Ubuntu-3.13.0-96.143
git bisect start 'Ubuntu-3.13.0-97.144' 'Ubuntu-3.13.0-96.143'
# good: [e5e45738175efd66844287ddcdf75e0e756fbd52] PCI: Add Netronome vendor 
and device IDs
git bisect good e5e45738175efd66844287ddcdf75e0e756fbd52
# good: [a70a25682944ac342dae0add0a4bb4c443e93411] Revert "UBUNTU: SAUCE: 
(no-up) ipv6: make the net.ipv6.conf.all.use_tempaddr sysctl propagate to 
interface settings"
git bisect good a70a25682944ac342dae0add0a4bb4c443e93411
# good: [6235189019f6136cb28646c2e637b76217a8d837] neigh: use tbl->family to 
distinguish ipv4 from ipv6
git bisect good 6235189019f6136cb28646c2e637b76217a8d837
# bad: [68a4a771678dd24d5eb30801d43412afb48723f5] neigh: ipv6: respect default 
values set before an address is assigned to device
git bisect bad 68a4a771678dd24d5eb30801d43412afb48723f5
# bad: [7b82096b0ebc9bf487b390fe970d66ffa5a5774e] neigh: restore old behaviour 
of default parms values
git bisect bad 7b82096b0ebc9bf487b390fe970d66ffa5a5774e
# first bad commit: [7b82096b0ebc9bf487b390fe970d66ffa5a5774e] neigh: restore 
old behaviour of default parms values

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or
  later causes 'invalid argument' error

Status in linux package in Ubuntu:
Status in linux-lts-trusty package in Ubuntu:

Bug description:
  Setting net.ipv4.neigh.default.gc_thresh1/2/3 on the 3.13.0-96-generic
  kernel and below worked fine using the following:

  $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128

  As of 3.13.0-97-generic, though, it no longer works as expected:

  $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128
  error: "Invalid argument" setting key "net.ipv4.neigh.default.gc_thresh1"

  There are two potentially related revisions in the -97 release -
  backport-trusty&id=563cf19389d8e999e69d6c94995966aeaf7c3a08 and

  The expected behavior is that changing neighbor table settings works
  using 'sysctl -w' with the same values as before the -97 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-98-generic 3.13.0-98.145~precise1
  ProcVersionSignature: Ubuntu 3.13.0-98.145~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-98-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1p', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  CurrentDmesg: [    4.586115] NET: Registered protocol family 40
  Date: Wed Oct 19 06:13:36 2016
  HibernationDevice: RESUME=UUID=d32abfeb-623f-4c11-ae4a-a7babe8c2139
  InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release 
amd64 (20140806.1)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  MarkForUpload: True
   PATH=(custom, no user)
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic 
root=UUID=febea164-78c3-4d3a-a0ce-0f09990df608 ro find_preseed=/preseed.cfg 
noprompt quiet
   linux-restricted-modules-3.13.0-98-generic N/A
   linux-backports-modules-3.13.0-98-generic  N/A
   linux-firmware                             1.79.16
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to