yas: "Regarding your question, effectively after reproducing the problem with the previous kernel I've got a crash file from google-chrome."
Please do file a crash report against that crash file as outlined in https://wiki.ubuntu.com/ReportingBugs . Despite this, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Description changed: - When a process demands increasingly to the limit of memory available the system becomes unusable, mouse start to not respond promptly or not at all, and eventually the system resets to the logon screen. - The expected behavior would be not to lose control of the machine but crash eventually the process or application asking for resources. + 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 I have done? - - Discard hardware problems, testing memory with memtest86+. No issue detected there. - - Test without swap file and with swap file of 4Gb (similar to main memory). Same crash. - - Following the advise on http://askubuntu.com/questions/41778/computer-freezing-on-almost-full-ram-possibly-disk-cache-problem set the sysctl vm.min_free_kbytes and adjust swappiness as described here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/comments/41 - With this adjustment the issue have been reduced drastically, I'm not losing control of the system even if it slows down when ramping up the swap use. - - I've not yet tried the suggestion here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/comments/35 because with the previous tip the system is behaving much as expected, but I have it in the list to test it if I experiment further crashes. + What happens instead is the mouse stops responding promptly or not at + all, and eventually the system resets to the logon screen. - How did I reproduce it? - - First, I experience this when having several chrome tabs open (chrome is eating a lot of memory lately being in tabs or in extensions). It's easy to press CTRL+T several times and arrive to a memory limit. - - Second, I experience this when using virtualbox, given that the vm was asking 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. + 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. - Tell me if I should add any other log to help diagnose the issue. - Hope this helps. + 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 + 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 + 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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504914 Title: System freeze/restart on high memory usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1504914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
