kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: habanero@linux.vnet.ibm.com
Cc: kvm@vger.kernel.org
Subject: Re: kernel bug in kvm_intel
Date: Tue, 13 Oct 2009 08:50:07 +0200	[thread overview]
Message-ID: <4AD4231F.6040608@redhat.com> (raw)
In-Reply-To: <1255372957.4883.49.camel@twinturbo.austin.ibm.com>

On 10/12/2009 08:42 PM, Andrew Theurer wrote:
> On Sun, 2009-10-11 at 07:19 +0200, Avi Kivity wrote:
>    
>> On 10/09/2009 10:04 PM, Andrew Theurer wrote:
>>      
>>> This is on latest master branch on kvm.git and qemu-kvm.git, running
>>> 12 Windows Server2008 VMs, and using oprofile.  I ran again without
>>> oprofile and did not get the BUG.  I am wondering if anyone else is
>>> seeing this.
>>>
>>> Thanks,
>>>
>>> -Andrew
>>>
>>>        
>>>> Oct  9 11:55:13 virtvictory-eth0 kernel: BUG: unable to handle kernel
>>>> paging request at ffffffff9fe9a2b4
>>>> Oct  9 11:55:13 virtvictory-eth0 kernel: IP: [<ffffffffa02e1af1>]
>>>> vmx_vcpu_run+0x26d/0x64f [kvm_intel]
>>>>          
>> Can you run this through objdump or gdb to see what source this
>> corresponds to?
>>
>>      
> Somewhere here I think (?)
>
> objdump -d
>    


Look at the address where vmx_vcpu_run starts, add 0x26d, and show the 
surrounding code.

Thinking about it, it probably _is_ what you showed, due to module page 
alignment.  But please verify this; I can't reconcile the fault address 
(ffffffff9fe9a2b) with %rsp at the time of the fault.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2009-10-13  6:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09 20:04 kernel bug in kvm_intel Andrew Theurer
2009-10-11  5:19 ` Avi Kivity
2009-10-12 18:42   ` Andrew Theurer
2009-10-13  6:50     ` Avi Kivity [this message]
2009-10-13 14:04       ` Andrew Theurer
2009-10-14 17:10         ` Avi Kivity
2009-10-15 20:18           ` Andrew Theurer
2009-10-30 18:07             ` Andrew Theurer
2009-10-31 15:47               ` Avi Kivity
2009-10-31 16:25                 ` Andrew Theurer
2009-10-31 16:32                   ` Avi Kivity
2009-10-31 16:38                     ` Avi Kivity
2009-11-01 10:00                       ` Tejun Heo
2009-11-01 10:20                         ` Avi Kivity
2009-11-01 10:45                           ` Tejun Heo
2009-11-01 11:31                             ` Avi Kivity
2009-11-18  9:26                               ` Tejun Heo
2009-11-26  1:35                                 ` Andrew Theurer
2009-11-26  1:41                                   ` Tejun Heo
2009-11-26 10:31                                   ` Avi Kivity
2009-11-26 13:47                                     ` Andrew Theurer
2009-11-29 14:46                                   ` Avi Kivity
2009-11-30 16:27                                     ` Andrew Theurer
2009-10-13 14:31       ` Marcelo Tosatti

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=4AD4231F.6040608@redhat.com \
    --to=avi@redhat.com \
    --cc=habanero@linux.vnet.ibm.com \
    --cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).