Bug #1162073 “[NP900X4C-A04US] System freeze on high memory usag...” : Bugs : linux package : Ubuntu

Revision history for this message

Ivan Danov (danov) wrote on 2013-03-29:

#1

AlsaInfo.txt Edit (28.0 KiB, text/plain; charset="utf-8")
BootDmesg.txt Edit (55.7 KiB, text/plain; charset="utf-8")
CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (3.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.5 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (513 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (9.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (476 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (3.7 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (319 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.3 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.0 KiB, text/plain; charset="utf-8")
PulseList.txt Edit (17.7 KiB, text/plain; charset="utf-8")
RfKill.txt Edit (246 bytes, text/plain; charset="utf-8")
UdevDb.txt Edit (137.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (323.9 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (784.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Brad Figg (brad-figg) wrote on 2013-03-30: Status changed to Confirmed

#2

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Ivan Danov (danov) on 2013-03-30

tags:

added: kernel-bug-exists-upstream

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2013-04-01: Re: System freeze on high memory usage

#3

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

Changed in linux (Ubuntu):
importance:	Undecided → Medium

Revision history for this message

Joseph Salisbury (jsalisbury) wrote on 2013-04-01:

#4

Also, was there a prior release or kernel version that did not exhibit this bug?

Changed in linux (Ubuntu):
status:	Confirmed → Triaged

Revision history for this message

Ivan Danov (danov) wrote on 2013-04-01: System freezes when RAM is full (64-bit)

#5

The system freezes when RAM gets completely full. By using MATLAB, I can
get all 8GB RAM of my laptop full and it immediately freezes, needing
restart using the hardware button. Other people have reported the bug at
since 2007. It seems that only the 64-bit version is affected and people
have reported that enabling DMA in BIOS settings solve the problem.
However, my laptop lacks such an option in the BIOS settings, so I am
unable to test it. More information about the bug could be found at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1162073 and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356.

Best Regards,
Ivan

Revision history for this message

Ivan Danov (danov) wrote on 2013-04-04:

#6

bug.tar.gz Edit (54.4 KiB, application/x-gzip; name="bug.tar.gz")

Hi Michal,

Yes, I use swap partition (2GB), but I have applied some things for
keeping the life of the SSD hard drive longer. All the things I have
done are under point 3. at
http://www.rileybrandt.com/2012/11/18/linux-ultrabook/. By system
freezes, I mean that the desktop environment doesn't react on my input.
Just sometimes the mouse is reacting very very choppy and slowly, but
most of the times it is not reacting at all. In the attached file, I
have the output of the script and the content of dmesg for all levels
from warn to emerg, as well as my kernel config.

Best,
Ivan
--
On 04/04/13 09:08, Michal Hocko wrote:
> On Thu 04-04-13 08:27:18, Simon Jeons wrote:
>> On 04/03/2013 08:12 PM, Michal Hocko wrote:
>>> On Mon 01-04-13 21:14:40, Ivan Danov wrote:
>>>> The system freezes when RAM gets completely full. By using MATLAB, I
>>>> can get all 8GB RAM of my laptop full and it immediately freezes,
>>>> needing restart using the hardware button.
>>> Do you use swap (file/partition)? How big? Could you collect
>>> /proc/meminfo and /proc/vmstat (every few seconds)[1]?
>>> What does it mean when you say the system freezes? No new processes can
>>> be started or desktop environment doesn't react on your input? Do you
>>> see anything in the kernel log? OOM killer e.g.
>>> In case no new processes could be started what does sysrq+m say when the
>>> system is frozen?
>>>
>>> What is your kernel config?
>>>
>>>> Other people have
>>>> reported the bug at since 2007. It seems that only the 64-bit
>>>> version is affected and people have reported that enabling DMA in
>>>> BIOS settings solve the problem. However, my laptop lacks such an
>>>> option in the BIOS settings, so I am unable to test it. More
>>>> information about the bug could be found at:
>>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1162073 and
>>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356.
>>>>
>>>> Best Regards,
>>>> Ivan
>>>>
>>> ---
>>> [1] E.g. by
>>> while true
>>> do
>>> STAMP=`date +%s`
>>> cat /proc/meminfo > meminfo.$STAMP
>>> cat /proc/vmscan > meminfo.$STAMP
>> s/vmscan/vmstat
> Right. Sorry about the typo and thanks for pointing out Simon.
>
>>> sleep 2s
>>> done

Hi Michal,

Yes, I use swap partition (2GB), but I have applied some things for 
keeping the life of the SSD hard drive longer. All the things I have 
done are under point 3. at 
http://www.rileybrandt.com/2012/11/18/linux-ultrabook/. By system 
freezes, I mean that the desktop environment doesn't react on my input. 
Just sometimes the mouse is reacting very very choppy and slowly, but 
most of the times it is not reacting at all. In the attached file, I 
have the output of the script and the content of dmesg for all levels 
from warn to emerg, as well as my kernel config.

Best,
Ivan
--
On 04/04/13 09:08, Michal Hocko wrote:
> On Thu 04-04-13 08:27:18, Simon Jeons wrote:
>> On 04/03/2013 08:12 PM, Michal Hocko wrote:
>>> On Mon 01-04-13 21:14:40, Ivan Danov wrote:
>>>> The system freezes when RAM gets completely full. By using MATLAB, I
>>>> can get all 8GB RAM of my laptop full and it immediately freezes,
>>>> needing restart using the hardware button.
>>> Do you use swap (file/partition)? How big? Could you collect
>>> /proc/meminfo and /proc/vmstat (every few seconds)[1]?
>>> What does it mean when you say the system freezes? No new processes can
>>> be started or desktop environment doesn't react on your input? Do you
>>> see anything in the kernel log? OOM killer e.g.
>>> In case no new processes could be started what does sysrq+m say when the
>>> system is frozen?
>>>
>>> What is your kernel config?
>>>
>>>> Other people have
>>>> reported the bug at since 2007. It seems that only the 64-bit
>>>> version is affected and people have reported that enabling DMA in
>>>> BIOS settings solve the problem. However, my laptop lacks such an
>>>> option in the BIOS settings, so I am unable to test it. More
>>>> information about the bug could be found at:
>>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1162073 and
>>>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356.
>>>>
>>>> Best Regards,
>>>> Ivan
>>>>
>>> ---
>>> [1] E.g. by
>>> while true
>>> do
>>> 	STAMP=`date +%s`
>>> 	cat /proc/meminfo > meminfo.$STAMP
>>> 	cat /proc/vmscan > meminfo.$STAMP
>> s/vmscan/vmstat
> Right. Sorry about the typo and thanks for pointing out Simon.
>
>>> 	sleep 2s
>>> done

Revision history for this message

Ivan Danov (danov) wrote on 2013-04-05:

#7

Tried with vm.swappiness=60, but the only improvement is that now the
mouse input is less choppy than before, but still the problem remains -
the computer is not usable at all, one could not even stop the program,
causing the problem.

Best,
Ivan
--
On 04/04/13 17:16, Michal Hocko wrote:
> On Thu 04-04-13 16:10:06, Ivan Danov wrote:
>> Hi Michal,
>>
>> Yes, I use swap partition (2GB), but I have applied some things for
>> keeping the life of the SSD hard drive longer. All the things I have
>> done are under point 3. at
>> http://www.rileybrandt.com/2012/11/18/linux-ultrabook/.
> OK, I guess I know what's going on here.
> So you did set vm.swappiness=0 which (for some time) means that there is
> almost no swapping going on (although you have plenty of swap as you are
> mentioning above).
> This shouldn't be a big deal normally but you are also backing your
> /tmp on tmpfs which is in-memory filesystem. This means that if you
> are writing to /tmp a lot then this content will fill up your memory
> which is not swapped out until the memory reclaim is getting into real
> troubles - most of the page cache is dropped by that time so your system
> starts trashing.
>
> I would encourage you to set swappiness to a more reasonable value (I
> would use the default value which is 60). I understand that you are
> concerned about your SSD lifetime but your user experience sounds like a
> bigger priority ;)
>
>> By system freezes, I mean that the desktop environment doesn't react
>> on my input. Just sometimes the mouse is reacting very very choppy
>> and slowly, but most of the times it is not reacting at all. In the
>> attached file, I have the output of the script and the content of
>> dmesg for all levels from warn to emerg, as well as my kernel config.
> I haven't checked your attached data but you should get an overview from
> Shmem line from /proc/meminfo which tells you how much shmem/tmpfs
> memory you are using and grep "^Swap" /proc/meminfo will tell you more
> about your swap usage.
>
>> Best,
>> Ivan
> HTH

Tried with vm.swappiness=60, but the only improvement is that now the 
mouse input is less choppy than before, but still the problem remains - 
the computer is not usable at all, one could not even stop the program, 
causing the problem.

Best,
Ivan
--
On 04/04/13 17:16, Michal Hocko wrote:
> On Thu 04-04-13 16:10:06, Ivan Danov wrote:
>> Hi Michal,
>>
>> Yes, I use swap partition (2GB), but I have applied some things for
>> keeping the life of the SSD hard drive longer. All the things I have
>> done are under point 3. at
>> http://www.rileybrandt.com/2012/11/18/linux-ultrabook/.
> OK, I guess I know what's going on here.
> So you did set vm.swappiness=0 which (for some time) means that there is
> almost no swapping going on (although you have plenty of swap as you are
> mentioning above).
> This shouldn't be a big deal normally but you are also backing your
> /tmp on tmpfs which is in-memory filesystem. This means that if you
> are writing to /tmp a lot then this content will fill up your memory
> which is not swapped out until the memory reclaim is getting into real
> troubles - most of the page cache is dropped by that time so your system
> starts trashing.
>
> I would encourage you to set swappiness to a more reasonable value (I
> would use the default value which is 60). I understand that you are
> concerned about your SSD lifetime but your user experience sounds like a
> bigger priority ;)
>
>> By system freezes, I mean that the desktop environment doesn't react
>> on my input. Just sometimes the mouse is reacting very very choppy
>> and slowly, but most of the times it is not reacting at all. In the
>> attached file, I have the output of the script and the content of
>> dmesg for all levels from warn to emerg, as well as my kernel config.
> I haven't checked your attached data but you should get an overview from
> Shmem line from /proc/meminfo which tells you how much shmem/tmpfs
> memory you are using and grep "^Swap" /proc/meminfo will tell you more
> about your swap usage.
>
>> Best,
>> Ivan
> HTH

Revision history for this message

Ivan Danov (danov) wrote on 2013-04-05:

#8

bug-with-swappiness.tar.gz Edit (11.8 KiB, application/x-gzip; name="bug-with-swappiness.tar.gz")

Here you can find attached the script, collecting the logs and the logs
themselves during the described process of freezing. It appeared that
the previous logs are corrupted, because both /proc/vmstat and
/proc/meminfo have been logging to the same file.
--
On 05/04/13 13:59, Michal Hocko wrote:
> On Fri 05-04-13 12:13:11, Ivan Danov wrote:
>> Tried with vm.swappiness=60, but the only improvement is that now
>> the mouse input is less choppy than before, but still the problem
>> remains - the computer is not usable at all, one could not even stop
>> the program, causing the problem.
> OK, could you collect /proc/vmstat and /proc/meminfo during that load?
>
>> Best,
>> Ivan
>> --
>> On 04/04/13 17:16, Michal Hocko wrote:
>>> On Thu 04-04-13 16:10:06, Ivan Danov wrote:
>>>> Hi Michal,
>>>>
>>>> Yes, I use swap partition (2GB), but I have applied some things for
>>>> keeping the life of the SSD hard drive longer. All the things I have
>>>> done are under point 3. at
>>>> http://www.rileybrandt.com/2012/11/18/linux-ultrabook/.
>>> OK, I guess I know what's going on here.
>>> So you did set vm.swappiness=0 which (for some time) means that there is
>>> almost no swapping going on (although you have plenty of swap as you are
>>> mentioning above).
>>> This shouldn't be a big deal normally but you are also backing your
>>> /tmp on tmpfs which is in-memory filesystem. This means that if you
>>> are writing to /tmp a lot then this content will fill up your memory
>>> which is not swapped out until the memory reclaim is getting into real
>>> troubles - most of the page cache is dropped by that time so your system
>>> starts trashing.
>>>
>>> I would encourage you to set swappiness to a more reasonable value (I
>>> would use the default value which is 60). I understand that you are
>>> concerned about your SSD lifetime but your user experience sounds like a
>>> bigger priority ;)
>>>
>>>> By system freezes, I mean that the desktop environment doesn't react
>>>> on my input. Just sometimes the mouse is reacting very very choppy
>>>> and slowly, but most of the times it is not reacting at all. In the
>>>> attached file, I have the output of the script and the content of
>>>> dmesg for all levels from warn to emerg, as well as my kernel config.
>>> I haven't checked your attached data but you should get an overview from
>>> Shmem line from /proc/meminfo which tells you how much shmem/tmpfs
>>> memory you are using and grep "^Swap" /proc/meminfo will tell you more
>>> about your swap usage.
>>>
>>>> Best,
>>>> Ivan
>>> HTH

Here you can find attached the script, collecting the logs and the logs 
themselves during the described process of freezing. It appeared that 
the previous logs are corrupted, because both /proc/vmstat and 
/proc/meminfo have been logging to the same file.
--
On 05/04/13 13:59, Michal Hocko wrote:
> On Fri 05-04-13 12:13:11, Ivan Danov wrote:
>> Tried with vm.swappiness=60, but the only improvement is that now
>> the mouse input is less choppy than before, but still the problem
>> remains - the computer is not usable at all, one could not even stop
>> the program, causing the problem.
> OK, could you collect /proc/vmstat and /proc/meminfo during that load?
>
>> Best,
>> Ivan
>> --
>> On 04/04/13 17:16, Michal Hocko wrote:
>>> On Thu 04-04-13 16:10:06, Ivan Danov wrote:
>>>> Hi Michal,
>>>>
>>>> Yes, I use swap partition (2GB), but I have applied some things for
>>>> keeping the life of the SSD hard drive longer. All the things I have
>>>> done are under point 3. at
>>>> http://www.rileybrandt.com/2012/11/18/linux-ultrabook/.
>>> OK, I guess I know what's going on here.
>>> So you did set vm.swappiness=0 which (for some time) means that there is
>>> almost no swapping going on (although you have plenty of swap as you are
>>> mentioning above).
>>> This shouldn't be a big deal normally but you are also backing your
>>> /tmp on tmpfs which is in-memory filesystem. This means that if you
>>> are writing to /tmp a lot then this content will fill up your memory
>>> which is not swapped out until the memory reclaim is getting into real
>>> troubles - most of the page cache is dropped by that time so your system
>>> starts trashing.
>>>
>>> I would encourage you to set swappiness to a more reasonable value (I
>>> would use the default value which is 60). I understand that you are
>>> concerned about your SSD lifetime but your user experience sounds like a
>>> bigger priority ;)
>>>
>>>> By system freezes, I mean that the desktop environment doesn't react
>>>> on my input. Just sometimes the mouse is reacting very very choppy
>>>> and slowly, but most of the times it is not reacting at all. In the
>>>> attached file, I have the output of the script and the content of
>>>> dmesg for all levels from warn to emerg, as well as my kernel config.
>>> I haven't checked your attached data but you should get an overview from
>>> Shmem line from /proc/meminfo which tells you how much shmem/tmpfs
>>> memory you are using and grep "^Swap" /proc/meminfo will tell you more
>>> about your swap usage.
>>>
>>>> Best,
>>>> Ivan
>>> HTH

Revision history for this message

penalvch (penalvch) wrote on 2013-04-06: Re: System freeze on high memory usage

#9

Ivan Danov, for regression testing purposes could you please test for this in Lucid via http://releases.ubuntu.com/lucid/ubuntu-10.04.4-desktop-amd64.iso ?

tags:	added: kernel-bug-exists-upstream-v3.9-rc4 needs-upstream-testing removed: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status:	Triaged → Incomplete

Revision history for this message

Ivan Danov (danov) wrote on 2013-04-06:

#10

Can I use virtual machine for testing it or it should be a completely new installation on the same hardware?

Revision history for this message

Ivan Danov (danov) wrote on 2013-04-10:

#11

Tested with ubuntu-10.04.4 on a desktop machine with 4GB of RAM and 10GB of swap. The problem remains, but needed higher demand to simulate and the input is less choppy, making it easier to use the UI. This leads me to the conlcusion that the problem happens when the whole virtual memory is full, i.e. both RAM and Swap memory.

I would expect a behaviour that keeps reserved some of the RAM for sustaining the basic OS operations.

However, I will try to increase the Swap and see if the problem is not so severe.

Revision history for this message

Ivan Danov (danov) wrote on 2013-04-12: Re: System freezes when RAM is full (64-bit)

#12

bug.tar.gz Edit (17.2 KiB, application/x-gzip; name="bug.tar.gz")

Download full text (7.0 KiB)

$ cat /proc/sys/vm/swappiness
60

I have increased my swap partition from nearly 2GB to around 16GB, but
the problem remains. Here I attach the logs for the larger swap
partition. I use a MATLAB script to simulate the problem, but it also
works in Octave:
X = ones(100000,10000);

I have tried to simulate the problem on a desktop installation with 4GB
of RAM, 10GB of swap partition, installed Ubuntu Lucid and then upgraded
to 12.04, the problem isn't there, but the input is still quite choppy
during the load. After the script finishes, everything looks fine. For
the desktop installation the hard drive is not an SSD hard drive.

On 12/04/13 12:20, Michal Hocko wrote:
> [CCing Mel and Johannes]
> On Fri 05-04-13 22:41:37, Ivan Danov wrote:
>> Here you can find attached the script, collecting the logs and the
>> logs themselves during the described process of freezing. It
>> appeared that the previous logs are corrupted, because both
>> /proc/vmstat and /proc/meminfo have been logging to the same file.
> Sorry for the late reply:
> $ grep MemFree: meminfo.1365194* | awk 'BEGIN{min=9999999}{val=$2; if(val<min)min=val; if(val>max)max=val; sum+=val; n++}END{printf "min:%d max:%d avg:%.2f\n", min, max, sum/n}'
> min:165256 max:3254516 avg:1642475.35
>
> So the free memory dropped down to 165M at minimum. This doesn't sound
> terribly low and the average free memory was even above 1.5G. But maybe
> the memory consumption peak was very short between 2 measured moments.
>
> The peak seems to be around this time:
> meminfo.1365194083:MemFree: 650792 kB
> meminfo.1365194085:MemFree: 664920 kB
> meminfo.1365194087:MemFree: 165256 kB <<<
> meminfo.1365194089:MemFree: 822968 kB
> meminfo.1365194094:MemFree: 666940 kB
>
> Let's have a look at the memory reclaim activity
> vmstat.1365194085:pgscan_kswapd_dma32 760
> vmstat.1365194085:pgscan_kswapd_normal 10444
>
> vmstat.1365194087:pgscan_kswapd_dma32 760
> vmstat.1365194087:pgscan_kswapd_normal 10444
>
> vmstat.1365194089:pgscan_kswapd_dma32 5855
> vmstat.1365194089:pgscan_kswapd_normal 80621
>
> vmstat.1365194094:pgscan_kswapd_dma32 54333
> vmstat.1365194094:pgscan_kswapd_normal 285562
>
> [...]
> vmstat.1365194098:pgscan_kswapd_dma32 54333
> vmstat.1365194098:pgscan_kswapd_normal 285562
>
> vmstat.1365194100:pgscan_kswapd_dma32 55760
> vmstat.1365194100:pgscan_kswapd_normal 289493
>
> vmstat.1365194102:pgscan_kswapd_dma32 55760
> vmstat.1365194102:pgscan_kswapd_normal 289493
>
> So the background reclaim was active only twice for a short amount of
> time:
> - 1365194087 - 1365194094 - 53573 pages in dma32 and 275118 in normal zone
> - 1365194098 - 1365194100 - 1427 pages in dma32 and 3931 in normal zone
>
> The second one looks sane so we can ignore it for now but the first one
> scanned 1074M in normal zone and 209M in the dma32 zone. Either kswapd
> had hard time to find something to reclaim or it couldn't cope with the
> ongoing memory pressure.
>
> vmstat.1365194087:pgsteal_kswapd_dma32 373
> vmstat.1365194087:pgsteal_kswapd_normal 9057
>
> vmstat.1365194089:pgsteal_kswapd_dma32 3249
> vmstat.1365194089:pgsteal_kswapd_normal 56756
>
> vmstat.136519409...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 14/04/13 16:58, Michal Hocko wrote:
> On Fri 12-04-13 14:38:00, Ivan Danov wrote:
>> On 12/04/13 13:11, Michal Hocko wrote:
>>> On Fri 12-04-13 12:49:30, Ivan Danov wrote:
>>>> $ cat /proc/sys/vm/swappiness
>>>> 60
>>> OK, thanks for confirming this. It is really strange that we do not swap
>>> almost at all, then.
>>>> I have increased my swap partition from nearly 2GB to around 16GB,
>>>> but the problem remains.
>>> Increasing the swap partition will not help much as it almost unused
>>> with 2G already (at least last data shown that).
>>>
>>>> Here I attach the logs for the larger swap partition. I use a MATLAB
>>>> script to simulate the problem, but it also works in Octave:
>>>> X = ones(100000,10000);
>>> AFAIU this will create a matrix with 10^9 elements and initialize them
>>> to 1. I am not familiar with octave but do you happen to know what is
>>> the data type used for the element? 8B? It would be also interesting to
>>> know how is the matrix organized and initialized. Does it fit into
>>> memory at all?
>> Yes, 8B each, so it will be almost 8GB and it should fit into the
>> memory.
>
> It won't fit in because kernel and other processes consume some memory
> as well. So you have to swap.
>
>> I don't know details how it actually works, but if it cannot
>> create the matrix, MATLAB complains about that. Since it starts
>> complaining even after 2000 more in the second dimension, maybe it
>> needs the RAM to create it all. However on the desktop machine, both
>> RAM and swap are being used (quite a lot of them both).
>
> How much you swap depends on vm.swappiness. I would suggest increasing
> the value if your workload is really so anononymous memory based.
> Otherwise a lot of file pages are reclaimed which can lead to problems
> you are seeing.
>
>>>> I have tried to simulate the problem on a desktop installation with
>>>> 4GB of RAM, 10GB of swap partition, installed Ubuntu Lucid and then
>>>> upgraded to 12.04, the problem isn't there, but the input is still
>>>> quite choppy during the load. After the script finishes, everything
>>>> looks fine. For the desktop installation the hard drive is not an
>>>> SSD hard drive.
>>> What is the kernel version used here?
>> $ uname -a
>> Linux ivan 3.2.0-40-generic #64-Ubuntu SMP Mon Mar 25 21:22:10 UTC
>> 2013 x86_64 x86_64 x86_64 GNU/Linux
>
> Is there any chance you could test with the latest vanilla kernel and
> Mel's patches from https://lkml.org/lkml/2013/4/11/516 on top?
Sorry for the late comeback, I've been quite busy these days. I will try
to compile the kernel in the weekend. However, I will do kernel
compiling for first time, so maybe it could take me some time. Btw I
have upgraded to Ubuntu 13.04, so my kernel now is:
$ uname -a
Linux ivan 3.8.0-19-generic #30-Ubuntu SMP Wed May 1 16:35:23 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux

The problem is still there.
>
> [...]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRkldrAAoJEJ8e6XRVH9TGgAIIAI7hw+YWhtiZ3LAr4SOQRvce
xkRcSFUjmhW3FCSm5TERtUY6Ney3hJ9NU7I4yA56WGwOf2E6GnNkG0plewNMsWrM
4ZCFevsm1MoGP5576PUm8F0FF/0EfpFRLLwNNB7dDYDsXdmG8KlOYjlEB5H31lrR
Ycx155ZvUgVUQXNg0tthaPoy8Qaw5sGI062d9tRA4f45fh7KFhX58HVHKT+L6LtV
caLXwdH5Wkzi+Xshl6h8BGnB57fjQCDCEdltR3f1ddbUnh5kjvXKLGUWvuut7Ish
vkbOTfSBbjOPtQly6DJ/xxS8HbSIsdDU4ecfWHGztl6r1lteFJDiqFA+bPsBszU=
=oULy
-----END PGP SIGNATURE-----

penalvch (penalvch) on 2013-05-15

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

penalvch (penalvch) on 2013-05-28

tags:	added: needs-computer-model raring
Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-06-04: Re: System freeze on high memory usage

#15

I can't believe it that it is a known bug, I supposed it was a problem related to some configuration error. I have Ubuntu 12.04 64-bit with 12 Gb of RAM and 12 Gb of swap and the problem happened also with previous versions of Ubuntu. When my RAM got full the system freezes, when I'm lucky I am able to kill MATLAB by ssh login otherwise I need to restart the system. I tried to change the vfs_cache_pressure but nothing has changed. If you confirm me that this is an Ubuntu bug I'll start to find another distribution.

Revision history for this message

penalvch (penalvch) wrote on 2013-06-08:

#16

matteodefelice, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-08-08:

#17

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Ivan Danov (danov) on 2013-08-19

Changed in linux (Ubuntu):
status:	Expired → Incomplete

Revision history for this message

Ivan Danov (danov) wrote on 2013-08-19:

#19

Samsung Series 9 NP900X4C-A04US

Revision history for this message

penalvch (penalvch) wrote on 2013-08-20:

#20

Ivan Danov, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

summary:	- System freeze on high memory usage + [NP900X4C-A04US] System freeze on high memory usage
tags:	removed: needs-computer-model

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-05:

#21

This bug is still happening on my ubuntu updated to 13.04 with the latest kernel update.

Revision history for this message

Daniel Letzeisen (dtl131) wrote on 2013-09-05:

#22

@matteo-defelice: please follow the instructions in comment #20.

penalvch (penalvch) on 2013-09-06

tags:

added: needs-oops-log regression-potential

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: apport information

#23

ApportVersion: 2.9.2-0ubuntu8.4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: matteo 3153 F.... pulseaudio
/dev/snd/controlC0: matteo 3153 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=18c94b06-56ba-4d27-876e-2ac6eff3b9ed
MachineType: Dell Inc. Precision WorkStation T3500
MarkForUpload: True
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-generic root=UUID=384a0a8d-fc24-453d-9c40-c0ec21d1b727 ro quiet splash
ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6
RelatedPackageVersions:
linux-restricted-modules-3.8.0-30-generic N/A
linux-backports-modules-3.8.0-30-generic N/A
linux-firmware 1.106
RfKill:

Tags: raring
Uname: Linux 3.8.0-30-generic x86_64
UpgradeStatus: Upgraded to raring on 2013-07-29 (42 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
dmi.bios.date: 04/20/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 09KPNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd04/20/2011:svnDellInc.:pnPrecisionWorkStationT3500:pvr:rvnDellInc.:rn09KPNV:rvrA01:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T3500
dmi.sys.vendor: Dell Inc.

tags:

added: apport-collected

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: AlsaInfo.txt

#24

apport information

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: BootDmesg.txt

#25

apport information

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: CurrentDmesg.txt

#26

apport information

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: HookError_cloud_archive.txt

#27

apport information

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: IwConfig.txt

#28

apport information

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: Lspci.txt

#29

apport information

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: Lsusb.txt

#30

apport information

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: ProcCpuinfo.txt

#31

apport information

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: ProcEnviron.txt

#32

apport information

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: ProcInterrupts.txt

#33

apport information

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: ProcModules.txt

#34

apport information

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: PulseList.txt

#35

apport information

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: UdevDb.txt

#36

apport information

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: UdevLog.txt

#37

apport information

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2013-09-10: WifiSyslog.txt

#38

apport information

Revision history for this message

penalvch (penalvch) wrote on 2013-09-10:

#39

matteodefelice, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

tags:

removed: apport-collected

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-11-10:

#40

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

Russell (russelljbrennan) wrote on 2014-02-20:

#41

I experience this as well, latest Ubuntu. When data goes to swap, the entire system freezes.

Changed in linux (Ubuntu):
status:	Expired → Confirmed

Revision history for this message

matteodefelice (matteo-defelice) wrote on 2014-02-20:

#42

I am quite sure that this problem is related to my RAID configuration. I'm waiting for the next LTS to remove the RAID to try to fix this issue.

Revision history for this message

penalvch (penalvch) wrote on 2014-02-21:

#43

Russell / matteodefelice, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

penalvch (penalvch) on 2014-02-21

description:

updated

Revision history for this message

tim pierson (tim-pierson) wrote on 2014-04-17:

#44

I can confirm that I'm also experieancing this bug. 12.04, clean install 16gb ram, 32 swap. It can be replicated in python with:

import numpy as np
l=[]
for i in range(10000):
l.append(np.array(np.ones(10000000), dtype=np.float64))

this can be done in console mode or GUI, the arrays are allocated, ram fills and swap begins, then the system freezes requiring a hard reboot.

Revision history for this message

penalvch (penalvch) wrote on 2014-04-18:

#45

tim pierson, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

tags:

added: bios-outdated-p06aac

Revision history for this message

ThePhoenix (cosminstefanxp) wrote on 2014-05-20:

#46

I'm also having the same issue. I've created a new bug report, as instructed: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321240

Revision history for this message

Launchpad Janitor (janitor) wrote on 2014-07-20:

#47

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

Lancillotto (antonio-petricca) wrote on 2018-03-30:

#48

Here is the solution my similar problem: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1526537/comments/27 .

Ubuntu
linux package

[NP900X4C-A04US] System freeze on high memory usage

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntulinux package

[NP900X4C-A04US] System freeze on high memory usage

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package