Attaching current slabtop

---
# cat /proc/meminfo 
MemTotal:       32856000 kB
MemFree:          381632 kB
MemAvailable:   30990804 kB
Buffers:        28709688 kB
Cached:           221664 kB
SwapCached:          184 kB
Active:         24854232 kB
Inactive:        5393552 kB
Active(anon):     783780 kB
Inactive(anon):   538772 kB
Active(file):   24070452 kB
Inactive(file):  4854780 kB
Unevictable:          32 kB
Mlocked:              32 kB
SwapTotal:      33553332 kB
SwapFree:       33552460 kB
Dirty:              2472 kB
Writeback:             0 kB
AnonPages:       1316236 kB
Mapped:            42768 kB
Shmem:              6164 kB
Slab:            2120976 kB
SReclaimable:    2086268 kB
SUnreclaim:        34708 kB
KernelStack:        4480 kB
PageTables:         9944 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:    49981332 kB
Committed_AS:    1326540 kB
VmallocTotal:   34359738367 kB
VmallocUsed:           0 kB
VmallocChunk:          0 kB
HardwareCorrupted:     0 kB
AnonHugePages:    868352 kB
CmaTotal:              0 kB
CmaFree:               0 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
DirectMap4k:      188008 kB
DirectMap2M:    33275904 kB


** Attachment added: "slabtop.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+attachment/4822862/+files/slabtop.txt

-- 
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/1666260

Title:
  "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Same as #1655842 - Started seeing oom-killer on multiple servers
  upgraded to 4.4.0-59.

  Unlike #1655842, also seeing the same oom-killer on multiple servers
  updated to 4.8.0-34.

  First upgraded them all 4.8 servers 4.8.0-36, then downgraded a few to
  4.4.0-63.  I am seeing no change in the memory usage, so I can only
  assume that 4.4.0-63 is also bugged with the same problem as 4.4.0-59
  and 4.8.0-34.  Either because #1655842 is not fixed, or it is only
  fixed for certain kinds of workloads.

  However, on closer inspection, there is definitely a notable
  difference between 4.4.0-59 and 4.4.0-63/4.8.0-34.

  The symptoms I'm seeing are:

  Upgrading 4.4.0-57 -> 4.4.0-59:
  - /proc/meminfo:Buffers: Up from 9GB to 15GB
  - /proc/meminfo:Cached: Up from 5GB to 10GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 5GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Upgrading 4.4.0-57 -> 4.8.0-34:
  - /proc/meminfo:Buffers: Up from 9GB to 14GB
  - /proc/meminfo:Cached: Down from 5GB to 2GB
  - /proc/meminfo:SReclaimable: Down from 15GB to 14GB.
  - /proc/meminfo:SUnreclaim: No notable change

  Downgrading 4.8.0-34 -> 4.4.0-63:  (however uptime is only 1 hour)
  - /proc/meminfo:Buffers: No notable change
  - /proc/meminfo:Cached: No notable change
  - /proc/meminfo:SReclaimable: No notable change
  - /proc/meminfo:SUnreclaim: No notable change

  Setting vm.vfs_cache_pressure = 300 seems to have a positive effect of
  not causing OOMs.

  Downgrading to 4.4.0-57 also works.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-63-generic 4.4.0-63.84
  ProcVersionSignature: Ubuntu 4.4.0-63.84-generic 4.4.44
  Uname: Linux 4.4.0-63-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  Date: Mon Feb 20 16:15:56 2017
  InstallationDate: Installed on 2012-06-04 (1721 days ago)
  InstallationMedia:
   
  IwConfig:
   lo        no wireless extensions.
   
   eth0      no wireless extensions.
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: System manufacturer System Product Name
  PciMultimedia:
   
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-63-generic 
root=UUID=b790930f-ad81-4b27-a353-a4b3d6a29007 ro nomodeset nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-63-generic N/A
   linux-backports-modules-4.4.0-63-generic  N/A
   linux-firmware                            1.157.8
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2017-02-16 (4 days ago)
  dmi.bios.date: 10/17/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1106
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1106:bd10/17/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1666260/+subscriptions

-- 
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