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. (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@lists.xensource.com http://lists.xensource.com/xen-devel
> 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@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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@cl.cam.ac.uk] Sent: Tuesday, 13 September 2005 12:19 PM To: Bonnell, David; xen-devel@lists.xensource.com Cc: Keir Fraser; ian.pratt@cl.cam.ac.uk 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@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
> 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".It looks like it''s going at it through /proc/pci raher than /dev/mem. I seem to recall we fixed the memmap functions od /dev/mem a couple of weeks back, but I wander if read/write have been attended to? Having the fragment of source that''s causing the crash would be useful to target the search. Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel