On Sat, Jan 21, 2012 at 2:58 PM, kordex <[email protected]> wrote: > On Thu, Jan 19, 2012 at 21:12, kordex <[email protected]> wrote: > > On Thu, Jan 19, 2012 at 20:34, kordex <[email protected]> wrote: > >> Full dmesg of the case attached. > >> On Thu, Jan 19, 2012 at 13:12, Bart Van Assche <[email protected]> wrote: > >>> On Thu, Jan 19, 2012 at 11:54 AM, kordex <[email protected]> wrote: > >>>> > root@teletex:/usr/src/linux# dmesg > >>>> > +0x12e7/0x1c50 > >>>> > [<ffffffff810dc322>] ? page_add_new_anon_rmap+0x52/0xa0 > >>> > >>> The above output is truncated - the most interesting part is missing. > > Do I need to give you anything else? Any leads on what the problem > might be? The machine is still running and in this state.
In the /proc/meminfo output I see that the system has 16 GB RAM and 33 GB swap memory. Also, MemFree + Buffers = 400 KB, which makes me assume the system was under heavy memory pressure ? Some essential information is still missing - the reason why the kernel started spewing out all these call traces. Did someone hit the SysRq key ? Is it because a task was hanging ? Was a BUG or WARNING hit ? Bart. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
