public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alec Joseph Rivera <eijhei@gmail.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Alexander Graf <agraf@suse.de>,
	kvm@vger.kernel.org, Meric Mara <mmara@8layertech.com>,
	Renan Mara <rmara@8layertech.com>
Subject: Re: 2.6.16 Guest Hangs on Boot
Date: Thu, 16 Sep 2010 19:11:17 +0800	[thread overview]
Message-ID: <1284635477.7482.223.camel@nami.8liens.com> (raw)
In-Reply-To: <20100916110247.GA15338@8bytes.org>

On Thu, 2010-09-16 at 13:02 +0200, Joerg Roedel wrote:
> On Thu, Sep 16, 2010 at 12:27:29PM +0200, Alexander Graf wrote:
> > Alec Joseph Rivera wrote:
> > > Program received signal SIGINT, Interrupt.
> > > 0xc015405f in ?? ()
> > > (gdb) bt
> > > #0  0xc015405f in ?? ()
> > >   
> > 
> > 0xc015405a <__pte_alloc_kernel+82>:    mov    (%edi),%eax
> > 0xc015405c <__pte_alloc_kernel+84>:    mov    0x4(%edi),%edx
> > 0xc015405f <__pte_alloc_kernel+87>:    lock cmpxchg8b (%edi)
> > 0xc0154063 <__pte_alloc_kernel+91>:    jne    0xc015405a
> > <__pte_alloc_kernel+82>
> 
> This looks like a bug I also have seen recently on 32 bit host-kvm. The
> instruction emulation for 'lock cmpxchg8b' was broken so that the rip
> was not advanced and the guest just iterated over this instruction again
> and again. I thought this was fixed with the latest kvm updates in
> 2.6.36.
> 

Will wait for a 2.6.36 kernel then or compile a .36-rc myself on free
time :-)

Thanks, will update the list when either comes.

> 	Joerg
> 


-- 
--- 


Follow me: 
http://twitter.com/agirivera
Invite as a
friend: 
http://www.facebook.com/agirivera




  reply	other threads:[~2010-09-16 11:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 16:53 2.6.16 Guest Hangs on Boot Alec Joseph Rivera
2010-09-15 17:28 ` Alexander Graf
2010-09-15 17:48   ` Alec Joseph Rivera
2010-09-15 17:51     ` Alexander Graf
2010-09-15 18:07       ` Alec Joseph Rivera
2010-09-15 18:15         ` Alexander Graf
2010-09-15 18:26           ` Alec Joseph Rivera
2010-09-16  1:55           ` Alec Joseph Rivera
2010-09-16  6:39             ` Gleb Natapov
2010-09-16  7:52               ` Alec Joseph Rivera
2010-09-16  7:56                 ` Gleb Natapov
2010-09-16  8:03                   ` Alec Joseph Rivera
2010-09-16 10:11                     ` Alec Joseph Rivera
2010-09-16 10:14                       ` Gleb Natapov
2010-09-16 11:13                         ` Alec Joseph Rivera
2010-09-16 11:18                           ` Gleb Natapov
2010-09-16 10:27             ` Alexander Graf
2010-09-16 11:02               ` Joerg Roedel
2010-09-16 11:11                 ` Alec Joseph Rivera [this message]
2010-09-16 11:32                   ` Joerg Roedel
2010-09-16 11:35                     ` Michael Tokarev
2010-09-16 11:41                       ` Gleb Natapov
2010-09-16 11:43                       ` Joerg Roedel
2010-09-16 11:37                     ` Alec Joseph Rivera
2010-09-16 11:41                       ` Gleb Natapov
2010-09-16 11:51                         ` Alec Joseph Rivera
2010-09-15 18:37         ` Michael Tokarev
2010-09-16  8:17           ` Alec Joseph Rivera
2010-09-16  8:32             ` Dave Young
2010-09-16  9:56               ` Alec Joseph Rivera

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=1284635477.7482.223.camel@nami.8liens.com \
    --to=eijhei@gmail.com \
    --cc=agraf@suse.de \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=mmara@8layertech.com \
    --cc=rmara@8layertech.com \
    /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