[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1050694] Re: Interrupt 0xffffffff when debug is turned
From: |
Adam Clark |
Subject: |
[Qemu-devel] [Bug 1050694] Re: Interrupt 0xffffffff when debug is turned on |
Date: |
Fri, 14 Sep 2012 01:04:48 -0000 |
** Attachment added: "Test case for bug..."
https://bugs.launchpad.net/bugs/1050694/+attachment/3313662/+files/harddisk.img
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1050694
Title:
Interrupt 0xffffffff when debug is turned on
Status in QEMU:
New
Bug description:
Hi,
I have been getting a GPF when I enable interrupts, working on
implementing processes and a scheduler. When I comment out the
scheduler code, I still get the GPF. I used the following QEMU command
line to capture a log:
qemu-system-i386 -smp 4 -monitor stdio -cpu core2duo -D
/home/adam/century/util/qemu.log -d int,in_asm -s -hda
"$harddisk_image" -m 3.5G
Rather than posting the entire log, I need some help interpreting the
following section (notice "INT=0xffffffff" on the top line):
Servicing hardware INT=0xffffffff
1: v=ffffffff e=0000 i=0 cpl=0 IP=0008:0010b63f pc=0010b63f SP=0010:0012b768
EAX=00000000
EAX=00000000 EBX=00002000 ECX=00000018 EDX=05a00780
ESI=00112faa EDI=000b8fa0 EBP=0012b780 ESP=0012b768
EIP=0010b63f EFL=00207202 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
CS =0008 00000000 ffffffff 00cf9a00 DPL=0 CS32 [-R-]
SS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
DS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
FS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
GS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
LDT=0000 00000000 00000000 00008200 DPL=0 LDT
TR =0008 00000580 00000067 00008900 DPL=0 TSS32-avl
GDT= 00127760 00000027
IDT= 00122f40 000007ff
CR0=80000011 CR2=00000000 CR3=0014a000 CR4=00000000
DR0=00000000 DR1=00000000 DR2=00000000 DR3=00000000
DR6=ffff0ff0 DR7=00000400
CCS=00000024 CCD=0012b75c CCO=ADDL
EFER=0000000000000000
check_exception old: 0xffffffff new 0xd
2: v=0d e=fffffffa i=0 cpl=0 IP=0008:0010b63f pc=0010b63f SP=0010:0012b768
EAX=00000000
EAX=00000000 EBX=00002000 ECX=00000018 EDX=05a00780
ESI=00112faa EDI=000b8fa0 EBP=0012b780 ESP=0012b768
EIP=0010b63f EFL=00207202 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
CS =0008 00000000 ffffffff 00cf9a00 DPL=0 CS32 [-R-]
SS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
DS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
FS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
GS =0010 00000000 ffffffff 00cf9300 DPL=0 DS [-WA]
LDT=0000 00000000 00000000 00008200 DPL=0 LDT
TR =0008 00000580 00000067 00008900 DPL=0 TSS32-avl
GDT= 00127760 00000027
IDT= 00122f40 000007ff
CR0=80000011 CR2=00000000 CR3=0014a000 CR4=00000000
DR0=00000000 DR1=00000000 DR2=00000000 DR3=00000000
DR6=ffff0ff0 DR7=00000400
CCS=00000024 CCD=0012b75c CCO=ADDL
EFER=0000000000000000
To the best of my ability to interpret, I an getting an undefined
interrupt, which is then triggering a GPF, which is caught. However,
do not know where it might be coming from.
Some additional information:
This command works:
qemu-system-i386 -smp 4 -monitor stdio -cpu core2duo -s -hda
"$harddisk_image" -m 3.5G
This command works:
qemu-system-i386 -monitor stdio -cpu core2duo -D
/home/adam/century/util/qemu.log -d int,in_asm -s -hda
"$harddisk_image" -m 3.5G
And, as above, this does not:
qemu-system-i386 -smp 4 -monitor stdio -cpu core2duo -D
/home/adam/century/util/qemu.log -d int,in_asm -s -hda
"$harddisk_image" -m 3.5G
address@hidden ~]$ qemu-system-i386 -version
QEMU emulator version 1.2.0, Copyright (c) 2003-2008 Fabrice Bellard
Attached is an image as a test case. Please let me know if you need
any additional information.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1050694/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |