public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	KVM list <kvm@vger.kernel.org>
Subject: Re: openbsd system_powerdown: "KVM internal error. Suberror: 1"
Date: Mon, 21 Mar 2011 11:57:20 +0200	[thread overview]
Message-ID: <20110321095720.GM10151@redhat.com> (raw)
In-Reply-To: <4D871DC4.7000704@redhat.com>

On Mon, Mar 21, 2011 at 11:43:32AM +0200, Avi Kivity wrote:
> >47965.428797: kvm_mmio: mmio read len 4 gpa 0xbfff4 val 0x0
> >47965.428797: kvm_entry: vcpu 0
> >47965.428798: kvm_exit: reason npf rip 0xd020203c
> >47965.428798: kvm_page_fault: address bfff8 error_code 4
> >47965.428799: kvm_emulate_insn: 0:d020203c: 58 (prot32)
> 
> That's a POP instruction.  So openbsd mapped the stack into the
> framebuffer, and kvm has to emulate everything.
> 
IIRC openbsd had always have this problem with powerdown. Last time
I looked at it I found that when openbsd receives ACPI interrupt it
enters some kind of interrupt injection loop where with each received
interrupt stack grows a little bit. When stack starts to overlap with
frame buffer emulation error happens. May be something wrong with our MP
tables, but I couldn't figure what.

> Please post a complete binary trace from bootup until the
> host_state_reload issue appears.
> 
> >47965.428799: kvm_mmio: mmio unsatisfied-read len 4 gpa 0xbfff8 val 0x0
> >47965.428801: kvm_mmio: mmio read len 4 gpa 0xbfff8 val 0x30
> >47965.428801: kvm_entry: vcpu 0
> >47965.428802: kvm_exit: reason vintr rip 0xd0202041
> >47965.428802: kvm_inj_virq: irq 81
> >47965.428802: kvm_inj_virq: irq 81
> >47965.428803: kvm_entry: vcpu 0
> >47965.428803: kvm_exit: reason npf rip 0xd0202041
> >47965.428804: kvm_page_fault: address bfffc error_code 6
> >47965.428804: kvm_emulate_insn: 0:d0202041: cf (prot32)
> >47965.428805: kvm_emulate_insn: 0:d0202041: cf (prot32) failed
> 
> We don't emulate IRET-with-mmio-stack.
> 

--
			Gleb.

  reply	other threads:[~2011-03-21  9:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 11:54 openbsd system_powerdown: "KVM internal error. Suberror: 1" Michael Tokarev
2011-03-16 19:44 ` Marcelo Tosatti
2011-03-16 20:09   ` Michael Tokarev
2011-03-17 17:52     ` Marcelo Tosatti
2011-03-17 20:18       ` Michael Tokarev
2011-03-21  9:43         ` Avi Kivity
2011-03-21  9:57           ` Gleb Natapov [this message]
2011-03-21 10:12           ` Michael Tokarev
2011-03-21 10:28             ` Avi Kivity
2011-03-21 10:41               ` Gleb Natapov
2011-03-21 10:47                 ` Avi Kivity
2011-03-21 10:49                   ` Gleb Natapov

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=20110321095720.GM10151@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=mtosatti@redhat.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