qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] Re: [SeaBIOS] IO APIC emulation failure with qemu-kvm


From: Avi Kivity
Subject: [Qemu-devel] Re: [SeaBIOS] IO APIC emulation failure with qemu-kvm
Date: Mon, 07 Feb 2011 15:17:02 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.7

On 02/07/2011 12:28 PM, Ravi Kumar Kulkarni wrote:
On Mon, Feb 7, 2011 at 3:24 PM, Avi Kivity<address@hidden>  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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]