From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 30402] Debian 4 fails to boot in KVM
Date: Tue, 20 May 2014 21:22:25 +0000 [thread overview]
Message-ID: <bug-30402-28872-icRPf4D9t0@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-30402-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=30402
--- Comment #3 from Joerg Roedel <joro@8bytes.org> ---
(In reply to Jidong Xiao from comment #2)
> Joerg, how do you know this?
>
> "Some investigation showed that this kernel uses MMX instructions to access
> MMIO regions. These instructions are not emulated by the instruction
> emulator and need to be added there."
AFAIR the stack-trace and instruction pointer of the crashing kernel pointed to
an MMX instruction and the kernel was trying to access an MMIO region.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2014-05-20 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 14:31 [Bug 30402] New: Debian 4 fails to boot in KVM bugzilla-daemon
2012-08-17 15:09 ` [Bug 30402] " bugzilla-daemon
2014-05-20 21:04 ` bugzilla-daemon
2014-05-20 21:22 ` bugzilla-daemon [this message]
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=bug-30402-28872-icRPf4D9t0@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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).