From: Avi Kivity <avi@redhat.com>
To: Ravi Kumar Kulkarni <ravilinux4u@gmail.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
seabios@seabios.org, qemu-devel@nongnu.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: [Qemu-devel] Re: [SeaBIOS] IO APIC emulation failure with qemu-kvm
Date: Mon, 07 Feb 2011 15:17:02 +0200 [thread overview]
Message-ID: <4D4FF0CE.7000702@redhat.com> (raw)
In-Reply-To: <AANLkTi=Neds4Zm8sVE4k8yA_YQJ+TqMhTSRZEMKZcPhs@mail.gmail.com>
On 02/07/2011 12:28 PM, Ravi Kumar Kulkarni wrote:
> On Mon, Feb 7, 2011 at 3:24 PM, Avi Kivity<avi@redhat.com> wrote:
> > On 02/07/2011 11:47 AM, Ravi Kumar Kulkarni wrote:
> >>
> >> >
> >> > That is not the same address. And the code you posted doesn't make any
> >> > sense.
> >> >
> >> sorry for the mistake. here's the correct one
> >>
> >>
> >> (qemu) xp /20iw 0x1e2f3f7b
> >> 0x000000001e2f3f7b: (bad)
> >> 0x000000001e2f3f7c: std
> >> 0x000000001e2f3f7d: (bad)
> >> 0x000000001e2f3f7e: (bad)
> >
> > That looks like garbage. Are you sure you're disassembling the right code?
> >
> ok . Just to be clear i ran the command qemu-kvm once and i found
> got the crash report below which i have attached and in that eip is at
> 0x1e2f3f77
> and then
>
> (qemu) xp /20iw 0x1e2f3f77
> 0x000000001e2f3f77: pop %ds
> 0x000000001e2f3f78: inc %edx
> 0x000000001e2f3f79: loope 0x1e2f3fc8
> 0x000000001e2f3f7b: pop %ds
> 0x000000001e2f3f7c: jnp 0x1e2f3f5e
> 0x000000001e2f3f7e: dec %ebp
> 0x000000001e2f3f7f: pop %ds
> 0x000000001e2f3f80: xchg %eax,%esp
> 0x000000001e2f3f81: aas
> 0x000000001e2f3f82: das
This still doesn't look like real code. The problem was likely much
earlier and caused a branch into a data section.
Someone with a good understanding of your OS needs to examine the trace
and see what went wrong.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-02-07 13:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 13:35 [Qemu-devel] IO APIC emulation failure with qemu-kvm Ravi Kumar Kulkarni
2011-02-04 13:58 ` [Qemu-devel] " Jan Kiszka
2011-02-06 17:20 ` [Qemu-devel] Re: [SeaBIOS] " Avi Kivity
2011-02-07 8:33 ` Ravi Kumar Kulkarni
2011-02-07 8:49 ` Avi Kivity
2011-02-07 9:24 ` Ravi Kumar Kulkarni
2011-02-07 9:29 ` Avi Kivity
2011-02-07 9:47 ` Ravi Kumar Kulkarni
2011-02-07 9:54 ` Avi Kivity
2011-02-07 10:28 ` Ravi Kumar Kulkarni
2011-02-07 13:17 ` Avi Kivity [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=4D4FF0CE.7000702@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=ravilinux4u@gmail.com \
--cc=seabios@seabios.org \
--cc=virtualization@lists.linux-foundation.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).