Post Reply 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
SWarp threads deadlock?
05-02-2016, 07:46 (This post was last modified: 05-02-2016 07:54 by luvaul.)
Post: #1
SWarp threads deadlock?
Hi all, I'm a non-astronomer trying to get SWarp to run successfully but I keep running into this problem: SWarp runs at 100% cpu (or >100% cpu if using more than 1 thread) for a time, presumably doing it's thing, but then enters an indefinite period of 0% cpu use. I have left it in this state for many days (6) with no change, so I suspect a deadlock.

strace reveals:
>strace -p 61462 -f
Process 61462 attached with 2 threads
[pid 48375] futex(0x697d074, FUTEX_WAIT_PRIVATE, 575173, NULL <unfinished ...>
[pid 61462] futex(0x697daf4, FUTEX_WAIT_PRIVATE, 1, NULL

Which looks like this Linux system bug:!topic/...bmpZxp6C64

However I think we have the patch installed that fixes this problem so I'm not sure this is the cause:
>sudo rpm -q --changelog kernel-`uname -r` | grep futex | grep ref
- [kernel] futex: Mention key referencing differences between shared and private futexes (Larry Woodman) [1205862]
- [kernel] futex: Ensure get_futex_key_refs() always implies a barrier (Larry Woodman) [1205862]

Has anyone else had these (or similar) problems? Any help at all would be appreciated! (BTW, I'm using SWarp version 2.38.0.)

Many thanks,
Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
SWarp threads deadlock? - luvaul - 05-02-2016 07:46
RE: SWarp threads deadlock? - luvaul - 05-03-2016, 15:13
RE: SWarp threads deadlock? - aticuic - 05-10-2016, 13:43

Forum Jump:

User(s) browsing this thread: 1 Guest(s)