Re: [Qemu-devel] E5-2620v2 - emulation stop error

Kevin O'Connor
2015-03-26T17:07:20Z

On Thu, Mar 26, 2015 at 07:48:09PM +0300, Andrey Korolyov wrote:
> On Thu, Mar 26, 2015 at 7:36 PM, Kevin O'Connor <kevin@koconnor.net> wrote:
> > I'm not sure if the crash always happens at the "int $0x19" location
> > though. Andrey, does the crash always happen with "EIP=d331" and/or
> > with "Code=... <cd> 19"?
>
> There are also rare occurences for d3f9 (in the middle of ep) and d334
> ep (less than one tenth of events for both). I`ll post a sample event
> capture with and without Radim`s proposed patch maybe today or
> tomorrow.
>
> /root/seabios-1.8.1/src/romlayout.S:289
> d3eb: 66 50 pushl %eax
> d3ed: 66 51 pushl %ecx
> d3ef: 66 52 pushl %edx
> d3f1: 66 53 pushl %ebx
> d3f3: 66 55 pushl %ebp
> d3f5: 66 56 pushl %esi
> d3f7: 66 57 pushl %edi
> d3f9: 06 pushw %es
> d3fa: 1e pushw %ds
>
> 0000d334 <irq_trampoline_0x1c>:
> irq_trampoline_0x1c():
> /root/seabios-1.8.1/src/romlayout.S:196
> d334: cd 1c int $0x1c
> d336: cb lretw

Thanks. The d334 looks very similar to the d331 report (code=<cd>
1c). That path could happen during post (big real mode) or
immiediately after post (real mode).

The d3f9 report does not look like the others - interrupts are
disabled there. If you still have the error logs, can you post the
full kvm crash report for d3f9?

-Kevin