Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#8767 - X apps dieing

Attached to Project: Arch Linux
Opened by T. S. Collins (tscollins) - Monday, 26 November 2007, 15:36 GMT
Last edited by Greg (dolby) - Tuesday, 17 June 2008, 10:41 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: X Applications are dieing randomly

Additional info:
Here is part of my /var/log/message file:
Nov 26 08:48:32 tsc64 top invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 08:48:32 tsc64
Nov 26 08:48:32 tsc64 Call Trace:
Nov 26 08:48:32 tsc64 [<ffffffff80270bcd>] out_of_memory+0x1bd/0x200
Nov 26 08:48:32 tsc64 [<ffffffff80272902>] __alloc_pages+0x322/0x340
Nov 26 08:48:32 tsc64 [<ffffffff802747c1>] __do_page_cache_readahead+0x161/0x330
Nov 26 08:48:32 tsc64 [<ffffffff804ad625>] __wait_on_bit_lock+0x65/0x80
Nov 26 08:48:32 tsc64 [<ffffffff8026d6bf>] __lock_page+0x5f/0x70
Nov 26 08:48:32 tsc64 [<ffffffff80251600>] wake_bit_function+0x0/0x30
Nov 26 08:48:32 tsc64 [<ffffffff8026fe36>] filemap_fault+0x2c6/0x470
Nov 26 08:48:32 tsc64 [<ffffffff8027a5aa>] __do_fault+0x6a/0x4a0
Nov 26 08:48:32 tsc64 [<ffffffff8027c528>] handle_mm_fault+0x1d8/0x920
Nov 26 08:48:32 tsc64 [<ffffffff80226cdd>] do_page_fault+0x1dd/0x890
Nov 26 08:48:32 tsc64 [<ffffffff802340d0>] default_wake_function+0x0/0x10
Nov 26 08:48:32 tsc64 [<ffffffff802a2ff4>] do_ioctl+0x84/0xa0
Nov 26 08:48:32 tsc64 [<ffffffff804af9cd>] error_exit+0x0/0x84
Nov 26 08:48:32 tsc64
Nov 26 08:48:32 tsc64 Mem-info:
Nov 26 08:48:32 tsc64 DMA per-cpu:
Nov 26 08:48:32 tsc64 CPU 0: Hot: hi: 0, btch: 1 usd: 0 Cold: hi: 0, btch: 1 usd: 0
Nov 26 08:48:32 tsc64 CPU 1: Hot: hi: 0, btch: 1 usd: 0 Cold: hi: 0, btch: 1 usd: 0
Nov 26 08:48:32 tsc64 DMA32 per-cpu:
Nov 26 08:48:32 tsc64 CPU 0: Hot: hi: 186, btch: 31 usd: 29 Cold: hi: 62, btch: 15 usd: 50
Nov 26 08:48:32 tsc64 CPU 1: Hot: hi: 186, btch: 31 usd: 22 Cold: hi: 62, btch: 15 usd: 54
Nov 26 08:48:32 tsc64 Normal per-cpu:
Nov 26 08:48:32 tsc64 CPU 0: Hot: hi: 186, btch: 31 usd: 11 Cold: hi: 62, btch: 15 usd: 16
Nov 26 08:48:32 tsc64 CPU 1: Hot: hi: 186, btch: 31 usd: 32 Cold: hi: 62, btch: 15 usd: 58
Nov 26 08:48:32 tsc64 Active:492847 inactive:494015 dirty:0 writeback:0 unstable:0
Nov 26 08:48:32 tsc64 free:5408 slab:2782 mapped:1776 pagetables:3557 bounce:0
Nov 26 08:48:32 tsc64 DMA free:11532kB min:16kB low:20kB high:24kB active:0kB inactive:0kB present:9236kB pages_scanned:0 all_unreclaimable? yes
Nov 26 08:48:32 tsc64 lowmem_reserve[]: 0 3512 4017 4017
Nov 26 08:48:32 tsc64 DMA32 free:9084kB min:7080kB low:8848kB high:10620kB active:1741080kB inactive:1744816kB present:3596448kB pages_scanned:6655929 all_unreclaimable? yes
Nov 26 08:48:32 tsc64 lowmem_reserve[]: 0 0 505 505
Nov 26 08:48:32 tsc64 Normal free:1016kB min:1016kB low:1268kB high:1524kB active:230308kB inactive:231244kB present:517120kB pages_scanned:891784 all_unreclaimable? yes
Nov 26 08:48:32 tsc64 lowmem_reserve[]: 0 0 0 0
Nov 26 08:48:32 tsc64 DMA: 1*4kB 5*8kB 2*16kB 2*32kB 4*64kB 3*128kB 2*256kB 0*512kB 2*1024kB 0*2048kB 2*4096kB = 11532kB
Nov 26 08:48:32 tsc64 DMA32: 9*4kB 15*8kB 4*16kB 1*32kB 0*64kB 1*128kB 0*256kB 1*512kB 0*1024kB 0*2048kB 2*4096kB = 9084kB
Nov 26 08:48:32 tsc64 Normal: 30*4kB 0*8kB 0*16kB 0*32kB 0*64kB 1*128kB 1*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 1016kB
Nov 26 08:48:32 tsc64 Swap cache: add 899047, delete 899033, find 41028/59146, race 0+4
Nov 26 08:48:32 tsc64 Free swap = 0kB
Nov 26 08:48:32 tsc64 Total swap = 996020kB
Nov 26 08:48:32 tsc64 Free swap: 0kB
The system is a AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ with MemTotal: 4052988kB, started seeing this problem about two weeks ago. Here are some other highlights from the /var/log/message file:
Nov 21 10:42:14 tsc64 sshd invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 21 10:42:15 tsc64 bash invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 25 04:58:02 tsc64 rxvt invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 25 16:02:54 tsc64 wmaker invoked oom-killer: gfp_mask=0xa00d2, order=0, oomkilladj=0
Nov 25 20:02:10 tsc64 crond invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 25 20:02:11 tsc64 init invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 25 20:02:11 tsc64 X invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 25 20:02:11 tsc64 alsamixer invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 02:23:05 tsc64 vmware-vmx invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 08:48:32 tsc64 audacious invoked oom-killer: gfp_mask=0xa00d2, order=0, oomkilladj=0
Nov 26 08:48:32 tsc64 top invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 08:48:32 tsc64 syslog-ng invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 08:48:32 tsc64 firefox-bin invoked oom-killer: gfp_mask=0xa00d2, order=0, oomkilladj=0

