All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: David Brown <dmlb2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Oopse in kvm
Date: Wed, 18 Apr 2007 07:57:05 +0300	[thread overview]
Message-ID: <4625A521.6010407@qumranet.com> (raw)
In-Reply-To: <9c21eeae0704171348r71a62af8nc98bb018313ca35-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

David Brown wrote:
> I was wondering of anyone could help out on this, just found an oopse
> when trying to start rhel4 on i386 box. I was wondering if anyone else
> has seen this with kvm-18 and if I should submit a bug for it.
>
> [10937.520000] BUG: unable to handle kernel NULL pointer dereference
> [10937.521000] EIP: [<f9004eec>] mmu_page_remove_parent_pte+0xc/0xf0
> [kvm] SS:ESP 0068:c918fbbc
> [10937.521000]
>
>   


I've seen a few reports like this, but never managed to get one of my own.

Is this reproducible?  If so, a recipe would be _very_  valuable.

At what stage in the boot process does it crash?

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

  parent reply	other threads:[~2007-04-18  4:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-17 20:48 Oopse in kvm David Brown
     [not found] ` <9c21eeae0704171348r71a62af8nc98bb018313ca35-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-04-17 20:50   ` David Brown
2007-04-18  4:57   ` Avi Kivity [this message]
     [not found]     ` <4625A521.6010407-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-18  5:11       ` David Brown
2007-04-18  8:21       ` Avi Kivity
     [not found]         ` <4625D50A.3010005-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-18 14:18           ` Thomas Glanzmann
     [not found]             ` <20070418141819.GA13284-vCsBGSbFJi4XOLVLeuLo0p3xXOyapcuTYd9OGiuxSwg@public.gmane.org>
2007-04-18 14:30               ` Avi Kivity
     [not found]                 ` <46262BA3.8070307-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-18 14:35                   ` Thomas Glanzmann
     [not found]                     ` <20070418143548.GD13284-vCsBGSbFJi4XOLVLeuLo0p3xXOyapcuTYd9OGiuxSwg@public.gmane.org>
2007-04-18 14:42                       ` Avi Kivity
     [not found]                         ` <46262E3B.4010608-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-18 15:02                           ` David Brown
     [not found]                             ` <9c21eeae0704180802o492dc754p1eef426bc4408e0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-04-18 15:32                               ` Avi Kivity
     [not found]                                 ` <462639F1.4020802-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-04-18 17:07                                   ` David Brown
2007-04-18 15:07           ` Kiselev, Sergey

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=4625A521.6010407@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=dmlb2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.