[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] RE: [UPDATE] Xen crashes


  • To: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Bonnell, David" <David_Bonnell@xxxxxxx>
  • Date: Tue, 13 Sep 2005 16:20:12 -0500
  • Delivery-date: Wed, 14 Sep 2005 01:32:44 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcW349WaEb7ZpMy3SsSt0R7Od68IrAACv8iwABjSccAACjGFEA==
  • Thread-topic: [UPDATE] Xen crashes

The complete Xen boot log and strace are attached however I'm not sure
the strace log is complete (in fact, I'm almost certain it is not!) as
the latest entries may not have been flushed to disk before the crash
and hence lost.  (Unless Xen is booted with "noreboot" the strace log
file is not even created!).

The only output from restoretextmode before the crash is:

        Using nvidia driver, 65536KB, Type: GeForce (NV 11).

I'll pull down the source and compile restoretextmode/svgalib with debug
symbols so I can step through it in gdb until the point of the "bang".


-Dave

-----Original Message-----
From: Ian Pratt [mailto:m+Ian.Pratt@xxxxxxxxxxxx] 
Sent: Tuesday, 13 September 2005 12:19 PM
To: Bonnell, David; xen-devel@xxxxxxxxxxxxxxxxxxx
Cc: Keir Fraser; ian.pratt@xxxxxxxxxxxx
Subject: RE: [Xen-devel] [UPDATE] Xen crashes

> The crash I reported last week (dma_map_single for net I/O in guest
> domain) appears to be fixed in changeset 6726 however the 
> dom0 MM crash triggered by resizetextmode (from svgalib) is 
> still there.  Reproducing this is very easy.  Boot Xen, run 
> "resizetextmode -w foo" in dom0 and bang.

Please can you post the boot log including the e820 map. Also, please
can you determine how resizetextmode is accessing the VGA device. strace
should do the trick.

It seems to want to access address 0a5f9000 which is pretty odd.

Ian

> (XEN) (file=/xen/xen-unstable/xen/include/asm/mm.h, line=201) 
> Error pfn
> a5f9: rd=ffbfa900, od=00000000, caf=00000000, taf=00000000
> (XEN) (file=/xen/xen-unstable/xen/include/asm/mm.h, line=201) 
> Error pfn
> a5f9: rd=ffbfa900, od=00000000, caf=00000000, taf=00000000
> (XEN) DOM0: (file=mm.c, line=2935) ptwr: Could not re-validate l1 page
> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> (XEN) CPU:    0
> (XEN) EIP:    0061:[<c015e577>]
> (XEN) EFLAGS: 00000246   CONTEXT: guest
> (XEN) eax: 0000000e   ebx: b37e3000   ecx: fe27003f   edx: 00000000
> (XEN) esi: 00000000   edi: fe27003f   ebp: b37e3000   esp: c350fe78
> (XEN) cr0: 8005003b   cr3: 032ec000
> (XEN) ds: 007b   es: 007b   fs: 0000   gs: 0033   ss: 0069   cs: 0061
> (XEN) Guest stack trace from esp=c350fe78:
> ...
> 
> 
> -Dave
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 

Attachment: xen-restoretextmode.log
Description: xen-restoretextmode.log

Attachment: xen-restoretextmode-strace.log
Description: xen-restoretextmode-strace.log

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.