Steps to reproduce:
Just leave apps up and running
This task depends upon

Closed by  Greg (dolby)
Tuesday, 17 June 2008, 10:41 GMT
Reason for closing:  None
Comment by Tobias Powalowski (tpowa) - Monday, 26 November 2007, 15:53 GMT
vmware-vmx you use not supported software vmware is something that is used deep in the system and a black box, this is not solvable from our side
Comment by Tobias Powalowski (tpowa) - Monday, 26 November 2007, 15:53 GMT
probably your vmware leaks the memory, it's a pure run out of memory error you have.
Comment by T. S. Collins (tscollins) - Monday, 26 November 2007, 16:53 GMT
Will not run VMware Workstation for a few days and see if the apps still crash, if they don't will file a bug with VMware.
Comment by Jan de Groot (JGC) - Monday, 26 November 2007, 22:08 GMT
Just configure your system correct:

Nov 26 08:48:32 tsc64 [<ffffffff80270bcd>] out_of_memory+0x1bd/0x200

You don't have enough memory and either your system is out of swap or you're running applications that block swapping (yes, on linux you can map memory that never gets swapped out to disk for security purposes).
Comment by T. S. Collins (tscollins) - Monday, 26 November 2007, 22:38 GMT
I think 4GB is plenty of memory! Since Arch64 is always being updated I have not compiled my own kernel but instead rely on the defaults of the distro and I do a 'pacman -Syu' on a weekly basis. I started seeing this problem about two weeks ago so maybe there is a problem with some default setting of Arch64. I will keep any eye on memory usage and what applications are doing with memory.
Comment by Jan de Groot (JGC) - Monday, 26 November 2007, 22:54 GMT
Hmm, I thought you were running a VMware machine with not enough memory, the comment by tpowa made me think that way.

