From: Andreas Bollhalder <bolle@geodb.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU freeze with "Servicing hardware INT=0x08"
Date: Wed, 08 Feb 2006 19:33:16 -0000 [thread overview]
Message-ID: <43EA4684.7030302@geodb.org> (raw)
In-Reply-To: <42E64B9C.8080202@geodb.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello
I'm using QEMU 0.8.0 CVS under Windows. In the x86 version, one of my
DOS application freezes QEMU amd I have to close it.
I enabled the debugging with "-d in_asm,op_opt". At the end of the log
file, I have over 1770 times the entry stating that QEMU is serving Int
0x08.
Is this because the DOS application is poorly written or could this be a
problem of QEMU ?
What debug options are the best to use in my case ?
Thanks for your opinions.
Andreas
- ----------------
IN:
0x0000cd0a: repnz scas %es:(%di),%ax
AFTER FLAGS OPT:
0x0000: jnz_ecxw 0x0
0x0001: goto_tb1 0x174b6e0
0x0002: movl_eip_im 0xdbc
0x0003: movl_T0_im 0x174b6e1
0x0004: exit_tb
0x0005: movl_T0_EAX
0x0006: movl_A0_EDI
0x0007: andl_A0_ffff
0x0008: addl_A0_seg 0x40
0x0009: lduw_user_T1_A0
0x000a: cmpl_T0_T1_cc
0x000b: movl_T0_Dshiftw
0x000c: addw_EDI_T0
0x000d: decw_ECX
0x000e: set_cc_op 0xf
0x000f: jz_subw 0x1
0x0010: goto_tb0 0x174b6e0
0x0011: movl_eip_im 0xdba
0x0012: movl_T0_im 0x174b6e0
0x0013: exit_tb
0x0014: end
- ----------------
IN:
0x0000cd0c: jne 0xcd8b
AFTER FLAGS OPT:
0x0000: setz_T0_cc
0x0001: jnz_T0_label 0x0
0x0002: goto_tb0 0x174b720
0x0003: movl_eip_im 0xe3b
0x0004: movl_T0_im 0x174b720
0x0005: exit_tb
0x0006: goto_tb1 0x174b720
0x0007: movl_eip_im 0xdbe
0x0008: movl_T0_im 0x174b721
0x0009: exit_tb
0x000a: end
- ----------------
IN:
0x0000cd8b: addw $0x1,1114
0x0000cd90: adcw $0x0,1116
0x0000cd95: jmp 0xccd6
AFTER FLAGS OPT:
0x0000: movl_A0_im 0x45a
0x0001: addl_A0_seg 0x70
0x0002: movl_T1_im 0x1
0x0003: lduw_user_T0_A0
0x0004: addl_T0_T1
0x0005: stw_user_T0_A0
0x0006: update2_cc
0x0007: movl_A0_im 0x45c
0x0008: addl_A0_seg 0x70
0x0009: movl_T1_im 0x0
0x000a: lduw_user_T0_A0
0x000b: set_cc_op 0x7
0x000c: adcw_user_T0_T1_cc
0x000d: goto_tb0 0x174b760
0x000e: movl_eip_im 0xd86
0x000f: movl_T0_im 0x174b760
0x0010: exit_tb
0x0011: end
- ----------------
IN:
0x0000ccd6: mov $0x8001,%ax
0x0000ccd9: or %ax,%ax
0x0000ccdb: jmp 0xcd6c
AFTER FLAGS OPT:
0x0000: movl_T0_im 0x8001
0x0001: movw_EAX_T0
0x0002: movl_T1_EAX
0x0003: movl_T0_EAX
0x0004: orl_T0_T1
0x0005: movw_EAX_T0
0x0006: update1_cc
0x0007: set_cc_op 0x17
0x0008: goto_tb0 0x174b7a0
0x0009: movl_eip_im 0xe1c
0x000a: movl_T0_im 0x174b7a0
0x000b: exit_tb
0x000c: end
- ----------------
IN:
0x0000cd6c: pop %di
0x0000cd6d: mov %dx,%ds
0x0000cd6f: lret
AFTER FLAGS OPT:
0x0000: movl_A0_ESP
0x0001: andl_A0_ffff
0x0002: addl_A0_SS
0x0003: lduw_user_T0_A0
0x0004: addw_ESP_2
0x0005: movw_EDI_T0
0x0006: movl_T0_EDX
0x0007: movl_seg_T0_vm 0x6c
0x0008: movl_A0_ESP
0x0009: andl_A0_ffff
0x000a: movl_T1_A0
0x000b: addl_A0_seg 0x60
0x000c: lduw_user_T0_A0
0x000d: andl_T0_ffff
0x000e: jmp_T0
0x000f: addl_A0_im 0x2
0x0010: lduw_user_T0_A0
0x0011: movl_seg_T0_vm 0x4c
0x0012: addw_ESP_4
0x0013: movl_T0_0
0x0014: exit_tb
0x0015: end
- ----------------
IN:
0x00008c02: jne 0x8c09
AFTER FLAGS OPT:
0x0000: setz_T0_cc
0x0001: jnz_T0_label 0x0
0x0002: goto_tb0 0x174b820
0x0003: movl_eip_im 0x399
0x0004: movl_T0_im 0x174b820
0x0005: exit_tb
0x0006: goto_tb1 0x174b820
0x0007: movl_eip_im 0x394
0x0008: movl_T0_im 0x174b821
0x0009: exit_tb
0x000a: end
- ----------------
IN:
0x00008c09: pop %bx
0x00008c0a: jmp 0x8c13
AFTER FLAGS OPT:
0x0000: movl_A0_ESP
0x0001: andl_A0_ffff
0x0002: addl_A0_SS
0x0003: lduw_user_T0_A0
0x0004: addw_ESP_2
0x0005: movw_EBX_T0
0x0006: goto_tb0 0x174b860
0x0007: movl_eip_im 0x3a3
0x0008: movl_T0_im 0x174b860
0x0009: exit_tb
0x000a: end
Servicing hardware INT=0x08
... 1770 times repeated
Servicing hardware INT=0x08
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFD6kaEkyKr2gmercERAlv/AKCS6Yt0Zvd/amFAYkYvv2jK91DXrACfd0rv
V0CkkLrB4vxWstfeZ9q/lgY=
=juM5
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-02-08 19:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 17:11 [Qemu-devel] qemu/slirp bootp.c bootp.h ip_icmp.h libslirp.h Fabrice Bellard
2005-06-05 18:00 ` Andreas Bollhalder
2005-06-06 1:02 ` [Qemu-devel] " Ronald
2005-06-07 16:48 ` Andreas Bollhalder
2005-07-19 18:00 ` [Qemu-devel] Writing to ROM-Range 0xC800-EFFF Andreas Bollhalder
2005-07-25 15:39 ` Jim C. Brown
2005-07-26 14:41 ` Andreas Bollhalder
2006-02-08 19:33 ` Andreas Bollhalder [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=43EA4684.7030302@geodb.org \
--to=bolle@geodb.org \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.