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

RE: [Xen-ia64-devel] [IPF-xenU] "xm destroy" xenU may make xen0 crash

To: "Akio Takebe" <takebe_akio@xxxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] [IPF-xenU] "xm destroy" xenU may make xen0 crash
From: "Zhang, Jingke" <jingke.zhang@xxxxxxxxx>
Date: Tue, 21 Nov 2006 16:20:00 +0800
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 21 Nov 2006 00:20:10 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AccNRYGpFopRrJgyRQSycS/fl5gHOwAABxww
Thread-topic: [Xen-ia64-devel] [IPF-xenU] "xm destroy" xenU may make xen0 crash
Hi,
    Here is a serial console log (destroy a SMP_XenU):
==============================================
(XEN) ### domain f000000007b34080: rid=80000-c0000 mp_rid=2000
(XEN) arch_domain_create: domain=f000000007b34080
(XEN) DomainU EFI build up: ACPI 2.0=0x1000
(XEN) dom mem: type=13, attr=0x8000000000000008, range=[0x0000000000000000-0x000
0000000001000) (4KB)
(XEN) dom mem: type=10, attr=0x8000000000000008, range=[0x0000000000001000-0x000
0000000002000) (4KB)
(XEN) dom mem: type= 6, attr=0x8000000000000008, range=[0x0000000000002000-0x000
0000000003000) (4KB)
(XEN) dom mem: type= 7, attr=0x0000000000000008, range=[0x0000000000003000-0x000
000000fff4000) (255MB)
(XEN) dom mem: type=12, attr=0x0000000000000001, range=[0x00000ffffc000000-0x000
0100000000000) (64MB)
(XEN) vcpu_get_lrr0: Unmasked interrupts unsupported
(XEN) vcpu_get_lrr1: Unmasked interrupts unsupported
(XEN) Domain set shared_info_va to 0xfffffffffff00000
(XEN) Linux version 2.6.16.29-xen (build@hp-build) (gcc version 3.4.5 20051201 (
Red Hat 3.4.5-2)) #1 SMP Tue Nov 21 05:13:58 CST 2006
EFI v1.00 by Xen/ia64: SALsystab=0x2178 ACPI 2.0=0x1000
SAL 0.1: Xen/ia64 Xen/ia64 version 0.0
SAL: AP wakeup using external interrupt vector 0xf3
xen_pal_emulator: UNIMPLEMENTED PAL CALL 42!!!!
(XEN) No logical to physical processor mapping available
ACPI: Local APIC address c0000000fee00000
ACPI: Error parsing MADT - no IOSAPIC entries
2 CPUs available, 2 CPUs total
Running on Xen! start_info_pfn=0x3ffd nr_pages=16384 flags=0x0
SMP: Allowing 2 CPUs, 0 hotplug CPUs
Built 1 zonelists
Kernel command line:  root=/dev/hda1 ro nomca console=tty0 root=/dev/hda1 3
PID hash table entries: 1024 (order: 10, 32768 bytes)
arch_boot_vcpu: vcpu 1 awaken
(XEN) vcpu_get_lrr0: Unmasked interrupts unsupported
(XEN) vcpu_get_lrr1: Unmasked interrupts unsupported
(XEN) lookup_domain_mpa: d 0xf000000007b34080 id 12 current 0xf000000007ae0000 i
d 0
(XEN) lookup_domain_mpa: bad mpa 0xffffc019064 (=> 0x10000000)
(XEN) Warning: UC to WB for mpaddr=ffffc019064
(XEN) BUG at mm.c:407
(XEN) FIXME: implement ia64 dump_execution_state()
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 1:
(XEN) BUG at mm.c:407
(XEN) ****************************************
(XEN)
(XEN) Reboot in five seconds...
???s
==============================================

Thanks,
Zhangjingke

>-----Original Message-----
>From: Akio Takebe [mailto:takebe_akio@xxxxxxxxxxxxxx]
>Sent: Tuesday, November 21, 2006 4:17 PM
>To: Zhang, Jingke; xen-ia64-devel
>Subject: Re: [Xen-ia64-devel] [IPF-xenU] "xm destroy" xenU may make xen0
>crash
>
>Hi, Zhang
>
>Could you show serial console log to us?
>
>Best Regards,
>
>Akio Takebe
>
>>Hi all,
>>    In recently Csets of IA64-unstable, "xm destroy" XenU guest is very
>>likely to make xen0 crash.   But destroying VTI guest will not.
>>    So I have reported a P1 xen-bug for this issue, URL is:
>>http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id?8
>>
>>Thanks,
>>Zhangjingke
>>
>>_______________________________________________
>>Xen-ia64-devel mailing list
>>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>http://lists.xensource.com/xen-ia64-devel

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