All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@suse.de>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: "xm save" trouble -- deadlock?
Date: Tue, 01 Nov 2005 17:43:56 +0100	[thread overview]
Message-ID: <43679B4C.3030804@suse.de> (raw)

   Hi,

"xm save" doesn't work for me, the command just blocks forever.  In the 
process list it looks like this:

  6567 ?        Ssl    0:00 python /usr/sbin/xend restart
  7978 ?        SL     0:00  \_ /usr/lib/xen/bin/xc_save 14 17 10 0 0 0

xc_save is blocked, in a write call to stderr:

   master-xen root /vm/ttylinux# strace -p7978
   Process 7978 attached - interrupt to quit
   write(2, "FNI 28 : [10000004,815] pte=2b92"..., 80 <unfinished ...>
   Process 7978 detached

stderr is a pipe to xend:

   master-xen root /vm/ttylinux# ll /proc/7978/fd/2
   l-wx------  1 root root 64 Nov  1 17:25 /proc/7978/fd/2 -> pipe:[40419]
   master-xen root /vm/ttylinux# ll /proc/*/fd/* | grep 40419
   lr-x------  1 root root 64 Nov  1 17:25 /proc/6567/fd/22 -> pipe:[40419]
   l-wx------  1 root root 64 Nov  1 17:25 /proc/7978/fd/2 -> pipe:[40419]

xend in turn doesn't read from the pipe but is waiting for some lock:

   master-xen root /vm/ttylinux# strace -p6567
   Process 6567 attached - interrupt to quit
   futex(0x8087370, FUTEX_WAIT, 0, NULL <unfinished ...>
   Process 6567 detached

Ideas anyone what is going on here?

   Gerd

             reply	other threads:[~2005-11-01 16:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-01 16:43 Gerd Knorr [this message]
2005-11-01 17:15 ` "xm save" trouble -- deadlock? Gerd Knorr
2005-11-01 18:54   ` Ewan Mellor
2005-11-02  9:25     ` Gerd Knorr
2005-11-02 10:04       ` Ewan Mellor
2005-11-02 11:24         ` Gerd Knorr
2005-11-02 15:35         ` Gerd Knorr
2005-11-02 15:41           ` Ewan Mellor
2005-11-02 17:23             ` Gerd Knorr
2005-11-01 18:58   ` Ewan Mellor
2005-11-02 11:34     ` Gerd Knorr
2005-11-02 18:28       ` Kip Macy
2005-11-03  8:53         ` Gerd Knorr

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=43679B4C.3030804@suse.de \
    --to=kraxel@suse.de \
    --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.