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-devel

[Xen-devel] xen unstable crashes ...

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xen unstable crashes ...
From: Gerd Knorr <kraxel@xxxxxxxxxxx>
Date: Thu, 19 May 2005 17:32:30 +0200
Delivery-date: Thu, 19 May 2005 15:34:28 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
... when built with optimize=n debug=y

I get first a line like this one:

  (XEN) (file=extable.c, line=76) Pre-exception: ff105b48 -> 00000000

Then xen dies because of a page fault in IRQ context:

  [ ... ]
  (XEN) CPU0 FATAL TRAP 14 (page fault), ERROR_CODE 0002, IN INTERRUPT CONTEXT.

ff105b48 is _not_ the start address of some instruction, it's
somewhere inbetween:

  ff105b45:       f0 0f ab 02             lock bts %eax,(%edx)
  ff105b49:       19 c0                   sbb    %eax,%eax

Without "debug=y" xen boots just fine.  This is x86_32.

  Gerd


-- 
-mm seems unusually stable at present.
        -- akpm about 2.6.12-rc3-mm3

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

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