Re: [PATCH for 3.2.34] memcg: do not trigger OOM from add_to_page_cache_locked
From: azurIt <hidden>
Date: 2012-11-30 15:59:41
Also in:
linux-mm, lkml
Possibly related (same subject, not in this thread)
- 2013-02-08 · Re: [PATCH for 3.2.34] memcg: do not trigger OOM from add_to_page_cache_locked · Michal Hocko <hidden>
- 2013-02-08 · Re: [PATCH for 3.2.34] memcg: do not trigger OOM from add_to_page_cache_locked · Michal Hocko <hidden>
- 2013-02-08 · Re: [PATCH for 3.2.34] memcg: do not trigger OOM from add_to_page_cache_locked · Greg Thelen <hidden>
- 2013-02-05 · Re: [PATCH for 3.2.34] memcg: do not trigger OOM from add_to_page_cache_locked · Michal Hocko <hidden>
- 2013-02-05 · Re: [PATCH for 3.2.34] memcg: do not trigger OOM from add_to_page_cache_locked · Greg Thelen <hidden>
quoted
Here is the full boot log: www.watchdog.sk/lkml/kern.logThe log is not complete. Could you paste the comple dmesg output? Or even better, do you have logs from the previous run?
What is missing there? All kernel messages are logging into /var/log/kern.log (it's the same as dmesg), dmesg itself was already rewrited by other messages. I think it's all what that kernel printed.