Linux Container Development
 help / color / mirror / Atom feed
From: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
To: Sukadev Bhattiprolu
	<sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
Cc: Containers
	<containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [C/R][BUG] run-pthread1.sh hangs on restart
Date: Tue, 14 Jul 2009 04:34:47 -0400	[thread overview]
Message-ID: <4A5C4327.7000200@cs.columbia.edu> (raw)
In-Reply-To: <20090714072255.GA3166-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>


These "MIA" messages are false alarms, but once given they
break the restart. I'm working on a fix.

Oren.

Sukadev Bhattiprolu wrote:
> 
> Sorry. I was on the wrong machine which has a different kernel. Will
> re-run the test tomorrow.
> 
> 
> Sukadev Bhattiprolu [sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org] wrote:
> | 
> | When I run the 'process-tree/run-pthread1.sh' test on ckpt-v17-rc1, 
> | after restart, I see following three processes running in 'ps'
> | 
> | root     21165 21114  0 00:11 ttyp0    00:00:00 ../ns_exec -cpuimP pid.pthread1 -- /home/suka/ckpt/user-cr/mktree -vd
> | root     21167 21165  0 00:11 ttyp0    00:00:00 /home/suka/ckpt/user-cr/mktree -vd
> | root     21169 21167  0 00:11 ?        00:00:00 /home/suka/ckpt/user-cr/mktree -vd
> | 
> | Attached is output of mktree (-vd) (The "Parent MIA" message is interesting)
> | 
> | Following is the kernel stack trace of the above processes - the
> | processes seem hung here even after 5 minutes.
> 

      parent reply	other threads:[~2009-07-14  8:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14  7:15 [C/R][BUG] run-pthread1.sh hangs on restart Sukadev Bhattiprolu
     [not found] ` <20090714071507.GA337-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-07-14  7:22   ` Sukadev Bhattiprolu
     [not found]     ` <20090714072255.GA3166-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-07-14  8:34       ` Oren Laadan [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=4A5C4327.7000200@cs.columbia.edu \
    --to=orenl-eqauephvms7envbuuze7ea@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox