Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

[Xen-devel] xcs segfaults on vm shutdown

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xcs segfaults on vm shutdown
From: Richard Sterling Cox <rick@xxxxxxxxxxxxxxxxx>
Date: Sat, 12 Mar 2005 11:59:56 -0800
Delivery-date: Sat, 12 Mar 2005 20:00:37 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.2.1i
hi,

I'm experiencing regular seg-faults of the xcs daemon during vm
shutdown operations (occurring somewhere between 5 and 25 VMs run,
typically).

xen: unstable patched through 2005-03-07
dom0: linux-2.6.10-xen0 / Fedora Core 3
gcc: 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)
vmtools: 0.0.3 I believe, but they report (-V) 0.0.1, which is not
         true
(not using xend)

The errors usually seem to occur while running 'vm-shutdown'.

I have been running 'xcs -i' under gdb and found that, at least twice,
the error is at xen/tools/xcs/ctrl_interface.c:143. Here is the output
of one such session (the error is repeatable enough that I should be
able to provide other info if anyone is interested):

Program received signal SIGSEGV, Segmentation fault.
0x080490b9 in ctrl_chan_request_to_read (cc=0x8050a60) at ctrl_interface.c:143
143         return (RING_HAS_UNCONSUMED_REQUESTS(CTRL_RING, &cc->tx_ring));

(gdb) bt
#0  0x080490b9 in ctrl_chan_request_to_read (cc=0x8050a60) at 
ctrl_interface.c:143
#1  0x0804a8d7 in handle_ctrl_if () at xcs.c:550
#2  0x0804ae93 in main (argc=2, argv=0xbffffa74) at xcs.c:737
(gdb) print cc
$1 = (control_channel_t *) 0x8050a60
(gdb) print *cc
$2 = {connected = 1, ref_count = 1, type = 0, remote_dom = 26, local_port = 73, 
remote_port = 1,
  interface = 0xb7ff0800, tx_ring = {rsp_prod_pvt = 0, req_cons = 0, sring = 
0xb7ff0800},
  rx_ring = {req_prod_pvt = 0, rsp_cons = 0, sring = 0xb7ff0a08}, virq = 0}
(gdb) print *(cc->tx_ring->sring)
Cannot access memory at address 0xb7ff0800
(gdb) up
#1  0x0804a8d7 in handle_ctrl_if () at xcs.c:550
550             while (ctrl_chan_request_to_read(cc))
(gdb) print chan
$4 = 73
(gdb) print cc_list[chan]
$6 = (control_channel_t *) 0x8050a60


rick



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

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