summary refs log tree commit diff stats
path: root/results/classifier/111/debug/1050694
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/111/debug/1050694')
-rw-r--r--results/classifier/111/debug/1050694113
1 files changed, 0 insertions, 113 deletions
diff --git a/results/classifier/111/debug/1050694 b/results/classifier/111/debug/1050694
deleted file mode 100644
index 63d4ee7a..00000000
--- a/results/classifier/111/debug/1050694
+++ /dev/null
@@ -1,113 +0,0 @@
-debug: 0.085
-PID: 0.080
-device: 0.078
-other: 0.076
-semantic: 0.076
-permissions: 0.076
-performance: 0.075
-graphic: 0.074
-vnc: 0.069
-files: 0.068
-boot: 0.068
-socket: 0.067
-KVM: 0.056
-network: 0.053
-debug: 0.665
-semantic: 0.055
-other: 0.051
-performance: 0.048
-files: 0.036
-device: 0.034
-socket: 0.024
-PID: 0.017
-network: 0.015
-boot: 0.012
-KVM: 0.011
-permissions: 0.011
-graphic: 0.011
-vnc: 0.010
-
-Interrupt 0xffffffff when debug is turned on
-
-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
-
-
-[adam@os-development ~]$ 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.
-
-
-
-Original conversation about this issue on osdev.org: http://forum.osdev.org/viewtopic.php?f=1&t=25795
-
-Triaging old bug tickets ... is there still something left to do here, or could we close this ticket nowadays?
-
-[Expired for QEMU because there has been no activity for 60 days.]
-