public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Tobias Diedrich <ranma+kernel@tdiedrich.de>,
	Chris Wright <chrisw@sous-sol.org>, Avi Kivity <avi@qumranet.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: kvm: unable to handle kernel NULL pointer dereference
Date: Thu, 5 Jun 2008 00:27:28 -0700	[thread overview]
Message-ID: <20080605072728.GF30402@sequoia.sous-sol.org> (raw)
In-Reply-To: <20080605060931.GA11704@yamamaya.is-a-geek.org>

* Tobias Diedrich (ranma+kernel@tdiedrich.de) wrote:
> Almost:
> ranma@melchior:~/src/linux-2.6.26-rc4.forcedwol$ gdb -q vmlinux
> Using host libthread_db library "/lib/libthread_db.so.1".
> (gdb)  p/x 0xffffffff8021d456 + 0x6f9cba
> $1 = 0xffffffff80917110
> (gdb) p/x &per_cpu__svm_data
> $2 = 0xffffffff809170f8
> (gdb) 

Sorry, my math was bad.  I gave you 0xffffffff8021d44f + 7 + 0x6f9cba,
but it should have been 0xffffffff8021d44f - 17 + 0x6f9cba.  Which is
correct (as one would hope, it was a grasp at straws).

Oh, wait.  Is this a laptop?  Do you suspend/resume?  Suspend will free
svm_data, and on resume, any launching a guest will definitely hit the
oops you are seeing.

Do you ever see this in dmesg?

  svm_cpu_init: svm_data is NULL on 0

thanks,
chris

  reply	other threads:[~2008-06-05  7:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-01  8:48 kvm: unable to handle kernel NULL pointer dereference Tobias Diedrich
2008-06-04 10:41 ` Avi Kivity
2008-06-04 18:10   ` Tobias Diedrich
2008-06-05  4:25     ` Chris Wright
2008-06-05  6:09       ` Tobias Diedrich
2008-06-05  7:27         ` Chris Wright [this message]
2008-06-05 18:28           ` Tobias Diedrich
2008-06-05 18:34             ` Chris Wright
2008-06-29 18:02               ` Tobias Diedrich
2008-06-29 18:28                 ` [PATCH] " Tobias Diedrich

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=20080605072728.GF30402@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=avi@qumranet.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ranma+kernel@tdiedrich.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox