[Qemu-devel] [Bug 1050694] Re: Interrupt 0xffffffff when debug is turned on
[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- 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 0x when debug is turned on Status in QEMU: Expired 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=0x" on the top line): Servicing hardware INT=0x 1: v= e= i=0 cpl=0 IP=0008:0010b63f pc=0010b63f SP=0010:0012b768 EAX= EAX= EBX=2000 ECX=0018 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 00cf9300 DPL=0 DS [-WA] CS =0008 00cf9a00 DPL=0 CS32 [-R-] SS =0010 00cf9300 DPL=0 DS [-WA] DS =0010 00cf9300 DPL=0 DS [-WA] FS =0010 00cf9300 DPL=0 DS [-WA] GS =0010 00cf9300 DPL=0 DS [-WA] LDT= 8200 DPL=0 LDT TR =0008 0580 0067 8900 DPL=0 TSS32-avl GDT= 00127760 0027 IDT= 00122f40 07ff CR0=8011 CR2= CR3=0014a000 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 CCS=0024 CCD=0012b75c CCO=ADDL EFER= check_exception old: 0x new 0xd 2: v=0d e=fffa i=0 cpl=0 IP=0008:0010b63f pc=0010b63f SP=0010:0012b768 EAX= EAX= EBX=2000 ECX=0018 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 00cf9300 DPL=0 DS [-WA] CS =0008 00cf9a00 DPL=0 CS32 [-R-] SS =0010 00cf9300 DPL=0 DS [-WA] DS =0010 00cf9300 DPL=0 DS [-WA] FS =0010 00cf9300 DPL=0 DS [-WA] GS =0010 00cf9300 DPL=0 DS [-WA] LDT= 8200 DPL=0 LDT TR =0008 0580 0067 8900 DPL=0 TSS32-avl GDT= 00127760 0027 IDT= 00122f40 07ff CR0=8011 CR2= CR3=0014a000 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 CCS=0024 CCD=0012b75c CCO=ADDL EFER= 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. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1050694/+subscriptions
[Qemu-devel] [Bug 1050694] Re: Interrupt 0xffffffff when debug is turned on
Triaging old bug tickets ... is there still something left to do here, or could we close this ticket nowadays? ** Changed in: qemu Status: New => Incomplete -- 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 0x when debug is turned on Status in QEMU: Incomplete 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=0x" on the top line): Servicing hardware INT=0x 1: v= e= i=0 cpl=0 IP=0008:0010b63f pc=0010b63f SP=0010:0012b768 EAX= EAX= EBX=2000 ECX=0018 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 00cf9300 DPL=0 DS [-WA] CS =0008 00cf9a00 DPL=0 CS32 [-R-] SS =0010 00cf9300 DPL=0 DS [-WA] DS =0010 00cf9300 DPL=0 DS [-WA] FS =0010 00cf9300 DPL=0 DS [-WA] GS =0010 00cf9300 DPL=0 DS [-WA] LDT= 8200 DPL=0 LDT TR =0008 0580 0067 8900 DPL=0 TSS32-avl GDT= 00127760 0027 IDT= 00122f40 07ff CR0=8011 CR2= CR3=0014a000 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 CCS=0024 CCD=0012b75c CCO=ADDL EFER= check_exception old: 0x new 0xd 2: v=0d e=fffa i=0 cpl=0 IP=0008:0010b63f pc=0010b63f SP=0010:0012b768 EAX= EAX= EBX=2000 ECX=0018 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 00cf9300 DPL=0 DS [-WA] CS =0008 00cf9a00 DPL=0 CS32 [-R-] SS =0010 00cf9300 DPL=0 DS [-WA] DS =0010 00cf9300 DPL=0 DS [-WA] FS =0010 00cf9300 DPL=0 DS [-WA] GS =0010 00cf9300 DPL=0 DS [-WA] LDT= 8200 DPL=0 LDT TR =0008 0580 0067 8900 DPL=0 TSS32-avl GDT= 00127760 0027 IDT= 00122f40 07ff CR0=8011 CR2= CR3=0014a000 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 CCS=0024 CCD=0012b75c CCO=ADDL EFER= 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. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1050694/+subscriptions
[Qemu-devel] [Bug 1050694] Re: Interrupt 0xffffffff when debug is turned on
** 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 0x 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=0x on the top line): Servicing hardware INT=0x 1: v= e= i=0 cpl=0 IP=0008:0010b63f pc=0010b63f SP=0010:0012b768 EAX= EAX= EBX=2000 ECX=0018 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 00cf9300 DPL=0 DS [-WA] CS =0008 00cf9a00 DPL=0 CS32 [-R-] SS =0010 00cf9300 DPL=0 DS [-WA] DS =0010 00cf9300 DPL=0 DS [-WA] FS =0010 00cf9300 DPL=0 DS [-WA] GS =0010 00cf9300 DPL=0 DS [-WA] LDT= 8200 DPL=0 LDT TR =0008 0580 0067 8900 DPL=0 TSS32-avl GDT= 00127760 0027 IDT= 00122f40 07ff CR0=8011 CR2= CR3=0014a000 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 CCS=0024 CCD=0012b75c CCO=ADDL EFER= check_exception old: 0x new 0xd 2: v=0d e=fffa i=0 cpl=0 IP=0008:0010b63f pc=0010b63f SP=0010:0012b768 EAX= EAX= EBX=2000 ECX=0018 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 00cf9300 DPL=0 DS [-WA] CS =0008 00cf9a00 DPL=0 CS32 [-R-] SS =0010 00cf9300 DPL=0 DS [-WA] DS =0010 00cf9300 DPL=0 DS [-WA] FS =0010 00cf9300 DPL=0 DS [-WA] GS =0010 00cf9300 DPL=0 DS [-WA] LDT= 8200 DPL=0 LDT TR =0008 0580 0067 8900 DPL=0 TSS32-avl GDT= 00127760 0027 IDT= 00122f40 07ff CR0=8011 CR2= CR3=0014a000 CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 CCS=0024 CCD=0012b75c CCO=ADDL EFER= 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. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1050694/+subscriptions
[Qemu-devel] [Bug 1050694] Re: Interrupt 0xffffffff when debug is turned on
Original conversation about this issue on osdev.org: http://forum.osdev.org/viewtopic.php?f=1t=25795 ** Description changed: 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=0x on the top line): Servicing hardware INT=0x 1: v= e= i=0 cpl=0 IP=0008:0010b63f pc=0010b63f SP=0010:0012b768 EAX= EAX= EBX=2000 ECX=0018 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 00cf9300 DPL=0 DS [-WA] CS =0008 00cf9a00 DPL=0 CS32 [-R-] SS =0010 00cf9300 DPL=0 DS [-WA] DS =0010 00cf9300 DPL=0 DS [-WA] FS =0010 00cf9300 DPL=0 DS [-WA] GS =0010 00cf9300 DPL=0 DS [-WA] LDT= 8200 DPL=0 LDT TR =0008 0580 0067 8900 DPL=0 TSS32-avl GDT= 00127760 0027 IDT= 00122f40 07ff CR0=8011 CR2= CR3=0014a000 CR4= - DR0= DR1= DR2= DR3= + DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 - CCS=0024 CCD=0012b75c CCO=ADDL + CCS=0024 CCD=0012b75c CCO=ADDL EFER= check_exception old: 0x new 0xd 2: v=0d e=fffa i=0 cpl=0 IP=0008:0010b63f pc=0010b63f SP=0010:0012b768 EAX= EAX= EBX=2000 ECX=0018 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 00cf9300 DPL=0 DS [-WA] CS =0008 00cf9a00 DPL=0 CS32 [-R-] SS =0010 00cf9300 DPL=0 DS [-WA] DS =0010 00cf9300 DPL=0 DS [-WA] FS =0010 00cf9300 DPL=0 DS [-WA] GS =0010 00cf9300 DPL=0 DS [-WA] LDT= 8200 DPL=0 LDT TR =0008 0580 0067 8900 DPL=0 TSS32-avl GDT= 00127760 0027 IDT= 00122f40 07ff CR0=8011 CR2= CR3=0014a000 CR4= - DR0= DR1= DR2= DR3= + DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 - CCS=0024 CCD=0012b75c CCO=ADDL + CCS=0024 CCD=0012b75c CCO=ADDL EFER= 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. + Attached is an image as a test case. Please let me know if you need any + additional information. -- 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 0x 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=0x on the top line): Servicing hardware INT=0x 1: v= e= i=0 cpl=0 IP=0008:0010b63f pc=0010b63f SP=0010:0012b768 EAX= EAX= EBX=2000 ECX=0018 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 00cf9300 DPL=0 DS [-WA] CS =0008 00cf9a00 DPL=0 CS32 [-R-] SS =0010
