System became frozen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Seems that there's a bug in kernel related to working with memory, especially to decide when to run oom-killer.
One morning I found my system frozen with he following in logs after reboot:
May 12 07:51:41 big -- MARK --
May 12 08:00:37 big kernel: [233387.108621] type=1503 audit(124210083
May 12 08:00:37 big kernel: [233387.108630] type=1503 audit(124210083
May 12 08:00:37 big kernel: [233387.108636] type=1503 audit(124210083
May 12 08:00:37 big kernel: [233387.108652] type=1503 audit(124210083
May 12 08:00:37 big kernel: [233387.108657] type=1503 audit(124210083
May 12 08:00:37 big kernel: [233387.108663] type=1503 audit(124210083
May 12 08:00:37 big kernel: [233387.108843] rhythmbox invoked oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0
May 12 08:00:37 big kernel: [233387.108848] Pid: 11357, comm: rhythmbox Tainted: P 2.6.28-12-generic #43-Ubuntu
May 12 08:00:37 big kernel: [233387.108851] Call Trace:
May 12 08:00:37 big kernel: [233387.108862] [<c04fca36>] ? printk+0x18/0x1a
May 12 08:00:37 big kernel: [233387.108868] [<c0191525>] oom_kill_
May 12 08:00:37 big kernel: [233387.108872] [<c0191c03>] ? select_
May 12 08:00:37 big kernel: [233387.108877] [<c0191ce2>] out_of_
May 12 08:00:37 big kernel: [233387.108881] [<c0194350>] __alloc_
May 12 08:00:37 big kernel: [233387.108886] [<c0196c52>] __do_page_
May 12 08:00:37 big kernel: [233387.108890] [<c0196d9b>] do_page_
May 12 08:00:37 big kernel: [233387.108894] [<c018fd78>] filemap_
May 12 08:00:37 big kernel: [233387.108899] [<c01a0f1b>] __do_fault+
May 12 08:00:37 big kernel: [233387.108904] [<c04272fd>] ? skb_dequeue+
May 12 08:00:37 big kernel: [233387.108909] [<c01a1e39>] handle_
May 12 08:00:37 big kernel: [233387.108915] [<c012ad96>] ? dequeue_
May 12 08:00:37 big kernel: [233387.108919] [<c050118d>] do_page_
May 12 08:00:37 big kernel: [233387.108924] [<c0102ab7>] ? __switch_
May 12 08:00:37 big kernel: [233387.108929] [<c0122d58>] ? default_
May 12 08:00:37 big kernel: [233387.108934] [<c04feb7e>] ? _spin_lock_
May 12 08:00:37 big kernel: [233387.108939] [<c0152a0a>] ? hrtimer_
May 12 08:00:37 big kernel: [233387.108943] [<c0152a71>] ? hrtimer_
May 12 08:00:37 big kernel: [233387.108947] [<c04fded9>] ? do_nanosleep+
May 12 08:00:37 big kernel: [233387.108951] [<c0153083>] ? hrtimer_
May 12 08:00:37 big kernel: [233387.108955] [<c0152440>] ? hrtimer_
May 12 08:00:37 big kernel: [233387.108959] [<c04fdebf>] ? do_nanosleep+
May 12 08:00:37 big kernel: [233387.108963] [<c0153170>] ? sys_nanosleep+
May 12 08:00:37 big kernel: [233387.108966] [<c0500f90>] ? do_page_
May 12 08:00:37 big kernel: [233387.108970] [<c04feff2>] error_code+
May 12 08:00:37 big kernel: [233387.108973] Mem-Info:
May 12 08:00:37 big kernel: [233387.108975] DMA per-cpu:
May 12 08:00:37 big kernel: [233387.108978] CPU 0: hi: 0, btch: 1 usd: 0
May 12 08:00:37 big kernel: [233387.108981] CPU 1: hi: 0, btch: 1 usd: 0
May 12 08:00:37 big kernel: [233387.108983] Normal per-cpu:
May 12 08:00:37 big kernel: [233387.108985] CPU 0: hi: 186, btch: 31 usd: 64
May 12 08:00:37 big kernel: [233387.108988] CPU 1: hi: 186, btch: 31 usd: 111
May 12 08:00:37 big kernel: [233387.108990] HighMem per-cpu:
May 12 08:00:37 big kernel: [233387.108992] CPU 0: hi: 186, btch: 31 usd: 55
May 12 08:00:37 big kernel: [233387.108995] CPU 1: hi: 186, btch: 31 usd: 61
May 12 08:00:37 big kernel: [233387.109000] Active_anon:308247 active_file:643 inactive_
May 12 08:00:37 big kernel: [233387.109001] inactive_file:3442 unevictable:2 dirty:4 writeback:0 unstable:0
May 12 08:00:37 big kernel: [233387.109002] free:12464 slab:8574 mapped:6798 pagetables:1932 bounce:0
May 12 08:00:37 big kernel: [233387.109007] DMA free:8124kB min:64kB low:80kB high:96kB active_anon:256kB inactive_anon:324kB active_file:0kB inactive_file:4kB unevictable:0kB present:15804kB pages_scanned:916 all_unreclaimable? yes
May 12 08:00:37 big kernel: [233387.109011] lowmem_reserve[]: 0 861 2015 2015
May 12 08:00:37 big kernel: [233387.109020] Normal free:41256kB min:3720kB low:4648kB high:5580kB active_
ll_unreclaimable? yes
May 12 08:00:37 big kernel: [233387.109023] lowmem_reserve[]: 0 0 9235 9235
May 12 08:00:37 big kernel: [233387.109032] HighMem free:476kB min:512kB low:1756kB high:3004kB active_
all_unreclaimable? yes
May 12 08:00:37 big kernel: [233387.109035] lowmem_reserve[]: 0 0 0 0
May 12 08:00:37 big kernel: [233387.109041] DMA: 5*4kB 5*8kB 6*16kB 5*32kB 6*64kB 6*128kB 6*256kB 6*512kB 2*1024kB 0*2048kB 0*4096kB = 8124kB
May 12 08:00:37 big kernel: [233387.109054] Normal: 1096*4kB 565*8kB 1692*16kB 45*32kB 8*64kB 4*128kB 3*256kB 0*512kB 0*1024kB 1*2048kB 0*4096kB = 41256kB
May 12 08:00:37 big kernel: [233387.109066] HighMem: 15*4kB 8*8kB 0*16kB 1*32kB 3*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 476kB
May 12 08:00:37 big kernel: [233387.109079] 4288 total pagecache pages
May 12 08:00:37 big kernel: [233387.109081] 1 pages in swap cache
May 12 08:00:37 big kernel: [233387.109084] Swap cache stats: add 1077658, delete 1077657, find 268689/329272
May 12 08:00:37 big kernel: [233387.109087] Free swap = 0kB
May 12 08:00:37 big kernel: [233387.109089] Total swap = 2000052kB
May 12 08:00:37 big kernel: [233387.114904] 524144 pages RAM
May 12 08:00:37 big kernel: [233387.114907] 297858 pages HighMem
May 12 08:00:37 big kernel: [233387.114909] 8794 pages reserved
May 12 08:00:37 big kernel: [233387.114911] 14931 pages shared
May 12 08:00:37 big kernel: [233387.114913] 494101 pages non-shared
May 12 10:25:21 big syslogd 1.5.0#5ubuntu3: restart.
Before submitting this bug, I searched the net about it and found this problem is common:
http://
https:/
https:/
http://
I have 2 GiGs physical memory and 2 GiGs swap space, and I just don't believe that all this memry got used so that oom-killer should be invoked.
ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=
MachineType: System manufacturer System Product Name
NonfreeKernelMo
Package: linux-image-
ProcCmdLine: root=UUID=
ProcEnviron:
PATH=(custom, user)
LANG=ru_RU.UTF-8
SHELL=/bin/zsh
ProcVersionSign
SourcePackage: linux
Hi Black,
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? Can you try with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, could you run the following command from a Terminal (Applications- >Accessories- >Terminal) . It will automatically gather and attach updated debug information to this report.
apport-collect -p linux 377267
Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Once you've tested the upstream kernel, please remove the 'needs- upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs- upstream- testing' text. Please let us know your results.
Thanks in advance.
[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]