All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Rousse <Guillaume.Rousse@inria.fr>
To: xen-devel@lists.xensource.com
Subject: Re: xend crash at startup
Date: Thu, 06 Dec 2007 18:46:30 +0100	[thread overview]
Message-ID: <47583576.3070109@inria.fr> (raw)
In-Reply-To: <472F5334.9050401@inria.fr>

Guillaume Rousse wrote:
> xend crashes at startup with following stack trace:
> ...
> File "/usr/lib64/python/xen/xend/XendPIF.py", line 68, in
> linux_get_phy_ifaces
>     phy_ifaces.append((name, int(mtu), bridged_mac))
> UnboundLocalError: local variable 'bridged_mac' referenced before assignment
> 
> The simple patch attached below prevent the crash, and allow xend to
> start normally.
> 
> It seems the crash happens when bridged_ifname is set to eth2, whereas
> eth2 doesn't appear in ip -o link show.
The problem surfaced again: xend start just crashes with previous message.

If I apply submitted patch, xend start just hang infinitly, and strace 
shows a futex issue:
Process 18743 attached - interrupt to quit
futex(0xcce634, FUTEX_WAIT, 1627, NULL) = 0
futex(0xcce608, FUTEX_WAKE, 1)          = 0
futex(0xcce660, FUTEX_WAKE, 1)          = 1
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
futex(0xb18840, FUTEX_WAKE, 1)          = 0
futex(0xb18840, FUTEX_WAKE, 1)          = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
write(19, "\2\0\0\0\0\0\0\0\304\0\0\0009\0\0\0", 16) = 16
write(19, "/vm/2cc873ba-81ea-4a3e-a6bc-15e9"..., 57) = 57
futex(0xcce634, FUTEX_WAIT, 1641, NULL) = 0
futex(0xcce608, FUTEX_WAKE, 1)          = 0
futex(0xcce660, FUTEX_WAKE, 1)          = 1
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
futex(0xb18840, FUTEX_WAKE, 1)          = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
write(19, "\7\0\0\0\0\0\0\0\304\0\0\0\2\0\0\0", 16) = 16
write(19, "T\0", 2)                     = 2
futex(0xcce634, FUTEX_WAIT, 1655, NULL) = 0
futex(0xcce608, FUTEX_WAKE, 1)          = 0
futex(0xcce660, FUTEX_WAKE, 1)          = 1
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
futex(0xb18840, FUTEX_WAKE, 1)          = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
write(19, "\6\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0", 16) = 16
write(19, "\0", 1)                      = 1
futex(0xcce634, FUTEX_WAIT, 1669, NULL) = 0
futex(0xcce608, FUTEX_WAKE, 1)          = 0
futex(0xcce660, FUTEX_WAKE, 1)          = 1
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
futex(0xb18840, FUTEX_WAKE, 1)          = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL)    = 0
write(19, "\2\0\0\0\0\0\0\0\313\0\0\0009\0\0\0", 16) = 16
write(19, "/vm/2cc873ba-81ea-4a3e-a6bc-15e9"..., 57) = 57
futex(0xcce634, FUTEX_WAIT, 1683, NULL) = 0
futex(0xcce608, FUTEX_WAKE, 1)          = 0
futex(0xcce660, FUTEX_WAKE, 1)          = 1
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
futex(0xb18840, FUTEX_WAKE, 1)          = 0
futex(0xb18840, FUTEX_WAKE, 1)          = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, {SIG_IGN}, 8) = 0
futex(0xcce660, FUTEX_WAIT, 2, NULL <unfinished ...>

It may be related to the fact I had to use kill -9 on processus 
resulting from previous run, tough.
-- 
Guillaume Rousse
Moyens Informatiques - INRIA Futurs
Tel: 01 69 35 69 62

      reply	other threads:[~2007-12-06 17:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-05 17:30 xend crash at startup Guillaume Rousse
2007-12-06 17:46 ` Guillaume Rousse [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47583576.3070109@inria.fr \
    --to=guillaume.rousse@inria.fr \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.