WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-bugs

[Xen-bugs] [Bug 36] GPF in Xen during ptwr update

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 36] GPF in Xen during ptwr update
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 13 May 2005 08:18:46 +0000
Delivery-date: Fri, 13 May 2005 08:18:55 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=36

kaf24@xxxxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



------- Additional Comments From kaf24@xxxxxxxxxxxx  2005-05-13 08:18 -------
The GPF is triggered by a hardware interrupt, so the stack backtrace won't help 
for this bug. The GPF 
error code indicates that the fault is caused by a hardware interrupt 
attempting to jump through 
interrupt vector 0x20. This ought to be valid: it is the vector programmed into 
the legacy PIC for irq0 
(timer interrupt).

It is probably worth dumping the contents of idt_table[] (one idt entry per 
line, printing index + 
word1(hex) + word2(hex)), or at least the contents of idt_table[0x20]. Also 
boot with 'apic=debug' and 
see if that gives any useful diagnostics during boot.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>