← Back to team overview

kernel-packages team mailing list archive

[Bug 1504914] Re: System freeze/restart on high memory usage

 

Hi Christopher: I've tested it with the latest upstream kernel available
4.3.0-040300rc5 and the problem persist with the same symptoms described
previously. This time tough I've got a crash file  _usr_bin_Xorg.0.crash
but when I've tried to send it as bug report it gives an error and
prevent me to send it. The title of the crash report would be "Xorg
crashed with SIGABRT in __libc_message()". HTH


** Changed in: linux (Ubuntu)
       Status: Incomplete => Confirmed

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

Title:
  System freeze/restart on high memory usage

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  What is expected to happen is when all RAM and swap is either nearly
  or fully consumed by a process or application, the OS remains
  responsive, it doesn't crash to the login screen, and eventually the
  process or application asking for the majority of resources is force
  closed.

  What happens instead is the mouse stops responding promptly or not at
  all, and eventually the system resets to the logon screen.

  Specific scenarios to reproduce:
  - First, when having several chrome tabs open, press CTRL+T several times and arrive to a memory limit.
  - Second, I experience this when using virtualbox, given that the VM was asking for half of the memory available, as soon as I open a couple of tabs in chrome in the host the system started to be unusable.
  - Third, to reproduce it easily I've installed memtester application and run a couple of instances of it asking 2G chunks, this effectively reproduce the crash very effectively.

  I've checked:
  - All 4GB of memory passed memtest86+.
  - Tested with and without 4GB swap file same crash.

  Untested: Adding in /etc/rc.local :
  sysctl vm.vfs_cache_pressure=100000

  WORKAROUND: By adding into /etc/sysctl.conf the following, I'm not losing control of the system even if it slows down when ramping up the swap use:
  vm.min_free_kbytes=131072
  vm.swappiness=5

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-65-generic 3.13.0-65.106
  ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  yas        3625 F.... pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 11 10:41:41 2015
  InstallationDate: Installed on 2015-01-17 (266 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X3E/900X4C/900X4D
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic.efi.signed root=UUID=c5d1dcf0-367e-4643-99f9-735befcdaba1 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-65-generic N/A
   linux-backports-modules-3.13.0-65-generic  N/A
   linux-firmware                             1.127.15
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P11ABK
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: NP900X3E-A01ES
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP11ABK:bd07/15/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X3E/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP900X3E-A01ES:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 900X3C/900X3D/900X3E/900X4C/900X4D
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


References