| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <40a4ed590904241124m2f5eb1e9gb6b43a4012fcda36@mail.gmail.com> Date: Fri, 24 Apr 2009 20:24:08 +0200 From: Zeno Davatz <zdavatz@...il.com> To: David Rientjes <rientjes@...gle.com>, linux-kernel@...r.kernel.org Cc: Hannes Wyss <hwyss@...see.com> Subject: Re: Kernel 2.6.29 runs out of memory and hangs. On Fri, Apr 24, 2009 at 7:17 PM, David Rientjes <rientjes@...gle.com> wrote: > On Fri, 24 Apr 2009, Zeno Davatz wrote: > >> Dear All >> >> Our Kernel-Version: >> >> Linux thinpower 2.6.29 #5 SMP Sun Apr 5 20:04:08 UTC 2009 x86_64 >> Intel(R) Xeon(R) CPU E5450 @ 3.00GHz GenuineIntel GNU/Linux >> >> This morning our Server ran out of memory and had to be hard rebooted. >> The system hast 32 GB or memory and 4 QuadCore Xeon CPUs. >> /var/log/kernel/current tells us the following: >> >> Apr 24 09:01:06 thinpower [1349923.491914] postgres invoked >> oom-killer: gfp_mask=0x1201d2, order=0, oomkilladj=0 >> Apr 24 09:01:06 thinpower [1349923.491919] postgres cpuset=/ mems_allowed=0 >> Apr 24 09:01:06 thinpower [1349923.491922] Pid: 2393, comm: postgres >> Not tainted 2.6.29 #5 >> Apr 24 09:01:06 thinpower [1349923.491924] Call Trace: >> Apr 24 09:01:06 thinpower [1349923.491934] [<ffffffff8106eda9>] ? >> cpuset_print_task_mems_allowed+0x99/0x9f >> Apr 24 09:01:06 thinpower [1349923.491939] [<ffffffff81083d28>] >> oom_kill_process+0x96/0x246 >> Apr 24 09:01:06 thinpower [1349923.491942] [<ffffffff8106dcf0>] ? >> cpuset_mems_allowed_intersects+0x1c/0x1e >> Apr 24 09:01:06 thinpower [1349923.491944] [<ffffffff810840a5>] ? >> badness+0x1a3/0x1e6 >> Apr 24 09:01:06 thinpower [1349923.491946] [<ffffffff8108421c>] >> __out_of_memory+0x134/0x14b >> Apr 24 09:01:06 thinpower [1349923.491949] [<ffffffff8108438b>] >> out_of_memory+0x158/0x18a >> Apr 24 09:01:06 thinpower [1349923.491951] [<ffffffff81087906>] >> __alloc_pages_internal+0x372/0x434 >> Apr 24 09:01:06 thinpower [1349923.491954] [<ffffffff810aa490>] >> alloc_pages_current+0xb9/0xc2 >> Apr 24 09:01:06 thinpower [1349923.491957] [<ffffffff81081a59>] >> __page_cache_alloc+0x67/0x6b >> Apr 24 09:01:06 thinpower [1349923.491959] [<ffffffff81089426>] >> __do_page_cache_readahead+0x96/0x192 >> Apr 24 09:01:06 thinpower [1349923.491961] [<ffffffff81089575>] >> do_page_cache_readahead+0x53/0x60 >> Apr 24 09:01:06 thinpower [1349923.491963] [<ffffffff81081ec7>] >> filemap_fault+0x15e/0x313 >> Apr 24 09:01:06 thinpower [1349923.491967] [<ffffffff81094451>] >> __do_fault+0x53/0x393 >> Apr 24 09:01:06 thinpower [1349923.491969] [<ffffffff81030531>] ? >> __wake_up_sync+0x45/0x4e >> Apr 24 09:01:06 thinpower [1349923.491972] [<ffffffff81096702>] >> handle_mm_fault+0x36b/0x854 >> Apr 24 09:01:06 thinpower [1349923.491976] [<ffffffff813a1acb>] ? >> release_sock+0xb0/0xbb >> Apr 24 09:01:06 thinpower [1349923.491979] [<ffffffff81022c8f>] ? >> default_spin_lock_flags+0x9/0xe >> Apr 24 09:01:06 thinpower [1349923.491984] [<ffffffff814ac6fe>] >> do_page_fault+0x662/0xa5c >> Apr 24 09:01:06 thinpower [1349923.491988] [<ffffffff81400b8e>] ? >> inet_sendmsg+0x46/0x53 >> Apr 24 09:01:06 thinpower [1349923.491992] [<ffffffff8139ed97>] ? >> __sock_sendmsg+0x59/0x62 >> Apr 24 09:01:06 thinpower [1349923.491994] [<ffffffff8139f6d8>] ? >> sock_sendmsg+0xc7/0xe0 >> Apr 24 09:01:06 thinpower [1349923.491996] [<ffffffff81086b5e>] ? >> free_pages+0x32/0x36 >> Apr 24 09:01:06 thinpower [1349923.492000] [<ffffffff8104e7ec>] ? >> autoremove_wake_function+0x0/0x38 >> Apr 24 09:01:06 thinpower [1349923.492004] [<ffffffff810c1d76>] ? >> core_sys_select+0x1df/0x213 >> Apr 24 09:01:06 thinpower [1349923.492007] [<ffffffff810b2cc2>] ? >> nameidata_to_filp+0x41/0x52 >> Apr 24 09:01:06 thinpower [1349923.492009] [<ffffffff8139f028>] ? >> sockfd_lookup_light+0x1b/0x54 >> Apr 24 09:01:06 thinpower [1349923.492013] [<ffffffff81011ac8>] ? >> read_tsc+0xe/0x24 >> Apr 24 09:01:06 thinpower [1349923.492017] [<ffffffff81055990>] ? >> getnstimeofday+0x58/0xb4 >> Apr 24 09:01:06 thinpower [1349923.492019] [<ffffffff810516ed>] ? >> ktime_get_ts+0x49/0x4e >> Apr 24 09:01:06 thinpower [1349923.492022] [<ffffffff810c0d35>] ? >> poll_select_copy_remaining+0xc5/0xea >> Apr 24 09:01:06 thinpower [1349923.492023] [<ffffffff810c1ff3>] ? >> sys_select+0xa7/0xbc >> Apr 24 09:01:06 thinpower [1349923.492026] [<ffffffff814aa305>] >> page_fault+0x25/0x30 >> > > Are these the last messages in the dmesg? There should be subsequent > information that describes the current state of memory following the stack > trace. > > If this is reproducible, I'd recommend enabling > /proc/sys/vm/oom_dump_tasks so that the oom killer will dump the tasklist > and show us what may be causing the livelock. Ok, I believe I enabled it with echo 1 > /proc/sys/vm/oom_dump_tasks Where would I find the output if it livelocks again? Thank you for your Feedback. Best Zeno -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists