From: Avi Kivity <avi@qumranet.com>
To: Parag Warudkar <kernel-stuff@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS - KVM in 2.6.20-rc2
Date: Thu, 28 Dec 2006 11:36:08 +0200 [thread overview]
Message-ID: <45939008.106@qumranet.com> (raw)
In-Reply-To: <122820060049.5177.4593147E000B4D2C0000143922007621949D0E050B9A9D0E99@comcast.net>
Parag Warudkar wrote:
> Running qemu with 512M ram out of available 480M total invoked the OOM killer (that's obvious along with other OOM-killer stupidities like killing totally irrelevant processes) followed by the below OOPS.
>
> Killed process 19271 (trashapplet)Out of memory: kill process 12475 (qemu) score 7899 or a childOut of memory: kill process 12475 (qemu) score 7899 or a childKilled process 12475 (qemu)Killed process 12475 (qemu)
>
> BUG: unable to handle kernel NULL pointer dereference at virtual address 00000004 printing eip:c0153aa2*pde = 17339067*pte =
I've committed a fix for this, and will send it to Andrew shortly.
Thanks for the report.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2006-12-28 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 0:49 OOPS - KVM in 2.6.20-rc2 Parag Warudkar
2006-12-28 9:36 ` Avi Kivity [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45939008.106@qumranet.com \
--to=avi@qumranet.com \
--cc=kernel-stuff@comcast.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.