Try to find out which program eats all your memory, it's not normal on a system with 4GB memory.
Comment by T. S. Collins (tscollins) - Tuesday, 27 November 2007, 03:13 GMT
No VMware or VMware services running, syslog-ng crashed first:
Nov 26 19:43:43 tsc64 syslog-ng invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 19:43:43 tsc64
Nov 26 19:43:43 tsc64 Call Trace:
Nov 26 19:43:43 tsc64 [<ffffffff80270bcd>] out_of_memory+0x1bd/0x200
Nov 26 19:43:43 tsc64 [<ffffffff80272902>] __alloc_pages+0x322/0x340
Nov 26 19:43:43 tsc64 [<ffffffff802747c1>] __do_page_cache_readahead+0x161/0x330
Nov 26 19:43:43 tsc64 [<ffffffff802a49a0>] __pollwait+0x0/0x130
Nov 26 19:43:43 tsc64 [<ffffffff802340d0>] default_wake_function+0x0/0x10
Nov 26 19:43:43 tsc64 [<ffffffff802340d0>] default_wake_function+0x0/0x10
Nov 26 19:43:45 tsc64 [<ffffffff8026fe36>] filemap_fault+0x2c6/0x470
Nov 26 19:43:45 tsc64 [<ffffffff8027a5aa>] __do_fault+0x6a/0x4a0
Nov 26 19:43:45 tsc64 [<ffffffff802340d0>] default_wake_function+0x0/0x10
Nov 26 19:43:45 tsc64 [<ffffffff8027c528>] handle_mm_fault+0x1d8/0x920
Nov 26 19:43:45 tsc64 [<ffffffff80294ca9>] do_sync_write+0xd9/0x120
Nov 26 19:43:45 tsc64 [<ffffffff80226cdd>] do_page_fault+0x1dd/0x890
Nov 26 19:43:45 tsc64 [<ffffffff804af9cd>] error_exit+0x0/0x84
Nov 26 19:43:45 tsc64
Nov 26 19:43:45 tsc64 Mem-info:
Nov 26 19:43:45 tsc64 DMA per-cpu:
Nov 26 19:43:45 tsc64 CPU 0: Hot: hi: 0, btch: 1 usd: 0 Cold: hi: 0, btch: 1 usd: 0
Nov 26 19:43:45 tsc64 CPU 1: Hot: hi: 0, btch: 1 usd: 0 Cold: hi: 0, btch: 1 usd: 0
Nov 26 19:43:45 tsc64 DMA32 per-cpu:
Nov 26 19:43:45 tsc64 CPU 0: Hot: hi: 186, btch: 31 usd: 30 Cold: hi: 62, btch: 15 usd: 56
Nov 26 19:43:45 tsc64 CPU 1: Hot: hi: 186, btch: 31 usd: 42 Cold: hi: 62, btch: 15 usd: 41
Nov 26 19:43:45 tsc64 Normal per-cpu:
Nov 26 19:43:45 tsc64 CPU 0: Hot: hi: 186, btch: 31 usd: 28 Cold: hi: 62, btch: 15 usd: 55
Nov 26 19:43:45 tsc64 CPU 1: Hot: hi: 186, btch: 31 usd: 161 Cold: hi: 62, btch: 15 usd: 61
Nov 26 19:43:45 tsc64 Active:600795 inactive:385932 dirty:0 writeback:0 unstable:0
Nov 26 19:43:45 tsc64 free:5397 slab:2878 mapped:1838 pagetables:3610 bounce:0
Nov 26 19:43:45 tsc64 DMA free:11532kB min:16kB low:20kB high:24kB active:0kB inactive:0kB present:9236kB pages_scanned:0 all_unreclaimable? yes
Nov 26 19:43:45 tsc64 lowmem_reserve[]: 0 3512 4017 4017
Nov 26 19:43:45 tsc64 DMA32 free:9052kB min:7080kB low:8848kB high:10620kB active:2169100kB inactive:1315328kB present:3596448kB pages_scanned:6635102 all_unreclaimable?
yes
Nov 26 19:43:45 tsc64 lowmem_reserve[]: 0 0 505 505
Nov 26 19:43:45 tsc64 Normal free:1004kB min:1016kB low:1268kB high:1524kB active:234080kB inactive:228400kB present:517120kB pages_scanned:733081 all_unreclaimable? yes
Nov 26 19:43:45 tsc64 lowmem_reserve[]: 0 0 0 0
Nov 26 19:43:45 tsc64 DMA: 1*4kB 5*8kB 2*16kB 2*32kB 4*64kB 3*128kB 2*256kB 0*512kB 2*1024kB 0*2048kB 2*4096kB = 11532kB
Nov 26 19:43:45 tsc64 DMA32: 13*4kB 7*8kB 1*16kB 1*32kB 1*64kB 1*128kB 0*256kB 1*512kB 0*1024kB 0*2048kB 2*4096kB = 9052kB
Nov 26 19:43:45 tsc64 Normal: 45*4kB 1*8kB 1*16kB 1*32kB 0*64kB 0*128kB 1*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 1004kB
Nov 26 19:43:45 tsc64 Swap cache: add 1180166, delete 1180166, find 50729/73478, race 0+5
Nov 26 19:43:45 tsc64 Free swap = 0kB
Nov 26 19:43:45 tsc64 Total swap = 996020kB
Nov 26 19:43:45 tsc64 Free swap: 0kB
but here is the order of 'oom-killer' since I stoped VMware services
Nov 26 19:43:43 tsc64 syslog-ng invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 19:43:45 tsc64 audacious invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 19:43:45 tsc64 audacious invoked oom-killer: gfp_mask=0xa00d2, order=0, oomkilladj=0
Nov 26 19:43:45 tsc64 syslog-ng invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 19:43:45 tsc64 X invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 19:43:45 tsc64 X invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 19:43:45 tsc64 wmCalClock invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 19:43:45 tsc64 X invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 19:43:45 tsc64 wmCalClock invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 19:43:45 tsc64 X invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Nov 26 19:43:45 tsc64 pidgin invoked oom-killer: gfp_mask=0xa01d2, order=0, oomkilladj=0
Comment by Jan de Groot (JGC) - Tuesday, 27 November 2007, 07:27 GMT
When you leave open top and sort on memory usage (shift+M), which process eats all your memory?
Comment by T. S. Collins (tscollins) - Tuesday, 27 November 2007, 15:14 GMT
Had laptop connected to the desktop system and with top running there was able to see that audacious was consuming 97.6 %Mem
Comment by Jan de Groot (JGC) - Tuesday, 27 November 2007, 15:28 GMT
So it's audacious that has a memleak. Any specific file you're playing at that moment? If it isn't too big and doesn't have copyright issues, could you attach it here?
Comment by T. S. Collins (tscollins) - Tuesday, 27 November 2007, 15:41 GMT
I have seen audacious complain about a few songs in my collection and will pay more attention to which ones and what the errors are, right now I know it has problems with some Dead Moon albums (ripped in both Ogg and MP3) and Desert Sessions Vol. 9 & 10 (ripped as MP3).
Comment by Roman Kyrylych (Romashka) - Friday, 11 January 2008, 11:46 GMT
status?
Comment by T. S. Collins (tscollins) - Tuesday, 04 March 2008, 17:21 GMT
So the memory leak was with audacious and some songs in my collection. I have been having problems with a Firewire hard drive so I tried some different distros to see if one could handle it better, now running openSUSE 10.3 (X86-64).
Comment by Greg (dolby) - Saturday, 10 May 2008, 16:48 GMT
should it be closed then?

Loading...