[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init
** No longer affects: qtmir -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init Status in lttng-ust package in Ubuntu: New Status in qtmir package in Ubuntu: Fix Released Status in ust package in Ubuntu: New Bug description: Happens when running tests for https://code.launchpad.net/~dandrader/qtmir/content-hub- clipboard/+merge/303863 by CI. This is the backtrace of where it gets stuck: #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 <_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51 #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, the_map=) at dl-tls.c:778 #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158 #3 0x in lttng_ust_init () at lttng-ust-comm.c:369 #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481 #5 0x in call_init (l=, argc=argc@entry=1, argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72 #6 0x in _dl_init (env=, argv=, argc=, l=) at dl-init.c:30 #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, env=0xbefff3dc) at dl-init.c:120 #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3 It gets stuck during initialization, more specifically, inside lttng_fixup_urcu_bp_tls() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lttng-ust/+bug/1618201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init
** Changed in: qtmir (Ubuntu) Status: Triaged => Fix Released ** Changed in: qtmir Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init Status in QtMir: Fix Released Status in lttng-ust package in Ubuntu: New Status in qtmir package in Ubuntu: Fix Released Status in ust package in Ubuntu: New Bug description: Happens when running tests for https://code.launchpad.net/~dandrader/qtmir/content-hub- clipboard/+merge/303863 by CI. This is the backtrace of where it gets stuck: #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 <_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51 #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, the_map=) at dl-tls.c:778 #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158 #3 0x in lttng_ust_init () at lttng-ust-comm.c:369 #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481 #5 0x in call_init (l=, argc=argc@entry=1, argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72 #6 0x in _dl_init (env=, argv=, argc=, l=) at dl-init.c:30 #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, env=0xbefff3dc) at dl-init.c:120 #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3 It gets stuck during initialization, more specifically, inside lttng_fixup_urcu_bp_tls() To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1618201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init
Looks like a glibc 2.21 bug with TLS constructors, see: https://bugzilla.redhat.com/show_bug.cgi?id=1223055 Seems to be fixed upstream by these commits: https://github.com/bminor/glibc/commit/e400f3ccd36fe91d432cc7d45b4ccc799dece763 https://github.com/bminor/glibc/commit/90b37cac8b5a3e1548c29d91e3e0bff1014d2e5c ** Bug watch added: Red Hat Bugzilla #1223055 https://bugzilla.redhat.com/show_bug.cgi?id=1223055 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init Status in QtMir: Triaged Status in lttng-ust package in Ubuntu: New Status in qtmir package in Ubuntu: Triaged Status in ust package in Ubuntu: New Bug description: Happens when running tests for https://code.launchpad.net/~dandrader/qtmir/content-hub- clipboard/+merge/303863 by CI. This is the backtrace of where it gets stuck: #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 <_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51 #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, the_map=) at dl-tls.c:778 #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158 #3 0x in lttng_ust_init () at lttng-ust-comm.c:369 #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481 #5 0x in call_init (l=, argc=argc@entry=1, argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72 #6 0x in _dl_init (env=, argv=, argc=, l=) at dl-init.c:30 #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, env=0xbefff3dc) at dl-init.c:120 #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3 It gets stuck during initialization, more specifically, inside lttng_fixup_urcu_bp_tls() To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1618201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init
libc6 2.21-0ubuntu4.0.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init Status in QtMir: Triaged Status in lttng-ust package in Ubuntu: New Status in qtmir package in Ubuntu: Triaged Status in ust package in Ubuntu: New Bug description: Happens when running tests for https://code.launchpad.net/~dandrader/qtmir/content-hub- clipboard/+merge/303863 by CI. This is the backtrace of where it gets stuck: #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 <_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51 #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, the_map=) at dl-tls.c:778 #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158 #3 0x in lttng_ust_init () at lttng-ust-comm.c:369 #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481 #5 0x in call_init (l=, argc=argc@entry=1, argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72 #6 0x in _dl_init (env=, argv=, argc=, l=) at dl-init.c:30 #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, env=0xbefff3dc) at dl-init.c:120 #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3 It gets stuck during initialization, more specifically, inside lttng_fixup_urcu_bp_tls() To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1618201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init
What is your glibc version ? You provided your libglib version which is unrelated to lttng-ust. Or are you using Android bionic libc... ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init Status in QtMir: Triaged Status in lttng-ust package in Ubuntu: New Status in qtmir package in Ubuntu: Triaged Status in ust package in Ubuntu: New Bug description: Happens when running tests for https://code.launchpad.net/~dandrader/qtmir/content-hub- clipboard/+merge/303863 by CI. This is the backtrace of where it gets stuck: #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 <_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51 #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, the_map=) at dl-tls.c:778 #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158 #3 0x in lttng_ust_init () at lttng-ust-comm.c:369 #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481 #5 0x in call_init (l=, argc=argc@entry=1, argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72 #6 0x in _dl_init (env=, argv=, argc=, l=) at dl-init.c:30 #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, env=0xbefff3dc) at dl-init.c:120 #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3 It gets stuck during initialization, more specifically, inside lttng_fixup_urcu_bp_tls() To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1618201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init
But on CI it also deadlocks in amd64. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init Status in QtMir: Triaged Status in lttng-ust package in Ubuntu: New Status in qtmir package in Ubuntu: Triaged Status in ust package in Ubuntu: New Bug description: Happens when running tests for https://code.launchpad.net/~dandrader/qtmir/content-hub- clipboard/+merge/303863 by CI. This is the backtrace of where it gets stuck: #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 <_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51 #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, the_map=) at dl-tls.c:778 #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158 #3 0x in lttng_ust_init () at lttng-ust-comm.c:369 #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481 #5 0x in call_init (l=, argc=argc@entry=1, argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72 #6 0x in _dl_init (env=, argv=, argc=, l=) at dl-init.c:30 #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, env=0xbefff3dc) at dl-init.c:120 #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3 It gets stuck during initialization, more specifically, inside lttng_fixup_urcu_bp_tls() To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1618201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init
liblttng-ust 2.7.1-1~vividoverlay1 libglib2.0 2.44.1-1ubuntu1 About comments #4 and #5: what seems more relevant is actually ubuntu release/pkg versions since my desktop runs xenial+stable-phone-overlay whereas my arm devices run vivid+stable-phone-overlay. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init Status in QtMir: Triaged Status in lttng-ust package in Ubuntu: New Status in qtmir package in Ubuntu: Triaged Status in ust package in Ubuntu: New Bug description: Happens when running tests for https://code.launchpad.net/~dandrader/qtmir/content-hub- clipboard/+merge/303863 by CI. This is the backtrace of where it gets stuck: #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 <_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51 #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, the_map=) at dl-tls.c:778 #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158 #3 0x in lttng_ust_init () at lttng-ust-comm.c:369 #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481 #5 0x in call_init (l=, argc=argc@entry=1, argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72 #6 0x in _dl_init (env=, argv=, argc=, l=) at dl-init.c:30 #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, env=0xbefff3dc) at dl-init.c:120 #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3 It gets stuck during initialization, more specifically, inside lttng_fixup_urcu_bp_tls() To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1618201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init
It might have something to do with arm or chroot envs (likely what CI does) as tests run fine on my amd64 desktop but deadlock in a chroot on an arm device (like mako or flo). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init Status in QtMir: Triaged Status in lttng-ust package in Ubuntu: New Status in qtmir package in Ubuntu: Triaged Status in ust package in Ubuntu: New Bug description: Happens when running tests for https://code.launchpad.net/~dandrader/qtmir/content-hub- clipboard/+merge/303863 by CI. This is the backtrace of where it gets stuck: #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 <_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51 #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, the_map=) at dl-tls.c:778 #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158 #3 0x in lttng_ust_init () at lttng-ust-comm.c:369 #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481 #5 0x in call_init (l=, argc=argc@entry=1, argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72 #6 0x in _dl_init (env=, argv=, argc=, l=) at dl-init.c:30 #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, env=0xbefff3dc) at dl-init.c:120 #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3 It gets stuck during initialization, more specifically, inside lttng_fixup_urcu_bp_tls() To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1618201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init
It seems odd that touching a shared object TLS (which triggers a TLS fixup) from a constructor would deadlock. Which version of glibc are you using ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init Status in QtMir: Triaged Status in lttng-ust package in Ubuntu: New Status in qtmir package in Ubuntu: Triaged Status in ust package in Ubuntu: New Bug description: Happens when running tests for https://code.launchpad.net/~dandrader/qtmir/content-hub- clipboard/+merge/303863 by CI. This is the backtrace of where it gets stuck: #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 <_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51 #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, the_map=) at dl-tls.c:778 #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158 #3 0x in lttng_ust_init () at lttng-ust-comm.c:369 #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481 #5 0x in call_init (l=, argc=argc@entry=1, argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72 #6 0x in _dl_init (env=, argv=, argc=, l=) at dl-init.c:30 #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, env=0xbefff3dc) at dl-init.c:120 #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3 It gets stuck during initialization, more specifically, inside lttng_fixup_urcu_bp_tls() To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1618201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init
Which version of liblttng-ust is that? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init Status in QtMir: Triaged Status in lttng-ust package in Ubuntu: New Status in qtmir package in Ubuntu: Triaged Status in ust package in Ubuntu: New Bug description: Happens when running tests for https://code.launchpad.net/~dandrader/qtmir/content-hub- clipboard/+merge/303863 by CI. This is the backtrace of where it gets stuck: #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 <_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51 #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, the_map=) at dl-tls.c:778 #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158 #3 0x in lttng_ust_init () at lttng-ust-comm.c:369 #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481 #5 0x in call_init (l=, argc=argc@entry=1, argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72 #6 0x in _dl_init (env=, argv=, argc=, l=) at dl-init.c:30 #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, env=0xbefff3dc) at dl-init.c:120 #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3 It gets stuck during initialization, more specifically, inside lttng_fixup_urcu_bp_tls() To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1618201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618201] Re: deadlock in lttng_ust_init
This issue was worked around, but with a far-from-ideal solution ** Also affects: lttng-ust (Ubuntu) Importance: Undecided Status: New ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Changed in: qtmir (Ubuntu) Status: New => Triaged ** Changed in: qtmir (Ubuntu) Importance: Undecided => Medium ** Also affects: qtmir Importance: Undecided Status: New ** Changed in: qtmir Status: New => Triaged ** Changed in: qtmir Importance: Undecided => Medium ** Branch linked: lp:~dandrader/qtmir/no-lttng-on-tests -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ust in Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init Status in QtMir: Triaged Status in lttng-ust package in Ubuntu: New Status in qtmir package in Ubuntu: Triaged Status in ust package in Ubuntu: New Bug description: Happens when running tests for https://code.launchpad.net/~dandrader/qtmir/content-hub- clipboard/+merge/303863 by CI. This is the backtrace of where it gets stuck: #0 0x in __pthread_mutex_unlock_usercnt (mutex=0xb6fff514 <_rtld_global+1220>, decr=1) at pthread_mutex_unlock.c:51 #1 0x in tls_get_addr_tail (ti=0xb637021c, dtv=0xb3757008, the_map=) at dl-tls.c:778 #2 0x in lttng_ust_init () at /usr/include/urcu/static/urcu-bp.h:158 #3 0x in lttng_ust_init () at lttng-ust-comm.c:369 #4 0x in lttng_ust_init () at lttng-ust-comm.c:1481 #5 0x in call_init (l=, argc=argc@entry=1, argv=argv@entry=0xbefff3d4, env=env@entry=0xbefff3dc) at dl-init.c:72 #6 0x in _dl_init (env=, argv=, argc=, l=) at dl-init.c:30 #7 0x in _dl_init (main_map=0xb6fff958, argc=1, argv=0xbefff3d4, env=0xbefff3dc) at dl-init.c:120 #8 0x in _dl_start_user () at /lib/ld-linux-armhf.so.3 It gets stuck during initialization, more specifically, inside lttng_fixup_urcu_bp_tls() To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1618201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
