linux-kernel - Re: [Scst-devel] BUG: Process hang when kvm crashed, stacktrace cfs+kvm

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAO+b5-qsdn8i_BdAqJo_6CU3Lh6JTPSSsyg-m_bP+xcN5aBgxg@mail.gmail.com>
Date:	Sat, 21 Jan 2012 16:11:00 +0000
From:	Bart Van Assche <bvanassche@....org>
To:	kordex <kordex@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, mingo@...e.hu,
	peterz@...radead.org, kvm@...r.kernel.org, avi@...hat.com,
	scst-devel <scst-devel@...ts.sourceforge.net>
Subject: Re: [Scst-devel] BUG: Process hang when kvm crashed, stacktrace cfs+kvm

On Sat, Jan 21, 2012 at 2:58 PM, kordex <kordex@...il.com> wrote:
> On Thu, Jan 19, 2012 at 21:12, kordex <kordex@...il.com> wrote:
> > On Thu, Jan 19, 2012 at 20:34, kordex <kordex@...il.com> wrote:
> >> Full dmesg of the case attached.
> >> On Thu, Jan 19, 2012 at 13:12, Bart Van Assche <bvanassche@....org> wrote:
> >>> On Thu, Jan 19, 2012 at 11:54 AM, kordex <kordex@...il.com> wrote:
> >>>> > root@...etex:/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 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/